Privacy-First Architecture

Your certificate data stays on your device.

MailMyCertificate was designed around a simple idea: organizers should not need to upload participant data to external servers just to generate and send certificates.

Built because privacy should be part of the workflow — not an afterthought.

Local Processing

Certificate generation happens directly inside your browser using your own device.

No Participant Uploads

Your CSV files, participant names, and generated certificates are not uploaded to our servers.

Minimal Trust Required

The product is intentionally engineered to minimize how much user data ever leaves the browser.

This Privacy Policy explains how MailMyCertificate handles data when you use the application. By using the platform, you agree to the practices described below.

1. Local-First Processing

MailMyCertificate follows a local-first architecture. Certificate templates, participant data, generated PDFs, and workflow progress are processed directly inside your browser whenever possible.

Unlike many traditional SaaS tools, MailMyCertificate is intentionally designed to reduce dependency on external cloud storage for core certificate generation workflows.

  • Certificate templates are stored locally inside your browser storage.
  • CSV and Google Sheets imports are processed on the client side.
  • PDF generation occurs locally using browser processing capabilities.
  • Generated certificates are not permanently stored on MailMyCertificate servers.

2. Information We Collect

MailMyCertificate does not intentionally collect or sell participant information.

Some limited technical information may be collected automatically for operational and security purposes, including:

  • Browser type and version
  • Device information
  • Error logs and crash diagnostics
  • Basic anonymous usage analytics

Any monitoring or diagnostics services used by the platform are configured to avoid intentionally storing Personally Identifiable Information (PII) wherever reasonably possible.

3. Browser Storage & Local Data

MailMyCertificate may store temporary workflow data locally inside your browser using technologies such as IndexedDB or Local Storage.

This may include:

  • Uploaded certificate templates
  • Participant lists
  • Generated certificate references
  • Workflow progress and session recovery data

This local data exists only on your device and can typically be removed by clearing your browser storage.

4. Email Sending & Third-Party Providers

If you use email functionality, MailMyCertificate may connect directly to external email providers such as Gmail or other SMTP-based services.

Certificate delivery is handled through the provider you authorize. MailMyCertificate does not claim ownership over your email credentials, participant data, or outgoing communication content.

Depending on implementation details and future integrations, some email operations may rely on third-party APIs or authentication systems such as Google OAuth.

5. Hosting & Infrastructure

MailMyCertificate may use third-party hosting and infrastructure providers such as Vercel for website delivery, uptime, analytics, and security.

These providers may temporarily process technical request information such as IP addresses, browser metadata, and performance logs as part of normal web infrastructure operations.

However, participant certificate data is not intended to be permanently stored on these infrastructure services.

6. Open Source Transparency

MailMyCertificate is an open-source project.

Transparency is important for tools that process participant information and certificate workflows. Users may inspect the public source code repository to better understand how the application works.

View GitHub Repository

7. Policy Updates

This Privacy Policy may be updated from time to time to reflect technical improvements, legal requirements, or workflow changes.

Material privacy-related changes will be reflected on this page.

Engineering Commitment

MailMyCertificate was originally built to solve a real organizer workflow problem without forcing users to trust unknown servers with participant data.

The goal is simple: generate and send certificates with as little unnecessary data exposure as possible.

Last updated: January 2026