Last updated 23 August 2026
Zeea plans and writes social posts for design studios. Doing that means reading a studio’s website, holding what it concludes about their brand, and sending both to language-model providers. This page says exactly what is collected, where it goes and how long it stays.
Panoptikon State SRL, registered at Sos. Stefan cel Mare 14, Bl. 19, Sc. B, Et. 9, Ap. 57, Sector 2, 020141, Bucuresti, Romania under company number ROONRC.J2014001094409, is the controller of the personal data described here. Write to hello@zeea.ai about anything on this page.
Your email address, and your name and profile picture where your sign-in provider supplies them. Zeea signs you in with Google or with a link sent to your email; there is no password, and none is ever stored.
Brands, campaigns, the posts written for them, the photographs uploaded to illustrate them, and the brand library — the voice, values, audience and project descriptions Zeea proposes and you keep. Where you ask Zeea to read a website, the text of the pages it read is processed and the conclusions drawn from it are stored.
Handled entirely by Paddle, who are the merchant of record for every sale. Zeea never sees or stores card details. What reaches this application is which plan was bought, whether the subscription is active, and an identifier for it.
Ordinary server logs, and a record of each generation run against your workspace’s credit balance — what was run, when, by which member, and what it cost. This is what the credit ledger shows you, and it is how a bill is explained.
Zeea does not sell personal data, does not share it for advertising, and does not build profiles for marketing.
These are the only third parties that receive data, and what each receives. All of them act on instructions under a processing agreement.
| Who | What they receive | Where |
|---|---|---|
| Google Cloud & Firebase | Everything — hosting, database, file storage and sign-in | United States |
| Anthropic | Brand material and campaign text, to write and plan posts | United States |
| OpenAI | The same, when you choose one of their models | United States |
| Google (Gemini) | The same, when you choose one of their models | United States |
| Buffer | Finished posts and their images, to publish them on your behalf | United States |
| Paddle | Your billing details, taken directly by them | United Kingdom & United States |
Which model provider receives your text depends on the model chosen for a given run, which is shown in the app before the run starts. Zeea does not train any model on your content. What each provider does with data sent through their API is governed by their own terms, and those are worth reading if it matters to you.
The providers above are largely in the United States, so your data is transferred there. Those transfers rely on the European Commission’s Standard Contractual Clauses, or on an adequacy decision where one covers the provider.
You may ask for a copy of your data, ask for it to be corrected or deleted, ask us to restrict or stop processing it, and ask for it in a portable form. The portable copy needs no asking: Settings → Workspaces → Export this workspace gives you every brand, campaign and post as one file, at any hour, without us in the middle. For anything else, write to hello@zeea.ai and you will have an answer within 30 days.
If you think your data has been handled wrongly you may complain to the data protection authority where you live, or to the one in Romania.
Zeea stores what is needed to keep you signed in and to remember your choice of light or dark. There is no advertising, tracking or analytics cookie, and nothing follows you to other sites. If that changes, this page changes with it and you will be asked first where consent is required.
Traffic is encrypted in transit and data is encrypted at rest. Access to a workspace is limited to the people invited to it, per brand. Access to production is limited to those who operate the service, and administrative actions are logged.
When this page changes materially, we will say so by email before the change takes effect. The date at the top is always the date of the version you are reading.