# Security

Source: https://sig.surf/security (Markdown version of the page)

What exists today, in plain words. Where something isn't done yet, this page says so.

## Compliance status

- **SOC 2: in progress.** No report has been issued.
- Sig.Surf holds no security certification today. We will not describe Sig.Surf as certified or compliant with any standard until a report or certificate exists.
- **Google OAuth verification:** `gmail.settings.basic` is a restricted Google scope, so Google reviews apps that use it and may require an independent security assessment. We will publish the status here when it is complete.
- Sig.Surf's use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. See the [privacy policy](https://sig.surf/privacy).

## What access you grant

- A Google Workspace super admin authorizes Sig.Surf through domain-wide delegation. Nobody shares a password.
- Two scopes: `gmail.settings.basic` to write each user's send-as signature, and `admin.directory.user.readonly` to read users. Sig.Surf's Gmail code calls only the send-as endpoints (list a user's send-as addresses and update the signature).
- One optional scope: `admin.directory.group.readonly`, only if you want Google groups synced. Without it, users still sync.
- Sign in with Google asks only for your basic profile (`openid`, `email`, `profile`).
- Sig.Surf does not request access to read, send or delete messages, and no mail is routed through Sig.Surf.
- Revoke access at any time in the Admin console. After that Sig.Surf cannot write to any mailbox in the domain.

## How it is built

- **Sign in with Google only.** Sig.Surf does not store passwords. There is no other sign-in method.
- **No per-customer Google secret.** One Sig.Surf service account serves every customer. Each customer's grant is the admin's authorization, which the admin can revoke.
- **Tenant separation.** Every record that belongs to a customer is tied to that customer's organization, and every query filters by it.
- **Safe signature output.** Signatures are built from a structured document, not raw HTML, and links or images with a missing or unsafe address are dropped before the signature is rendered.
- **Deployment records.** Sig.Surf records each deployment and a hash of what was pushed, and skips unchanged signatures.
- **Hosting.** The web app runs on Vercel with a managed Postgres database. Everyone who processes customer data is listed on the [subprocessors page](https://sig.surf/subprocessors).
- **Chrome extension.** It runs only on mail.google.com, reads no message bodies and talks only to sig.surf.

## Not available yet

- Single sign-on other than Sign in with Google, role-based permissions beyond owner and admin, and an audit log are not available.
- There is no published uptime SLA.
