Privacy and GDPR policy

1. What we process, and why

Pre-registration list: email and language (Romanian, English, German, Italian, French or Spanish). Basis: steps before a contract, and the consent you give by submitting the form. Purpose: to tell you when we open on 15 October 2026. You can ask to be removed via the contact address.

Account: email, auth identifier, and password hash, held by the auth provider. Basis: contract. Purpose: signing in.

Studio: chat messages, uploaded files (up to 50, 100 MB each), posts, schedules, Team clients (name only), the selected client, and leads (message, transcript, name, phone, email, status). Basis: contract. Purpose: publishing, scheduling, history, and the lead list.

Networks: identifiers and names of connected accounts, plus the access tokens needed to publish and to read the inbox. We read connected-account messages and comments to detect interest, reply (qualification in private; a public comment only invites a private message), and store a qualified lead after express YES / DA consent to the Terms and conditions, sent in chat. We do not put phone, email, or salary in public comments. Basis: contract. Purpose: the action you asked for.

The person who writes to the page: if they reply YES, we process the message and the name, phone, and email they leave, so the studio account holder can contact them. Basis: the consent given by YES. They can ask us to erase it via the contact address. Without YES we do not collect contact details.

Voice: the browser turns speech into text. We store the message text if you send it. We do not store audio.

Payments: Stripe processes the card. We keep the Stripe customer id, payment status, amount, and date, so we know the subscription is active and so we can invoice. We do not store the full card number. Basis: contract and legal accounting duty.

Contact form: name, email, and message. Basis: legitimate interest or pre-contract steps, so we can reply.

2. Who receives data

Hosting (Vercel), database and authentication (Supabase), payments (Stripe), transactional email (Resend), an AI-model provider that receives the chat message in order to draft text, and a publishing provider that sends the confirmed post to the network you connected.

Networks you connect receive the content you confirm. They have their own rules.

A qualified lead (name, phone, email, transcript) is visible in the studio to the account holder, on the selected client. We do not sell it.

We disclose data when the law requires it, for example an invoice or an authority request.

3. How long

A waitlist email stays until launch and the announcement, or until you ask us to delete it, whichever comes first.

Studio data is deleted when you delete the account: the user, conversations, live posts, stored files, and leads. Encrypted database backups rotate on their own and are not used for day-to-day processing.

Accounting and invoice records are kept for the period required by Romanian tax law, even if the studio was deleted.

4. Your rights

You can ask for access, rectification, erasure, restriction, objection, and portability, and you can withdraw consent for the pre-registration list. If you wrote to a page and replied YES in chat, you can withdraw that consent and ask us to erase the lead. Deleting the account in the studio is the direct way to erase studio data.

You can complain to the ANSPDCP, the Romanian data-protection authority.

Send requests to opozacolor@gmail.com or through the contact page, from the account email. We reply within the GDPR period, usually one month.

5. Deleting the account

Signed in: account menu → Delete account → confirm. Networks are disconnected, then the user and live data are deleted.

Signed out: a message from the contact page, same email, asking for deletion. We check that you are the account holder before we delete.

Deletion does not by itself cancel a fee for a period that already started, and it does not delete invoices the law requires us to keep.