Legal
Privacy policy
Last updated 6 October 2026.
Who we are
SmashSSO is operated by SmashSSO, LLC (“we”, “us”). This policy explains what personal data we process when you use smashsso.com and the SmashSSO application. Contact: [email protected].
What we collect
- Account data. When you sign in: your name, email address and profile picture. Your company's workspace is identified by your email domain.
- Directory data. If your workspace owner connects Google Workspace, a read-only copy of your company's user list: each person's name, primary email address, job title, department, profile picture and whether their account is suspended. See “Google user data” below.
- Tool data. For each tool you add: its roles, and its members' names, email addresses or usernames and roles. If you choose to add an API token for a tool, we store that token. For tools operated through the browser extension we do not collect or store your session in the tool, your password or your two-factor codes.
- Extension data. For each browser you pair: a name for it, the extension version, when it last checked in, and a hash of its pairing token. While a run is in progress, the extension sends us the content of the tool page it is working on.
- Activity data. A record of the changes you request, the steps taken to carry them out, and screenshots of the tool's admin pages taken during a run.
- Billing data. Which plan your company is on and whether it is paid up. Card details are entered on Stripe's pages and never reach us.
- Technical data. Standard server logs such as IP address, browser type and timestamps.
How we use it
To provide the service: to show who has access to what, and to add, change and remove access when you ask. To keep the service secure, to take payment, to send you alerts you have turned on, and to answer your messages.
When a run on a tool fails, we keep a record of the steps it took, with the name and email address of the person it concerned removed, and use it to improve the directions our agent follows for that tool.
We do not sell personal data and we do not use it for advertising.
Google user data
SmashSSO asks Google for two things, at two separate moments.
- Signing in with Google shares your name, email address and profile picture, and nothing else.
- Connecting Google Workspace is a separate step that only a workspace owner can start, and that a Google Workspace administrator must approve. It asks for one permission: to see information about the users on your domain (
admin.directory.user.readonly).
What we read. With that permission we list the users of your own Google Workspace domain: when the owner connects it, once a day after that, and each time an admin presses Sync. From each user we keep the name, primary email address, job title, department, profile picture address and whether the account is suspended. We do not read or keep passwords, recovery details, phone numbers, addresses, aliases or groups. The permission is read-only: we cannot create, change, suspend or delete users in Google Workspace, and we request no permission that would allow it.
What we use it for. To show your people in SmashSSO so that your admins can give, review and remove their access to your tools, and to tell your admins when someone has been suspended or deleted in Google Workspace and still has access elsewhere. For nothing else.
Who sees it. Your company's own SmashSSO admins. It is processed for us by the service providers listed below, only to run the service. When you ask for someone to be added to or removed from a tool, that person's name and email address are passed to our agent, and so to the AI model behind it, so that it can find them or type them into that tool.
Limits we keep to. SmashSSO's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- We use Google user data only to provide the features described here.
- We do not sell it, and we do not use it for advertising, for credit decisions or to build profiles of people.
- We do not use it to develop, improve or train generalised AI or machine-learning models.
- Nobody at SmashSSO reads it, unless you ask us to in order to help you, it is needed for security or to comply with the law, or it has been aggregated and anonymised.
How it is protected. Google user data is sensitive, and we protect it in these ways. It is encrypted in transit: we fetch it from Google over TLS, and it only ever travels between your browser, our servers and our database over TLS. It is encrypted at rest: the database it is stored in, and that database's backups, are encrypted. The token Google gives us, which is what allows us to read your directory, is encrypted a second time by the application itself, with AES-256-GCM, before it is stored, and the key is kept outside the database. Access is restricted: only signed-in admins of your own workspace can see your directory, and every request is checked against the workspace it belongs to. The full list of safeguards is under “How we protect your data” below, and all of it applies to Google user data.
Storage and removal. The token Google gives us is encrypted before it is stored. A workspace owner can disconnect Google Workspace in Settings at any time: we revoke our access with Google and erase the token. You can also remove SmashSSO from your Google Account's third-party access page. People already imported stay in your workspace until you remove them or ask us to delete the workspace.
Who processes data for us
- Vercel hosts the application and passes the agent's requests on to the AI model.
- PlanetScale hosts the database.
- Clerk handles sign-in and sessions, and holds your name, email address and profile picture for that purpose.
- Google provides sign-in with Google and, if you connect it, your Workspace directory.
- Anthropic provides the AI model that operates tools' admin pages. Page content and screenshots from those pages, which can include your team's names and email addresses, are sent to it during a run. Under its commercial terms it does not use them to train its models.
- Perplexity runs web searches of tools' public help pages when we improve our agent's directions for a tool. It receives search queries about the tool, not your account or directory data.
- Stripe takes payments and holds your card and billing details.
- Cloudflare provides DNS and sends alert emails.
How we protect your data
These safeguards apply to all the personal data described in this policy, including sensitive data: Google user data, the tokens that give access to your Google Workspace directory and to your tools, and the names and email addresses of your team.
Encryption in transit
Everything sent between your browser, the SmashSSO extension and our servers travels over HTTPS (TLS). Plain HTTP requests are redirected to HTTPS, and browsers are told to use HTTPS only (HSTS). Our servers connect to the database over TLS and verify its certificate. Requests to Google and to the other providers listed above are made over TLS.
Encryption at rest
The database and its backups are encrypted at rest by our database provider. On top of that, the most sensitive values, your Google refresh token and any API tokens you give us for your tools, are encrypted by the application with AES-256-GCM before they are written to the database. The encryption key is held in the application's encrypted environment settings, never in the database and never in our source code.
Secrets we only keep as hashes
The token that pairs a browser with your workspace is stored as a one-way hash, so it cannot be read back from the database.
Credentials we never hold
We do not store passwords: sign-in is through Google. We do not collect or store your sessions in your tools, or the passwords and two-factor codes you use for them.
Access control
Only admins sign in to SmashSSO. Every request is checked for a signed-in admin and limited to that admin's own workspace, so one company cannot reach another's data. A workspace belongs to one email domain; colleagues can join only when its owner invites them. Only the owner can connect or disconnect Google Workspace.
Least privilege
We ask Google for read-only access to your user directory and nothing more, and we keep only the fields listed in this policy.
Restricted access on our side
Access to our production systems and database is limited to the people who need it to run the service. Nobody at SmashSSO reads your data unless you ask us to in order to help you, or it is needed for security or to comply with the law.
Protection against forged requests
Our API refuses changes sent from any website other than our own, checks the pairing token on every request from the extension, verifies the signature on every message it receives from Clerk and Stripe, and sends standard security headers with every response.
Less data in records we keep
When we keep a record of a failed run to improve our agent, the name and email address of the person it concerned are removed first.
Removal
Disconnecting Google Workspace revokes our access with Google and erases the token at once. Deleting a tool's API token or unpairing a browser erases it at once. You can ask us to erase your whole workspace, as described under “Retention”.
If something goes wrong
If we learn of a security incident that affects your data, we tell your workspace owner by email without undue delay, with what happened and what we are doing about it.
No system is perfectly secure. The security page says in more detail what we hold, how it is protected and where the limits are. To report a security problem, write to [email protected].
Retention
We keep your data while your workspace exists. When you remove something in SmashSSO, such as a tool, an admin or a bundle, it disappears from the app and its record is kept, marked as removed. Secrets are not kept: deleting a tool's API token, removing the tool, disconnecting Google Workspace or unpairing a browser erases the token or pairing at once. You can ask us to erase your workspace and all of its data for good at any time by writing to [email protected]; we do so within 30 days.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to or restrict its processing. Write to [email protected] and we will respond within 30 days. If you are an employee whose data appears in a customer's workspace, please contact that customer first; we act on their instructions.
Changes
If we change this policy in a way that matters, we will tell workspace owners by email before the change takes effect.