Account…
Explore add-ons

Privacy Policy

This Privacy Policy applies to all products provided by Zetomation, including Zeto Sheet Automation, Zeto Sheet Notification & Alerts, and Zeto Form Notification & Alerts, and Zeto Sign. We do not rent or sell your personal data. We use and disclose information as needed to deliver and support our products, including the publisher and delivery-service workflows described below.

Google API Services User Data Policy

Zetomation's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Zeto Sign dashboard and signing evidence

When signing evidence is enabled, we record submitted answers, the signature, form revision, submission action, server timestamps and observed IP address. Any signing disclosure presented in an earlier flow remains recorded with that response; the current sealed-signing form uses a drawn signature and Submit without that separate disclosure. The sealed-signing flow also records session opening, browser-reported signature actions and times, normalized browser information and publisher-enabled signer name/email fields. These details are self-reported, not verified, and are shared with the recorded publisher. Opening a session does not prove a document was read. IP addresses and email addresses do not establish legal identity. Historical records retain their original evidence and any actual mailbox-verification times.

Publishers can enable owner notifications and respondent delivery through Amazon SES. When available, Pro and Business publishers can opt into signed PDF emails sent to their verified publisher address; this does not require a respondent email. Respondent delivery defaults to confirmation email and publishers may turn it off; sending the complete signed PDF requires an active Pro or Business plan. If paid access ends, new responses receive confirmation only. Respondent delivery requires an address without OTP verification; check it carefully. The complete PDF contains answers, signature and completion evidence. Oversized attachments use a document-scoped private link valid for seven days. Forwarding the email or link shares access. These addresses are not enrolled in marketing. Suppression and sending limits apply; email delivery does not grant dashboard access.

For new responses after sealed-signing activation, we retain one privately stored PDF with its response, hashes and publication metadata. Authorized owners and email recipients receive the same stored bytes. Historical responses retain legacy generated PDF downloads; they are not backfilled or rewritten. Public verification compares a browser-calculated hash and exposes only integrity/reference information, never document contents or personal details. Sealed PDFs follow the existing support-managed response deletion policy and normal backup retention. Previously downloaded or emailed copies cannot be recalled by backend deletion.

Existing signature-image links remain public to preserve Google Sheets image links: anyone with a signature link may view that image. Treat those links as sensitive. For access, correction or deletion requests, contact support@zetomation.com. We verify authority and coordinate with the publisher; deleting a signature object can break linked Google Sheets images. These evidence reports are not certificate-backed digital signatures or independently trusted timestamps.

Google OAuth scopes we use

Our add-ons require specific Google permissions to function. The scopes below are listed separately for each add-on based on its Apps Script manifest.

Zeto Sheet Automation scopes

  • https://www.googleapis.com/auth/spreadsheets (Read and write spreadsheet data)
  • https://www.googleapis.com/auth/script.container.ui (Display add-on UI)
  • https://www.googleapis.com/auth/script.external_request (Call webhooks and external APIs)
  • https://www.googleapis.com/auth/script.send_mail (Send emails)
  • https://www.googleapis.com/auth/script.scriptapp (Create and manage automation triggers)
  • https://www.googleapis.com/auth/userinfo.email (Identify user)
  • https://www.googleapis.com/auth/forms (Trigger workflows from Google Form responses)
  • https://www.googleapis.com/auth/script.deployments (Create and update Apps Script deployments)
  • https://www.googleapis.com/auth/script.projects (Manage automation scripts)
  • https://www.googleapis.com/auth/script.locale (Read script locale settings)

Zeto Sheet Notification & Alerts scopes

  • https://www.googleapis.com/auth/script.container.ui (Display add-on UI)
  • https://www.googleapis.com/auth/spreadsheets (Read and write spreadsheet data)
  • https://www.googleapis.com/auth/userinfo.email (Identify user)
  • https://www.googleapis.com/auth/script.scriptapp (Create and manage notification triggers)
  • https://www.googleapis.com/auth/script.send_mail (Send notification emails)
  • https://www.googleapis.com/auth/forms (Trigger alerts from Google Form responses)
  • https://www.googleapis.com/auth/script.deployments (Create and update Apps Script deployments)
  • https://www.googleapis.com/auth/script.projects (Manage notification scripts)
  • https://www.googleapis.com/auth/script.external_request (Call webhooks and external APIs)

Zeto Form Notification & Alerts scopes

  • https://www.googleapis.com/auth/forms (Read form data and trigger workflows)
  • https://www.googleapis.com/auth/script.container.ui (Display add-on UI)
  • https://www.googleapis.com/auth/script.send_mail (Send Apps Script emails)
  • https://www.googleapis.com/auth/script.scriptapp (Manage workflow triggers)
  • https://www.googleapis.com/auth/script.external_request (Call approved external services)
  • https://www.googleapis.com/auth/userinfo.email (Identify user)

For additional information about how these permissions are used by this add-on, see Zeto Form Notification & Alerts Privacy Policy.

Zeto Sign scopes

  • https://www.googleapis.com/auth/forms.currentonly (Read and update the current Google Form)
  • https://www.googleapis.com/auth/script.external_request (Sync forms with Zetomation and load signed responses)
  • https://www.googleapis.com/auth/script.container.ui (Display sidebar and response dialogs)
  • https://www.googleapis.com/auth/userinfo.email (Identify the form owner)

Information we collect

  • Personal information: Email addresses captured via Google Sign-In for authentication and subscription management.
  • Zetomation add-on onboarding information: The verified Google account email, or the effective Google account email exposed by the Apps Script execution when authorization is required, plus add-on source, authorization status, locale, first/last-seen timestamps, and welcome-email delivery status needed to operate and support the add-on.
  • Account information: Subscription status, plan validity, and renewal history.
  • Log/activity data: Anonymous execution metrics (e.g., runtime, error rates) to improve reliability.
  • Zeto Sign form and submission data: When you use Zeto Sign, we process the Google Form title, description, question schema, Google Form identifiers, generated signing link metadata, signer answers, signature image data, and signature URLs needed to create and return signed submissions.

How we use the information

  • Service delivery: Identify accounts and enforce plan limits.
  • Support: Investigate outages, debug issues, and improve performance.
  • Communications: Send critical updates about service changes or new features.
  • Zeto Sign signing workflows: Render hosted signing forms, store signed submissions, upload signature images, show signed responses to the form owner, and submit the signed response back into the connected Google Form when available.

Data Sharing, Transfer, and Disclosure

Zetomation strictly protects your Google user data. We do not sell, rent, trade, or disclose any raw, aggregated, or anonymized Google Workspace user data to any third parties, including data brokers, advertising networks, or third-party AI/ML model training services.

For hosting and operating Zeto Sign, we share necessary data with our secure, trusted cloud infrastructure providers (such as our secure database and web hosting services) strictly limited to what is technically necessary to host, operate, and maintain the Zeto Sign application. These infrastructure partners are bound by strict confidentiality obligations and are absolutely prohibited from accessing or using your Google data for their own purposes.

Zeto Sign billing

Website accounts can use Google or email and password. Supabase Auth manages passwords, confirmation and recovery; Zetomation does not maintain a separate password database. We use Cloudflare Turnstile for authentication abuse protection and AWS SES to deliver account emails. Optional display name and organisation details are stored privately with your account. A connected, verified Google publisher identity—not a matching email address or profile field—controls form access. Respondent confirmation emails are separate from website account verification.

When you choose a paid plan, Dodo Payments processes the purchase as merchant of record. We share the purchasing owner's account email and an internal billing reference to create checkout. Dodo Payments collects payment and tax details directly; we do not store card numbers. We retain limited customer, subscription, transaction and payment-status identifiers to manage access, invoices, cancellation and reconciliation. Form answers, respondent emails, signature images and signing evidence are not sent to Dodo Payments.

We associate usage with the owner's verified Google identity. The private usage ledger contains response and form identifiers, account references and timestamps—not copies of answers or signatures. These billing records are kept separately from response retention so deleting a response does not reset usage. Billing notices are separate from per-form response notifications and respect delivery suppression and safety limits. Contact support@zetomation.com about retention or deletion; records required for accounting, disputes or applicable law may need to be retained. See Dodo Payments's privacy notice for its handling of billing information.

Add-on Onboarding and Zeto Sign Data Handling

Account onboarding

When an eligible Zetomation add-on is opened, Zetomation may receive the effective Google account email from a privacy-safe Apps Script execution event before authorization, or verify the account through the authorized OAuth token after consent. We store limited identity, authorization, onboarding, and welcome-delivery metadata in our secure database. Zetomation sends one getting-started email through Brevo after an idempotent server-side delivery claim and stores only safe status, attempt, and provider-code information for support and retry diagnosis.

Installing a Zetomation add-on from Google Workspace Marketplace on desktop or mobile without opening or executing the add-on does not expose an install callback or account email to Zetomation, so no onboarding email is sent from a silent installation alone.

1. Data Accessed via Google APIs (The Add-on)

When a form owner syncs a form using the Zeto Sign Google Workspace Add-on, we utilize Google APIs to read the specific form's schema (question titles and types) and metadata (form ID and owner email). This data is stored securely on Zetomation-controlled servers strictly for the purpose of rendering a mirrored, hosted signing page. The Add-on does not read, access, or store form responses from your Google account.

2. Data Collected via Zetomation (The Web App)

When a signer visits the Zetomation-hosted signing link, the submitted answers and drawn signature are collected directly by our web application. Signature images are uploaded to Zetomation-controlled storage and hosted via a public URL. Zetomation then acts as a proxy, securely posting the respondent's standard answers and the signature URL back to the original Google Form so that the connected Google Sheet can receive a standard response row.

3. Google API Limited Use Disclosure

Zeto Sign'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.

Data security & limited use

We rely on Google's infrastructure for Google Workspace add-on execution and use secure backend infrastructure for Zeto Sign's hosted signing pages, response APIs, database records, and signature storage. Access to backend service credentials is limited to server-side systems needed to operate the service. We adhere strictly to Google's Limited Use requirements.

Data retention and deletion

Configuration and submission data is kept only as needed to provide the service, support users, maintain reliability, and meet legal or security obligations. Form owners can remove Google-side data by deleting the source Google Form or linked Sheet. To request deletion of Zetomation-hosted Zeto Sign records or signature files, contact us at the email below.

Contact us

Questions about this policy? Email us atsupport@zetomation.com.