Privacy policy

Overview

This privacy policy explains how these Chrome extensions approach privacy for Gmail, Google Workspace Gmail and PDF document workflows. The extensions are not affiliated with Google.

Extension permissions

Chrome extension permissions are requested to support the stated product features. Depending on the extension, this may include selected Gmail email processing, saving email records as PDFs, printing selected emails, downloading selected attachments, exporting ZIP files, reviewing selected Gmail recipients, creating Gmail replies or drafts, editing PDF files, merging PDFs, signing PDFs, redacting PDFs, exporting PDF pages, or managing subscription status.

Data handling details

Selected Gmail content is handled only when a user chooses a Gmail workflow button. PDF document content is handled only when a user opens a PDF workflow. Processing is limited to the requested task, such as preparing selected email records, files, attachments, ZIP archives, print output, reviewed recipients, draft messages, PDF edits, subscription status, support troubleshooting, security, and payment-related account handling.

Subscriptions and payments

Subscription management may involve Stripe or another payment provider. Users should use the account email shown in the relevant extension account screen when managing paid access or cancellation.

Chrome Web Store user data policy answers

This section answers practical user-data questions raised by the Chrome Web Store Program Policies user data FAQ. The short version: permissions are requested only for the features users choose, data is used only to provide those features, and Gmail or PDF content is not sold or used for advertising.

What user data may the extensions handle?

When a user runs a workflow, an extension may process selected email content, message metadata, sender or recipient details, imported address lists, CSV rows, attachment names, attachment files, browser download output, PDF document content, subscription email, and basic account status needed to complete the requested task.

Why is Gmail data accessed?

Gmail data is accessed only to provide user-requested actions such as printing selected Gmail emails, saving selected Gmail emails as PDFs, downloading attachments, exporting a ZIP file, reviewing selected senders, creating private BCC drafts, sending individual replies, saving drafts, or checking paid access after a trial allowance.

Why is PDF data accessed?

PDF data is accessed only when the user chooses a PDF editing workflow such as editing text, adding text, signing, redacting, whiteout, highlighting, annotating, adding images, merging PDFs, converting websites to PDF, exporting PDF pages, extracting images, or converting supported documents to PDF.

Is Gmail or PDF data sold or used for ads?

No. Gmail content, attachment data, recipient data, PDF document content, and workflow output are not sold, used for advertising, used for creditworthiness, or used to build unrelated profiles.

Is data shared with third parties?

Data may be shared only when necessary to operate the service, such as payment and subscription management through Stripe, hosting or infrastructure services, security, debugging, or support. Service providers must be limited to the purpose required to provide the extension.

How long is user data kept?

Workflow output should be saved by the user in their browser or chosen folder. Subscription and support records may be retained as needed for billing, cancellation, fraud prevention, security, tax, and support obligations.

How can users control or delete data?

Users can stop using an extension, remove it from the browser, cancel paid access from the extension account page where applicable, and use the support page for privacy questions.

Does the policy apply to future features?

Yes. New features should follow the same narrow-use rule: request only the permissions needed, explain what data is handled, and use that data only for the workflow the user chooses.

This page is written to align with the Chrome Web Store Program Policies user data FAQ and should be reviewed whenever permissions, storage, payment, or support systems change.

Contact

For privacy questions, use the support page.