Privacy Policy
Last updated: September 2026Identity:CreatorOS (“we”, “us”) is operated by its founder as a solo developer. This policy describes what we collect, what we don’t, and how we keep your data safe.
What we collect
- Account data: email address, password hash (Supabase Auth).
- Project data: the ideas, Scripts, and metadata you create. We never train on it or sell it.
- Voice notes: Telegram voice is transcribed through Groq Whisper; we discard the audio and keep the transcript on your account.
- Usage telemetry (app only): Sentry (errors) and PostHog (anonymised events). No PII beyond
user_id. - Signal: “Something’s off” / “I want this” is emailed to the founder via Resend. We do not store the note or stills in our database.
- Marketplace receipts: when a brand records a UPI payment we store amount (minor units), UPI reference, timestamps, and a receipt token. We do not collect card numbers, UPI PINs, or bank passwords. Identity does not process the UPI transfer itself.
What we do NOT collect
No Google Analytics, Facebook pixel, or ad-tech on this website. We do not sell your data. We do not train any model on your private content. We do not invoice a platform fee today, so we collect no GST billing profile.
Google user data (YouTube)
Connecting a YouTube channel is optional. Identity:CreatorOS only asks for Google authorisation when you tap Connect YouTube in Settings → Platforms, and Google’s own consent screen shows you the exact scopes before anything is granted.
| Scope | Why we request it | What we do with it |
|---|---|---|
https://www.googleapis.com/auth/youtube.upload |
Publish a finished video to your channel | Uploads the video file plus the title, description, tags, and privacy setting you entered in the app. Nothing is uploaded until you tap Publish. |
https://www.googleapis.com/auth/youtube.force-ssl |
Attach a caption track to the video you just published, and read back the public stats of your own channel | Posts a WebVTT caption track built from your Script transcript, and reads view / like / comment counts for your own videos so the Oracle screen can show your performance. We never modify or delete anything we did not create on your behalf. |
Limited Use
Identity:CreatorOS’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, this means:
- Google user data is used only to provide the publishing and analytics features described above.
- We do not sell, rent, or transfer Google user data to third parties, data brokers, advertisers, or information resellers.
- We do not use Google user data for advertising, ad targeting, or credit-scoring purposes.
- We do not use Google user data to train, fine-tune, or evaluate any generalised AI or ML model. Your video, its metadata, and its statistics are never sent to Anthropic, Groq, Replicate, or any other AI sub-processor.
- No human at Identity:CreatorOS reads your Google user data, except where you have given explicit consent for a specific support ticket, where it is necessary for security investigations or to comply with applicable law, or where the data has been aggregated and de-identified.
Storage, retention, and revoking access
Your Google OAuth access and refresh tokens are stored server-side in our Supabase Postgres database (row platform_connections), never in the app bundle and never in browser storage. They are exchanged and used only from server-side Supabase Edge Functions over TLS.
You can disconnect at any time from Settings → Platforms → Disconnect, which deletes the stored tokens, or from Google Account → Third-party apps, which revokes the grant at Google. Deleting your Identity account deletes the tokens along with everything else. Video statistics cached for the Oracle screen are removed within 30 days of disconnecting.
Your use of YouTube through Identity is also governed by the YouTube Terms of Service and the Google Privacy Policy.
Data sharing
| Recipient | Data shared | Purpose |
|---|---|---|
| YouTube / Google | Video, title, description, tags, privacy | Publish, only when you tap Publish |
| Supabase | Account and project data | Auth and storage |
| Cloudflare | Files, this website | Delivery and hosting |
| Anthropic | Scripts, captions you send to Intelligence | Generation |
| Resend | Signal notes and Deal emails | Transactional mail |
Sub-processors
| Provider | Purpose |
|---|---|
| Supabase | Auth + Postgres + Edge Functions |
| Cloudflare | Pages / R2 / Stream |
| Anthropic | LLM completions |
| Groq | Audio transcription |
| Brave Search | Web research lookups |
| Auphonic | Audio repair |
| Replicate | Thumbnail generation |
| Hugging Face | Thumbnail readability scoring |
| Sentry | App crash reporting |
| PostHog | Anonymous app analytics |
| Resend | Transactional email |
How we protect your data
Sensitive data — Google OAuth tokens, account credentials, your private Scripts and recordings — is protected by the following mechanisms:
| Control | Mechanism |
|---|---|
| Encryption in transit | TLS 1.2+ (HTTPS) on every connection between the app, our Supabase backend, Cloudflare, and every third-party API. No plaintext endpoints exist. |
| Encryption at rest | AES-256 on the Postgres database, on Cloudflare R2 object storage, and on database backups. |
| Credential handling | Passwords are never stored by us — Supabase Auth stores a bcrypt hash. OAuth tokens are stored server-side only and are never written to logs, crash reports, or analytics events. |
| Access control | PostgreSQL Row Level Security is enabled on every user-scoped table, so a signed-in user's token can only ever read or write their own rows. Third-party API keys live only in server-side Edge Function secrets and are never shipped in the mobile app. |
| Least privilege | Only the founder has production database access, protected by a unique password and 2-factor authentication. There are no shared accounts and no standing third-party access. |
| Scope minimisation | We request the narrowest OAuth scopes that make the feature work, and only at the moment you enable that feature. |
| Logging hygiene | Error reports (Sentry) and product analytics (PostHog) carry no video content, no transcripts, no tokens, and no PII beyond an opaque user_id. |
| Data minimisation and retention | We store only what a feature needs. Voice audio is discarded after transcription. Deleting your account cascades across every table — there is no soft delete and no orphaned copy. |
| Vulnerability response | Dependencies are patched on release cadence. Report a security issue to devanddeadlifts@gmail.com; we aim to acknowledge within 72 hours and will notify affected users of any confirmed breach. |
Website measurement
This marketing site has no analytics pixel. The funnel is unmeasured on the web on purpose, until we pick a first-party counter and update this paragraph.
Your rights
Export or delete your account from Settings → Account. Deletion cascades. Details: Account & Data Deletion.
Privacy questions: devanddeadlifts@gmail.com.