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 12 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).
• Website analytics — on our public pages (the home page, the affiliate page, Support, this policy, the Terms and our page-not-found page), our own code counts page views, taps on links to the App Store or to Join, how far down the page people scroll (25, 50, 75 or 100%), and where on the page people click, as one cell of a 20 × 50 grid laid over the page. With a page view we count the page, whether the window is phone-, tablet- or desktop-sized, the name of the website that linked to it (for example google.com, never the full address) and the campaign name described above. Each of these only adds one to a daily total: we keep no record of the visit, so two counts from the same visit cannot be connected afterwards. Nothing is stored in your browser, and no cookie, identifier, IP address, browser details or anything you type is recorded. If your browser sends a Global Privacy Control or Do Not Track signal, nothing is counted. Pages that show a shared problem, a public card set or a creator's code, the affiliate portal and our staff area are not counted this way.
• Creator code pages — when you open a creator's code link (moozgy.com/r/…), the page asks our backend, from your browser, whose code it is and whether it is live, so it can show you the creator's name. To count visits for that creator, our backend records that the page was opened, at most once per visitor, per code, per UTC day. It recognises a repeat visit by a key made from a keyed hash of your IP address, the code and the day, so the key is different for every code and every day; it stores no IP address, account, cookie or other identifier with it. Shortly after each UTC day ends, that day's keys are deleted and replaced by one number: how many people opened the code's page that day. The creator sees only those daily totals, never who visited. The page also sends a random number our backend requires with each request; it is new on every page load and is not stored. To stop abuse, our backend counts the requests each IP address makes in a minute and, under a keyed hash of the address, how many codes that do not exist it tries in an hour; it refuses requests over those limits.
• Affiliate portal — to apply to our creator and affiliate programme at /creators/apply, you sign in with your Moozgy account, by email and password or with Sign in with Google. Your application is stored with that account. It holds the name you give, each platform you list with its handle and follower count, your niche, your country, why you want to join, the commitments you confirm, and which version of the Affiliate Terms you accepted and when. We reply at the email address on your Moozgy account, and record whether we approved or declined the application, when, and any note we wrote about it.
• If you become a partner — we keep the name you applied with; the codes and links you create, with their dates, limits, campaign labels and chosen perk; how often each code has been used; the referrals and payments credited to you, the commission on each and its state; and your payout and clawback records.
• Videos you submit as a partner — if you submit a video you posted about Moozgy, we keep, for each platform you posted it on, its link, the account you posted it from, the date and time you posted it, and the view, like, comment and share counts you enter or we read; for the video itself, its type (for example a challenge or an app review) and any hashtags, caption, description or transcript you add; any screenshot of your own statistics you upload; and whether we approved it, when, and any note we wrote about it. For a YouTube video, our backend reads its publish time and its view, like and comment counts from YouTube through the YouTube API Services (Section 4). With our own totals of downloads, sign-ups and subscriptions, we use these to estimate how many more people than usual signed up and subscribed after the video. The estimate is made from totals only: we never decide that any particular person came from a video. If you use the planner to plan videos, we keep each plan's platform, type and planned time, and which post it became; other partners see only how many videos are planned in each time slot, never whose. Please crop any screenshot to the video's own statistics.
• Accounts you connect — if you connect your YouTube, TikTok or Instagram account in the affiliate portal, Section 10 explains what we read from it, what we keep and for how long.
• Payouts — to be paid, you set up a Stripe Connect account from the portal. Stripe collects the identity, tax and bank details it needs directly, under its own terms and privacy policy (Section 4). We store your Stripe account ID and whether Stripe has finished onboarding you and enabled payouts, never your bank details.
• 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, creator code page visits and the website analytics are recorded there; Supabase sees the same. The affiliate portal runs on Supabase too, and each sign-in is logged there with your IP address and browser details, as a sign-in to the app is.

The website sets no cookies and uses no browser storage, except the sign-in cookies the affiliate portal and our staff admin area need (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.
• Where you heard about Moozgy — we may ask where you heard about Moozgy: on the website when you apply to our affiliate programme, and in the app when you create an account. Answering is optional. You can pick one answer: a creator in our affiliate programme, found by their display name; TikTok, Instagram or YouTube; a friend; App Store search; a web search; or "Somewhere else", where you can type up to 60 characters. Please don't type anyone's name or contact details there. We store your answer on your account, with the date you gave it, and it can't be changed afterwards. If you answer while applying, it is also included in your application. It is stored whether or not product analytics is on, because it is only what you choose to tell us. We use it to count, in totals, how people hear about Moozgy, and, if you pick a creator, so that creator can earn commission on your subscription where our Affiliate Terms provide for it (see "What other people can see" below).
• Subjects you vote for — the app lists subjects we have not built yet under "Coming soon", and tapping one is a vote for it. We store one vote per subject on your account: the subject, when you first voted for it, and whether you voted while setting up the app or later. If you vote before you have an account, or as a guest, the vote waits on your device and is saved to the next account that signs in on that device; if you sign out of a guest session without creating an account, its votes are deleted from the device. Votes are stored whether or not product analytics is on, because a vote is something you choose to tell us. We use them only to count, in totals, which subjects people want next.
• 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; if you are under 18, it is off unless you turn it on. We use no third-party analytics SDK.
• Feature tests — we sometimes show different versions of a feature to different people, chosen at random, to see which works better, and we may turn a feature on for a group of accounts defined by when they signed up, the app version, the creator code they used, or their product-analytics events. If product analytics is on, we record which version you were shown so the results can be counted; if it is off, we record nothing about it.
• 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. If you subscribed with a creator's or affiliate's code, we also record which code (see "What other people can see" below). 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.

Partners whose code or link you use. If you subscribe with a creator's or affiliate's code or link, that partner earns commission on your payments for a set period (see the Affiliate Terms). Their dashboard lists, under a reference only we can link to your account, which of their codes you used, whether you pay through the App Store or the website, and the date of each payment, the amount we received from it, their commission on it, and any refund. It never shows your name, handle, email address or anything else from your account.

A creator you name. If you pick a creator when we ask where you heard about Moozgy, and no partner's code or link is recorded for you, that creator can earn commission on your payments where our Affiliate Terms provide for it. Their dashboard then shows the same details as above, marked as coming from your answer, and nothing else from your account. If a partner's code or link is recorded for you, that partner is credited instead.

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 and test which version of a feature works better, 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;
• count, in aggregate, page views, link taps, scroll depth and clicks on the website's public pages, so we can see which pages work and improve them — legal basis: legitimate interests (Art. 6(1)(f)); these counts carry no identifier of yours and stop when your browser sends a Global Privacy Control or Do Not Track signal;
• count, per code and per day, the people who open a creator's code page, so the creator and we can see how their link performs — legal basis: legitimate interests (Art. 6(1)(f)); we keep only the daily total once the day ends;
• 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 your affiliate application and reply to it, and, if you join, issue your codes, credit your referrals, calculate your commission and pay you — legal basis: steps you ask us to take before entering into a contract, then performance of that contract (Art. 6(1)(b)); and keep commission and payout records — legal basis: the tax and accounting obligations we are subject to (Art. 6(1)(c));
• record which partner's code or link a subscription used, and show that partner the referral details described in Section 1, so commission is paid on the right payments and partners can check it — legal basis: legitimate interests (Art. 6(1)(f));
• count, in totals, the votes for subjects we have not built yet, so we can decide what to build next — legal basis: legitimate interests (Art. 6(1)(f)); voting is optional;
• ask where you heard about Moozgy, count the answers in totals, and, where our Affiliate Terms provide for it, credit the creator you name — legal basis: legitimate interests (Art. 6(1)(f)); answering is optional;
• review the videos partners submit and estimate, from totals of downloads, sign-ups and subscriptions, how many more people than usual came after each one, so partners and we can see how their videos perform and, where our Affiliate Terms provide for it, pay them for it — legal basis: performance of our contract with the partner (Art. 6(1)(b)) and legitimate interests (Art. 6(1)(f)); no individual is linked to a video;
• use what we read from an account you connect as Section 10 explains — legal basis: steps you ask us to take before entering into our contract, then performance of that contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) for reading comments on YouTube and for totals across creators;
• 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 and the website 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 (website)

The website's public pages set no cookies and store nothing in your browser. There is no cookie banner because there is nothing to ask you about: we use no analytics, advertising or third-party cookies, and nothing in your browser records which link or code brought you here. (Section 1 explains the daily visit count a creator's code page keeps on our backend, without cookies.)

The website analytics described in Section 1 also work without cookies or browser storage: they keep only daily totals, record nothing that identifies you or your device, and stop when your browser sends a Global Privacy Control or Do Not Track signal, so they do not ask for your consent.

The website sets cookies only when you sign in to the affiliate portal (/creators) or our staff admin area. They are strictly necessary first-party cookies, set by Supabase, the sign-in service we use (Section 4). Signing in and staying signed in do not work without them, so they do not need your consent, and we use them for nothing else.

These cookies are sent only to our own website (SameSite=Lax). To delete them sooner, clear this site's cookies in your browser; that also signs you out. Signing out also deletes them. 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, Download button taps, creator code page visits and website analytics described in Section 1 are recorded there. The affiliate portal's sign-in, and everything it stores (Section 1), also run on Supabase, as does everything we read from accounts you connect (Section 10). 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. If you try a test version of the app through Apple's TestFlight, for example from the link in the affiliate portal, Apple shares with us your device model and a device identifier, your iOS version and language, how many times you installed and opened each test build, and its crash logs, together with any feedback you send through TestFlight: your comments and screenshots, details of your device at that moment, and your email address. If you joined through a public link, as the portal's is, Apple shows us your name and email address only with feedback you send. We use this only to fix the app, and Apple does not let us share it. See Apple's TestFlight & Privacy notice. Our email, including hello@moozgy.com, is hosted on Apple's iCloud Mail, so messages you send us, and replies to affiliate applications, are stored there, as are affiliate applications emailed to us before the portal opened. 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. When a partner submits a YouTube video, our backend uses the YouTube API Services to read the video's public publish time and view, like and comment counts. We send YouTube the video's ID and nothing about you. If you connect a YouTube channel, we read what Section 10 lists through the YouTube API Services. 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. If you are an affiliate partner and set up payouts, Stripe runs your Stripe Connect account: it collects your identity, tax and bank details itself and acts as their controller, and we send it an internal reference to your partner account and the amount of each payout. See Stripe's privacy policy.

Apart from these providers, those listed in Section 9 for creators we contact, the platforms whose accounts you connect (Section 10), and the partners who see the referral details described in Section 1, 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.

Website analytics exist only as daily totals, which are combined into monthly totals as they age. They identify no one, and we keep them for as long as they are useful to us.

On a creator's code page, each day's visit keys are deleted shortly after that UTC day ends. The daily totals that replace them identify no one and are kept with the creator's programme records. The abuse counters described in Section 1 are deleted within two days of an address's last request.

Affiliate applications made in the portal are kept with your Moozgy account until we decide on them. If we decline yours, it is deleted on the day (UTC) six months after our decision: the name you gave, the platforms you listed, what you wrote and any note we wrote about it, together with our staff's log entry recording the decision. After that you can apply again. If we approve it, it stays with your partner record. You can delete the account, or ask us to delete an application, at any time. Applications emailed to us before the portal opened are kept for as long as we need to decide on them and, if you joined, to run the programme with you, or until you ask us to delete them. If you are a partner, your codes, your commission, payout and clawback records, your Stripe account ID and our staff's log of changes to your partner account are kept as long as tax and accounting law requires, including after you leave the programme or delete your Moozgy account. Deleting the account removes your application, your partner name and your access to the portal. If you subscribed with a partner's code, or named a creator who was credited, and then delete your account, the payments credited to that partner stay in their commission records with no link to your account.

Your answer to where you heard about Moozgy is kept with your account and deleted with it; the totals it was counted in identify no one. Your votes for subjects are kept the same way. To withdraw a vote without deleting your account, email us (Section 12). Videos partners submit are kept with their partner record for as long as the video can earn commission under our Affiliate Terms, and then as long as tax and accounting law requires us to keep the commission records based on them. A screenshot is kept with the video's record; once we have decided on the video, you can ask us to delete it. Plans in the planner are kept with your partner record. View counts we read from YouTube are refreshed or deleted within 30 days of reading them, as YouTube's rules require; our estimates based on them are kept.

What we hold about creators we contact is kept for the periods set out in Section 9. What we read from accounts you connect is kept for the periods set out in Section 10.

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 12).

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 12) 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. Product analytics in the app is off for anyone under 18 unless they turn it on in Settings. Votes for subjects (Section 1) are stored for every account, because they are something you choose to tell us, and are used only to count, in totals, which subjects people want next.

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 12) and we will delete it promptly.

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

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. Accounts you connect

If you apply to or take part in our affiliate programme, you can connect your YouTube, TikTok or Instagram account in the affiliate portal (/creators). This section explains what we read, why, who receives it, how long we keep it, and how to disconnect and have it deleted. Connecting is optional. You can always give us a video's details yourself, with a screenshot of your own statistics, or paste a YouTube video's link (Section 1). Only people aged 18 or over can use the portal.

We can only read, never act. We ask each platform for read-only access. Moozgy never posts, edits, deletes, comments, likes, replies, hides comments or sends messages on your account.

What we read

• YouTube. Moozgy uses YouTube API Services. With your permission we read your channel's ID, name, handle, and subscriber and video counts; the list of videos you uploaded, with each video's title, description, publish time and length and its view, like and comment counts; and, from YouTube Analytics, each video's views, likes, comments and shares per day. We also read the public comments on your videos, as explained under "Comments" below.
• TikTok. Your display name, username, and follower and video counts, and your public videos, with each one's link, posting time, title, caption and length, and view, like, comment and share counts. TikTok gives us no comment text.
• Instagram (professional accounts only). Your username, name, and follower and post counts, and your video posts and Reels, with each one's link, posting time, caption, and like and comment counts, plus their insights: views, reach, saves, shares, likes and comments. We read no comment text on Instagram.

We store a video's title (on Instagram, the start of its caption) and its hashtags. We read descriptions and full captions only to find hashtags and your creator code, and do not store them. If a platform returns more than we use, we discard it without storing it. We read nothing about the people who follow you or watch your videos, never your messages, and nothing from an account you have not connected. While you are connected, our backend updates each video's figures every hour for its first three days and then once a day until it is 30 days old. This is ordinary scheduled code, not AI.

Why we use it

To check that the account is yours and is the one named in your application; to show you your own videos and how they perform; and to estimate, from totals, how many more people than usual downloaded Moozgy, signed up and subscribed after each video, so that we can credit you and, where our Affiliate Terms provide for it, pay you commission. The estimate never decides that any particular person came from a video. Our staff see your figures when they review your application, your videos and your payouts. Our legal basis is the steps you ask us to take before entering into the affiliate contract, then that contract (GDPR Art. 6(1)(b)).

We also add up figures across creators, as totals, to learn which formats, hashtags and platforms bring people to Moozgy (legitimate interests, Art. 6(1)(f)). When two creators' videos come out close together, we use each video's views to share the estimate between them. We never show one creator's data to another creator.

Comments

On YouTube, each time we update a video's figures we read its public comments to count them and to count how many ask what the app is, where to get it or what it costs, or talk about its difficulty, the answer, how much they like it, or whether it is an ad. Our own code does this, by matching words; no AI is involved. The text, and the names and channels of the people who wrote it, are used only at that moment. We never store comment text or who wrote a comment. We keep only those counts, for 30 days. We never reply to, like, hide or report a comment. If you comment on the YouTube video of a creator who has connected their channel, this is everything we do with your comment; our legal basis is legitimate interests (Art. 6(1)(f)) in measuring interest in Moozgy, and you can contact us about it (Section 12). Because we keep nothing that identifies you, we cannot find your comment again afterwards. On TikTok and Instagram we read only the number of comments.

AI

We do not send anything we read from a connected account to an AI service. We will update this section before we do. AI never decides your commission: that comes from our estimate and our staff's review under the Affiliate Terms.

Who receives it

Supabase stores it and runs the code that reads it; Vercel, our website host, carries the sign-in round trip with each platform. Each platform knows that you connected Moozgy and receives our requests for your data, under its own privacy policy: Google's Privacy Policy for YouTube, TikTok's Privacy Policy, and Instagram's Privacy Policy, from Meta. We do not sell this data, use it for advertising, or let anyone else serve ads with it. The affiliate portal stores nothing on your device apart from the sign-in cookies in Section 3.

Moozgy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we keep it safe

The access tokens each platform gives us are stored encrypted in our backend's vault, never in an ordinary table, a log or anything sent to a browser, and only our backend uses them, to read what this section lists. Everything we read is visible only to you and to our staff who review creators and payouts.

How long we keep it

• While you are connected: your profile details for as long as you stay connected, refreshed every day; a video's statistics at most until 12 months after it was posted. Titles, hashtags, comment counts and YouTube's public view, like and comment counts are deleted 30 days after we read them. At least every 30 days we check that you still allow our access to YouTube.
• When you disconnect, or leave the programme, or close your Moozgy account, or we decline your application, or you connect an account but have not applied 7 days later: we delete the access tokens at once and, for YouTube and TikTok, withdraw our access with the platform. Instagram gives us no way to withdraw it, so remove Moozgy in Instagram's own settings as well; the portal reminds you. We delete everything else we read through that connection within 7 days.
• If you remove Moozgy in the platform's own settings instead, we delete it within 30 days.
• What we keep afterwards: the records of commission credited to you, including how we calculated it, for as long as tax and accounting law requires (Section 6); and the videos you submitted for credit, including those you chose from a connected account: their link, posting time and review status, as Sections 1 and 6 describe. For a YouTube video, we keep reading its public view count with our own YouTube API key, as we do for any YouTube link a partner submits, until the video is 30 days old, and delete each reading 30 days after we take it.

How to disconnect and delete your data

1. Sign in at moozgy.com/creators, open Settings, and choose Disconnect next to the account.
2. Or remove Moozgy in the platform's own settings. For YouTube, that is your Google Account's security settings page, security.google.com/settings/security/permissions. On TikTok and Instagram, it is the list of apps and websites connected to your account.
3. Or email hello@moozgy.com from the email address on your Moozgy account and ask us to delete what we read from your connected accounts. We delete it within 7 days and confirm by reply. Deleting it from Moozgy does not delete anything from the platform itself.

Questions or complaints about this section: hello@moozgy.com (Section 12). Your rights in Section 7 apply to this data. We will update this section before we add any other platform.

11. 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 and subject votes on your device are stored in protected, backup-excluded files, payments are handled by Apple and Stripe (PCI DSS Level 1), and the website stores nothing about you beyond the earlier sign-up sheet, the website events, website analytics and creator code page visits described in Section 1 and, if you use the affiliate portal, what Sections 1 and 10 list for it; the portal's sign-in cookies are sent only over HTTPS, and the access tokens for accounts you connect are stored encrypted (Section 10). 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.

12. Contact

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

13. 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.