No business records
We never take your business records. Not contacts, accounts, leads, or orders. ctx10 reads your setup, not your data.
Security
We only read. We never write.
ctx10 reads how your Creatio is set up: the processes, rules, pages, and fields. It never reads the records inside it. Everything below is built into the code, not just promised on a page.
We can tell you who changed a setting, without ever reading a customer record.
ctx10 reads Creatio’s own list of users. It never touches your customer data. That is a better privacy story than the other way, and few tools can say it.
Enforcement
Four locks, not one
A read-only promise is only as strong as its weakest point. So there are four. A query has to pass all of them. Any one on its own would stop a write.
- 01
In your Creatio: a read-only guard
The ctx10 add-on takes one kind of command: a read. It turns down everything else before it ever reaches the database.
- 02
In our system: every query is rewritten
We rewrite each query and lock it to your data. If a query cannot be locked down, we refuse to run it. We never guess.
- 03
At the database: a read-only login
Queries run under a login that cannot write, and cannot reach anything outside your data. In production, the service will not even start without it.
- 04
At the key: fixed when it is made
Every key belongs to one person and can be turned off. What it can do is set the moment it is made. A key can never grant itself more.
Data we never hold
The safest data is the data we never took
Personal data removed as we read
We drop personal data as we read it. Emails, phone numbers, passwords. They are never saved. So they cannot be searched, exported, or leak later.
A database per customer
Your index gets its own database. You are kept apart from everyone else by design, not by a filter.
No AI training
We never train AI models on your data. Your index answers your questions. Nothing else.
The add-on
Built so it can’t write, said plainly
The ctx10 add-on runs inside Creatio. We don’t say it can’t write. We say it doesn’t, and we can show you why. Two things make that true:
A guard checks first
Every command has to be a read. One command at a time, nothing risky. Anything else is turned down before it runs.
A read-only session, rolled back
We open a session that is set to read-only, then roll it back when it is done. Even a write could not stick.
Access & audit
Off by default. Logged when on.
Live access starts off
Reading a saved index is the normal way. To query your live instance, you turn it on for that instance first.
We log every query
The command we got, the command we ran, how many rows, how many bytes, the caller’s address and browser. All of it, every time.
SSO
Sign in with single sign-on. Admins can keep a password login as a backup.
Keys you control
Each key belongs to one seat. You can turn it off anytime. What it can do is fixed when it is made.
Data & privacy
What we keep, and how to ask about it
ctx10 keeps the index of your Creatio setup: your processes, rules, pages, fields, and roles. Plus the account and query logs we need to run the service. Personal data from your records is removed as we read, and never saved. Your index sits in its own database. We delete it when you ask.
Doing a security review? Need a signed DPA or a filled-out questionnaire? Email hello@ctx10.com and we will turn it around fast.