Your data. Clear boundaries.

Know who has access, where information lives, and what connected services process.

Separate company workspaces.

Each company has a separate workspace and database, with sign-in, billing, and hosting managed by Sinora.

Workspace A
Workspace B
Workspace C

How we handle your data

Conversations and company memory belong to the workspace database; files belong to the workspace runtime. Account, billing, and usage records are handled separately by Sinora.

What’s protected.

Workspace isolation

Dedicated hosting and a separate database keep your company data apart from other customers.

Encrypted Transit

HTTPS encrypts browser-to-workspace traffic in transit, but does not provide end-to-end encryption.

Connected processing

Share only authorized information with connected providers, who process task-relevant data under their own terms.

Protected app access

Generated apps receive limited access, not your Sinora sign-in credentials.

Safeguards you control.

Decide who sees your memory, what gets approved, and which AI accounts do the work.

Private memory

Your personal memory stays yours. Teammates can’t read it, and workspace admins need a support access grant that you start.

Support access you start

You pick who helps, what they can see, and for how long, up to one hour. End it any time. Every read is logged.

Passwords and keys stay out of AI models

Passwords and keys that Sinora recognizes in a message are removed before the text reaches an AI model. Add them as a connection instead.

Approvals before you can’t undo

Sending or deleting Google email, and creating, changing or deleting Google Calendar events and tasks, wait for your approval every time.

Bring your own AI account

Use your own ChatGPT plan, or an API key from Anthropic, OpenAI and others. Replies from your own account use no Sinora credits, and those connections belong to you, not the workspace.

Claude subscriptions run through the official Claude Code. You sign in with Anthropic directly. Sinora does not read, copy or store that sign-in; it stays in Claude Code’s own private folder on your workspace server. Small helper checks can still use Sinora credits.

Memory import you review

Bring memories from ChatGPT or Claude. You review every item before it’s saved, the raw import is discarded after processing, and passwords and keys are dropped.

Storage and recovery.

Encrypted connection secrets

Passwords, keys and tokens you save for connected tools are encrypted with AES-256-GCM.

Nightly encrypted backups

Each workspace server is backed up every night. Backups are encrypted before upload, then again at rest in a private bucket. We keep 7 daily and 4 weekly recovery points. Servers hold no storage credentials, because a Sinora broker controls every write.

Personal Claude sign-ins are never copied into backups.

Signed updates

Workspace servers accept an update only when it carries a valid signature from a Sinora release key.

Your requirements.

Workspace controls

Control who can access shared work

Manage project membership so teammates can use the context they need, while memory follows the conversation’s access scope rather than individual permissions for every saved fact.

Access controls
Project membership Project owners can remove members
Sign-in handoff Revocable access, separate from admin roles
Deployment review

Confirm your requirements

Confirm hosting, recovery, and provider requirements with us before adopting the new workspace.

Hosting location Confirm for your workspace
Review
Backup and recovery Confirm requirements
Review
Provider data handling Confirm requirements
Review
Compliance requirements Ask for current evidence before relying on a certification or regulatory claim.
Discuss with us

Questions about our security practices? Ask our security team