Privacy Policy

At a glance

• We use information to run OZZI and the features you choose.

• First-party measurements and optional advertising have separate purposes and controls.

• Parents manage child permissions and can request access or deletion.

1. Who this policy covers

This policy explains how OZZI, Inc., a Delaware corporation operating in the United States, handles personal information when you visit OZZI.com, play games, build, or participate in families and groups. OZZI is responsible for the processing described here. Contact [email protected] with privacy questions.

You can try public games without an account. Signing in lets OZZI keep supported progress, your library and other account features. Guest play still needs limited technical information to deliver games and keep the service working.

2. Information we use

• Accounts and families. Account or display name, email for independent accounts, child username, protected login credentials, age and location information needed for eligibility, family relationships, permissions and records of consent. A child profile uses the parent's contact email; it does not need the child's own email.

• Things you build and share. Games, uploaded source and assets, studio details, artwork, game descriptions, group invitations and memberships, comments and other content you choose to provide.

• Play and preferences. Games played, supported saves, submitted scores, hearts, pinned games, followed studios and appearance settings.

• Technical and safety information. IP address, browser and device information, session and connection identifiers, access times, errors, security events, game checks, reports, moderation decisions and correspondence with us.

• Connected tools. The identity of a tool you authorize, its permissions and access credentials, connection history, and the files or instructions it submits to OZZI on your behalf.

If you choose to confirm adult eligibility with Google, we request its reported age range for that linked account. We use the result for adult-game access for at most 30 days before requiring renewal. Disconnecting Google ends that eligibility immediately. This does not require a government ID, and the reported range is not proof that Google verified your identity.

We receive information directly from you, from a parent managing your profile, from authorized tools, and automatically as the service runs. Other people may provide information involving you in an invitation or report. We do not ask for your contacts, precise device location or government ID for ordinary play or account use. Please keep passwords and unnecessary personal information out of games, comments and reports.

3. Why we use it

We use this information to create and secure accounts; apply family and audience permissions; host, check and deliver games; keep progress and requested preferences; support groups and eligible public scores; moderate games and conversations; handle questions and reports; diagnose problems; and meet legal obligations.

Account messages include verification, recovery, consent requests and important service or policy notices. We use service activity and error information to understand what works and improve OZZI. First-party game measurement is independent of advertising choices. It records observations using random account or browser identifiers; names, emails, IP addresses, exact birthdays, raw user agents and private support text are not stored in measurements. Where Google advertising is offered, Google may use cookies and activity to personalize and measure ads, subject to your separate choices and applicable restrictions. We do not sell information for money. Advertising disclosures and opt-out rights apply where a law treats advertising-related sharing as a sale or sharing. We do not use your uploads or children's personal information to train general-purpose AI models.

4. Who can see what

Public content. A public game, its presentation and studio identity can be seen and shared by anyone, including search engines. Public comments and submitted leaderboard scores include the display name used for them. Avoid using a child's full name as a public display name.

Your selected audience. Private games are limited to the builder and managing parent. Anyone-with-the-link games are available to people who have the link and can be forwarded. Group membership does not unlock a private game. Group conversations and membership are for members; an invitation link reveals the group name and description to its recipient. A group's challenge may use a public leaderboard.

Game statistics. Builders and authorized studio collaborators receive aggregate audience, discovery, activity, return and feedback statistics. Group organizers see their group-owned creations and activity originating through their group; membership or curation does not unlock another studio’s worldwide statistics. Country, region and city are approximate IP-derived locations; statistics records do not contain raw IP addresses or precise coordinates, and small city samples are combined. Aggregate reports do not identify individual players.

Source and player data. Publishing does not make your separately uploaded source package available for others to download. Files needed to run a browser game are delivered to the player's device and can be inspected there. Game code receives the gameplay input and supported save data needed to run; builders do not receive your account email or a general right to your personal information. Games must use OZZI's supported services rather than collect personal information or add their own trackers.

Parents and authorized staff. A managing parent can review their child's builder work, permissions, group memberships and available conversation activity. Authorized OZZI personnel may access content, including nonpublic material, where needed for support, security, moderation or legal duties. A private setting limits audience access; it does not prevent these necessary operations.

5. Providers and other disclosures

We use providers for hosting and databases, file storage and delivery, security, and account email. Our planned launch providers are Render for application hosting and databases, Cloudflare for storage, delivery and security, and Postmark for account email. They receive the information needed for their work under contractual restrictions. We identify additional providers involved in children's information before using them for that purpose.

When you authorize a coding tool, it may receive builder details and private game files within the permissions you grant. Its provider handles that information under its own policy. Revoking the connection stops further authorized access to OZZI; it does not erase copies the tool already received. External links and sharing destinations also have their own privacy practices.

We may disclose necessary information to respond to lawful requests, protect people and the service, investigate misuse, or establish and defend legal claims. Relevant copyright notices and counter-notices may be shared with the other party. If OZZI is acquired or reorganized, information may transfer with the business subject to this policy and applicable notice and consent requirements.

6. Cookies and device storage

OZZI uses cookies for sign-in, authorized connections and guest play security. Sign-in sessions currently last up to seven days; a guest play identifier can last up to 30 days. The guest identifier is limited to authorizing play and limiting abusive reports. We do not use it to build behavioral profiles or track you across other services.

Guest game checkpoints stay in memory for the current run and are lost on reload. Signed-in studio previews and guide drafts may use browser storage to keep local work. Account game progress is saved on our servers where the game supports it. You can clear cookies and browser storage through your browser; doing so can sign you out and remove local drafts or previews, but does not delete server-side account data.

OZZI uses a separate first-party recognition cookie for visits, discovery, active play and returns. It expires 90 days after actual foreground use; another foreground visit refreshes that period. Background polling and delayed measurement retries do not extend it. After 90 days without use, or after clearing or rejecting the cookie, a guest browser is no longer recognized as returning. Signed-in accounts use a separate random identifier across devices. Earlier guest activity is not attached to a later sign-in. Historical observations remain in PostgreSQL independently of cookie expiry, and are not used for advertising or tracking across other services. A small per-tab session-storage buffer retries pending observations for up to 24 hours.

A separate necessary cookie, ozzi.consent, remembers acceptance, refusal or dismissal for 90 days after your last actual use on this browser. Returning or actively playing refreshes that period without asking again or changing your decision. Signing in or out preserves it. The receipt records the purposes, notice wording and version, original decision time and expiry; explicit changes preserve the previous receipt. We retain expired or replaced proof for another 12 months. Choices are not restored on other devices or from account history. Optional advertising stays disabled for known young accounts regardless of the saved browser choice.

Google advertising is inactive. Advertising measurement and personalization preferences can be saved separately now, but Google may require another consent step when integrated. Availability may vary by market and may begin or end; a saved preference does not override applicable legal, regional, child or Google requirements. No Google advertising code runs merely because a preference is saved. How Google uses information from partner sites.

Change or withdraw advertising permissions at Cookies. Closing the initial notice leaves optional purposes off. Terms acceptance, Privacy acknowledgment and cookie choices are separate. Browser Do Not Track does not change essential processing; applicable Global Privacy Control and advertising opt-outs must be honored when advertising is offered.

7. Children and parent choices

Children under 13, or below the applicable independent-account age, use a parent-managed profile only where available and permitted. During supported US young-builder setup, the parent signs in, reads a short notice, types their full name and explicitly approves the account. We retain that parental declaration with the notice, choices and child account; it is not an identity-verification service. We keep the private birthday supplied by the parent to determine age-appropriate games as the child grows. A parent must separately approve optional disclosure, such as public posting and scores, where required. A child can use the basic supervised experience without agreeing to optional public sharing.

Children and their current managing guardians can see the child’s game-by-game playing history, dates, confirmed ending or last observed activity, and active playing time for up to 90 days. This private association is limited to activity recorded in the same supervising family; a new family does not gain earlier family history. Children see a notice of this supervision. Named history is separate from audience facts and is never included in operator support or audience responses. Audience reports use random identifiers and available coarse age bands: under 13, 13–17, 18+ or unknown. Exact birthdays remain with the identity owner and are not copied into measurement. Parents do not gain another studio’s private audience data because their child collaborates there.

The necessary account, safety and supervised-feature practices in this policy also apply to child profiles; optional advertising does not. Games and comments can contain personal information if a child puts it there. Communication and public-score permissions start off for managed profiles; parents control them and approve connections and required publication actions. We do not condition participation on providing more information than an activity reasonably needs.

A parent can ask to review or delete their child's information, withdraw consent, or stop further collection by writing to [email protected]. We verify the relationship before sharing information or making account changes. Withdrawal can mean disabling the affected feature or closing the child profile. Tell us at the same address if you believe a child is using an independent account below the permitted age; we restrict access and remove information collected without required consent.

Draft contact details: OZZI, Inc.'s business mailing address and parent-contact telephone number will be added here before this policy takes effect.

8. How long information stays

These are the current storage lifecycles, including children's information:

• Active accounts and games: while needed to provide the account, hosted work and saved progress. After a verified deletion request, we remove or de-identify the relevant information from active systems within 30 days, or sooner when required. If an account is unused for 24 months, we give 30 days' notice before closing it and applying the same deletion schedule.

• Unfinished child consent: parent contact and pending setup information are deleted after 14 days if consent is not completed.

• Audience measurements: historical facts remain independently of recognition-cookie expiry and resource deletion, with unavailable-resource labels after a game or studio is removed. Account deletion removes the identity-to-measurement mapping. Named personal and supervised playing associations last up to 90 days and are removed with the profile; historical private-only records are never reclassified as audience facts.

• Routine access, session and diagnostic records: up to 90 days after the event or session expiry, to troubleshoot and prevent abuse.

• Support, safety and consent records: up to 12 months after a case closes or the related account closes, to document the response or permission and handle follow-up. We retain only what is needed for that purpose.

• Backups: deleted information ages out within 90 days after removal from active systems. It is isolated from ordinary use; if a backup is restored, deletion requests are reapplied.

A specific legal duty, active dispute or documented security incident may require limited records for longer. We restrict their use and delete them when that need ends. Making a game private or hiding a post is not a deletion request. We cannot delete independent copies already made by other people or services.

9. Your choices and requests

Use account, family, audience and connection controls for the choices available there. For access, correction, a copy of your information, account closure or deletion, email [email protected]. You can ask for help even if a control is not available in the interface. Please identify the account and request; do not send your password or identity documents in an ordinary email.

We use proportionate verification before releasing or deleting information. Depending on applicable law, you may also object to processing, ask us to restrict it, withdraw consent, use an authorized agent, or appeal a refusal by replying with "Privacy appeal." We respond within applicable deadlines, explain any permitted refusal or extension, and do not penalize you for exercising privacy rights. You can also complain to the privacy regulator where you live. Withdrawal does not change the lawfulness of earlier processing.

10. Location and security

OZZI operates from the United States, and information may be processed there and in countries where our providers operate. Available legal protections can differ. Where European or UK data law applies, we use an applicable transfer mechanism, such as approved contractual safeguards, rather than treating your use of the site as consent to a transfer. Contact us for information about the safeguards relevant to your data.

Where those laws apply, our legal bases are providing the service under our agreement, legitimate interests in security, support and improvement balanced against your rights, compliance with legal obligations, and consent where required. Optional consent can be withdrawn. Children's interests receive particular weight; the account-age rules in our Terms still apply.

We use access controls, protected credentials, separate game delivery and other reasonable safeguards appropriate to the information. Access is limited to people and providers who need it. No security method eliminates every risk; report a suspected problem to [email protected].

11. Policy updates and contact

We post the current version here with its effective date. For material changes, we give notice through OZZI or account email before they take effect where required. If a new use requires consent, including renewed parental consent, we obtain it before that use begins.

Privacy and parent requests: [email protected]. General assistance: [email protected]. For the rules about using OZZI, read the Terms of Service and Community Guidelines.