Security
It works in your browser, as you. Here is what that means.
SmashSSO changes access inside your tools as the admin account you are signed in with, through an extension in your own Chrome. That is a lot of trust, so this page says plainly what we hold, how it is protected, and where the limits are.
What we hold
- API tokens
- For tools you chose to connect by API, we store the token you gave us.
- A pairing token per browser
- When you pair a Chrome with the SmashSSO extension, we store a hash of the token that browser uses to check in. It identifies the browser; it cannot log in to any of your tools.
- A Google refresh token
- Read-only access to your Workspace user directory, so we can keep your list of people current.
- Your access data
- People, tools, roles, who has what, and a log of every run and change.
What we never hold
- Your sessions in your tools
- Tools are driven in your own Chrome, by our extension, in tabs where you are already signed in. Your cookies stay in your browser. We do not copy or store them.
- Your passwords
- If a tool is signed out, the extension asks you to log in yourself, in that tab. You type into the tool's own page. We do not record keystrokes, and the extension steps back while you log in.
- Your 2FA codes or seeds
- Same. You complete 2FA yourself.
- Your employees' credentials
- Employees never sign in to SmashSSO and we never log in as them.
How it is protected
- Encrypted in transit
- Everything between your browser, the extension, our servers and our database travels over TLS. Plain HTTP is redirected to HTTPS.
- Encrypted at rest
- The database and its backups are encrypted at rest. API tokens and the Google refresh token are also encrypted with AES-256-GCM before they reach the database. The key lives in the application's environment, not in the database.
- Each company sees only its own data
- Every request is checked for a signed-in admin and limited to that admin's workspace.
- Work happens where you can see it
- Each run gets its own tab, in a tab group labelled SmashSSO. Chrome shows a “started debugging this browser” bar while the extension is working. The tab closes when the run ends.
- Only paired browsers
- The extension only takes instructions from SmashSSO, and only after an admin has paired that browser from inside the app. You can unpair a browser at any time, from the app or from the extension.
- Only while Chrome is open
- Nothing runs when no paired browser is online. Changes wait in a queue and start when one is.
What the agent may do
- Only the task
- Each run has one job: read members, invite one person, change one role, or remove one person. The agent is instructed to do that and nothing else.
- Only its own tab, on the tool's own site
- The agent can read and act in the tab opened for the run. It cannot read your other tabs, your cookies or your saved passwords, and it is kept on the tool's own site.
- Nothing that costs money without you
- A step that would add a paid seat or touch billing pauses the run for your approval. Buttons that look like purchases are also blocked in code until you approve.
- Web pages are not instructions
- Text on a tool's page is treated as untrusted. The agent is told not to follow instructions it finds there.
- Everything is logged
- Each run records its steps and a final screenshot, and every change lands in an audit log you can read.
The limits
What you should know before you trust us.
Agents act as you
Changes appear in each tool's audit log under the account you are signed in with in Chrome. The extension can act on any site you are signed in to, which is what lets it work with any tool; we limit it to the tool's own site and the task you asked for.
Screens go to an AI model
To operate a tool, the agent sends what is on the admin page, as text and screenshots, to Anthropic's Claude models, by way of Vercel's AI Gateway. That can include names and email addresses of your team.
Agent limits are instructions plus guardrails
The rules above are enforced by how the agent is prompted and by checks in our code. That is strong, but it is not a formal guarantee that an AI model can never take a wrong step.
A breach of us would matter
Someone who took over our servers could send instructions to paired browsers while they are online, and could use stored API tokens. You can cut that off at any time by unpairing the browser or removing the extension, and by revoking the tokens.
Some tools forbid automation
A tool's terms may restrict automated use of its interface. Check the terms of what you connect. Where your plan includes a member API, you can add a token and we use that instead.
No certifications yet
SmashSSO, LLC has no SOC 2 or ISO 27001 report today. If you need one from a vendor, we are not there.
Found a problem? Write to [email protected].
Still here? Good. Try it.
Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.