Privacy Policy

This Privacy Policy describes how Batch Merge ("we," "our," or "the add-on") collects, uses, and protects information when you use our Google Sheets add-on available through the Google Workspace Marketplace. We are committed to protecting your privacy and handling your data with full transparency.

1. What Data Batch Merge Accesses

Batch Merge accesses only the data necessary to perform document merges on your behalf. This includes:

• Spreadsheet data: Batch Merge reads the contents of the active Google Sheets spreadsheet, including column headers and row data, in order to populate template tags and generate personalized documents.
• Google Docs templates: Batch Merge opens and reads Google Docs files that you select as merge templates. It scans these documents for {{tag}} placeholders and creates copies with your spreadsheet data substituted in.
• Email addresses: If you configure per-row email delivery, Batch Merge reads the email addresses from the column you designate in your spreadsheet in order to send generated documents to the intended recipients.
• Google Drive folders: Batch Merge accesses the Google Drive folders you select as output destinations for saving generated documents.
• Add-on configuration: Batch Merge stores your merge settings (template selection, output format, email options, scheduling preferences) in the spreadsheet's Document Properties.

2. How Your Data Is Processed

All data processing happens entirely within Google's infrastructure via Google Apps Script. Batch Merge operates as a server-side Google Apps Script project that runs within your Google Workspace environment. Specifically:

• No external servers: Batch Merge does not transmit, send, or relay any of your data to external servers, third-party services, or any infrastructure outside of Google.
• No external network requests: The add-on makes no HTTP requests to non-Google endpoints. All operations -- reading spreadsheets, generating documents, sending emails -- are executed through official Google Apps Script services (SpreadsheetApp, DocumentApp, DriveApp, GmailApp).
• No data collection by us: We do not collect, aggregate, analyze, or store any of your spreadsheet data, document contents, or email addresses on our own systems. We have no servers that receive your data.

3. OAuth Scopes and Why They Are Required

When you authorize Batch Merge, Google will ask you to grant the following permissions. Each scope is required for specific functionality:

• Google Sheets (spreadsheets.currentonly): Read spreadsheet data (column headers and row values) to populate merge tags. Write status updates back to a designated status column to track which rows have been processed.
• Google Docs (documents): Open your selected template document, read its contents to identify {{tag}} placeholders, and create personalized copies with replaced tag values.
• Google Drive (drive): Access template files and output folders you select through the Google Picker. Save generated documents (PDF, DOCX, or Google Doc) to your chosen Drive folder. Export documents to PDF or DOCX format.
• Gmail (gmail.send): Send emails with generated documents attached or linked when you configure per-row email delivery or batch summary notifications.
• Script triggers (script.scriptapp): Create and manage time-based triggers for scheduled merges that run automatically at your configured interval.
• UI service (script.container.ui): Display the Batch Merge sidebar within Google Sheets and show dialog boxes for authorization prompts and status messages.

Batch Merge requests only the minimum scopes necessary for its functionality. No scope is used for purposes beyond what is described above.

4. Google API Services User Data Policy Compliance

Batch Merge's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• Batch Merge only uses access to Google user data to provide the document merge features described in this policy and visible in the add-on's user interface.
• Batch Merge does not transfer Google user data to third parties, except as necessary to provide the service (which requires no third-party transfers), with user consent, or for legal reasons.
• Batch Merge does not use Google user data for advertising or to serve ads.
• Batch Merge does not allow humans to read Google user data unless the user has provided affirmative consent, it is necessary for security purposes, or it is required by law.

5. Data Storage and Retention

Batch Merge does not maintain its own databases or storage systems. All data remains within your Google account:

• Spreadsheet data: Remains in your Google Sheets spreadsheet. Batch Merge reads it at merge time and does not copy it elsewhere.
• Generated documents: Saved to the Google Drive folder you specify. These files belong to your Google account and are subject to your own Google Drive storage and retention settings.
• Merge configuration: Your settings (selected template, output format, email options, schedule) are stored as JSON in the spreadsheet's Document Properties using Google Apps Script's PropertiesService. This data is scoped to the individual spreadsheet and is deleted when the spreadsheet is deleted.
• Merge log: If logging is enabled, a "Merge Log" sheet is created within your spreadsheet to record merge activity (timestamps, row counts, status). This data lives in your spreadsheet and is under your control.
• Sent emails: Emails sent through Batch Merge appear in your Gmail "Sent" folder. They are subject to your Gmail storage and retention settings.

We retain no data outside of your Google account. When you uninstall the add-on, configuration data stored in Document Properties remains in your spreadsheet until you delete it or delete the spreadsheet.

6. Data Sharing

Batch Merge does not share your data with any third party. Since all processing occurs within Google's infrastructure and we operate no external servers, there is no mechanism by which your data could be shared with or accessed by us or any other party outside of your Google Workspace account.

7. Data Security

Batch Merge relies on Google's security infrastructure for all data protection:

• All data access is governed by Google's OAuth 2.0 authorization framework. You grant and can revoke permissions at any time.
• Data in transit is protected by Google's TLS encryption.
• Data at rest is protected by Google's encryption at rest for Google Drive, Sheets, Docs, and Gmail.
• Batch Merge implements document-level locking to prevent concurrent merge conflicts when multiple users access the same spreadsheet.

8. Your Rights and Controls

You maintain full control over your data and your relationship with Batch Merge:

• Revoke access: You can revoke Batch Merge's access to your Google account at any time by uninstalling the add-on from your Google Sheet (Extensions menu) or by removing it from your Google Account permissions.
• Delete configuration: Merge configurations stored in Document Properties can be removed by uninstalling and re-opening the spreadsheet, or by deleting the spreadsheet.
• Delete generated files: All documents created by Batch Merge are standard Google Drive files owned by you. You can move, share, or delete them at any time.
• Cancel scheduled merges: You can disable any scheduled merge from the Batch Merge sidebar or by removing the add-on's triggers from your Google Apps Script project settings.

9. Cookies and Tracking

Batch Merge does not use cookies, web beacons, pixels, or any other tracking technologies. The add-on runs entirely within the Google Sheets sidebar environment and does not load external analytics scripts, advertising trackers, or third-party resources. We do not track your usage behavior, create user profiles, or perform any form of cross-site tracking.

10. Children's Privacy

Batch Merge is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe that your child has provided personal information through the use of this add-on, please contact us at support@batchmerge.com and we will take steps to address the situation.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for legal, regulatory, or operational reasons. When we make material changes, we will update the "Effective Date" at the top of this page. We encourage you to review this Privacy Policy periodically. Your continued use of Batch Merge after changes are posted constitutes your acceptance of the updated policy.

12. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or how Batch Merge handles your data, please contact us at:

support@batchmerge.com