Privacy Policy

1. Information Pageant Atlas may process

The information processed depends on the features a user chooses to use.

Account and identity information

• Email address, authentication provider, internal user/account identifiers, sign-in/session records, account settings, and policy-acceptance records.
• For invited adult private-beta testers, the NDA/Beta Tester Agreement acceptance record may include full legal name, an account-email snapshot, county/state, typed electronic signature, agreement version, affirmative consent confirmations, server acceptance timestamp, app version, and limited device/build information needed to document the acceptance.
• Names or display names, family/profile role or relationship, optional age or birth date, optional gender, profile preferences, and similar profile information.
• Google or Facebook/Meta sign-in information only when the user chooses that sign-in provider.

Family, planning, calendar, and pageant information

• Saved pageants, entry status, results, titles, scorecards, checklists, notes, speech material, wardrobe information, schedules, and other pageant-planning records.
• Pageant-related calendar or schedule entries created or saved within Pageant Atlas. Pageant Atlas does not need to read unrelated device-calendar entries merely to maintain its own in-app planning calendar.
• Files, documents, and photos that a user intentionally uploads to private planning, Binder, wardrobe, profile, marketplace/vendor, or Community features.

Community and user-generated content

• Community profile/handle, bio, posts, comments, reactions, follows or friend relationships, groups/teams, Community photos, shared activity, reviews, marketplace/vendor submissions, claims, edit suggestions, and other content a user chooses to create.
• Private in-app messages. Messages are stored so participants can reopen conversations later. Pageant Atlas private messages are not end-to-end encrypted. Access for moderation is restricted to authorized safety/reporting workflows rather than general browsing of private conversations.

Approximate location and location-related queries

When a user chooses a feature that needs location and grants permission, Pageant Atlas may request approximate/coarse device location to find nearby pageants, vendors, weather, or other location-relevant information. Device-derived location is not intentionally maintained as a location-history feature. A query or approximate area may be sent to an appropriate public-data provider when needed to complete the user's request. Location text that a user intentionally adds to a profile or planning record may be stored with that record.

Speaking practice, microphone audio, and transcripts

When a user deliberately starts a speaking-practice or speech-recognition feature and grants microphone permission, Pageant Atlas may use microphone audio for transcription and vocal-delivery practice measurements. On supported devices, Pageant Atlas prefers on-device speech recognition. When on-device recognition is unavailable, the Android/system speech-recognition provider may process or transmit microphone audio to its service in order to provide recognition.

Search queries

Search terms may be sent to the Pageant Atlas backend or to a relevant public-data provider as needed to return requested results, such as Community/profile, pageant, vendor, geographic, or public-information searches. Pageant Atlas does not intentionally maintain a persistent user-facing search-history feature at this time.

Private beta applications and recruitment

If someone applies through the public Pageant Atlas beta signup page, we may collect the applicant's full name, Google Play account email, state, pageant involvement/role, optional Android device and Android version, optional testing interests, confirmation that the applicant is at least 18, and consent to receive beta-related contact. This information is used to review beta applications, manage closed-test access, contact approved applicants, provide beta support, and help recruit a useful mix of testers. The application is stored in Pageant Atlas's Supabase backend, and a transactional notification containing application details may be delivered to Big Boom Creations through Resend. Public beta and contact forms also use Cloudflare Turnstile to reduce spam and automated abuse.

Diagnostics and beta feedback

When a signed-in user voluntarily submits a beta bug, data, accessibility, suggestion, or other feedback report, Pageant Atlas may store the report together with limited diagnostic details such as browser/user-agent information, platform, online status, and viewport size. The current beta does not intentionally run a separate third-party crash-reporting or behavioral analytics SDK.

Safety and moderation information

Pageant Atlas may process reports, blocks, moderation status and actions, abuse/rate-limit counters, guardian safety settings, adult-verification status, and limited context necessary to investigate safety, fraud, abuse, policy, or legal concerns.

Local-only information

Some features may keep data only on the user's device, particularly when using local-only/guest functionality. Information that remains solely on the device and is not transmitted to Pageant Atlas or another provider is not collected by Pageant Atlas as cloud data.

2. Why we use information

Depending on the data and feature, Pageant Atlas may use information to:

• provide app functionality, including pageant discovery, profiles, planning, calendars, practice tools, messaging, Community, marketplace/vendor tools, saved content, and uploads;
• create, authenticate, secure, recover, and manage signed-in accounts;
• personalize optional features such as profile experiences and location-relevant results;
• protect users, enforce age/guardian controls, prevent fraud or abuse, investigate reports, comply with law, and maintain platform safety;
• diagnose and fix bugs when a user voluntarily submits beta feedback;
• administer the private beta, document NDA/Beta Tester Agreement acceptance, protect confidential prerelease materials, and handle related contractual, security, or dispute matters; and
• respond to privacy, account, support, and data-deletion requests.

Pageant Atlas does not use the information described in this policy for behavioral advertising in the current beta.

3. When information may be transferred or shared

Pageant Atlas does not sell personal information. Information may be transferred only where needed to provide a requested feature, operate the service, comply with law, or protect users.

• Supabase: hosted authentication, database, storage, and server-side functions used to operate Pageant Atlas cloud features.
• Resend: transactional email delivery for messages submitted through the official contact form and notifications about new private-beta applications. The information included in the applicable message or application notification may be processed to deliver that email to Big Boom Creations.
• Cloudflare Turnstile: anti-abuse verification on public Pageant Atlas forms such as Contact and Private Beta applications. Cloudflare may process technical request, browser, network, and device signals needed to distinguish legitimate submissions from automated abuse, subject to Cloudflare's applicable privacy practices.
• Google and Facebook/Meta: only when a user chooses the corresponding sign-in provider.
• Have I Been Pwned — Pwned Passwords: for a privacy-preserving breached-password check. The app hashes the candidate password locally and sends only the first five characters of the SHA-1 hash for the k-anonymity range lookup, not the full password or full password hash.
• Open/public-data providers: services such as U.S. Census geographic data, OpenStreetMap-related services, weather services, or similar public-information providers when a feature requires them. A search query or approximate area may be sent when the user requests that feature.
• Android/system speech-recognition providers: microphone audio may be processed by the device's recognition provider when on-device recognition is unavailable or not used.
• User-directed sharing: information may be shown to another user or the Community when the user intentionally sends a message, publishes content, shares a profile/activity, submits a listing/review, or uses another sharing feature.
• Safety, legal, and compliance: information may be preserved or disclosed when reasonably necessary to respond to valid legal process, protect users, address fraud or abuse, enforce policies, or satisfy child-safety or other legal reporting obligations.

Service providers that process information on behalf of Pageant Atlas are expected to use the information only to provide the contracted or requested service, subject to their applicable terms and privacy practices.

4. Children, teens, and family profiles

Pageant Atlas is family-oriented and uses conservative age and guardian controls for Community features.

• Profiles known to be under 13 cannot independently use Pageant Atlas Community; those family profiles are guardian-managed.
• If a profile's age cannot be established, Pageant Atlas treats the profile as restricted rather than assuming the person is an adult.
• Teen profiles ages 13–17 require an adult-verified guardian or household manager to enable Community access.
• Teen discovery, social connections, follow or friend requests, group invitations, Community photo posting, personal/contact-information exchange, and automatic activity sharing are separately controlled and default off in the beta safety model.
• New Community material from restricted/teen contexts may be moderated before publication, and safety reports may cause content to be quarantined while reviewed.

An adult may create and manage a family profile containing information about a child. Pageant Atlas should not be used to provide information directly from a child where parental consent or other legal authorization is required and has not been obtained.

Adult-verification minimization

For the beta guardian-control age check, an adult account holder may enter a date of birth to establish that the account holder is at least 18. The age-check flow does not retain the entered date of birth itself; it stores the verification method, verification timestamp, and expiration. This is an age gate, not government-ID identity verification. Separately, a user or guardian may choose to store age/birth-date information in a family profile where that feature is used.

5. Private family data and Community content

Private family/planning data and Community user-generated content are intentionally separated.

• Private family/Binder material is access-controlled and is not automatically published to Community.
• Community content uses separate Community workflows and may be reviewed as part of moderation and safety processes.
• Moderators are not intended to have unrestricted blanket access to private family storage.
• Users should avoid sending passwords, government IDs, payment-card information, precise home addresses, or similarly sensitive information through Community or private messages.

6. Security

Pageant Atlas uses safeguards intended to protect account and family information, including encrypted network connections, access-controlled database policies, private storage areas, server-side authorization checks, scoped permissions, abuse/rate limits, age/guardian gates, moderated Community publication, authenticated account deletion, Content Security Policy, and private application source repositories.

No online service can guarantee absolute security. Pageant Atlas treats significant security and privacy findings as issues requiring review, remediation, testing, and appropriate incident response.

7. Retention and deletion

Pageant Atlas retains personal information only for as long as reasonably necessary to provide the feature or account, maintain safety and security, handle disputes, meet legal obligations, or fulfill another legitimate purpose described in this policy.

When a verified account-deletion request is completed, Pageant Atlas deletes the account and associated cloud data that is not required to be retained for a legitimate legal, contractual, safety, fraud-prevention, security, dispute, or reporting purpose.

For invited private-beta testers, a limited signed NDA/Beta Tester Agreement acceptance record may be retained after account deletion when reasonably necessary to document the agreement, protect legal or contractual rights, resolve disputes, or address security or misuse concerns. This retained record is not used for advertising.

Local-only data stored exclusively on a user's device may need to be removed from that device by clearing app data or uninstalling the app.

For detailed account and data-deletion instructions, visit the Pageant Atlas Account & Data Deletion page.

8. Your choices and privacy rights

Depending on the feature and applicable law, users may be able to:

• use local-only features without creating a cloud account;
• decline optional permissions such as location or microphone access;
• choose whether to create Community content, messages, uploads, searches, profiles, calendar/planning entries, or saved practice attempts;
• edit or delete many user-created items within the app;
• request correction, access, restriction, or deletion of account-associated information where applicable; and
• delete the signed-in account and associated cloud data through the app or by using the web deletion method.

To request deletion of specific data without deleting the entire account, follow the partial-deletion instructions on the Account & Data Deletion page.

9. Changes to this policy

We may update this Privacy Policy when Pageant Atlas features, providers, legal obligations, or data practices change. Material changes to child, teen, Community, advertising, or sensitive-data practices will receive additional review and, where required, renewed notice or consent. The effective and last-updated dates at the top of this page will be changed when the policy is revised.