Your data stays yours. People stay in charge.
How Residention separates customer data, who can act on it, how AI is kept within bounds, and what we do and do not claim. It describes how the product is built; it is not an independent certification.
Four commitments.
Separated by workspace. Each customer’s data lives in its own workspace, separated in the database itself. A request that cannot prove its workspace returns nothing. Access by role and scope. People see the portfolio, building or record they are given, and nothing wider. Our own support access needs your time-limited grant and is logged. People decide what matters. Payments, invoices, contracts, complaints and deletions always need a named person with the authority to approve them. Every change leaves a trail. Who changed what, when and why stays with the record. History is added to, never rewritten, and a deletion keeps a snapshot.
How AI agents are allowed to act.
Agents are useful because they act. They are safe because every action is bounded: by who owns the agent, what it is for, where it may work and when its authority ends. Read: Looks at records inside its granted scope, and no further. Propose: Drafts a reply, a task or a classification for a person to review. Approve: Reserved for people. An agent can ask for approval; it cannot give it. Execute: Carries out one granted action on one building until the grant expires. Every agent has a named owner, a stated purpose, a scope, an expiry date. When risk rises, authority drops: the agent falls back to read-only rather than guessing. A workspace administrator can stop any agent at once. Agents never, without a person: Approve invoices or release payments; Post entries to the books; Sign or change contracts; Close a complaint or a compliance item; Delete records.
What happens to your data.
Separation: The workspace is the security boundary, enforced in the database on every read and write. Access that cannot resolve its scope fails closed. Personal data: Residention processes personal data on your behalf under the GDPR, the UK GDPR and the Dutch UAVG. The data processing notice sets out the terms. AI suggestions: smartAI answers from your own records and shows where each fact came from. Every suggestion is stored with its model, confidence and evidence, so it can be reviewed later. If AI is unavailable, the product keeps working. Connected sources: Each connection to a mailbox or document store states what it may read. Revoking a connection closes access straight away, not at the next sync. Deletion: Every deletion is confirmed, logged with a snapshot of what was removed, and can be undone.
Standards, read honestly.
The product is designed to the control areas below. Residention holds no external certification for them today; where that changes, this page will say so.
Who is responsible for what.
Residention: Separating your workspace from every other customer; Checking access on every request; Keeping the change history and deletion snapshots; Holding agents to their owner, purpose, scope and expiry; Keeping this page accurate. Your organisation: Who has access, and at which scope; Approval rules and spending limits; Which agents run, and with which grants; The decisions your people approve.
Questions or a security review?
Email trust@residention.com, or book a technical briefing and we will walk your security team through the product.