One database per space
Each space has its own Postgres database: knowledge base, conversations, log and costs. No engine query touches a database outside the space context. Exporting or deleting a space is a single operation.
Security and data
One database per space, no model that retains
Your conversations are your customers’ data. 0seat is built so they stay compartmentalised, encrypted where needed, and handed to model providers for the duration of a single call.
Model providers with no retention
Calls go through providers configured not to retain or reuse the data sent. A free model never sees customer data without prior anonymisation.
Encrypted, write-only secrets
Your inbox token and WHMCS credentials are encrypted with AES-256-GCM. Once saved, they are never sent back to the browser or written to a log.
WHMCS read-only, fields filtered
Access goes through a closed list of read actions of the API. Password, postal address and phone number are stripped in code before any model call.
Customer messages are data, not instructions
An incoming message cannot change the assistant’s instructions. The tools available to it are typed, with validated arguments and no free access to any system.
Access per space
The organisation’s owner and administrators see all its spaces; an agent sees only the ones they are assigned to. Members join by invitation, with a one-time code by e-mail, no password to protect.
What 0seat does not claim
- No SOC 2 or ISO 27001 certification: we will not display one until an independent audit has issued it.
- No writes to WHMCS: the API role carries read actions only, and 0seat suspends, refunds and changes nothing.
- No model training on your data: providers are configured not to retain it, and 0seat trains no model.
- No numbered uptime commitment at this stage: the platform runs on a dedicated server in Finland, with backups at the same host.
Frequently asked questions
Where is the data hosted?
On a dedicated server in Finland, with one database per space. Model calls go through the providers listed among our subprocessors, configured not to retain data.
Can a customer manipulate the assistant through their message?
The message is treated as data: it does not change the instructions. The assistant has no write tool, and any request touching money or the account goes to a human.
Who on your side can access our conversations?
Internal access is limited to operating the service. On your side, only the members you invite see your spaces, according to their role.
Can we delete a space and all its data?
Yes. Since each space has its own database, deleting it removes the whole database: knowledge, conversations, log and costs.
Your team stays in charge. 0seat does the groundwork.
Connect an inbox, approve the suggested knowledge base, and get your first prepared replies.
See also
Subprocessors
List of the subprocessors handling data for the 0seat service.
WHMCS
Services, domains, invoices and orders read through a closed list of API actions. Minimal role, sensitive fields filtered, account summary by e-mail.
Human handoff
Money, disputes, cancellations, a request for a person, a second follow-up, an answer missing from the base: an agent takes over, whatever the mode.