Company
Subprocessors
Last updated 2026-11-18. These companies process data on Sig.Surf's behalf. We will update this page before adding one.
| Provider | Purpose | Data it receives | Notes |
|---|---|---|---|
| Vercel | Hosting and serverless compute for sig.surf and the app; request logs | Everything the web app handles, in transit and in logs: requests, account and workspace data, IP addresses | Hosts the app. Application logs record error names and identifiers, not signature content. |
| Vercel (Vercel Blob) | Storing images you upload or make with our tools for signatures: photos, logos, banners and handwritten sign-offs | The uploaded images, after Sig.Surf has re-encoded them and removed embedded metadata such as camera details and location | Only when you upload an image, or choose to use one made with the banner maker or the handwritten sign-off tool, instead of pasting an address. Each image is served from a public address that cannot be guessed, so that mail programs can show it. Images uploaded without an account are deleted after 30 days unless a saved signature uses them. |
| Managed Postgres database provider (Neon, through the Vercel Marketplace) | Primary database | Accounts, workspaces, employees and their directory fields, signatures, templates, deployment records, engagement events, survey responses, billing identifiers | Customer data is separated by organization in every query. |
| Stripe | Payments and subscriptions | Name, email, billing details and plan and seat counts of paying workspace owners | Card details go to Stripe directly and are not stored by Sig.Surf. |
| Anthropic | AI designer (prompt or image to signature) and survey-comment summaries | The prompt, image or survey comments you submit, and optional brand details you enter | Directory data from Google is not sent. Only sent when you use an AI feature; an organization admin can switch the AI designer off. |
| PostHog | Product analytics | Pseudonymous event data (internal user and organization IDs, page and action names). Never email, name, domain or signature content | Only if you accept analytics and your browser sends no Do Not Track or Global Privacy Control signal. Session recording and autocapture are off. |
| Resend | Sending invitation emails | The invited person's email address and the invitation message, which names the organization and carries the one-time link | Only when an admin sends an invitation by email. Invitations can also be shared as a link, which sends nothing. |
| Google (Google Workspace APIs) | The APIs you authorize: Directory (read) and Gmail settings (write the signature); Sign in with Google | Directory profile fields and group membership; the signature HTML written to each mailbox | Google is the source of this data and the destination of signatures rather than a processor chosen by Sig.Surf. |
We do not use any provider to send you product email at this time. If that changes, the provider will be added here first.
Questions or objections: privacy@sig.surf. See also the privacy policy and the security page.
This page is also available as Markdown.