Privacy Policy
Last updated November 16, 2026
This Privacy Policy describes how Massimo Sequeira, trading as UGC OS ("we", "us") collects, uses, stores, and shares information when you use UGC OS (the "Service"). We are based in Johannesburg, South Africa, and we are the responsible party (or controller) for that information.
1. What We Collect
Information You Provide
- Account data: your email address and name, and either a password (stored hashed by Supabase Auth) or, if you sign in with Google, the details Google shares with us (see section 2). You can also set a display name.
- API keys: your kie.ai key and, if you add them, your Higgsfield and ScrapeCreators keys. They are stored only in your browser's local storage on each device where you use the Service, never in our database, and each is sent over TLS to its own provider when you use it. Your Higgsfield key passes through our servers on the way, because Higgsfield does not accept calls from browsers; it is not stored there. If you switch on Generate on Your Credits (in UGC OS → MCP), we keep an encrypted copy of your keys on our servers so an AI app you connect to UGC OS can generate for you; switching it off deletes that copy. To remove a key, clear it in Settings or clear your browser storage.
- Inputs: prompts, scripts, products, character profiles, reference images, audio, and ads you upload or link for analysis.
- Outputs: generated images, videos, voiceovers, music, scripts, and analyses produced by the Service on your behalf.
Information We Get From Others
- Membership: access to the Service comes with membership of our community on Skool. We add your email address and name from the community's member list to our access list ourselves, so that your access can be switched on and off.
- Google: if you sign in with Google, the details in section 2.
Information Collected Automatically
- Authentication session tokens (managed by Supabase).
- Server logs (IP, user-agent, timestamps) generated by our hosting providers.
- Local browser storage (localStorage, IndexedDB) used to cache banks, settings, and asset blobs on your device.
- Usage: which tools you open and how long you spend in each (counted only while you are active in the tab), how many things you make with each tool per day, and how many seconds of audio you transcribe per day.
- Error reports: when something fails, the error message and technical details (the tool you were in, the page, your browser and screen size, the app version, the last few tools you opened, and the app's last few technical log lines). Your API keys are stripped out and your media is never included. Error reports are on by default and can be switched off in Settings → General.
2. Google User Data
If you choose Continue with Google, we use Google Sign-In only to create your account and sign you in.
- What we receive: your Google account's name, email address, and profile picture, and the identifier Google gives your account. These come from the only Google scopes we request:
openid,email, andprofile. We never see your Google password, and we do not request access to Gmail, Google Drive, Calendar, Contacts, YouTube, or any other Google data. - How we use it: to create your account and sign you in, to check your email address against the community access list, and to show your name in the app. We do not use it for advertising, and we do not send it to kie.ai or any AI model provider.
- How we store it: your email address, name, and a link to your profile picture are stored with your account by Supabase, our authentication and database provider, encrypted in transit and protected by access controls on every table.
- Who we share it with: no one, except Supabase, which stores it on our behalf, and an AI app you choose to connect to UGC OS, which can see your name and email address. We do not sell or rent Google user data.
- How long we keep it, and deleting it: for as long as your account exists. To delete your account and this data, email massimo@massimoseq.com. You can remove UGC OS's access to your Google account at any time at myaccount.google.com/connections; that stops future Google sign-ins but does not delete your UGC OS account.
UGC OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
3. How We Use Your Information
- To provide, operate, and improve the Service.
- To authenticate you and enforce the community access list.
- To route AI requests on your behalf through kie.ai and the underlying model providers.
- To store your banks, history, and assets so they persist across sessions and devices.
- To find and fix bugs, using error reports and usage data.
- To respond to support requests and enforce our Terms and Acceptable Use Policy.
- To prevent fraud and abuse, comply with the law, and establish, exercise, or defend legal claims.
We do not use your inputs or outputs to train AI models, and we do not sell your personal information or share it for cross-context behavioural advertising. The AI providers in section 5 handle what you send them under their own terms, which may differ.
Legal Bases
Where the law asks for a legal basis (such as the GDPR and POPIA), we rely on:
- Our contract with you: running your account, checking your membership, storing your work, and sending your requests to the AI providers.
- Our legitimate interests: keeping the Service secure, finding and fixing bugs, and understanding how it is used (usage data and error reports). You can switch error reports off and object to the rest by emailing us.
- Your consent: where you switch something on yourself, such as Generate on Your Credits or connecting an AI app. You can withdraw it at any time by switching it off.
- The law: where we must keep or hand over information to comply with it.
We need your email address to give you an account. Everything else you add is your choice, though the tools can't work without the inputs you give them.
Who Can See Your Content
Your library is private to your account, and no other member can see it. The operator can open an account's data (profile, usage, error reports, and stored content) only when needed to give support, fix a problem, enforce our Terms, or comply with the law.
4. Faces, Voices & Sensitive Information
- Photos and recordings of people that you upload (for example to Characters, B-Roll, or Playground) are used only to make what you ask for. When Characters reads a reference photo, the photo is sent to an AI model (through kie.ai), which writes a text description of how the person looks (such as apparent age, gender, ethnicity, hair, build, and clothing). That description is a guess from the picture, and it is saved to your library so you can edit it. We do not create, store, or use faceprints, voiceprints, or any other biometric identifier, and we never use your uploads to identify anyone.
- Only upload a real person's face or voice with their consent (see our Acceptable Use Policy). You are responsible for having it, and for any notice the law requires you to give them.
- Please don't put sensitive personal information (such as health information, ID documents, or financial account details) about yourself or anyone else into prompts or uploads. The Service doesn't need it.
5. Subprocessors and Data Sharing
We do not sell your personal data. We share data with the following service providers solely to operate the Service:
- Supabase: authentication and Postgres database (account, profile, banks, history rows).
- Cloudflare R2: object storage for generated images, videos, audio.
- Vercel: application hosting and server functions (signed asset links, the Higgsfield relay, the media proxy, transcription, and the AI connector).
- Google: sign-in, if you choose Continue with Google (see section 2), and the app's typefaces, which load from Google Fonts' servers; like any web server, those receive your IP address and browser details when the page loads.
- kie.ai: unified API gateway for AI model calls. Your prompts, reference images, and any other input data you submit for generation are sent from your browser to kie.ai. Reference files are uploaded to kie.ai's file host, which keeps them for a short time (three days, by its own account).
- Downstream AI providers via kie.ai: including OpenAI, Google (Gemini), DeepSeek, Suno, and others. Your inputs may be processed by these providers to produce outputs. Each provider has its own privacy practices; refer to theirs for details.
- Higgsfield: image generation with its Soul models, if you add a Higgsfield key. Your prompts and reference images are sent to Higgsfield through our servers.
- ScrapeCreators: Ad Spy's searches of public ad libraries and social posts, on your own ScrapeCreators key. Your search terms are sent from your browser, or from our servers when an AI app you connected searches for you.
- Groq: transcripts of ads you analyze. The ad's audio is sent to Groq through our servers.
- Skool: the platform the community runs on and memberships are sold on. We do not send it your content.
- Ad platforms' media servers: Ad Spy, the Swipe File, and announcements show thumbnails and videos from TikTok's, Meta's, Instagram's, and YouTube's servers. When your browser loads one, that platform receives your IP address and browser details, as it would on any web page that shows its media.
- AI apps you connect: if you connect an AI app or agent to UGC OS (such as Claude, ChatGPT, Codex, Cursor, or VS Code), you approve the connection first. That app can then read and change your library (products, characters, scripts, saved ads, and what you have made) and see your name and email address, and its maker handles what it reads under its own terms. You can disconnect it at any time.
We may also share information:
- When the law, a court order, or a government request requires it, or to protect the rights, safety, or property of our members, the public, or us.
- With a buyer or successor if the Service is sold, merged, or reorganised, under this policy's protections.
- With anyone else when you ask us to or agree to it.
6. Retention
- Account and profile data: retained while your account is active and for a reasonable period after deletion to comply with legal obligations.
- If your membership ends, your account is locked, not deleted, and your content is kept so it is there if you come back. Email us at any time to have your account and content deleted.
- Generate on Your Credits: the encrypted copy of your keys is kept until you switch it off.
- Generated assets: retained in Cloudflare R2 until you delete them or your account is closed.
- History (images, videos, voiceovers, music, scripts, analyses): kept until you delete it or your account is closed.
- Usage data and error reports: retained while your account is active.
- Server logs: retained for a limited period as determined by our hosting providers.
- Deleted data may stay in backups for a limited period before it is overwritten, and we may keep information longer where the law requires it or to resolve disputes and enforce our Terms.
7. Your Rights
Depending on your jurisdiction (South Africa's Protection of Personal Information Act (POPIA), the GDPR, UK GDPR, CCPA/CPRA, and similar laws), you may have the right to access, correct, delete, port, or restrict processing of your personal data, and to object to processing or withdraw consent. To exercise these rights, email massimo@massimoseq.com. We may need to verify your identity first, and we will respond within the time the law requires. You also have the right to complain to your local data-protection authority (in South Africa, the Information Regulator, at inforegulator.org.za), and we will never treat you differently for exercising these rights.
8. Cookies & Local Storage
We use first-party browser storage (localStorage, IndexedDB) to keep the app responsive and to cache your banks and assets locally. We do not use third-party advertising cookies or third-party analytics trackers. Authentication uses Supabase-managed cookies / tokens. The app's typefaces and some ad thumbnails and videos load from other companies' servers (see section 5). Because we don't track you across other sites, we don't change anything in response to "Do Not Track" signals.
9. Security
We use industry-standard measures including TLS in transit, scoped presigned URLs for asset access (5-minute lifetime, per-user prefix), Row-Level Security on all database tables, and a separate JWT verification step on signed-URL minting. No system is perfectly secure, and we cannot guarantee the security of your information; you use the Service at your own risk. If a breach affects your personal information, we will tell you and the authorities where the law requires.
Your API keys are kept out of our database: they live in your browser's local storage and go to each provider over TLS at request time (your Higgsfield key through our servers, unstored), so a compromise of our database cannot reveal them. The one exception is Generate on Your Credits, which you switch on yourself: it stores your keys encrypted with a secret that is not kept in our database, and switching it off deletes them.
10. International Transfers
We are based in South Africa, and the providers in section 5 store and process data in the United States, the European Union, and other countries. So your information leaves your own country, South Africa included, when you use the Service, and some of those countries may not protect personal information to the same standard as yours. For these transfers we rely on our providers' data-protection terms (which include standard contractual clauses where the provider offers them) and on the transfer being necessary to provide the Service you asked for.
11. Children
The Service is not directed to anyone under 18. We do not knowingly collect data from children. If you believe a child has given us information, email us and we will delete it.
12. People in Public Ads and Posts
Ad Spy shows ads and posts that are already public on ad libraries and social platforms. They can include the names, handles, faces, and voices of the people who made them or appear in them. Members can save a public ad's or account's details and thumbnail to their own library and analyze it. If you appear in something shown or saved here and want it removed, or have any other request about your information, email massimo@massimoseq.com.
13. Changes
We will update this Privacy Policy as the Service evolves, post the new version here with a new date, and announce material changes in the app.
14. Contact
The responsible party and Information Officer is Massimo Sequeira, Johannesburg, South Africa. Privacy questions or requests: massimo@massimoseq.com.
