Privacy Policy — Bulk Email & PDF Merge

Last updated: 2026-09-22

Bulk Email & PDF 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. We operate no database, no analytics, and no logging of your content.

This is not only a policy commitment. The add-on does not request the permission that would be required to contact any outside server, so it is technically incapable of sending your data anywhere. See “No outbound network access” below.

What the add-on asks permission for, and why

These are the four scopes the add-on requests, together with the classification Google Cloud Console shows for each one.

Permission requestedGoogle's classificationWhat it lets the add-on doWhy 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 create the merged documents and 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
Send email as you (script.send_mail) Sensitive Send each merged document 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

What we deliberately do not request

No outbound network access

An Apps Script add-on can only contact an outside server if it holds the script.external_request permission. This add-on does not request that permission.

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 else. The capability is absent, not merely unused.

What is stored, where, and for how long

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.

WhatWhereWhyLifetime
Your settings — which template, which columns, the subject and body text Properties Service, in your own Google account So you do not re-enter them on every run Until you clear them or uninstall
Progress of a running job — which rows have already been processed Properties Service, in your own Google account So a long job resumes where it stopped instead of sending anything twice Overwritten by the next run
The merged documents and PDFs 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, your email address, or any identifier of you, anywhere outside your own Google account.

What we do not do

Google API Services User Data Policy

Bulk Email & PDF 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.

Deleting your data

Because we hold no copy of your data, there is nothing for us to delete on our side.

Changes to this policy

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.

Contact

[email protected] — see also the support page.