Simple Merge

Privacy Policy

Last updated: 14 July 2026

In short: Simple Merge reads only the documents you choose, uses them solely to produce the merged file you asked for, and does not store your document content. We never sell your data, show ads, or let any person read your documents.

1. Who we are

Simple Merge (“the add-on”, “we”, “us”) is a Google Workspace™ Add-on that merges multiple documents into a single Google Doc. This policy explains what information the add-on accesses, how it is used, and the choices you have. It applies to the add-on and its supporting service, and does not cover Google's own products or any third-party website.

2. What data we access

The add-on accesses the minimum needed to do its job, and only when you actively use it:

The documents you select Files you explicitly choose in the picker, paste as a link or ID, or the document you currently have open. We read their content in order to merge them. We do not access files you have not selected, and we do not have access to your entire Google Drive™.
Files the add-on creates The merged Google Doc (and any optional PDF or Word copy) is created in your own Google Drive™ under your account.
Your Google account identifier A stable, pseudonymous account ID (the Google sub identifier) and email, obtained from Google when you use the add-on, used to identify your session and count your monthly usage against your plan.
Authorization tokens Short-lived Google tokens that authorize the add-on to act on your behalf for the duration of a single request. These are used transiently and are never stored.

The add-on requests these Google OAuth scopes, each for a specific purpose:

See, edit, create and delete your Google Docs™ documents Required to read the documents you choose, to create the merged document, and — when you choose “merge into the current document” or “preserve tabs” — to assemble content with full formatting fidelity.
See, create and delete only the files you use with this app (drive.file) To create the merged file and any PDF/Word copy, to save into a folder you pick, and to handle files you upload or select through the picker.
Sign in (openid) & connect to an external service To identify your account for usage limits, and to securely contact the add-on's own processing service.
Display and run within Google Docs™ To show the add-on's interface inside the Google Docs™ editor.

3. How we use it

We use the information above only to provide the add-on's core feature — merging the documents you select — and to operate the service reliably:

  • To read your selected documents and combine them, in your chosen order and with your chosen options (page breaks, headings, PDF/Word export, and so on).
  • To convert non-Google files (Word, ODT, RTF, Markdown, HTML, text, PDF) into Google Docs™ so they can be merged. Conversion is performed by Google Drive™; any temporary file created during conversion is deleted immediately after processing.
  • To create the merged document, and any PDF or Word copy, in your Drive.
  • To count how many merges you have run in the current month, so that plan limits can be applied fairly.
  • To keep short operational logs (for example, that a merge succeeded or failed, and error messages) needed to run and troubleshoot the service. These logs do not contain your document content.

Processing is carried out by the add-on's backend service, which runs on Google Cloud and acts on your behalf using the short-lived token your session provides. Document content passes through the service only for the moment it takes to complete your merge.

4. What we store — and what we don't

We do not store your document content. Files are read, merged, and the result written to your Drive within a single request; nothing about the contents of your documents is retained afterwards.

The only information we retain is a minimal usage record, held in Google Firestore:

What is storedYour Google account identifier (sub), the current month, and a count of merges performed that month. Optionally, a plan tier and its expiry if you are on a paid plan.
WhyTo enforce monthly usage limits and, for paid plans, to grant the correct limits.
What is not storedYour document content, file names, the merged output, your authorization tokens, or any browsing/behavioural profile.

5. Google API Services User Data Policy (Limited Use)

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

Specifically, information obtained through Google APIs is used only to provide and improve the add-on's user-facing merging feature. We do not:

  • transfer or sell this data to third parties, advertising platforms, data brokers, or information resellers;
  • use it for advertising, including personalized, retargeted, or interest-based advertising;
  • allow humans to read it, except with your explicit consent for a specific support request, where required for security or to comply with applicable law, or in a limited form necessary to operate the service (for example, an aggregated error rate that contains no document content).

6. Sharing and sub-processors

We do not sell your data and do not share it for anyone else's marketing. Data is processed using the following infrastructure providers, acting on our behalf:

Google (Google Cloud, Drive, Docs APIs) Hosts the processing service (Cloud Run), stores the usage counter (Firestore), and provides the Drive and Docs operations you request. Google processes this data under its own terms.

We may disclose information if required by law, or to protect the rights, safety, or security of our users or the service.

7. Security

  • All data is transmitted over encrypted connections (HTTPS/TLS).
  • The add-on requests least-privilege access and does not request access to your entire Drive.
  • The processing service is not publicly open: every request must be authenticated through Google's identity infrastructure before it is accepted.
  • No long-lived secrets or credentials for your account are stored by the add-on.

No method of transmission or storage is completely secure, but we take reasonable measures to protect your information.

8. Retention and deletion

Document content is not retained at all. The usage counter is kept only as long as needed to enforce monthly limits and expires automatically after a short period (on the order of weeks after the month it covers). Operational logs are retained for a limited period for troubleshooting and security, then deleted.

You can stop all data processing at any time by removing the add-on from your Google account (Google Account → Data & privacy → Third-party apps & services). To request deletion of your usage record, contact us using the details below.

9. Your rights

Depending on where you live, you may have rights to access, correct, or delete the personal data we hold about you, or to object to or restrict its processing. Because we hold only a minimal usage record keyed to your account ID, these requests are straightforward — contact us and we will respond within a reasonable time.

10. Children

The add-on is not directed to children under 13 (or the minimum age of digital consent in your country) and we do not knowingly collect their personal data.

11. Changes to this policy

We may update this policy from time to time. Material changes will be reflected by updating the “Last updated” date at the top of this page, and where appropriate we will provide additional notice.

12. Contact

Questions about this policy or your data? Email flowextractapi@outlook.com.

← Back to Simple Merge