Privacy Policy
Last updated August 24, 2026
Plain version: we collect what we need to run the platform, we store it on Google Cloud and Supabase, everything is encrypted, and we use what happens on the platform to make Platyps better.
What we collect
From you: name, email, password (hashed), billing details handled by our payment provider (we never see your full card number), project content (brainstorms, specifications, wireframes, code you upload, comments), credentials you add in the integrations tab, and anything you email us.
Automatically: what you use, credits spent, sessions, errors, IP address, browser, device, timestamps, and cookies needed to keep you logged in.
From others: if you sign in with Google or GitHub we get your name, email and profile picture. If you connect a repository, we get the repository data you authorise.
What we do with it
Run the service, charge you and meter credits, support you, detect abuse, and improve Platyps, including training and fine-tuning our own AI models.
About model training
We use content from the platform, brainstorms, specifications, wireframes, code, and how you interact with them to train and improve our own models. This is how Platyps gets better at understanding what you're building, catching drift, and producing guides your agent can actually work from.
Before anything is used for training, we strip out credentials, API keys and environment variables. Those are never included, ever.
We don't sell your data, and we don't hand your project content to anyone else to train their models.
If you'd rather your content wasn't used this way, email hello@platyps.comand we'll exclude your account. We're building a toggle for this in settings.
Who else touches your data
Google Cloud Platform for hosting, storage and sandbox compute. Supabase for database and authentication. AI model providers to generate specifications, wireframes and analysis. Our payment provider to take payment. Analytics and email tools to run the product. Full list on our sub-processors page. We may also disclose data if the law requires it, or if Platyps is acquired, in which case we'll tell you.
Where it lives
Google Cloud and Supabase, in [REGION — fill this in, it's the one detail buyers ask about]. Some providers process data elsewhere, including the United States.
Security
Everything is encrypted, in transit and at rest. Credentials are encrypted separately and isolated per environment, never sent to your coding agent, never visible in a shared preview. Sandboxes are isolated from each other. No system is perfect, so if something happens that affects you, we'll tell you. More on Security.
How long we keep it
Project content while your account is active, then 30 days after closure. Billing records as long as accounting rules require. Logs for 90 days. Backups up to 35 days after deletion. Content already used in training can't be removed from a trained model.
Your choices
Ask us for a copy of your data, corrections, deletion or export at hello@platyps.comand we'll sort it within 30 days. Most of it you can do yourself from settings. You can opt out of model training any time.
Under 18
Anyone can build on Platyps. If you're under 18, a parent or guardian should agree to this policy and stay across what you're doing here. Parents can email hello@platyps.comto see or delete a child's data, or opt them out of model training.