Clear routes.
Limited data.

Plain-language summary

• Alias does not read or transmit your Gmail inbox, sent mail, contacts, browsing history, or unrelated websites.
• It reads supported fields from the active Gmail compose window when you press Send via alias.
• Your chosen delivery provider receives the message data necessary to send that email.
• Alias does not sell user data, build advertising profiles, or use communications for advertising.
• No employee routinely reads message content. Human access is permitted only with your specific support consent, when required for security or abuse investigation, or when legally required.

01

Gmail draft data

The content script runs only on mail.google.com so it can locate Gmail compose windows and add the Alias send control. After you explicitly press that control, it may read the active draft’s sender, To recipient, Cc/Bcc where supported by the chosen provider, subject, HTML and plain-text body, and accessible attachments where supported.

Hosted delivery intentionally accepts a smaller message: exactly one To recipient, no Cc, Bcc, attachments, custom headers, or client-supplied Reply-To. Gmail’s normal Send button remains separate. Alias leaves the Gmail draft open after an alias send.

02

Delivery providers

You choose one of these delivery routes:

Cloudflare

The extension sends the supported message directly to Cloudflare’s Email Sending API using the Cloudflare connection you authorize. AudioFetcher’s Hosted infrastructure does not receive that message. Alias does not charge for this direct connection; Cloudflare’s plan and quotas apply, and sending to arbitrary recipients requires Workers Paid.

Resend

The extension sends the supported message directly to Resend using the Resend connection you authorize. AudioFetcher’s Hosted infrastructure does not receive that message. Alias does not charge for this direct connection; your Resend plan, quota, and any provider charges still apply.

Hosted (AWS SES)

Hosted subscriptions are currently closed. If Hosted opens and your account becomes active, the extension will send the allowlisted message fields and a short-lived access token to AudioFetcher’s hosted API. The API will validate your active paid subscription, account, exact sender and domain, quotas, service state, and idempotency before passing the message to Amazon SES.

Cloudflare, Resend, Amazon Web Services, and their subprocessors handle delivery data under their own agreements and privacy practices. Alias uses them only to provide the delivery route you selected.

03

Hosted access, billing, and domain verification

A Hosted access request contains your contact/login email, domain, exact sender address, sender display name, intended use case, expected monthly volume, and request timestamps/status. The request service returns a one-time private status token; the server stores only its SHA-256 hash.

Hosted is planned as a paid subscription service, but subscriptions and charges are currently closed. When Checkout opens, Stripe will handle payment processing. AudioFetcher will receive and store only the limited billing and account metadata needed to manage Hosted access, such as Stripe customer, checkout, subscription, price, and webhook-event identifiers, subscription status, and relevant timestamps. AudioFetcher will not receive or store full card numbers, CVCs, or bank-account credentials. Stripe will handle that payment data under its own privacy policy.

If approved, Alias creates a request-bound Amazon SES domain identity and shows three DKIM CNAME records. You add those records at your DNS provider. If SES confirms ownership and DKIM while Hosted subscriptions are available, Alias may reserve the login email before Checkout by creating a disabled, unverified Amazon Cognito user with invitation delivery suppressed. That reservation cannot sign in, receives no invitation, and cannot send. Account activation and invitation delivery proceed only after Stripe confirms the exact Hosted subscription is active.

The Hosted send service does not intentionally store recipients, message subjects, message bodies, attachments, authorization headers, provider message IDs, or SES message IDs. It stores bounded quota counters, hashed idempotency evidence, operational status, and aggregate bounce/complaint information.

04

Data stored in Chrome

Alias uses chrome.storage.local for configuration, disclosure acceptance, sender settings, provider connection material, the Hosted refresh session, Hosted request tracking, and one redacted last-send summary. The short-lived Hosted access token uses chrome.storage.session.

Chrome storage is restricted to trusted extension contexts. The Gmail content script cannot read provider credentials or Hosted tokens. Saved secrets are never written back into visible fields after saving and are excluded from diagnostics. Chrome storage is not an operating-system keychain or dedicated password manager; anyone controlling your device or Chrome profile may be able to recover locally stored material.

05

Retention and diagnostics

Local settings remain until you clear them or uninstall Alias. Hosted onboarding records normally expire after 30 days; approval extends a request to 90 days for DNS verification and optional Checkout, and rejected records expire 30 days after the decision. An unpaid disabled Cognito reservation follows the approved request’s expiry. When DynamoDB later removes that expired request, guarded cleanup removes only the exact disabled reservation bound to its request; AWS performs TTL deletion asynchronously, so cleanup may occur after the stated expiry. A paid active Cognito account remains while the Hosted account is active or as required for security and legal obligations. Limited Stripe customer, subscription, checkout, and webhook metadata may remain after cancellation as needed for billing administration, fraud prevention, disputes, accounting, and legal obligations. Stripe controls retention of invoices and the payment details it processes.

Diagnostics contain only bounded operational facts such as provider type, status code category, timestamp, counts, lengths, and sanitized error codes. They intentionally exclude complete addresses, recipients, subjects, bodies, attachments, credentials, tokens, and authorization headers. A separate private Hosted request-audit timeline keeps the request ID, bounded workflow stages, actions, statuses, safe facts, and correlation identifiers for up to 180 days. It excludes message content, provider credentials, plaintext request tokens, and raw Stripe webhooks. Its DynamoDB TTL deletion is asynchronous, so removal may occur after the stated expiry.

If you deliberately submit the feedback or uninstall form, AudioFetcher stores your selected reason, optional rating, optional contact email, optional written comment, extension version, and any safe diagnostics you choose to include. Feedback is retained for up to 180 days and is visible only in the private administrator dashboard. The form does not receive message content, recipients, provider credentials, tokens, inbox history, or browsing history.

Security logs and AWS delivery systems may retain limited operational records according to configured retention and provider requirements. They are used for delivery, fraud and abuse prevention, reliability, and legal compliance.

06

Your controls

• Do not enable Gmail integration until you have reviewed and accepted the in-product disclosure.
• Clear an inactive Cloudflare or Resend connection from the Sender settings.
• Sign out of Hosted mode to remove the local Hosted session.
• Cancel or manage a Hosted subscription through the available Hosted billing controls, or contact support for help.
• Clear the redacted last-send diagnostic summary.
• Choose whether to include the allowlisted safe diagnostic fields when submitting feedback.
• Uninstall Alias to remove its local Chrome storage.
• Email help@audiofetcher.com to request access, correction, or deletion of Hosted account or onboarding data, subject to necessary security and legal retention.

08

Changes and contact

Material changes to data handling will be disclosed in the extension before the new handling begins, and this page’s effective date will be updated.

Privacy and security questions: help@audiofetcher.com