Company
Trust & security
Saphion is built so your company’s data and decisions stay under your control. Beacon works inside your permissions, and your people stay accountable.
Keeping your work secure
For each person
You choose what Beacon may do for you.
- Beacon acts only as you could, checked on every action.
- For each tool, choose Always allow, Needs approval or Blocked. Sharing, sending and deleting for good always ask first.
- Your mailbox stays yours. Only the emails you link to a piece of work are shared, with the people on that work.
- You choose which actions require approval. Product reviews and sign-off remain with the accountable people.
- Compatible assistants such as Claude, Claude Code or Codex use only the tools and records permitted to the person and organisation, including approval checks for changes.
For your organisation
Layered protection for your company’s work.
- Your data is kept to your organisation and its members, by role.
- Everyone sees only what their account type, Permissions and access to each item allow.
- Everything new starts private. Sharing is explicit, and only an Admin, or someone given that Permission, can open something to the whole Organisation, and then only to view.
- An Admin can require two-factor sign-in: after their password, everyone enters the code from an email titled “Your Saphion code”. Admins are always asked for one.
- Documents keep their versions, and Documents, Boards, Dashboards, files, Teams, people and Automation rules each show their own History. On Business and Enterprise plans, Admins can read and export an Audit of changes to people, Permissions, seats and access.
Security at every step
Permission-checked AI
Every action Beacon takes is checked against the person’s own access at the moment it happens.
Governed sending
Replies go to the real thread, and you see every recipient before anything is sent. Every send follows the person’s own setting.
A full record
Drafts, changes and approvals are recorded and can be traced back. Deleted items can be restored from the Bin for the days your plan allows: 30, 90 or 365.
Trusted infrastructure
Saphion runs on Microsoft Azure. Beacon runs on Claude models from Anthropic, with OpenAI used for embeddings, transcription and images. Access to company records and connected systems is governed by your organisation’s permissions.
Subprocessors and service providers
| Provider | What it does | Where it is processed |
|---|---|---|
| Microsoft Azure | Hosts Saphion: the application, database, file storage, job queue, live updates and sign-in. | Hosted in the UK South region. |
| Microsoft 365 (Microsoft Graph) | Sends Saphion’s own email, such as sign-in codes, notifications and support replies. When a person connects their own mailbox, it is also how Saphion reads and sends that person’s email. | Location set by Microsoft for the Microsoft 365 account. |
| OpenAI | Embeddings, transcription and images. | Processing location set by the provider. |
| Anthropic | Provides the Claude models behind Beacon’s chat and specialist work. | Processing location set by the provider. |
| Recall | Recall joins the Microsoft Teams meetings you add Notetaker to, to capture captions. | Only when you add Notetaker to a meeting. Recall uses its EU region. |
| Google Analytics | Anonymous page-view counts on this website. It loads only after you accept analytics cookies. | Processing location set by Google. See the cookie policy. |
Some optional features call Google Maps (address and hospital lookup), Exa (web research) or Open-Meteo (weather) when they are configured. A UK hosting region does not mean all processing stays in the UK: AI, communications and connected-service providers may process information elsewhere. Read the privacy policy or talk to Saphion about the arrangements that apply to your service.
Reporting a vulnerability
How to report
If you think you have found a security issue in Saphion or this website, email support@saphion.co.uk with the subject “Security issue”. Reports go to the Saphion Support mailbox.
- Say what you found, where, and the steps to reproduce it.
- Do not include customer data. Tell us what you saw rather than attaching it.
What we ask of you
Please act in good faith.
- Test only against accounts you own, and do not access, change or delete other people’s data.
- Do not disrupt the service, for example with denial-of-service or spam.
- Give us reasonable time to fix an issue before you share it publicly.
Contact
Questions about security or data protection?
Read our privacy policy or ask us what your organisation needs to know.