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.
Know who has access, where information lives, and what connected services process.
Each company has a separate workspace and database, with sign-in, billing, and hosting managed by Sinora.
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.
Dedicated hosting and a separate database keep your company data apart from other customers.
HTTPS encrypts browser-to-workspace traffic in transit, but does not provide end-to-end encryption.
Share only authorized information with connected providers, who process task-relevant data under their own terms.
Generated apps receive limited access, not your Sinora sign-in credentials.
Decide who sees your memory, what gets approved, and which AI accounts do the work.
Your personal memory stays yours. Teammates can’t read it, and workspace admins need a support access grant that 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 that Sinora recognizes in a message are removed before the text reaches an AI model. Add them as a connection instead.
Sending or deleting Google email, and creating, changing or deleting Google Calendar events and tasks, wait for your approval every time.
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.
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.
Passwords, keys and tokens you save for connected tools are encrypted with AES-256-GCM.
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.
Workspace servers accept an update only when it carries a valid signature from a Sinora release key.
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.
Confirm hosting, recovery, and provider requirements with us before adopting the new workspace.
Questions about our security practices? Ask our security team