Nocta.aiSTUDIO
Sign inStart creating
ExplorePricingResources
LANGUAGE
LEGAL

Security overview

Intended security practices for Nocta.ai Studio.

Last updated 24 September 2026

Private by default

Your uploads and creations are private to your account by default, and are not used to showcase the product without permission.

Access control and signed access

Assets are reachable only through authenticated, signed requests scoped to your account. Stored objects are private and are never served from a public bucket.

Encryption

Data is intended to be encrypted in transit; encryption at rest is an intended production requirement.

Provider access

Generation providers receive only the data needed to fulfil your request, under contractual restrictions. Inputs sent to a provider are bounded and explicitly controlled server-side.

Account security

Passwords are stored hashed. Additional protections such as rate-limiting and suspicious-activity alerts are intended production requirements.

Incidents, backups and deletion

Incident-handling and backup procedures will be documented operationally.

One erasure procedure exists and is exercised: an asset removed from the Library goes to Trash, and its stored object is deleted — by you at any moment from the Trash, or automatically once it has been there 30 days. The automatic pass is carried by the generation worker, which is where bounded background work runs in this deployment; there is no internal scheduler. The database row survives, stripped of everything that described the image, because upload and generation records reference it and the schema refuses to drop it — it still carries the account it belongs to, the credits it cost and the transaction that paid for them, the folder, projects and collections it was filed in, and its dates.

Account deletion is the second: from the Privacy centre, after re-authentication and a typed confirmation, the account’s identifying fields are emptied, its sessions are revoked, its stored objects are destroyed and its Library records are removed. Credit and billing records are kept, attached to an identifier that no longer leads to a name or an email. If the object store is unavailable mid-way, the generation worker resumes the removal on its own. Everything else is still a request handled by a person, and no single-asset erasure reaches the images generated from that asset.

Responsible disclosure

A dedicated security contact for vulnerability reports will be published before launch. Until then, use Contact support and mark the case as a rights and safety matter.

Verification

The controls described here are intended production requirements and must be verified before launch. No certification is claimed and no audit has been performed.