Privacy policy

Data the application accesses

When you connect an account, Email Handler accesses account identifiers and email information needed to display and search your mailbox: message headers, sender and recipient details, subjects, dates, body text, formatting, folder or label information, and attachment metadata. Attachment files are downloaded when requested; their contents are not indexed for search.

Optional agenda connections access calendar and list names, event titles, times, locations and notes, and task or reminder details. Optional automatic reply access reads and updates your provider’s automatic reply settings, including message text, schedule and audience.

How your data is used

The application uses this information to import, display, search and organize mail; maintain local drafts and preferences; show your agenda; and carry out the sending, mailbox, calendar, task and automatic reply actions you enable and request.

Email Handler does not upload your mailbox to this informational website. The application has no integrated advertising, analytics or AI processing service for your mail.

Google permissions and optional features

Connecting Gmail initially requests read-only mail access. Additional permissions are requested for optional features:

• Mailbox management, sending and moving mail to Trash: Gmail modification access. The application separately controls which actions you enable.
• Permanent deletion: full Gmail access, required by Google for this operation.
• Google Calendar and Tasks: separate read access, or event/task write access when enabled, together with account identification.
• Automatic replies: separate Gmail basic settings access and account identification.

Enabling a permission does not itself send or delete mail. You can disable application write access separately from revoking a provider authorization.

Email Handler’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Local storage and security

Imported mail, account metadata, original message formatting, search indexes, local flags, drafts, sending history, agenda snapshots, preferences and operation records are stored on your computer. On macOS, the default workspace is in ~/Library/Application Support/Email Handler/workspace.

Mail and cache files use private file permissions but are not encrypted by the application. Your device security and backups affect their protection. OAuth tokens, client credentials and mailbox passwords use OS credential storage, including macOS Keychain. Approved credentials can also be held in memory while the application runs.

The browser interface connects to a local service on the same computer. Provider communication uses the provider’s HTTPS or verified TLS connections. Email HTML is sanitized and shown in an isolated reader with scripts blocked.

Provider communication and external content

Connecting and synchronizing an account communicates with its provider. Requested sends transmit your message, recipients and attachments to the sending provider for delivery. Mailbox changes, calendar/task changes and automatic reply settings are sent to the relevant provider when you request those actions. Providers handle that data under their own policies.

External email images are blocked until you choose to load them. Loading remote images contacts their hosts and can disclose your IP address and that the image was requested. Opening an external link also connects you to that destination.

Retention, disconnecting and deletion

Cached mail remains locally until removed by synchronization, deletion or account disconnect. The original-formatting cache has size limits and no time-based expiry. Disconnecting a mail account removes its mail credential and the account’s cached messages, formatting, search entries and message flags; it does not delete provider messages.

Local drafts, sending history, operation journals, preferences, exported attachments, backups and legacy workspace copies can remain independently. Deleting a source message does not erase text quoted in another draft or message. For removal of remaining local workspace files, close the application and contact support if you need help identifying them.

Agenda has its own disconnect control for its source snapshot and separate credential. Automatic reply authorizations are also separate. Do not assume that disconnecting mail revokes every grant. You can revoke Google access through Google Account connections and review other providers’ account controls. Revocation does not automatically erase existing local copies.

Provider deletion is a separate user action. Permanent deletion requires explicit confirmation and has no application Undo. Other clients’ copies, provider retention and user backups are outside the application’s control.

This website and support

This informational website has no sign-in, mailbox upload, advertising trackers, analytics scripts or application cookies. Its hosting and delivery infrastructure may process ordinary request metadata, such as IP address, requested URL, browser information and request time, to serve and operate the website.

If you contact support by email, your email address and the information you send are processed to respond to your request. Please avoid sending passwords, access tokens or unnecessary mailbox content.

Contact and updates

For privacy questions, support or help removing local data, email nodenub@gmail.com. Updates to this policy will appear on this page with a revised date.