Privacy Policy

This Privacy Policy explains how personal information is handled across the Moozgy website (moozgy.com) and the Moozgy iOS app. In this document, "Moozgy," "we," "us," and "our" refer to the individual founder who owns and operates the Moozgy project as a sole proprietor, currently based in Italy (contact details in Section 11 below). "You" means the person using the website or the app, or, in Section 9, a creator we contact. Operation of Moozgy and this policy may be assigned to a company formed for the Moozgy business in the future (see the Terms of Use, General provisions).

By using the website, creating a Moozgy account, or using the Moozgy app, you acknowledge this Privacy Policy. If you do not agree, please do not use the website or the app. See also the Terms of Use, which governs your use of the app and any purchase.

1. What we collect

We deliberately collect as little as possible, and what we collect differs between the website and the app itself. If you are a creator we have invited, or may invite, to our affiliate programme, Section 9 explains what we hold about you.

On the website

• Shared-problem page analytics — if you open a problem someone shared with you, we record that the page was viewed and whether you tapped the call-to-action, together with the share code and the referring user's id. These events carry no account and no personal identifier of yours.
• Download button taps — when you tap a Download button on the website, which opens Moozgy's page on the App Store, we record one event: that a Download button was tapped, when, and a short campaign name built from the utm_source and utm_campaign tags in the web address you arrived at (for example meta.launch-week, or web if there were none). Nothing else is recorded with it: no account, device, session or other identifier, and no ad click ids such as fbclid or gclid. We do not store your IP address with it. We use these events only to count taps per campaign.
• App Store links — the Download button's link to the App Store carries the same campaign name, so that Apple can report to us, as totals per campaign, how many App Store page views, pre-orders and downloads each campaign produced. Apple receives the name when you open the link (Section 4).
• Affiliate applications — the application form on our affiliate page sends nothing itself. It opens an email to us in your own email app, containing your email address, your name, the profile or website you give, and your country or region. We receive it only if you press Send, and we use it to review your application and reply to you.
• Earlier pre-launch sign-ups — until October 5, 2026, the website took email sign-ups for free spots and the waitlist, and offered the Founder plan and gifts. If you used one of those forms, we still hold your email address, the plan you chose (free / waitlist / Founder / gift), which form you used, the date and time, and any referral code from the link that brought you, so we can deliver what we promised. The website no longer collects any of this.
• Technical data — our host, Vercel (Section 4), necessarily sees your IP address and request metadata when your browser loads a page. Pages that show a shared problem or a public card set fetch it from our backend, Supabase, and Download button taps are recorded there; Supabase sees the same.

The website sets no cookies and uses no browser storage (Section 3). We do not use third-party analytics trackers, advertising pixels or fingerprinting on the website.

In the app

Creating a Moozgy account and using the app involves more information, because the app is a real product with an account, a subscription, and AI features:

• Account information — the email address (or Sign in with Google / Sign in with Apple identifier) you use to create your account, the handle (username) and display name you choose, and the name your sign-in provider passes to us. Your handle is public; see "What other people can see" below.
• Date of birth — Moozgy is for people aged 13 and over, and every sign-up path asks for your date of birth to check that. For an account, we store the date on your profile; it is never shown to other users. If you use the app as a guest, your date of birth stays on your device only and is never sent to us.
• Country or region — taken from your device's own region setting (not from GPS or any location sensor) and stored on your profile, so we can put you in the right pool for the "Local" leaderboard.
• Learning and usage data — problems you have seen and whether you got them right, answers, streaks, difficulty level, XP and achievements, session activity, and how you interact with the feed, Coach, and Explain features. This is what makes the adaptive difficulty and coaching work. Your detailed progress record is synced to your account so it survives a reinstall and follows you to a new device.
• Product-analytics events — first-party, in-house events (screens reached, onboarding and paywall steps, features used) recorded with a session id, your app version, and either your account id or, before you have an account, a random identifier generated on your device so pre-sign-up steps can be joined to the account you later create. You can turn product analytics off at any time in Settings, and we use no third-party analytics SDK.
• Contacts (optional, on-device hashing) — if you choose to look for friends already on Moozgy, the app reads the email addresses in your contacts, converts each one into a SHA-256 hash on your device, and sends only those hashes to our server to match against the email addresses of Moozgy accounts. We never receive your contacts' names, raw email addresses, or phone numbers; the hashes are used for the lookup and are not stored on either side. A hash is not anonymous: anyone who already knows an email address can compute the same hash, so we limit how often matching can run and limit who it can find (see "What other people can see" below). The app does not read your contacts' names or phone numbers at all. Nothing happens here unless you open "Find people" and grant iOS contacts permission, and permission can be withdrawn at any time in iOS Settings.
• Purchases — if you buy Moozgy Full Brain or redeem a gift or promo code, we record that the purchase or redemption happened, which transaction it corresponds to, and its status, so we can unlock your access. We never receive or store your card number; App Store purchases are billed and processed entirely by Apple.
• AI feature content — when you use Explain Anything, the Coach, or Coach-generated card sets, we send your question or the source material you provide — text you type or paste, and images or documents you upload — to our AI provider (see Section 4), together with minimal learning context, so it can answer or build your cards. We do not retain your uploaded source material. Files and the text extracted from them exist only for as long as it takes to answer your request, and are never written to our servers. We do save the card sets you create, so they are there when you come back, and we save reported answers when you report one. We do not store the text of your questions or the AI's answers otherwise. We record only the technical usage of each request (which feature, which model, token counts and cost) so we can meter fair use and control our costs. Your "Explain Anything" history is kept on your own device.
• Reports — if you report a problem as wrong or unclear, we receive the problem, the answer you gave, the reason you selected, and any note you type. If you report an AI answer, we also receive that answer and the question that produced it. If you report another person, we receive their handle as it read when you reported them, the reason you chose and any note you type. Reports are read only by our team, and the person you report is never told who reported them. We keep reports after an account is closed, with the link to the account removed, so that a record of abuse cannot be erased by deleting and re-registering.
• Email preference — whether you opted in to hear from us about Moozgy news.
• Technical data — standard information any server necessarily sees on a request, such as your IP address and the request metadata your device's network stack sends, held in our backend's operational logs.

We do not ask for, and do not intentionally process, precise location, payment card numbers, health data, or biometric data. Our Terms ask you not to upload source material containing them; because we do not retain uploaded material, anything that reaches us incidentally is discarded once your cards are made. We do not use advertising, attribution, or third-party tracking SDKs, we do not track you across other companies' apps or websites, and we do not sell any of the above.

What other people can see

Moozgy has leaderboards and friends. Other users can see your handle, the number of problems you have solved, and your rank — on the global board, on your region's local board, and among your friends. Your real name, email address, date of birth, and detailed progress are never shown to other users. You can remove yourself from the public global and local boards at any time in Settings; your friends board is unaffected.

Being found through contacts. While you appear on the public boards (Settings → "Show me on public leaderboards", on by default), another user who has your account's email address in their phone contacts can find your handle through "Find people". They see your handle, never your email address. Turn that setting off and only people you are already friends with can match you this way.

Sets you publish. If you choose to make a card set public, the set's title, its subject, and the full text of every card in it become readable by anyone who has the set's link, including people who are not Moozgy users. We do not attach your name, handle, email address, or any other detail about you to a public set — a visitor sees the cards and nothing about who made them. What the cards themselves contain is up to you; please read the "Sets you publish" section of our Terms before publishing one.

2. How and why we use your information

We use the information above only to:

• create and operate your account, sync your progress across your devices, and deliver the app's core features — legal basis: performance of a contract (GDPR Art. 6(1)(b));
• run the adaptive difficulty engine, the leaderboards, and the AI Coach / Explain features you use — legal basis: performance of a contract;
• check that you meet the 13+ age minimum — legal basis: legal obligation and legitimate interests (Art. 6(1)(c) and (f));
• match the contacts you choose to share against Moozgy accounts, using only on-device hashes — legal basis: consent (Art. 6(1)(a)); and let people who already have your email address find your handle while you appear on the public boards — legal basis: legitimate interests (Art. 6(1)(f)), which you can end with the Settings switch above;
• understand how the app is used in aggregate so we can improve it, using our own first-party analytics that you can switch off in Settings — legal basis: legitimate interests (Art. 6(1)(f));
• count, in aggregate, views and taps on shared-problem pages and taps on the website's Download buttons, so we know which links and advertising campaigns bring people to Moozgy — legal basis: legitimate interests (Art. 6(1)(f)); these website events carry no identifier of yours;
• process subscription purchases, trials, gift codes, and promo redemptions, and deliver the pre-launch benefits we promised to earlier website sign-ups — legal basis: performance of a contract / legitimate interests;
• review affiliate applications you send us and reply to them — legal basis: steps you ask us to take before entering into a contract (Art. 6(1)(b));
• invite creators to our affiliate programme and run it with them — legal basis: legitimate interests (Art. 6(1)(f)); performance of a contract once they join (Art. 6(1)(b)) (see Section 9);
• act on problem reports and support requests you send us — legal basis: legitimate interests;
• tell you about Moozgy launch news or account-related updates — legal basis: consent for marketing email; legitimate interests for service messages;
• keep the app secure, enforce fair-use limits, prevent abuse, and comply with legal obligations — legal basis: Art. 6(1)(c) and (f).

If someone sends us a copyright complaint about a set you published, we pass their notice — including their contact details — to you, and we pass any counter-notice you send back to them. United States copyright law requires this, and it is the only way either of you can resolve the dispute.

We do not sell your personal information, "share" it for cross-context behavioral advertising, or use it for automated decision-making producing legal or similarly significant effects. Any marketing email will include a way to opt out.

3. Cookies and browser storage (website)

The website sets no cookies and stores nothing in your browser's local or session storage. There is no cookie banner because there is nothing to ask you about: the website uses no cookies of any kind, and it does not remember you, or which link brought you here, from one visit to the next. The campaign name described in Section 1 is read from the web address while the page is open, is used only if you tap a Download button, and is never stored in your browser.

If that changes, we will update this section before the change goes live and, where the law requires it, ask for your consent first. The app does not use cookies; it uses a securely stored session token to keep you signed in.

4. Service providers (processors)

• Vercel — hosts the website. Vercel serves every page, so it receives your IP address and request metadata, as with any web request, and acts as our data processor. See Vercel's privacy notice.
• Supabase — the app's backend: authentication, the problem database, your synced progress, the social and leaderboard graph, and the AI edge functions described below all run on Supabase (Postgres + edge functions), acting as our data processor. On the website, the pages that show a shared problem or a public card set fetch it from Supabase, and the shared-problem page events and Download button taps described in Section 1 are recorded there. See Supabase's privacy policy.
• Resend — delivers the emails our systems send you, such as your sign-up and sign-in codes, so it receives your email address and the message. It acts as our data processor. Our outreach emails to creators go through a separate Resend account (Section 9). See Resend's privacy policy.
• Anthropic — powers Explain Anything, the Coach, and Coach-generated card sets through Claude. Your questions and any source material you provide are sent to Anthropic to produce the response. Anthropic does not use these inputs or outputs to train its models, and automatically deletes them within 30 days. See Anthropic's privacy policy.
• Apple — Moozgy Full Brain purchases, free trials, and Sign in with Apple are handled by Apple through StoreKit and your Apple ID; Apple acts as its own controller for the payment and account data it collects. App Store links on the website carry the campaign name described in Section 1; Apple reports to us only totals per campaign. Our email, including hello@moozgy.com, is hosted on Apple's iCloud Mail, so messages you send us, including affiliate applications, are stored there. See Apple's privacy policy.
• Google — the earlier website sign-ups described in Section 1 are stored in a private Google Sheet, and the app offers Sign in with Google, in which case Google receives your IP address and request metadata, as with any web request. See Google's privacy policy.
• Stripe — if you bought the website's Founder plan or a gift of Moozgy before October 5, 2026, checkout happened entirely on Stripe, Inc.'s hosted payment page. Stripe received your email address and independently collected and processed your payment details; we never see or store your card number. Stripe acts as its own controller for fraud prevention and compliance. See Stripe's privacy policy.

Beyond these providers and those listed in Section 9 for creators we contact, we disclose personal information to no other recipients, except if required by law, court order, or governmental authority, to enforce our terms, or in connection with a sale, merger, or transfer of the Moozgy business (in which case the recipient remains bound by this policy).

5. International data transfers

The founder operates from Italy; our service providers (Vercel, Supabase, Resend, Anthropic, Apple, Google, Stripe) store or process data primarily in the United States. Where personal data of EEA/UK residents is transferred outside the EEA/UK, the transfer relies on the providers' compliance mechanisms, including the EU–US Data Privacy Framework and/or Standard Contractual Clauses.

6. Data retention & deletion

Sign-up information from the earlier website forms is kept until Moozgy launches and any promised benefits have been delivered, plus a reasonable period thereafter (no longer than 24 months after launch), or until you ask us to delete it — whichever comes first.

Website events (shared-problem page views and taps, and Download button taps) are kept for no longer than 24 months, after which they are deleted automatically.

Affiliate applications you email us are kept for as long as we need to decide on your application and, if you join, to run the programme with you, or until you ask us to delete them.

What we hold about creators we contact is kept for the periods set out in Section 9.

Account data in the app is kept for as long as your account is active. Product-analytics events are in any case retained for no longer than 24 months, after which they are deleted automatically. Uploaded source material is not retained on our servers at all. Card sets you create are kept for as long as your account is active, and are deleted with your account. A set you make private again stops being readable from its link immediately, and a set we remove for breaking our rules stops being readable at the same moment. Both stay in your own account until you delete them, and both are deleted with your account. We cannot recall copies that people who opened the link have already saved.

You can delete your account and its associated data directly in the app (Settings → account deletion). This permanently removes your profile, date of birth, synced progress, friendships, AI usage records, and purchase links from our systems; historical analytics events are irreversibly detached from you and kept only in de-identified form. Reports you filed or were named in (content_reports) are kept as described in Section 1, with the link to your account removed rather than the report deleted. Records we must keep for legal, tax, or fraud-prevention purposes are retained, and backups age out on a routine schedule. You can also request deletion at any time by emailing us (Section 11).

7. Your rights

Everyone: you may request access to, correction of, or deletion of your data, or opt out of non-essential emails, at any time by emailing us (Section 11) or, for account data, using in-app account deletion. We will respond within 30 days.

EEA / UK residents (GDPR): you additionally have the rights to restriction of processing, data portability, objection to processing based on legitimate interests, and withdrawal of consent at any time (without affecting prior processing). You also have the right to lodge a complaint with a supervisory authority — in Italy, the Garante per la Protezione dei Dati Personali (garanteprivacy.it), or the authority of your habitual residence.

California residents: although Moozgy does not currently meet the thresholds that make the CCPA/CPRA apply, we voluntarily honor its core rights: to know what we collect (this policy), to delete, to correct, and to non-discrimination for exercising those rights. We do not sell or share personal information as those terms are defined in the CPRA, and we have not done so in the preceding 12 months.

8. Children

Moozgy is a general-audience product for people aged 13 and over. It is not directed to children under 13, it is not offered in the App Store Kids Category, and we do not knowingly collect personal information from anyone under 13. Every path into the app — email sign-up, Sign in with Google, Sign in with Apple, and guest — asks for your date of birth first and refuses to continue if you are under 13.

In some EEA countries, national law sets a higher age (between 13 and 16) below which a parent or guardian must consent to online services being provided to a child. If you are in one of those countries and are below that age, please use Moozgy only with your parent's or guardian's permission.

If you believe a child has created an account or submitted an email address, contact us (Section 11) and we will delete it promptly.

You must be at least 18 (or the age of majority where you live) to make a purchase.

9. Creators we contact

If you publish content online, we may invite you to Moozgy's affiliate programme. This section explains what we hold about you if we do, even if you have never used Moozgy.

What we hold and where it comes from. Your name and handle as you publish them, the platform and profile link, public follower and view counts, the topics you cover, the country your channel lists, and the business email you publish on your channel or link page, together with the web address where we found it. We never use personal email addresses or phone numbers, and we do not guess addresses. If we exchange messages, we also keep them, whether by email or by direct message on Instagram, TikTok or X.

Why, and our legal basis. To invite you to the programme, answer you, and, if you join, run the programme with you. Our basis is legitimate interests (GDPR Art. 6(1)(f)): working with independent creators who publish a contact for business enquiries. Once you join, it is performance of a contract (Art. 6(1)(b)). We send one invitation and at most one follow-up. We email cold only to adult creators based in the United States. If you are in the EEA or the UK, we write to you only after you contact us.

Who writes to you. Most of these messages are written by an AI assistant working for Moozgy's founder, which also answers your replies. Each message it writes says so. The founder can read every conversation and may write to you personally; those messages are signed by the founder. Reply "human" and the founder answers personally. Nothing the assistant does has legal or similarly significant effects on you: it offers only the programme's standard terms, and anything outside them is decided by the founder.

Who receives it. Resend, which sends and receives our outreach emails; Supabase, which stores the outreach record; Anthropic, whose Claude models run the AI assistant that writes and answers the messages; Meta, TikTok or X, if you message us on Instagram, TikTok or X, which run those messaging services under their own privacy policies; Apple iCloud Mail, which hosts hello@moozgy.com, for messages to or from that address; and our internal work-management tool, Multica, where our creator research is kept. Transfers of this information outside the EEA rely on the mechanisms described in Section 5.

How long. If we never contact you, 12 months from when we found you. If you don't reply, 6 months after our follow-up. If you reply but don't join, or apply and aren't accepted, 6 months after the last message or decision. If you join, for as long as you take part and 2 years after, except payment and tax records, which Italian law requires us to keep for 10 years. An application you make yourself is kept as Section 6 describes.

So we never invite you twice. When the rest is deleted, we keep a one-way hash of your handle and profile link, and the date, whether or not you replied. The only exception is if we never wrote to you and you never applied. If you didn't reply, we also keep a one-way hash of the email address we wrote to. We use these hashes only to make sure we never send you a second invitation. They are never used to stop mail you ask for, or an application you make yourself.

Saying no. Reply "stop", use the unsubscribe link, or email hello@moozgy.com, and we will never contact you again. To make sure of that, we keep a one-way hash of your email address, handle and profile link, and the date, and delete everything else within 30 days. You can also ask us at any time what we hold, or ask us to correct or delete it. Because Moozgy is run from Italy, the GDPR rights in Section 7 apply to you wherever you live, including the right to object at any time and to complain to the Italian Garante.

10. Security

We use reasonable technical and organizational measures appropriate to the scale of the data we hold: all traffic runs over HTTPS, access to backend systems is restricted and credential-protected, database access is governed by row-level security scoped to your own account, the queued analytics on your device is stored in a protected, backup-excluded file, payments are handled by Apple and Stripe (PCI DSS Level 1), and the website itself stores nothing about you beyond the earlier sign-up sheet and the website events described in Section 1. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security; if a breach affecting your data occurs, we will notify you and the competent authorities as required by applicable law.

11. Contact

Privacy questions, access/deletion requests, or opt-outs: hello@moozgy.com.

12. Changes to this policy

We may update this page from time to time. The "Last updated" date above will change, and material changes will be highlighted on this page. If you have an account and a change materially affects how your information is used, we will notify you at your account email before the change takes effect.