The Atelier HandbookFaden help centre

How Faden protects your studio

OwnerHelping a client 2 min read · updated · checked against the app
In short

Studios walled off from each other, encrypted fields, a tamper-evident audit trail and nightly encrypted backups, in plain language.

On this page

Your book is your business. Here's how it's protected, without the jargon.

Your data is walled off

Every studio's data is isolated at the database layer. The separation between studios is enforced by the database itself on every query, not by application code remembering to filter. One studio cannot read another's rows, full stop.

Sensitive fields are encrypted

Sensitive fields are encrypted at rest (AES-256-GCM), and backups are encrypted before they are stored.

Every action is on the record

Staff and platform actions write to a tamper-evident audit log. Entries are chained so alteration is detectable. See The audit log.

Backups

A backup of the database and uploaded files is taken every night, encrypted, and copied off-site. Backups are kept for 14 days on the server and 35 days off-site. You can also take your own export at any time. See Data Control.

Even our support knocks

Faden support enters your studio when you approve a request, for a set time. There is an emergency override, and it emails the owner at once. Every visit is in your audit log. Support can never open your security, team, billing, payments account, whole-studio data or domain pages.

Your side of the bargain: two-step verification on, a passkey where you can, and roles scoped to the job. See MFA and sessions.

Did this get you there?

Still stuck?

A person reads every message.

support@faden.techWe reply by email Service statusAll systems running