Security
Security and compliance at Maple
Your telemetry holds request paths, user ids and error messages. This page lists what protects it, what is still in progress, and the docs page behind each claim.
- DPA
- Available on request
- SOC 2 Type II
- Audit in progress
- ISO 27001
- Audit in progress
- Regions
- US or EU (Frankfurt)
Access
Who can see what
- Four roles Admin, Engineer, Member and Analyst. Analysts read everything and build dashboards, and cannot change settings, alerts or keys.
- SSO and SCIM SAML 2.0 or OIDC sign-in with verified domains and an option to require it. SCIM 2.0 provisions and removes members and maps IdP groups to roles. Both are self-serve add-ons, $100 a month each, on any plan. SSO and SCIM docs
- Audit log An append-only log records every action in the dashboard, API and MCP, allowed or denied, and every read of telemetry and session replays. Each entry names the user, API key or agent. Entries are kept for six years. Retention periods
Data
How your data is protected
- Encrypted in transit and at rest Telemetry reaches Maple over TLS and is stored encrypted.
- Credentials sealed per row Secrets Maple holds for you, such as OAuth tokens, webhook secrets and warehouse passwords, are sealed with AES-256-GCM. Each one is bound to its organization and row, so a value copied to another row or organization fails to open.
- Replays mask inputs by default The browser SDK masks every input value before it leaves the browser. One setting masks all rendered text as well. Masking options
- Retention you can read Hosted Maple deletes data once it passes its retention period, measured from the data's own timestamp. Every period is listed in the docs. Retention periods
Residency
Where your data lives
- United States or European Union Each organization picks a region once, when it is created. An EU organization's telemetry is stored and processed in Frankfurt, Germany, at the same price. EU hosting
- Or your own infrastructure The source is on GitHub under FSL-1.1, which becomes Apache 2.0 after two years. Self-hosting keeps the data inside your own network. The self-hosted version runs for one team; alerting and team accounts are on Cloud. Source on GitHub
Disclosure
Report a vulnerability
Email support@maple.dev with "Security" in the subject and the steps to reproduce. Please give us time to fix the issue before you publish it.
FAQ
Common questions
Is Maple SOC 2 compliant?
Not yet. SOC 2 Type II and ISO 27001 audits are in progress. Until they finish, a data processing agreement is available on request, the audit log is on every plan, and SSO and SCIM are add-ons on any plan.
Can I get a DPA?
Yes. Email privacy@maple.dev and ask for the data processing agreement.
Where is my telemetry stored?
In the region your organization chose when it was created: the United States, or the European Union in Frankfurt, Germany. Self-hosted Maple stores it wherever you run it.
How do I report a vulnerability?
Email support@maple.dev with "Security" in the subject. Include the steps to reproduce it. Please give us time to fix it before you publish.