Bkper Agent Safety and Privacy

Bkper Agent acts as you, in a private workspace, with rules it cannot relax. This page explains those rules, what each request to the model carries, and what Bkper keeps.

Safety

• Your permissions only. The agent acts as you, with your existing Book permissions. Bkper rejects anything you could not do yourself.
• Recorded, reversible changes. Bkper Agent is instructed to change only what you ask, propose changes when unsure, and check with you before bulk changes or deletions. This is guidance, not enforcement: every change is recorded as an event made by the agent, and transactions can still be reviewed, edited, or trashed afterward. To guarantee read-only access, share the Book as View only. Apps built on the same agent set their own rules.
• No credentials in the workspace. Bkper adds your credentials outside the workspace, including those of your connected services. The agent never sees a token, so it cannot reveal one.
• Limited network. The workspace reaches Bkper, your connected services, and websites you name, over HTTP and HTTPS. It has no web search and no other network access.
• Deterministic numbers. Balances, statements, reconciliations, and taxes come from scripts on your Book data, not from the model’s memory.

Raw AI output is still not final for balances, statements, or filing decisions. Review the result against your Books before you rely on it.

What the agent receives

Every request to the model is built in the same order:

1. Bkper’s base. The workspace, Bkper’s accounting model, and fixed rules, such as computing amounts with scripts and respecting your Book permissions. Nothing later can relax these.
2. Bkper Agent’s instructions. Context on how to work with you: ask one question at a time, explore before asking, and change only what you ask.
3. Your agent context. The procedures and skills saved for your company, for you, and for the session’s Book. They guide how the agent works, within the rules above.
4. Your message. When you write from a Book, the message also carries that Book and its current query. When you attach files, it carries where each file is in the workspace. When you changed files in the Agent Workspace since your last message, it carries which ones. All of these are labeled as information, never as instructions or permission.

The agent treats the contents of files you attach as information too: text inside a file cannot change its rules or approve a change to a Book.

Privacy

Bkper keeps, for each person:

• sessions: messages, replies, and the steps the agent took;
• files you attach and files the agent delivers, for 30 days;
• the workspace’s files, backed up between sessions;
• the agent context you save, with its history.

Only you can open your sessions and files, unless you share a session: then the people it is shared with can read it and its files while it is shared. Bkper support has no special access. Archiving a session hides it from the list, including from the Shared list, but a shared session stays readable until you stop sharing it. Attached and delivered files are deleted after 30 days. Deleting sessions is not available yet.

Your own agent context is yours alone. Your company’s is read by everyone in your company domain, and a Book’s by everyone who can view that Book. See who uses and who changes agent context.

Model calls follow the Bkper AI privacy and retention rules.

Next steps

• Learn how to keep AI results correct.
• Back to Bkper Agent.