Your rules, applied
The company decides which connections are offered, which parts of the product are switched on and who can see restricted company context. We apply those decisions in each agent's setup.
Trust and Data
You decide what AI should know and what it may touch, and anything sent or consequential waits for a person's sign-off. Agents connect to each person's own accounts, and Kriaka does not get blanket access to your business. Actions and approvals are logged, so there is a clear record of what the agent did and who signed it off.

Sending something or making a consequential change waits for sign-off on that exact action. The person approving sees what would be written, and if they decline, it does not happen.
The company decides which connections are offered, which parts of the product are switched on and who can see restricted company context. We apply those decisions in each agent's setup.
A few routine actions are approved in advance, such as changes to a person's own calendar and tasks, and email drafts. Email sent by scheduled work always waits for a person's sign-off.
Approvals, attempted actions and outcomes are recorded, including failures and outcomes that could not be confirmed. An approval works once and cannot be reused.
A person's conversations, working notes, personal memory and connected accounts are private to them. Other staff cannot see any of it.
Restricted Company Brain categories stay with the named groups that need them. Owners and admins see every category.
Kriaka staff have no routine access to private conversations. Any support access must be specifically authorised and limited to the material selected. The person grants it, and it ends at a set time.
Each company runs on its own copy of the platform, with its own data, kept apart from every other company's. Within a company, access controls keep each person's material separate.
AI processing uses only provider routes that keep neither the request nor the response, with no fallback to a route that does. Your content is not used for training. Processing may occur outside New Zealand. Web searches are processed in the United States and may reach third-party search indexes.
Your information is encrypted in transit and at rest, and so are backups. Connection credentials are sealed to each person and never reach an AI model.
We design for visible recovery when something fails, a clean exit when work ends, and plain answers on what we do and do not claim.
Backups are encrypted and kept for 35 days. A restore needs a deliberate approval and reopens with workflows and repeating tasks paused, so nothing runs unexpectedly. Your people are told, and the window of lost work is recorded.
Access can be revoked and accounts disconnected at any time. On request, we produce each person's conversations, documents, notes and records. Conversations and audit records are deleted 90 days after the engagement ends, and encrypted backups can hold them for up to 35 days more.
We do not claim certification or New Zealand-only processing. Nor do we claim that every action needs sign-off, or that nothing will ever fail. Privacy Policy