Privacy Policy
Last updated: July 13, 2026
This Privacy Policy explains what information the "EML to PDF" Chrome extension ("the Extension") collects, how it is used, and what stays entirely on your device.
Summary
- Your email files and their content never leave your device. Parsing
.emlfiles and generating PDFs happens entirely locally, inside your browser. - The only information that reaches our server is what's needed to (a) verify your Google sign-in and (b) check or grant paid access. Neither of these ever includes your email content.
- We do not sell, rent, or share your information with third parties for advertising or marketing purposes.
What the Extension processes locally (never transmitted)
- The content of any
.emlfile you open or convert, including sender/recipient details, message body, and attachments - The PDF files generated from your
.emlfiles
None of the above is uploaded, transmitted, logged, or stored anywhere outside your own device. The Extension's core conversion functionality requires no internet connection.
What is sent to our server, and why
| Data | When it's sent | Purpose |
|---|---|---|
| Your Google account email address | When you sign in, and when checking/restoring paid access | To identify your account for unlocking paid features and to prevent unauthorized use |
| Purchase/payment confirmation (via our payment processor's webhook) | When you complete a payment | To grant your account extended access |
We do not receive your Google password, contacts, or any other Google account data beyond the email address associated with your account, and only with your explicit sign-in action.
Data categories we collect
In our Chrome Web Store listing, we disclose collecting the following categories of user data, as defined by Google's Chrome Web Store Developer Program Policies:
- Personally identifiable information — specifically, your email address, obtained when you sign in with Google.
- Personal communications — the Extension's core function is processing the content of email messages (
.emlfiles). This processing happens entirely on your device; email content itself is never transmitted to or stored on our server. - Authentication information — specifically, an OAuth credential (access token) from Google Sign-In, used only to verify your identity and check your paid-access status. We do not receive or store your Google password.
We do not collect: health information, financial or payment information (handled entirely by Dodo Payments — see below), location data, web browsing history, user activity (such as keystrokes or clicks outside the Extension), or website content from other sites.
Third-party services
- Google Sign-In — used to verify your identity. Governed by Google's Privacy Policy.
- Dodo Payments — our payment processor, used to handle purchases. Dodo Payments processes your payment details directly; we never see or store your card information. See Dodo Payments' Privacy Policy for details on how they handle payment data.
Data storage and retention
We store, on our server:
- Your email address (if you've signed in)
- Your account's access status
- A record of any purchase transaction (for support and refund purposes)
We do not store your .eml files, their content, or any generated PDFs — these never reach our server in the first place.
You may request deletion of your stored account data at any time by contacting [SUPPORT EMAIL].
Permissions the Extension requests, and why
- downloads — to save the generated PDF files to your device
- storage — to remember your local preferences and usage locally in your browser
- identity — to enable Google Sign-In
- Host permission for our API domain — to communicate with our server for sign-in and purchase verification only, as described above
Children's privacy
The Extension is not directed at children under 13 (or the relevant minimum age in your jurisdiction), and we do not knowingly collect information from children.
Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be reflected in the "Last updated" date above. Continued use of the Extension after changes constitutes acceptance of the updated policy.
Contact
Questions about this Privacy Policy or your data can be sent to: [CONTACT EMAIL]
Developer: [YOUR NAME / COMPANY NAME]