Data controller
The legal operator’s name, country and postal address have not yet been confirmed. These details and a working privacy contact must be published before launch; this draft does not identify a final data controller.
The Contact page reaches an operations mailbox where this deployment configures outgoing mail. After submission, it tells you whether your message left the server. Otherwise, it shows a published alternative address if one is configured; it does not pretend that an unavailable channel delivered your request.
Data we collect
Your account holds your name, email and a password hash, or linked sign-in details when you use Google. The Studio stores your uploads, generated results, selected settings, Library organisation and saved looks. It also records your image-rights declaration and your optional product-email preference.
Using the service creates credit and billing records, technical activity and security logs, and any messages you submit to support. A payment provider processes billing information when you make a purchase. The Subprocessors page lists the data sent to each provider.
Optional Contact and Support photos are checked and re-encoded on the server, with embedded metadata removed, and attached to the operations email when delivery is configured. They are not added to your Library or published in Explore. Retention in the operations mailbox still requires operational and legal review.
Purposes and legal bases
Data is processed to run generations, keep your Library, secure accounts, bill usage, provide support, and meet legal obligations.
The mapping of each purpose to its legal basis (contract, consent, legitimate interest, legal obligation) will be finalised during legal review.
Accepting the Studio Terms or acknowledging this Privacy Policy is not blanket consent to every use of your personal data. Product emails and optional cookie choices are separate and can be refused without preventing account creation.
Real-person uploads
At email sign-up, or once before uploading or creating for an existing or Google account, you explicitly declare that you hold the necessary rights to your uploads and the permission of any people depicted for AI-generated edits. The account declaration is recorded with its wording, version and acceptance date; upload records retain the applicable rights confirmations. People depicted without consent can request removal without an account.
Providers and subprocessors
When you submit an enabled generation, the images selected for that operation, including photographs of real people, are sent to Google for processing. Uploading a file to your Library alone is not a generation request.
Stripe processes website payments when billing is enabled. Nocta operates its image-storage and authentication software; the physical host and its exact location still need to be documented. Google sign-in is available when configured. The Subprocessors page gives each provider’s purpose, data categories and the location or transfer information still to be confirmed.
International transfers
Google and Stripe are established providers that may process data outside your region. The applicable transfer mechanism for each of them is not yet documented; the Subprocessors page states this openly and must be completed before launch. Do not read the absence of a documented mechanism as an absence of transfer.
Retention
Your creations are private by default. Library Trash keeps an asset for 30 days so you can restore it. You can request permanent deletion sooner from Trash; deletion is postponed if a generation is still using the asset.
Permanent deletion removes the stored file and strips the Library record, but keeps accounting and filing metadata linked to your account. It does not delete separate images generated from it. A result you keep in your Library has no automatic expiry.
Two known limits remain: a generated image’s generation record retains a copy of its file metadata, and temporary copies from some older failed upload clean-ups may still be stored until an operator removes them. The details below explain exactly what is kept.
Account deletion erases your identifying fields and revokes access immediately. Library and stored-file removal can continue in the background, with files pending during a storage failure. Credit and billing history is kept without your name or email. Other retention periods, including logs and remaining business records, still require legal and operational review. Do not assume that inactive data expires automatically.
Storage and deletion details
Your creations are private by default. Removing an asset from your Library moves it to Trash, where it stays for 30 days: you can restore it, or delete it for good straight away from the Trash itself. Whichever comes first — your own permanent deletion or the 30 days running out — the stored file is erased from our object storage and the identifying fields of its record are emptied. One case is postponed rather than done at once: while a generation you started is still reading that asset, an immediate deletion is declined and you are asked to try again once it finishes, so that a generation you paid for cannot be left without a result; the automatic pass retries on its own.
What survives that erasure is a stripped record. Everything that described the image is gone: name, stored file, checksum, original file name, format, size, dimensions, tags, style, tone and the rights and consent confirmations you made when you uploaded it. What is deliberately kept is accounting and filing metadata: the record identifier, the account it belongs to, whether it was an upload or a generated result, the credits it cost and the link to the credit transaction that paid for it, the folder it was filed in and the projects or collections it was added to, and the dates it was created, last changed, moved to Trash and erased. The database refuses to drop the row itself, because upload and generation records point at it. Two consequences, so that the residue is not read as smaller than it is: the record stays attached to your account, and it stays attached to containers you named yourself, even though the erased asset is no longer shown or counted anywhere in the product.
An image you uploaded is described twice, so it is stripped twice. Besides the Library record, the upload ticket that carried your file in is emptied in the same operation: the checksum, the original file name, the format, the size, the dimensions, the storage locations and the two request fingerprints derived from them are removed there as well. What that ticket keeps is the identifier of the ticket itself, the two idempotency keys your client generated for it — random values that say nothing about the image — the state of the reservation, the link back to the stripped record, and the dates of the ticket: when it was opened, when it expired, when its temporary copy was deleted and when it last changed. They are kept for one reason: a retried upload must be recognised as the same upload instead of reserving, storing and charging a second time.
One residue this does not yet reach, named here rather than left to be discovered: for an image the service generated rather than one you uploaded, the generation record that produced it keeps its own copy of the storage location, the checksum, the format, the size and the dimensions. Erasing the asset empties the Library record and destroys the stored file, but leaves that copy standing. It is a known gap, not a design — the same stripping is owed there and has not been built yet.
A second residue, narrower, and closable only by hand. An upload is carried in through a temporary copy that is deleted once the image is filed. Before this version, when that clean-up failed the failure was recorded and the upload went through anyway, and erasing the asset never came back to it. For those older uploads only, the erasure still empties everything that describes the image, but keeps one field: the location of that temporary copy. That location is a random value nothing can recompute, so dropping it would leave the file sitting in storage with nothing left pointing at it — worse than keeping the pointer. So for those uploads the temporary copy may still be stored, and its recorded location still gives away the file format through its extension. Nothing in the running service closes this: an operator has to delete each remaining copy and clear its location, following a documented procedure. It cannot happen to an upload made from this version on — every erasure now destroys both copies in the same operation.
Two limits, stated plainly. Deleting an asset does not reach the images generated from it: those results are separate assets and stay in your Library until you remove them too. And the 30 days cover the Library Trash only — a generated result you keep carries no expiry date. Deleting your account erases its identifying fields and revokes access immediately; its Library and stored files are queued for permanent deletion. Remaining clean-up may continue in the background and stay pending during a storage failure. Credit and billing history is kept without your name or email. Retention periods for every other category of data are to be defined after legal and operational review. Until then, assume that data sent to the service is kept.
Security
The intended security practices are described in the Security overview. They are production requirements and must be verified before launch.
Your rights
Depending on your jurisdiction, you may have rights of access, correction, deletion, objection, restriction and portability, and a right to complain to a supervisory authority. This draft does not waive those rights or applicable legal deadlines.
You can use the controls below immediately. For requests that need a person to act, use Contact or Content removal. The form tells you whether delivery succeeded; sending a request does not automatically remove or reinstate content. A published privacy contact and working handling procedure are required before launch.
- Privacy centre → Download my data: download your account information as JSON, including your recorded image-rights declarations. Image files are linked, not included; their download links require sign-in.
- Privacy centre → Delete account: erase your identifying fields and revoke access immediately, then permanently remove your Library and stored files. File removal may continue in the background and stay pending during a storage failure. Credit and billing records remain without your name or email. Running generations or billing requiring a manual check can temporarily block deletion.
- Privacy centre → Email preferences: turn product emails off at any time. This withdraws your optional choice immediately. No product-email campaigns use that choice in the current product; re-enabling it from your account is not yet supported.
- Footer → Cookie settings: change or withdraw optional browser preferences. No analytics or marketing tracker is loaded in the current product.
- Library → Trash: restore an asset or delete it permanently, subject to the retention limits described above.
How these controls and requests work
The Contact and Content removal forms are the route for rights requests that need human handling: they send to an operations mailbox where this deployment configures outgoing mail, and say after you submit whether it actually left the server. Exercising any other right still requires a person to act on it. This preview has no automatic response or handling timetable; applicable legal rights and deadlines are not waived.
A published contact address and a working request procedure are required before launch. You may lodge a complaint with your supervisory authority at any time.
Five controls do take effect on their own. “Cookie settings” in the footer records your choice in your own browser and can be changed or withdrawn at any time. And from your Library Trash you can delete an asset for good: the stored file is really erased, without anyone acting on a request. One temporary exception applies to that second control: while a generation you started is still reading the asset, the deletion is declined and you are asked to try again once it finishes. It covers the asset you uploaded, not the images generated from it, it leaves the stripped record described in the Retention section, and it is not account deletion.
The third is the data export. “Download my data”, in the Privacy centre, gives you straight away a JSON copy of what your account holds: profile, credit history, billing, Library and Project details, generations with the settings you chose, saved styles, your recorded image-rights declarations with their version, wording, source and acceptance date, and your product email choice with the date and the exact wording you agreed to at sign-up. Image files are not inside that copy: it lists a download link for each file still stored, and those links only work while you stay signed in. Your password, sign-in tokens, internal storage locations and payment provider references are never included. For anything the copy leaves out, the Contact page remains the route.
The fourth is account deletion, in the Privacy centre. It erases your name, email address, password and linked sign-in straight away and revokes access from every device. It cannot be undone. Your Library, uploads, generated images, Projects, folders and saved models, together with their stored files, are queued for permanent deletion. The first clean-up is bounded; remaining removal may continue in the background, and a storage failure can leave files pending until the worker can remove them. What it keeps, without your name or email, is your credit and billing history: those records must be retained for accounting and fraud prevention. It is declined while a generation you started is still running. A subscription bought on this website is cancelled before account identity erasure; one bought in the App Store or Google Play must be cancelled in that store.
The fifth is product emails. You can agree to occasional product updates only when you create an account with an email address, and you can turn them off at any time from the Email preferences of the Privacy centre: the change is immediate and needs no request. Turning them back on from your account is not available yet.
The content removal and appeal routes send your request to a person; they never remove or reinstate anything automatically.
Automated processing
Image generation involves automated processing of the images you upload. No decision producing legal effects is made solely by automated means.
Minors
The service is not directed at minors. Age thresholds and verification measures will be confirmed during legal review.
Updates to this policy
The revision date above identifies this draft. The operator must confirm the final policy, legal bases, retention periods and change-notification procedure before launch. A revised page does not retrospectively create a permission you did not give.





