Trust Center
Security
How Magif protects your clients' conversations and your knowledge bases: encryption, access control, tenant isolation, monitoring, backups and incident handling.
Last updated: 21 September 2026
Security overview
The controls below cover the platform end to end, from data storage to incident handling. Each statement is scoped to what is in place today.
Encryption
Data is encrypted in transit with TLS and at rest across the primary database, file storage and backups.
Access control and least privilege
Access to production systems is restricted to authorized personnel on a least-privilege basis, and multi-factor authentication is enforced on all administrative and infrastructure accounts. Creator and end-user data access follows the platform's role model: creators see only their own workspace.
Tenant isolation
Workspaces are logically isolated per account. Agent knowledge and memory are scoped per agent and per end user.
For you as a coach, that means your knowledge bases stay inside your workspace, and what an agent remembers about one of your clients is scoped to that client.
Monitoring and logging
Application logs, traces and alerts are centralized in an EU-hosted monitoring platform for reliability and security monitoring.
Vulnerability management
Security issues are tracked through the engineering issue process and prioritised according to severity. Dependency and infrastructure updates are applied through regular maintenance, with urgent security fixes handled separately when required.
Backups and continuity
The primary database is backed up on a managed schedule. Backups are encrypted and expire on a rolling window of at most 1 year.
Backups are encrypted and kept on a rolling window of at most 1 year. Restores are exceptional disaster-recovery operations; if a restore re-introduces data that had been deleted, retention and deletion rules are applied again to the restored data through the standard deletion process.
Incident response
Security reports are reviewed and escalated according to severity. Customers affected by a personal-data breach are notified in accordance with applicable law and any contractual notification period.
Responsible disclosure
Reports are welcome at the security contact address. Magif reviews every report and responds to actionable findings. Write to [email protected].
Support access is logged
When an authorized administrator opens a conversation to resolve a support request, the system records who accessed it and when, and stores no conversation content in the log. Unauthorized accounts are refused.
Validated on staging 21 September 2026New control, shipping in the current release (pull request in review)View the walkthroughHide the walkthrough
When an authorised administrator opens a conversation in support tooling, the system records who did it and when, and never records what the conversation said. Unauthorised accounts are refused.
- 1
An authorised administrator opens a conversation
An administrator with support access reads a conversation through the internal tooling. The read succeeds.
Recorded output
GET /conversation-history/detail/{conversation_id}HTTP 200 · conversation returnedActing administrator identity forwarded on the request. Route path redacted to its shape.
- 2
An audit entry is written
The read writes one audit row. It records who acted, what they did and when. It stores a message count, and no message content.
Recorded output
- actor_email
- ••••@magif.ai (authorised administrator)
- action
- conversation_history.messages.read
- route
- /conversation-history/detail/{conversation_id}
- timestamp
- 2026-09-21T02:45:16Z
- metadata.message_count
- 2
No conversation content is stored in the log, only a message count.The recorded audit entry. Actor email and identifiers are redacted for publication.
- 3
An unauthorised account is refused
An account without support access that requests the audit log is rejected. The control fails closed.
Recorded output
GET /audit-logs (non-authorised account)HTTP 403 · refused - 4
Audit entries are kept for 400 days
Each audit row expires automatically after 400 days through a time-to-live index on the collection.
Retention is enforced by a time-to-live index set to 400 days.
This support-access audit control ships with the current release and is in review. It has not been running historically. Captured on an isolated staging replica of the production system, 21 September 2026. Names, emails and record identifiers are redacted for publication.