Privacy Policy

1. Who we are

Signatoro is operated by SecOne Inc., a Delaware C Corporation. We are the data controller for the personal data described in this policy. This policy explains what we collect when you visit signatoro.com or use the Signatoro service, why, and the choices you have.

2. What we collect

• Account data: your name, email address and password (stored as a hash), and, if you sign in with Google, the profile information Google shares with us.
• Content you provide: the data, documents and settings you create or upload while using the service.
• Billing data: plan, invoices and payment status. Card details are collected and stored by Stripe, our payment processor, not by us.
• Usage and device data: pages visited, actions taken in the service, browser type, approximate location derived from IP address, and error logs. We also count visits from known search engine and AI crawlers by their user agent and the page they fetched; these counts are not linked to any person.
• AI assistant connections: when you connect an AI assistant (such as Claude or ChatGPT) to your account, we keep the name the assistant registered with, the addresses it may return to after you approve it, a one-way hash of the IP address it registered from, one-way hashes of the codes and tokens we issue to it (never the codes or tokens themselves), when you approved it, when it last renewed its access, and whether you revoked it.
• API keys and usage: a one-way hash of each API key you create (never the key itself), its first characters so you can tell keys apart, and when it was created, last used and revoked. We count the signatures served to your account each calendar month, to apply your plan's limits.
• AI agents: the AI assistants you create and, for a company, the AI agents its owners create: the agent's name, role line, optional reply and contact email addresses, its disclosure line, whether it signs as a person or as itself and, for a company agent, the member it acts for. An agent is visible to the person who created it, the company's owners and the member it acts for.
• Signature requests: each time an assistant, agent or tool fetches your signature, we record which tool or endpoint served it, how it connected, the assistant's registered name and id, the signature's mode, your plan, your account id and, if an agent's signature was served, the agent's id. We never receive the email the signature goes on: not its text, subject or recipients.
• Ad click data: if a link from one of our ads brought you here, its click ID and campaign details (such as the campaign and the search term). With advertising cookies on we keep them in a cookie for 90 days, and when you create a company or pay we store them with your company and your payment record.
• Zoho Mail connection: only if you connect Zoho Mail to install your signature there. We keep the address you send from, your Zoho data center, the tokens Zoho issues (encrypted, AES-256-GCM, under a key used only for them), the id of the signature we add, and the time and any error of our last update. We read your Zoho Mail account details to find the address you send from, and your list of signatures to find ours. We never read your email or contacts, and the only signature we write is the one we added.
• Google Workspace connection: only if your company's Google Workspace administrator installs Signatoro for your domain. We keep the domain, the administrator account that installed it, and the time and any error of our last update for each person. Through Google's Directory API we read the people in the domain (name, email address and aliases) to match them to your company's Signatoro members, and, for the fields your company chooses, each member's name, job title, phone number and photo, which we store in their signature (the photo as a copy on our image host). We never read recovery email addresses or phone numbers, and we never write to the directory. If you are in your company's Google directory without a Signatoroaccount, we keep your work address and those details so your company can manage your Gmail signature; you get no account and no email from us unless your company invites you. Through the Gmail API we read and write only the signature setting of each member's send-as addresses. We never read, send or store email, contacts, calendars or files.
• Communications: emails you send us and transactional emails we send you (sign-up confirmation, password resets, invitations).
• Cookies: see our Cookie Policy for the exact cookies and how to control them.

3. How we use it, and on what legal basis

• To provide the service you signed up for, including authentication, storing your content and billing (performance of a contract).
• To install and update your signature in Zoho Mail, only if you connect it: we add a signature named “Signatoro” to your Zoho Mail and write each later change to it (performance of a contract). We use the data Zoho gives us only for this.
• To install and update signatures in Gmail for a company, only if its Google Workspace administrator installs Signatoro: we write each member's Signatoro signature into their Gmail signature setting, and write it again when it changes (performance of a contract with the company). We use the data Google gives us only for this.
• To serve your signature to the assistants, agents and tools you connect, together with your contact details as structured facts and any agent's disclosure line, so they can sign and write your email with your saved details (performance of a contract).
• To apply plan limits and protect connections: counting signature requests, enforcing limits on agents, and keeping connection and API key records so you can see and revoke them and we can detect misuse (performance of a contract and legitimate interests).
• To keep the service secure: fraud prevention, abuse detection, logging and backups (legitimate interests).
• To understand and improve the service through analytics and session replay (legitimate interests; analytics cookies only with your consent). Replays mask what you type and leave out your signatures, and you can turn them off at any time in Cookie settings.
• To understand how signatures are used: the signature request records above are sent from our servers to PostHog, without cookies, so we can see which assistants, tools and plans the service works for, and which pages search engines and AI crawlers read (legitimate interests). You can object at any time by emailing us.
• To measure our advertising: which ads lead to sign-ups and paid plans, and showing our ads to people who visited our site, through the Google Ads tag (consent where consent is required; elsewhere legitimate interests, with a way to opt out - see the Cookie Policy).
• To communicate with you about your account and changes to the service (performance of a contract / legitimate interests). Marketing email is sent only if you opt in, and every message has an unsubscribe link.
• To comply with law, including tax and accounting obligations (legal obligation).

4. Who we share it with

We do not sell personal data. We share it only with processors that help us run the service, under contracts that restrict their use of it:

• Supabase (database, authentication and file storage; hosted in the United States, us-east-1).
• Vercel (application hosting, DNS and edge network).
• Stripe (payments and invoicing).
• Resend (transactional email delivery).
• Google Analytics, Microsoft Clarity and Ahrefs Web Analytics (site analytics and session replay, loaded only after you accept analytics cookies).
• Google Ads (advertising measurement and ad audiences, only while advertising cookies are on). When you buy a plan, it may also receive your email address as a one-way SHA-256 hash, made in your browser, used only to match the purchase to an ad click.
• PostHog (product analytics, error reporting, session replay and the support chat and support email inbox, hosted in the EU; analytics run without cookies until you accept analytics cookies, replay stops when you turn analytics off, and both reach PostHog through our own domain). It also receives the signature request records and crawler counts described above, sent from our servers. Support messages are stored with the pages you visited and errors you ran into, so we can see what went wrong.
• Cloudinary (hosting the images you add to a signature, such as a photo or logo, at a public address so mail apps can show them).
• Slack (internal notifications to our team, including the email address of each new sign-up).
• Google, if you choose to sign in with your Google account.
• Zoho, only if you connect Zoho Mail: we send your signature to your own Zoho Mail account through Zoho's API. Zoho handles it under its own privacy policy.
• Google Workspace, only if your administrator installs Signatoro: we send each member's signature to their own Gmail settings through Google's API.

AI assistants and tools you connect. When you connect an AI assistant (for example Claude or ChatGPT) or give an API key to an agent or tool, we send it what it asks for on your behalf: your signature, and the details in it as structured facts (name, title, company, email, phone, website, LinkedIn and booking link) so it can use them in your email. If you own a company, an assistant you connect can also read and change the member details you manage. You choose these assistants and tools, and their providers handle the data under their own terms and privacy policies, not as our processors. Revoking the connection or the key stops further requests; it does not delete what the provider already received.

We may also disclose data when the law requires it, to protect our rights or the safety of users, or as part of a merger, acquisition or sale of assets, in which case this policy continues to apply to your data.

5. International transfers

Our servers and most of our processors are in the United States. If you are in the European Economic Area, the United Kingdom or Switzerland, your data is transferred to the United States under the processors' Standard Contractual Clauses or an equivalent lawful mechanism, and we take reasonable steps to protect it in line with this policy. Our team may access your data from Israel to run and support the service; the European Commission recognizes Israel as providing an adequate level of data protection. The AI assistants and tools you connect receive your data wherever their providers operate, under those providers' own terms.

6. How long we keep it

• Account and content data: for as long as your account exists. When you delete your account, we delete or anonymize it within 30 days, except where we must keep it longer.
• Billing records: 7 years, to meet tax and accounting rules.
• Server and security logs: up to 90 days.
• Analytics data, including signature request records: per the retention settings of each analytics provider, currently up to 14 months for Google Analytics.
• Ad click data: 90 days in the first-visit cookie; stored with your company and payment records for as long as those are kept.
• AI assistant connections: each approval lasts until you revoke it or until it goes 30 days unused, and the access it hands out expires within an hour unless renewed. When a connection is revoked or expires, its records are deleted automatically about a day later; an assistant registration with no connection left is deleted 30 days after it was registered, except one registered with a secret by a platform we connect with directly, which stays until we remove it.
• API keys and monthly usage counts: for as long as your account exists, revoked keys included, as hashes only.
• AI agents: until you, or for a company agent a company owner, delete the agent or the account. Deleting an agent also deletes its API keys and connection records at once.
• Zoho Mail connection: until you disconnect it or delete your account. Disconnecting revokes the access at Zoho and deletes what we stored; the signature stays in your Zoho Mail. You can also revoke the access in your Zoho account under Connected Apps.
• Google Workspace connection: until the administrator uninstalls Signatoro or the company deletes its account. We then delete what we stored about the connection within 30 days; the details already filled into a member's signature stay there as theirs to edit, and the signatures stay in Gmail. The administrator can also remove the access in the Google Admin console.

Google user data. Signatoro'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. We use Google user data only to provide and improve the signature features you or your administrator turned on, never for advertising, and we do not sell it, transfer it to others except as needed to run that feature or as the law requires, or let people read it except with your permission, for security or as the law requires.

7. Security

Data is encrypted in transit (TLS) and at rest by our hosting providers. Access to production systems is limited to staff who need it and protected by multi-factor authentication. No system is perfectly secure; if we learn of a breach affecting your data we will notify you and the relevant authorities as the law requires.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal data, to object to or restrict certain processing, and to withdraw consent at any time (which does not affect processing already done). You can change or delete most account data yourself in account settings. On your Connect page you can see the AI assistants connected to your account and revoke one, or all of one app's, at any time, and revoke an API key. You can delete an AI assistant you created, and a company owner can delete the company's agents. You can withdraw analytics or advertising consent at any time with Cookie settings (see the Cookie Policy). For anything else, email us at the address below; we respond within 30 days. You also have the right to complain to your local data protection authority. California residents have the rights set out in the CCPA/CPRA, including to know what we collect and to request deletion. We do not sell personal data. While advertising cookies are on, the Google Ads tag shares data about your visit with Google to measure our ads and show them to past visitors, which California law may treat as "sharing" for cross-context behavioral advertising. You can opt out at any time with Cookie settings or by sending a Global Privacy Control signal from your browser.

9. Children

The service is not directed to children under 16 and we do not knowingly collect their data. If you believe a child has provided us data, contact us and we will delete it.

10. Changes to this policy

We will post any changes here and update the date below. For material changes we will also notify you through the service or by email before they take effect.

11. Contact

Legal entity: SecOne Inc., a Delaware C Corporation (EIN 39-3563209), incorporated on July 31, 2025. SecOne Inc. owns and operates Signatoro.

Contact: ceo@signatoro.com
Website: signatoro.com
Response time: we aim to answer within two business days.