Security & data protection

Your workspace is isolated#

Each Opser workspace is a separate tenant. Your business records, files, users, and agents belong to your workspace, and the platform keeps them separated from every other workspace at the database level — not just in the interface. Access to your data always runs through your workspace's own permissions.

Your workspace has a configured hosting region. Connected services and model providers may process task content elsewhere; the hosting region is not a guarantee that every provider processes data in the same location. Confirm any data-location requirements with Opser before adding sensitive information.

Sign-in is protected#

Accounts sign in with an email and password, and Opser adds a verification step: after the password, you enter a one-time code sent to your account email. Passwords are stored only as a secure one-way hash, never in plain text, so they cannot be read back — which is why a forgotten password is reset, not retrieved.

If someone leaves your team, remove their account in Add & manage teammates. A password reset ends that account's existing sessions.

Agents act within limits you set#

An agent can only use the apps, records, and connected accounts its access allows. Two independent controls keep that boundary in place:

• Permissions decide what an agent and a person can reach. Grant access per person or agent, or with reusable access groups, instead of making everyone an administrator.
• Approvals decide which actions run on their own and which pause for your review. Sending email, deleting records, and changing settings ask first by default. See approvals & control.

A permission is not the same as an approval: approving one action never grants standing access to a restricted app, mailbox, or record.

Connected accounts and secrets#

When you connect an outside account — a mailbox, a calendar, or another service — check the selected agent and the access shown in its connection settings. How authorization is stored depends on the integration; some connections are managed by an integration provider. Connecting an account does not give every agent in your workspace access to it. Disconnect an account at any time from Connect your tools.

For values an app needs to keep, such as an API key, an administrator can store them in the workspace Vault, kept apart from ordinary records. Never paste a password, verification code, or API key into a conversation; connect accounts through their proper setup flow instead.

What agents send to model providers#

Agents use large language models and, when you enable them, services such as web search or media generation to do their work. The content of a task is processed by the provider running that model or service. Give an agent the context a task needs, and use permissions and approvals to keep sensitive actions under review. Web research keeps its findings linked to their sources so you can check them.

Managing your data#

Administrators can review and remove business records in Database & storage. Exporting or deleting your workspace's data is a deliberate action — canceling a subscription does not automatically export or erase your records. Plan an export before you make an irreversible billing change, and see subscriptions & payments for what a cancellation does and does not do.

Reporting a concern#

If you believe an account is compromised or you have a security question, contact Opser with the workspace address and what you observed. Do not include passwords, verification codes, or reset links in the report.