Last updated: 2026-10-01
Bulk Email & PDF Mail Merge has no server. It runs entirely inside your own Google account as a Google Apps Script add-on. No Google user data — no spreadsheet contents, no document contents, no email address, no recipient list — is ever sent to us or to any third party. The add-on talks to no server of ours; we run no analytics and no logging of your content. The only record we hold about anyone is the purchase record described under “Purchases and license keys” below, and it never comes from the add-on.
This is not only a policy commitment. The add-on's network access is restricted by an allow-list in its manifest, enforced by Google, to a single endpoint: Google's own Drive API, used to convert your document to PDF. It is technically incapable of contacting our servers or any other third party. See “Network access” below.
The add-on accesses only the following Google user data, and only while you are using it:
| Google user data | What exactly is accessed | Access |
|---|---|---|
| Google Sheets™ data — the spreadsheet the add-on is open in | The sheet names, the header row, and the cell values (as displayed) of the sheet you choose, including the recipient email addresses and the merge fields in each row | Read; and write to one status column |
| Google Docs™ data — the one template document you pick | The template's title and text, to find the {{placeholders}} in it |
Read only (the template itself is never modified) |
| Google Drive™ data — only files you pick or the add-on creates | The file ID and name of the template and the output folder you select in Google's file picker; the temporary copies and PDF files the add-on creates | Create, read, and delete the add-on's own files; read the template you picked |
| Email sending — through Apps Script's mail service | The messages the add-on composes from your sheet (recipient, subject, body, reply-to address you enter, PDF attachment), sent from your account; and the number of emails your account may still send today | Send only. The add-on cannot read, search, or modify any email in your mailbox |
The add-on does not access any other spreadsheet, any Drive file you did not pick
(or that it did not create), your Gmail™ inbox, your contacts, or your calendar. The Marketplace app
configuration also lists the userinfo.email and userinfo.profile scopes, but
the add-on's code never calls any API that reads your email address, name, or profile.
Google user data is used only to perform the mail merge you start, and for no other purpose:
Google user data is not transferred to us or to any third party, not sold, not used for advertising, and not read by any person other than you. Data obtained through Google Workspace APIs, whether raw or derived, is not used to develop, improve, or train generalized or non-personalized AI and/or ML models; the add-on contains no AI or ML features at all. The use and transfer of this data follow the Google API Services User Data Policy, including the Limited Use requirements (see below).
These mechanisms protect your Google user data, including sensitive data such as your recipients' email addresses and the contents of your sheet and documents:
https://www.googleapis.com/drive/v3/files/. Any
attempt to contact another server is refused by Google (see “Network access” below).drive.file limits Drive access to files you
pick or the add-on creates; spreadsheets.currentonly limits access to the one open
spreadsheet; script.send_mail can send but never read email. No restricted scope is
requested.These are the six scopes the add-on requests, together with the classification Google Cloud Console shows for each one.
| Permission requested | Google's classification | What it lets the add-on do | Why it is needed |
|---|---|---|---|
See, edit, create and delete only the specific Google Drive files you use with this
add-on (drive.file) |
Non-sensitive | Show Google's own file picker so you can select the document template and output folder, and create the temporary merged copies and the PDFs | Producing the documents is the product. Access is granted file-by-file through the picker selection itself — this scope cannot reach any file you did not pick, and cannot browse your Drive |
View and manage the spreadsheet this add-on is installed in
(spreadsheets.currentonly) |
Non-sensitive | Read the rows you want to send, and write a send status into one column of the same sheet | The rows are the input. The status column is how a re-run knows what already went out, so nobody is emailed twice. This scope cannot open any other spreadsheet |
Send email as you (script.send_mail) |
Sensitive | Send each merged PDF to the recipient named in its row | Delivery is the product. This scope can only send. It grants no ability to read, search, or modify your mailbox |
Display a sidebar inside Google Sheets (script.container.ui) |
Sensitive | Show the add-on's panel | The user interface |
Store settings in your own account (script.storage) |
Non-sensitive | Remember your choices and the progress of a running job | So long jobs can resume, and so you do not re-enter the same settings each time |
Connect to an external service (script.external_request) |
Sensitive | Call Google's Drive API to export each merged document as a PDF | Apps Script's built-in Drive service cannot work under the narrow drive.file scope,
so the add-on calls Google's Drive API directly for the PDF conversion. The manifest
allow-list limits this permission to https://www.googleapis.com/drive/v3/files/
— Google rejects any other URL. No data goes anywhere except back to your own Drive |
gmail.send,
gmail.modify, gmail.readonly, or any other Gmail scope. Google classifies
gmail.send as sensitive, and gmail.modify and gmail.readonly as
restricted because they can read the contents of your mailbox. This
add-on sends through Apps Script's own mail service instead, which cannot read mail at all.drive or
drive.readonly scopes, which would let it read files you never showed it. It uses
drive.file, which is limited to files you open with it or that it creates.Apps Script add-ons can only contact outside servers through the script.external_request
permission, and a published add-on must declare an allow-list of URL prefixes in its manifest; Google
refuses any request outside that list. This add-on's allow-list contains exactly one entry:
https://www.googleapis.com/drive/v3/files/ — Google's own Drive API, which the add-on
uses to convert each merged Google Doc into a PDF. The request carries only the file ID of a document
the add-on itself created in your Drive.
The practical consequence: there is no code path, present or possible, by which your spreadsheet rows, your documents, your recipients, or your identity could be transmitted to us or to anyone other than Google, whose services you are already using. The capability to reach any other server is absent, not merely unused. You can verify the allow-list yourself: it is part of the add-on's manifest that Google reviews before publication.
Everything the add-on stores is kept inside your own Google account, using Google Apps Script's Properties Service and the files in your own Drive. We cannot read any of it.
| What | Where | Why | Lifetime |
|---|---|---|---|
| Your settings — which template and folder you picked, which columns, the subject and body text | Properties Service, attached to that spreadsheet (so other editors of the same sheet see the same settings; file access itself is still granted per person through the picker) | So you do not re-enter them on every run | Until you change them. The output folder choice can be cleared with the ✕ button next to it |
| Free plan daily counter — today's date and how many recipients you have emailed today | Properties Service, in your own Google account | To apply the free plan's 20-recipients-per-day allowance | Resets every day |
| Send status per row — “SENDING” just before the email goes out, then “SENT” with a timestamp, or the error text Google returned | A column of your own spreadsheet (header “Merge Status” unless you rename it) | So a re-run skips rows that already went out and retries only the ones that failed | Yours. Clear the column to send again |
| Your license key, if you bought a plan | Properties Service, in your own Google account | To unlock the paid plan. The key is verified inside the add-on; it is never sent anywhere | Until you press “Remove license key” in the add-on |
| The PDFs, if you choose to keep them (the temporary merged copies are deleted right after each PDF is made) | Your own Google Drive, in the folder you choose | They are the output you asked for | Yours. Delete them whenever you like — we never had a copy |
We do not store your spreadsheet contents, your documents, your recipients' addresses, or any identifier of you, anywhere outside your own Google account — with one exception: if you buy a plan, the payment provider tells us your email address and order ID so that we can issue your license key. See “Purchases and license keys”.
Paid plans are sold through Link, Stripe's checkout, which acts as the merchant of record and handles payment, tax, receipts and invoices under its own privacy policy. We never see your card details.
When a purchase completes, Stripe notifies our licensing service, which stores your email address, the plan, the order ID, the subscription ID (Annual plan only) and the issued license key so that you can retrieve the key at license.sumitsubo.com and so we can reissue it if you lose it. When you use that page you send it the email address and order ID you type in; it keeps a short-lived per-network counter of attempts to prevent guessing, and nothing else. That is the entire record. It lives in Cloudflare's key-value storage, is kept for as long as your plan could reasonably need support, and is deleted on request — write to the address below with your order ID. This service is separate from the add-on: the add-on never contacts it, and it holds nothing from your spreadsheets, documents or emails.
Bulk Email & PDF Mail Merge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Because we hold no copy of your data, there is nothing for us to delete on our side.
If the add-on's permissions or data handling change, this page is updated before the change ships, and the “last updated” date above changes with it.
[email protected] — see also the support page.