Privacy Policy
Last updated 1 November 2026
Who we are
The controller of your personal data in AI Render Studio (app.3dstudio.co, the ChatGPT and Claude connectors and the API) is 3DST OÜ, an Estonian company, registry code 12454634, Pikk 67-3, Tallinn, Estonia. Questions about your data: hello@3dstudio.co. This policy covers the app only. The 3dstudio.co website and our design services have their own privacy policy. A shorter summary is in the docs; this policy applies if they differ.
What we collect and why
| What | Why | Legal basis (GDPR) |
|---|---|---|
| Email address, and your name and profile from Google if you sign in with Google. Plan, credit balance and credit history. | Create and run your account, sign you in, send sign-in links and receipts. | Contract (Art. 6(1)(b)) |
| The pictures you upload, the renders, fixes, videos and review links made from them, your notes and settings, and comments on review links. | Make the renders you ask for, keep your library, let you share it. | Contract |
| Payment records: Stripe customer and subscription ids, what you bought, amount, currency, billing country. We do not receive your card number. | Give you credits, handle refunds, keep accounts. | Contract, and legal obligation for accounting (Art. 6(1)(c)) |
| Technical data: IP address, browser, country from your connection, a language cookie, a sign-in session cookie, server logs. | Deliver the app, keep it secure, set country prices. | Legitimate interests (Art. 6(1)(f)) |
| Sign-up checks: an anonymous device id in a cookie, a hashed IP address, your email in normalized form, your country. | Stop people making many accounts to collect free renders. | Legitimate interests (fraud and abuse prevention) |
| Product events: which features you used, with an internal user id, and where you came from (campaign tags, referring site, landing page). | Fix problems, count usage, understand which pages lead to sign-ups. | Legitimate interests |
| Messages to us: feedback notes, testimonials, support chat and email. | Answer you and improve the app. | Legitimate interests, and consent for a testimonial we publish |
| Analytics and advertising data from Google Analytics, Google Ads and Meta, including Meta server-side events with a hashed email and your IP address. | Measure which ads and pages bring users, and show our ads to the right people. | Consent (Art. 6(1)(a)). Nothing loads in countries that require a yes until you accept. |
We do not sell personal data. We do not use your pictures to advertise to you or anyone else.
Who processes your data
We use these providers. Each one acts for us under its own data processing terms, except where noted.
| Provider | What for | What it receives |
|---|---|---|
| Supabase | Login, database, private file storage | Account data, credit history, render records, your uploaded pictures and finished renders. Project region: EU (Frankfurt, Germany). |
| fal.ai | AI image and video models that make the renders | The picture you upload, your look settings and your notes, for each render, fix, change, relight or video. Renders are processed by fal.ai under its terms. How long fal.ai keeps files, and what it may do with data derived from them, is set by those terms, not by us. |
| Stripe | Payments. Stripe is the merchant of record and handles payment data, sales tax and VAT. | Your email, payment details and billing address, entered on Stripe's checkout. Stripe is an independent controller for its own payment and compliance duties. |
| Vercel | Hosting and server logs | Every request to the app, including IP address and browser. |
| Resend | Sending email: sign-in links, receipts, account and lifecycle email | Your email address and the message. |
| Crisp | Help chat. Loads only when you open it. | What you type, your email if you give it, and technical data from your browser. |
| Sign in with Google, Google Analytics 4, Google Ads | Sign-in: your Google email and profile. Analytics and ads tags load only after consent where required. | |
| Meta | Meta Pixel and server-side conversion events | Page and purchase events, a hashed email and your IP address, only after consent where required. |
| Telegram and Pushover | Private alerts to our team: a sale, an error, a note you sent us | Mostly internal ids and amounts. An alert can include your email address when you send us feedback or when an account needs our attention. |
| ChatGPT and Claude (OpenAI, Anthropic) | Only if you connect the app to them | The assistant sends us your picture and instruction and gets back the render link and your credit balance. What they keep is covered by their own terms. |
Transfers outside the EEA
Several providers above, including fal.ai, Vercel, Stripe, Resend, Crisp, Google, Meta, Telegram and Pushover, process data in the United States or other countries outside the European Economic Area. Where they do, the transfer relies on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's standard contractual clauses. You can ask us for a copy of the safeguards.
How long we keep data
- Renders and uploads: until you delete them or your account. When you delete a render it disappears from your account at once and its share link stops working. The stored files are removed by an automatic clean-up that runs regularly. Backups at our providers may hold a copy a little longer.
- Review links: for the time you chose (7, 30 or 90 days, or until you delete them).
- Account and credits: while your account exists. Deleting the account removes your login, profile, credit history and team membership.
- Payment records: Stripe keeps the customer record and invoices as tax law requires. They are not deleted when you delete your account. Our own accounting records are kept for the period Estonian law requires.
- Sign-up checks: kept after account deletion so that deleting and signing up again does not give free renders again. At deletion your email is replaced with a one-way hash and the country is removed. The device id and hashed IP address remain. We do not have an automatic expiry for them yet.
- Product event logs: are tied to an internal user id, not your email, and have no automatic expiry yet. We delete or anonymize them on request.
- Sign-in tokens: connector access tokens last 1 hour and refresh tokens 30 days. API keys and tokens are stored only as hashes.
Your rights and how to use them
You can ask us for access to your data, a copy, correction, deletion, restriction or to object to processing based on legitimate interests. Where processing relies on consent you can withdraw it at any time, with no effect on what came before. You have the right to move your data to another service.
- Delete your account and data yourself: sign in, open Account, and use Delete my account and data. It cancels your subscription, removes your files, renders, folders, review links, API keys, connected apps and login. It cannot be undone, and unused credits are lost.
- Delete a single render: choose Delete on it in My renders.
- Anything else: write to hello@3dstudio.co from your account email. We answer within one month.
- Complaints: you can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee), or to the authority in the country where you live.
Giving us your email and your pictures is needed to use the app. We do not make decisions about you by automated means that have legal or similarly significant effects.
Cookies and consent
- Always on (needed to run the app): a sign-in session, your language, and an anonymous device id (kept up to 2 years) that limits abuse of the free renders.
- Only after you accept: Google Analytics, Google Ads, the Meta Pixel and Meta server-side events, and the cookie that remembers which page or campaign brought you here. In the EU, EEA, UK, Switzerland and Norway, and wherever we cannot tell your country, we ask first. Elsewhere they run until you decline.
- A browser Global Privacy Control signal counts as no until you accept.
- Your choice is stored in the
tds_consentcookie, shared with 3dstudio.co. Change it any time with Cookie settings in the account menu. - The help chat from Crisp loads only when you open it.
Security
Files sit in a private storage bucket and are served to you through the app, not from a public folder. API keys and connector tokens are stored as hashes. No system is perfectly safe, and if a breach puts your rights at risk we will tell you and the authority as the law requires.
Changes
If we change this policy in a way that matters, we tell account holders by email or in the app. The date at the top shows the current version.