Platform
Data handling
Last updated 6 October 2026
The specifics behind the Privacy Policy: where each kind of data sits, how it is protected, and who can read it. Platform is run by Ecodia Pty Ltd (ABN 89 693 123 278).
1. The databases and the AI stay in Australia
Your information is kept in our databases with Supabase in Sydney, and Platform runs on Vercel in Sydney. The engine that runs each AI is operated by Ecodia on Google Cloud in Sydney, and every call it makes to the AI model goes to Anthropic’s Claude on Amazon Web Services in Sydney (AWS Bedrock), using Australian model endpoints only. What does leave Australia, such as error reports and payments, is listed in the Privacy Policy.
2. What the AI receives
For each job, the engine sends the model your request and the context the job needs, such as your task, a document you gave your AI, or your site’s structure. It never receives your saved keys or passwords. Platform asks your permission before your information is sent to the AI for the first time. Ecodia does not use your information to train AI models.
3. Your keys are encrypted and we cannot read them
Each secret you save is encrypted with AES-256-GCM under a key unique to your site. The encrypted columns are blocked at the database itself from your browser and from every other account, so the plain values are not reachable from the app at all. Our server decrypts a single secret only at the instant it is needed to run a job you asked for, and writes that access to an audit log.
4. Your website lives on infrastructure you own
A site built with Platform runs on your own code repository, your own host, and your own database. Ecodia keeps a pointer to it and a deploy key, held in your encrypted vault, so your AI can ship your changes. We do not hold your website’s own data, and you can disconnect and keep all of it.
5. Every AI change to a site passes a safety gate
Before any AI-written change to a site goes live it is checked automatically: it must type-check and build, and it is blocked from importing secrets or reading environment variables. A change that fails the gate is never applied.
6. Who can read what
| Data | Where it is stored | Who can read it |
|---|---|---|
| Your account and sign-in | Our sign-in service and database (Supabase, Sydney) | You; your organisation sees your name and email |
| Your organisation's work: tasks, docs, files, decisions, team chats | Our database (Supabase, Sydney) | Members by their role; guests only what is addressed to them |
| You: memory, rules, people, errands, connections | Our database (Supabase, Sydney) | You and your AI |
| Your chats with your own AI | Our database (Supabase, Sydney); recent copies with the engine (Google Cloud, Sydney) | You only. Owners and admins see AI usage counts, never the chat |
| Saved keys and passwords | Your vault, encrypted (Supabase, Sydney) | Nobody as plain text, except our server at the moment of use |
| Error reports | Sentry (United States), up to 90 days | Ecodia, to fix faults. Not linked to your name or email |
| Payments | Stripe; Apple, Google and RevenueCat for subscriptions bought in the app | Your organisation's owner and Ecodia. Card details only Stripe |
| Your website's own data | Infrastructure you own | You |
7. Backups
Backups of our database are kept for up to 14 days, then deleted, so deleted information has left our backups within 14 days.
8. Deleting data
Delete a site and everything attached to it is removed with it. Delete your account and your data is removed from our database straight away; Delete your account explains how, and what is kept for a time. To request a copy or a deletion, email code@ecodia.au.