Company
Privacy policy
Last updated 2026-11-18. This policy covers sig.surf, the Sig.Surf web app and the Sig.Surf for Gmail Chrome extension.
Google user data and Limited Use
Sig.Surf'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.
- What we access. With the authorization of your Google Workspace super admin, Sig.Surf reads user profile details from your Google Directory (such as name, email address, job title, phone number and department) and, if the admin also grants it, group names and members. Sig.Surf then writes the signature of each mailbox in the domain through the Gmail settings API.
- What we do not access. Sig.Surf does not read, send, delete or search email messages, and does not read contacts, calendar or Drive files. No mail is routed through Sig.Surf.
- How we use it. Only to provide the features you see in Sig.Surf: filling signature fields from your directory, showing the people and groups in your admin screens, and writing each person's signature to their Gmail settings.
- No advertising, no sale. We do not use Google user data for advertising, we do not sell it, and we do not transfer it to data brokers or advertising platforms.
- No AI training. We do not use Google user data to develop, improve or train generalized AI or machine-learning models. Directory data is not sent to the AI designer.
- Humans. Sig.Surf staff do not read Google user data, except where you ask for support and agree, where needed for security or abuse investigation, or where the law requires it.
- Transfers. We transfer Google user data only to the service providers listed on the subprocessors page that host or run Sig.Surf, only as needed to provide Sig.Surf, and only as the Limited Use requirements permit.
Data we collect
| Data | Where it comes from | Why |
|---|---|---|
| Name, email address and profile picture | Sign in with Google (scopes openid, email, profile) | To create and secure your account. Sig.Surf stores no passwords. |
| Sign-in tokens and session details (including IP address and browser type) | Sign in with Google and your browser | To keep you signed in and protect your account. |
| Employee records: email address, directory fields (name, title, phone, department and similar), group membership | Your Google Directory (read-only), or entered by your admin or by the employee | To fill in signatures and decide who gets which template. |
| Signatures, templates, brand details, rules, campaigns, surveys | You | To design, assign and deploy signatures. |
| Images you upload or make with our tools (photos, logos, banners, handwritten sign-offs) | You | To show them in signatures. Sig.Surf re-encodes each image and removes embedded metadata such as camera details and location before storing it. Stored images have a public address that cannot be guessed, because mail programs must be able to load them. |
| Deployment records: which signature was pushed to which mailbox, a hash of it, time and any error | Sig.Surf | To skip unchanged signatures and to show you what happened. |
| Signature engagement: impressions, clicks and survey ratings and comments, with the campaign, link, employee and department they relate to | People who open or click a signature, or answer a survey | To show campaign and survey results. Recipients' IP address and browser type are used only to limit abuse and ignore automated traffic; survey responses keep a keyed hash, not the address. |
| Billing details | You, through Stripe | To charge for paid plans. Sig.Surf stores Stripe identifiers, plan and seat counts, not card numbers. |
| Prompts, images and survey comments you send to an AI feature | You | To produce a signature design or a survey summary. |
| Product analytics events (page views and actions, never signature content, names or email addresses) | Your browser and our server, only if you accept analytics | To see which parts of Sig.Surf are used. |
The Chrome extension
- The Sig.Surf for Gmail extension runs only on mail.google.com. It reads the compose window to decide whether a message is new, a reply or a forward (from the subject prefix and whether the message has a quote), and, if your plan has signature rules, the domains of the recipients. It never reads or stores message bodies. Recipient addresses are reduced to domains in memory and are not stored or sent.
- It fetches your signatures from sig.surf and keeps a copy in the browser's extension storage so that Gmail works offline. It contacts no other server.
- The extension's use of information received from Google APIs follows the same Limited Use commitments as above; the extension itself calls no Google API.
Who receives data
Sig.Surf shares data only with the companies that run it, listed with their purpose and location on the subprocessors page: Vercel (hosting and storage of uploaded images), the managed database provider, Stripe (payments), Anthropic (AI designer and survey summaries), PostHog (product analytics, only if you accept) and Google (the APIs you authorize). We do not sell personal data and we do not share it for advertising.
Cookies and analytics
- Sig.Surf sets a session cookie so you stay signed in. It is needed for the product to work.
- Product analytics (PostHog) run only after you accept them in the banner, and not at all if your browser sends Do Not Track or Global Privacy Control. This covers both what your browser sends and the few account events our servers record (signing up, a first installation, sending invitations). Autocapture and session recording are off. You can change your choice from the page footer.
- A small cookie remembers your answer to the analytics banner so that our servers can follow it. It holds only "granted" or "denied".
Retention and deletion
- We keep account and workspace data while your account is open. Unclaimed anonymous signatures and old job history are deleted automatically.
- Remove Sig.Surf's access at any time in the Google Admin console (Security, API controls, Domain-wide delegation). Sig.Surf can no longer reach any mailbox in the domain. Signatures already written stay in Gmail until you change them.
- To delete your account or workspace, or to ask for a copy of your data, email privacy@sig.surf. We delete it within 30 days unless the law requires us to keep it, for example billing records.
Security
Data is encrypted in transit with HTTPS. See the security page for what we do and do not hold; in particular, SOC 2 is in progress and Sig.Surf holds no certification.
Your rights and children
Depending on where you live you may have rights to access, correct, delete, export or object to the use of your personal data. Write to privacy@sig.surf. Sig.Surf is for businesses and is not directed at children under 16.
Changes and contact
We will post changes here and change the date above; for material changes we will tell workspace owners by email. Questions: privacy@sig.surf.
This page is also available as Markdown.