Security
How we protect what you give us
A concrete description, not a row of icons. Whatever is not finished yet is listed at the end.
Separation of customers
Every record carries your workspace identifier, which the server derives from verified membership — never from the browser. The second line of defence sits in the database itself: even if the application made a mistake, it would not hand over someone else's data. We test that by deliberately trying to reach it from another account.
Roles and revoking access
The owner controls integrations, billing and export. An assistant sees only the assigned scope. An accountant sees finances but neither private media nor conversations. Revoking a role also invalidates the session and any pending tasks.
Files
Originals live in private storage. Access comes only through a short-lived signed link, and only after a permission check. A quarantined file is available to nobody — not even through a direct URL.
Money
Amounts are stored as whole minor units together with the original currency. Sale, refund, fee and payout are separate types. A repeated import cannot raise revenue a second time, and an overlapping period must be resolved visibly. A refund corrects the original sale; a payout to your bank is not another sale.
What the language model does and does not do
The model receives only approved, pre-computed values and turns them into an explanation. It does not compute money, does not decide permissions and triggers no external action. Its output is checked against its input — if it cites an identifier that does not exist, it is discarded. Instructions planted inside an uploaded file are not commands to the system.
AI budget
Consumption has a daily limit per workspace. When it is reached, further jobs stop, but you do not lose the results you already have.
Backups and restore
Backups are encrypted. We rehearse restores regularly, because a backup nobody has restored is not a backup. If you deleted something, restoring a backup does not bring it back into service — the deletion is applied again.
A separate environment
Adult content runs in a dedicated environment with its own database, access, logs and backups. Development and testing never use real private data.
Logs
We never log message content, tokens or private media. IP addresses are stored only as an irreversible fingerprint.
What is not finished yet
- — An independent third-party security review is planned but has not happened yet.
- — The operator's identity and the contract documents are being finalised before paid operation.
- — Individual recommendations are switched on only once the specific purpose and conditions of processing are documented.
Please report any security problem to info@creaitor.cz.