This Privacy Policy explains how Smartplane (“Smartplane”, “we”, “us”) handles personal data when you visit smartplane.dev, use the Smartplane dashboard at app.smartplane.dev, connect an AI agent to the Smartplane gateway, or use the smartplane command-line tool. It is linked from the footer of every page on smartplane.dev, including the home page, at smartplane.dev/privacy.
Smartplane is an access control plane for AI agents. An organisation connects its tools, MCP servers, APIs, databases, integrations, skills, secrets and variables to Smartplane once; its members then connect their agents to one Smartplane endpoint and see only what their role, team and project allow. Rules the organisation writes are checked before each action, and every event is written to a tamper-evident audit log.
Related pages: Terms of Service, Subprocessors, and AI and your data, which describes every place a model sees your data.
Summary
- We hold account data from our identity provider, your organisation’s configuration, encrypted credentials, and an audit log of what happens in your organisation.
- Secret values and connected-account tokens are encrypted, are never shown to AI agents, and never appear in logs or audit data.
- The audit log records the name and arguments of each tool call your agents make. It does not record what the tool returned.
- We do not sell personal data, we do not show ads, and neither we nor our AI provider train models on your data.
- Smartplane runs on Cloudflare. WorkOS handles sign-in. Those are our only subprocessors today.
- Google user data is used only to carry out the actions your organisation’s agents request, under the Google API Services User Data Policy, including its Limited Use requirements.
Who is responsible for your data
Customer data. When an organisation uses Smartplane, the organisation decides what to connect, who gets access and what its agents do. For that data (the organisation’s configuration, its members’ accounts, its audit log, its secrets and connected accounts, and the content of its agents’ tool calls) the organisation is the controller and Smartplane is its processor. We process it only to provide the service, on the organisation’s instructions, as set out in our Terms of Service and, where one is signed, our data processing agreement. If you use Smartplane as a member of an organisation, contact your organisation’s administrator first about your data; we will help them answer you.
Our own data. Smartplane is the controller for the data we use to run our business: visits to smartplane.dev, messages you send us, the account relationship with each customer organisation, and, once we charge for the service, billing records.
Information we collect
Account and identity information
Sign-in, single sign-on (SSO) and directory sync (SCIM) are provided by WorkOS. When you sign in, accept an invitation, or are provisioned from your organisation’s directory, we receive and store:
- your name and email address, and the WorkOS identifiers for your user and organisation;
- your membership of the organisation: your role, whether you are active, invited or offboarded, whether you were added by hand, through WorkOS or through your directory, and when;
- when you were last seen.
If you sign in with Google, Microsoft or your company’s identity provider, WorkOS receives the basic profile that provider shares and passes us your name and email address. If your organisation uses directory sync, WorkOS passes us directory events for the people in your organisation (such as a user being deactivated) so that access is removed promptly.
Organisation configuration
Your administrators’ setup of Smartplane: the resources you add (for example MCP server and API addresses, database connection settings, integrations and skills), teams, roles and projects, access grants, guard rules and their tests, approval requests and decisions, access reviews, and invitations. Some of this names people, for example a grant to a specific member or a rule that mentions a colleague.
Secrets and connected-account credentials
API keys, passwords, connection strings, OAuth tokens and similar credentials that your organisation stores in Smartplane, or that a member connects for their own account. These are encrypted before they are stored (see Security). For a connected account we also store its identity as the provider reports it (for example the email address of a shared mailbox) and who connected it.
Audit log
Smartplane records an event for each sign-in-relevant change, administrative action, secret delivery and agent tool call in your organisation. An event contains:
- what happened (for example
mcp.tool_calledorpolicy.denied), when, and in which organisation; - who acted, as a user, service-account or system identifier, and for some events an email address (for example the member invited or offboarded, or the account a call went through);
- what it acted on, as a resource or member identifier;
- the IP address, user agent and request identifier of the request;
- for a tool call: the tool’s name, the arguments the agent sent, the decision (allowed, denied, flagged, or held for approval) and its reasons, the guard rule scores, how long the call took, and an error message if the call failed.
Arguments can contain personal data, such as the recipient and text of an email an agent asked to send. The audit log never contains secret values, tokens, refresh tokens or client secrets, and it does not store the content a tool returned to the agent.
Content passing through the gateway
When an agent calls a tool, Smartplane passes the request to the service your organisation connected and passes the response back to the agent. We do not store responses. Two narrow exceptions:
- Pinned items. If a guard rule is pinned to a specific item (for example one database or one project), Smartplane remembers the identifiers only of items it sees inside that pin in responses, so that later calls to them are recognised. It keeps at most 2,000 identifiers per pin, never titles or content, and each list expires 7 days after it was last updated. A pin itself stores the item’s identifier and the label an administrator confirmed.
- Tool lists. The list of tools an MCP server offers is cached for 5 minutes.
Skills
Skill files your organisation uploads, links or imports from GitHub are stored in Cloudflare R2, separately for each organisation, with a manifest of their versions.
Machine tokens and secret delivery
For each machine token we store its name, its allow-list, who created it, when it was last used and the IP address it was last used from. Each secret delivery is an audit event with the recipient, purpose, IP address and user agent, never the value.
Operational logs and telemetry
Our servers write operational logs to Cloudflare Workers Logs, which keeps them for up to 7 days. These logs and any traces are built not to contain secret values or tokens. We do not currently send telemetry to any other provider; if we add an observability provider, we will list it on our Subprocessors page first.
Website, dashboard and cookies
smartplane.dev sets no cookies, runs no analytics or advertising scripts, and serves its fonts itself. Cloudflare, which hosts the site, processes your IP address and request details to deliver pages and protect the site from abuse.
The dashboard at app.smartplane.dev uses one strictly necessary session cookie, which is HTTP-only and lasts up to 7 days, and stores your light or dark theme preference in your browser. We use no tracking cookies.
Command-line tool
The smartplane CLI stores the access token you give it in a file only your user can read (~/.config/smartplane/credentials.json, or %APPDATA%\smartplane on Windows). It sends no usage analytics.
When you contact us
If you email us, we keep your message, your email address and our reply.
How we use information
| Purpose | Data | Legal basis (GDPR and UK GDPR) |
|---|---|---|
| Provide the service: sign you in, show each person only what their grants allow, run your agents’ tool calls, apply your rules, deliver secrets your organisation made deliverable | Account, configuration, credentials, call content in transit | Performance of our contract with your organisation; for customer data we act on the organisation’s instructions |
| Keep the audit log your organisation relies on for security and compliance | Audit events | Performance of contract; our and your legitimate interest in security and accountability |
| Secure and operate the service: detect abuse, rate-limit, debug failures | Operational logs, IP addresses, request metadata | Legitimate interests in keeping the service secure and working |
| Communicate with you about the service, including security notices and changes to these terms | Name, email address | Performance of contract; legitimate interests |
| Answer your messages and sales enquiries | What you send us | Legitimate interests; steps before entering a contract |
| Comply with the law and enforce our terms | Whatever the obligation requires | Legal obligation; legitimate interests |
We do not use customer data to build advertising profiles, we do not sell it, and we do not use it to train AI models.
Google user data
This section applies when you sign in with Google, or when your organisation connects a Google Workspace integration (Gmail, Google Drive, Google Calendar or Google Sheets) to Smartplane so that its agents can use it.
What we access. When you sign in with Google, we receive your name and email address through WorkOS. When a Google account is connected to an integration, Smartplane receives an OAuth token for the permissions shown on Google’s consent screen. Smartplane uses that token only to perform the actions your organisation has enabled for that integration and granted to its members, when one of the organisation’s agents asks for that action. The permissions each integration requests are:
| Integration | Google permissions requested |
|---|---|
| Gmail | Send, read, compose and modify mail (gmail.send, gmail.readonly, gmail.compose, gmail.modify); your email address |
| Google Drive | See and manage Drive files (drive); your email address |
| Google Calendar | View calendars and manage events (calendar.readonly, calendar.events); your email address |
| Google Sheets | Manage spreadsheets (spreadsheets) and read or manage Drive files (drive.readonly, drive); your email address |
An organisation can narrow this further: an administrator chooses which actions an integration offers, and grants decide which members may use each one, down to permitted argument values. Smartplane does not read, scan or index your Google data in the background. One feature reads on an administrator’s request: when an administrator verifies a guard rule that names a specific item (for example “the Q3 folder”), Smartplane may run one read-only action through the gateway, as that administrator and subject to their grants and the organisation’s rules, to show them matching items to confirm.
How we use it. Google user data is used only to provide the user-facing feature your organisation set up: carrying out the requested action and returning the result to the agent that asked, checking the organisation’s guard rules before the action runs, and recording the call in the organisation’s audit log. To check a guard rule, the action’s arguments (for example an email’s recipient and subject) are sent to Cloudflare Workers AI; see AI and your data. Content Google returns, such as messages, files and events, is passed to the agent and not stored by Smartplane. The audit log keeps the arguments of each call, which for an email an agent sends can include its recipients and text.
What we do not do. We do not sell Google user data. We do not use it for advertising, retargeting or interest-based ads, or to determine creditworthiness. We do not use it to develop, improve or train AI or machine-learning models, ours or anyone else’s, and our AI provider does not train on it either. We do not transfer it to anyone except as needed to provide the service (to Cloudflare, which hosts and runs Smartplane), to comply with the law, or with your consent. Our staff do not read it unless you ask us to (for example in a support request), it is needed for security purposes such as investigating abuse, or the law requires it.
How we store it. OAuth tokens are encrypted with AES-256-GCM under a per-record data key, which is itself wrapped by a key-encryption key held as a Cloudflare Workers secret. Refresh tokens never leave Smartplane’s API service; the code that performs an action receives only a short-lived access token. Tokens never appear in audit data, logs or traces, and are never returned to agents.
How it is deleted. You can disconnect a Google account at any time from the integration’s Connection panel or from My connections in the dashboard. Disconnecting immediately stops all use of the token. A member’s own connection, including its encrypted token, is deleted at once. For an organisation-wide connection, the token is removed from the integration and marked deleted so that no part of the service can read or use it again; its encrypted record is erased when the organisation is deleted, or sooner if you ask us at privacy@smartplane.dev. Offboarding a member deletes their own connections. Disconnecting in Smartplane does not revoke the grant at Google; you can do that at any time at myaccount.google.com/permissions. Audit events about past calls are kept for the organisation’s audit retention period described below.
Limited Use. Smartplane’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
AI processing
Smartplane uses AI models in three places: to check each tool call against the rules that apply to it, to help administrators turn a rule written in plain language into a classifier prompt and test it, and, when turned on, to scan skills for risky instructions. All three run on Cloudflare Workers AI. Cloudflare’s Workers AI data usage terms say it does not use the content it processes to train AI models and does not keep inputs or outputs after it has answered a request. The models never receive secret values. The rule compiler never receives your member directory, and the call-time check receives a person’s email address only when a rule that judges that call names people. The full detail, including which fields are sent when, is on AI and your data.
How we share information
- Subprocessors. Cloudflare hosts and runs Smartplane, and WorkOS provides sign-in, SSO and directory sync. The current list, with what each does and where, is on our Subprocessors page.
- Services your organisation connects. When your agents call a tool, the request goes to the service your organisation connected (for example GitHub, Slack, Google or your own MCP server or database), with the credentials your organisation provided. Those services are chosen by your organisation, receive data at its direction, and handle it under their own terms. They are not our subprocessors.
- Within your organisation. Administrators with permission to read the audit log can see events about everyone in the organisation, including the arguments of their agents’ tool calls. Reviewers in an access review see members’ grants.
- Legal reasons. We may disclose information if the law requires it, to protect the rights, property or safety of our users or others, or to enforce our terms. Where we can, we will tell the affected customer first.
- Business transfers. If Smartplane is involved in a merger, acquisition or sale of assets, information may transfer as part of that deal, subject to this policy.
We do not sell personal data, and we do not share it for cross-context behavioural advertising.
International transfers
Cloudflare runs Smartplane across its global network, so data may be processed in the United States and in other countries where Cloudflare operates. WorkOS processes identity data in the United States. Where personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we rely on the safeguards in our providers’ data processing agreements, such as the European Commission’s Standard Contractual Clauses and the UK International Data Transfer Addendum, or on a provider’s certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions where applicable.
How long we keep information
| Data | How long |
|---|---|
| Audit events in the queryable log | For your organisation’s audit retention setting: 365 days by default, adjustable by an administrator between 365 days and 10 years. Events are removed from the queryable log only after Smartplane has confirmed they are in the archive. |
| Audit archive | Each day’s events are copied every night to write-once object storage (Cloudflare R2). Archives are not deleted automatically; we delete an organisation’s archive at its request after its subscription ends, unless the law requires us to keep it. |
| Account and membership records | While the organisation uses Smartplane. Offboarded members’ records are kept, marked offboarded, so that the audit history remains attributable, for as long as audit events that refer to them are kept. |
| Organisation configuration and skills | Until an administrator deletes them or the organisation is deleted. Skill versions are kept unchanged so that the version an agent used can always be identified. |
| Secrets | Until deleted. Deleting a secret takes it out of use immediately; its encrypted record is erased when the organisation is deleted. |
| A member’s own connected accounts | Deleted, with their encrypted credentials, as soon as the member disconnects, the member is offboarded, or the resource is deleted. |
| Identifiers of pinned items | 7 days after they were last seen |
| Cached tool lists; pending sign-in states | 5 minutes; 10 minutes |
| Operational logs | Up to 7 days |
| Database backups | Cloudflare D1 keeps a point-in-time history of our database so it can be restored, for up to 30 days. Data deleted from the database leaves this history within 30 days. |
| Emails you send us | As long as needed to deal with your message and any follow-up |
Deleting an organisation. To close an organisation and delete its data, an owner can write to privacy@smartplane.dev. We will confirm the request with the organisation, give it the chance to export its audit log, and delete its data within 30 days, apart from what remains in database backups until they expire and anything the law requires us to keep.
Offboarding a member. Removing a member, whether in the dashboard, through WorkOS or through the organisation’s directory, runs one process that switches off the membership, revokes the member’s personal access tokens and direct grants, removes them from every team and deletes their own connected accounts. Machine tokens they created belong to the organisation and stay active until an administrator revokes them; access reviews list them so that someone decides.
Security
We describe these measures in more detail on our security page. In short:
- Secrets and connected-account credentials are envelope-encrypted: each version is encrypted with AES-256-GCM under its own data key, and data keys are wrapped with AES key wrap by a key-encryption key stored as a Cloudflare Workers secret. Keys can be rotated and data keys re-wrapped. Plaintext is never stored or logged.
- By default a secret never leaves Smartplane and is usable only through gateway tools. The one exception is a secret an administrator explicitly marks deliverable, which can be fetched only through one endpoint, by a member with a current grant or a machine token that lists it; every delivery is audited and rate-limited. Gateway tools never return secret values to agents.
- Access tokens are stored only as SHA-256 hashes, expire after at most 90 days, and stop working when the membership ends.
- The audit log is append-only and hash-chained per organisation, with a single writer per organisation, so changes or gaps can be detected.
- Guard rules fail closed: if the classifier is unavailable and an enforcing rule applies, the action is denied.
- Nobody can approve their own approval request or review their own access.
Smartplane’s controls are designed around SOC 2. We are SOC 2-ready; we have not yet completed a SOC 2 audit. No system is perfectly secure, and we cannot guarantee that information will never be accessed or disclosed without authorisation. If we learn of a personal data breach that affects you or your organisation, we will notify you and the authorities as the law requires.
Your rights
Depending on where you live, you may have the right to access the personal data we hold about you, to correct it, to delete it, to receive a copy in a portable format, to object to or restrict our processing, and to withdraw consent where we rely on it. You can also complain to your local data protection authority; in the UK that is the Information Commissioner’s Office.
If your data is part of an organisation’s account, we process it for that organisation, so please send your request to the organisation’s administrator. If you contact us instead, we will pass your request to the organisation and help it respond. Some requests are limited by the audit log’s purpose: because the log is tamper-evident evidence that the organisation relies on, entries in it are not edited or deleted individually before the organisation’s retention period ends.
For data we control, write to privacy@smartplane.dev. We will respond within one month, or sooner where the law requires, and may need to confirm your identity first.
California residents
Under the California Consumer Privacy Act, as amended, you have the right to know what personal information we collect, use and disclose, to request its deletion or correction, and not to be discriminated against for exercising these rights. The categories we collect are described in Information we collect: identifiers (such as name, email address and IP address), commercial information about your organisation’s account, internet activity within the service (such as audit events), and the content of tool calls. We use them for the business purposes described above. We do not sell personal information or share it for cross-context behavioural advertising, and we do not use or disclose sensitive personal information except to provide the service. For customer data, Smartplane acts as a service provider to the organisation. You or an authorised agent can make a request by writing to privacy@smartplane.dev.
Children
Smartplane is a business service and is not directed to children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, contact us and we will delete it.
Changes to this policy
We will post any change on this page and update the date at the top. If a change materially affects how we handle personal data, we will tell organisation administrators by email or in the dashboard before it takes effect.
Contact
Questions or requests about privacy: privacy@smartplane.dev. Security issues: security@smartplane.dev.
