Legal

Privacy Policy

Effective 13 November 2026

1. Who we are

Transmitly is operated by Swift Nodes LLC (“Transmitly”, “we”, “us”). This policy explains how we collect, use, share and retain personal data when you visit transmitly.io, create a workspace, use the API, or receive mail through the service.

For account, billing and website data we act as the controller. For message content and recipient data that customers submit to the service, the customer is the controller and Transmitly acts as a processor. The current Data Processing Addendum is available at transmitly.io/legal/dpa; executed copies can be requested at [email protected].

2. Data we collect

Account and workspace data: name, email address, organization name, role, password hash, email-verification state, session metadata (IP address and user agent), API-key metadata, and audit events such as sign-ins, domain changes, suppression changes and autopilot decisions.

Sending data: sender and recipient addresses, subject lines, message bodies, headers, tags, attachments you submit, delivery attempts and outcomes, bounce and complaint reports, suppression entries, and inbound messages accepted by your routes.

Billing data: plan, usage, invoices, tax identifiers and Stripe customer/payment identifiers. We do not store full payment-card numbers; card data is handled by Stripe.

Technical data: request logs, IP addresses, timestamps, service health, error diagnostics and security events. We do not use advertising cookies or third-party analytics trackers.

3. Why we use it

We process data to provide the service and perform our contract with you: accepting and delivering mail, verifying domains, routing inbound mail, enforcing suppressions, reporting delivery events and operating your workspace.

We also process data for our legitimate interests in keeping the service secure and reliable: detecting abuse, preventing spam and fraud, debugging failures, maintaining audit trails, improving deliverability and enforcing our terms. We process billing and tax data to comply with legal obligations.

We use aggregate, bounded operational telemetry to generate autopilot proposals. The model receives incident metrics, provider statistics, policy bounds and similar aggregate context; it does not receive recipient addresses, message bodies, credentials or raw headers. Proposals are validated deterministically and never execute themselves.

We may send service, security and account notices. We do not send marketing email without a lawful basis or consent where required.

4. Legal bases

Where the GDPR or similar law applies, we rely on: performance of a contract (providing the service), legitimate interests (security, abuse prevention, reliability and product improvement), legal obligation (tax, accounting and lawful requests), and consent where we specifically ask for it. You can object to processing based on legitimate interests at [email protected].

5. Sharing and subprocessors

We do not sell personal data and we do not share it for cross-context behavioral advertising. We share data with service providers that help us operate the platform, under contracts that restrict their use of it:

  • • Contabo GmbH — cloud hosting and infrastructure (European Union, France).
  • • Backblaze, Inc. — S3-compatible object storage for attachments, compose images, cold message bodies and encrypted database backups (United States, us-east-005).
  • • Cloudflare, Inc. — DNS, CDN and security for transmitly.io; the optional Cloudflare integration lets a customer authorize DNS changes in the customer’s own Cloudflare account.
  • • DeepSeek — model inference for autopilot proposals, receiving bounded aggregate telemetry only.
  • • Stripe, Inc. — payment processing, subscription billing, invoices and tax calculation. Stripe receives payment and billing-contact data and acts as an independent controller for some processing under its own privacy terms.

We may also disclose data when required by law, to protect rights or safety, or in connection with a merger or acquisition subject to appropriate confidentiality. Where a provider processes data outside the EEA or UK, we rely on appropriate safeguards such as standard contractual clauses.

6. Cookies and similar technologies

We use one strictly necessary session cookie (tx_session) to keep you signed in. It is HttpOnly, SameSite=Lax and Secure in production. We do not use advertising cookies, cross-site tracking pixels or third-party analytics.

Our infrastructure and security providers may process request metadata (IP address, user agent, timestamps) to deliver and protect the service. The Cloudflare dashboard and customer-authorized Cloudflare zones are governed by Cloudflare’s own privacy terms. Stripe Checkout and the Stripe billing portal are hosted by Stripe and may set cookies on those pages under Stripe’s privacy policy.

7. Retention

Message bodies and content-bearing event payloads are retained according to your plan: Free 7 days, Starter 30 days, Scale 90 days and Enterprise 365 days, unless a custom retention term applies. After that window they are pruned automatically.

Delivery metadata, usage records, audit events and AI call metadata may be retained longer for security, billing, dispute resolution and legal compliance. Suppression entries are retained so we can continue honoring opt-outs and complaints.

Account data is retained while the workspace is active and for a reasonable period after closure to meet legal, tax and security obligations. Backups are access-controlled and retained for up to 14 days.

8. Security

We use TLS for data in transit, password hashing, encrypted storage for OAuth credentials, scoped API keys, role-based access, audit logging, suppression enforcement and least-privilege service accounts. Our current controls and documents are summarized at transmitly.io/security. No system is perfectly secure; if we become aware of a breach affecting your data, we will notify you and the relevant authorities as required by law.

You are responsible for keeping API keys and account credentials confidential and for configuring member roles appropriately.

9. Your rights

Depending on where you live, you may have the right to access, correct, delete, port, restrict or object to processing of your personal data, and to withdraw consent where processing is based on consent. Contact [email protected]. We may need to verify your identity and may retain certain records where law requires it.

If you are a recipient of mail sent through a customer’s workspace, the customer is the controller of that data. Please contact the sender first; we will assist the customer with valid requests. You can also use the unsubscribe link in marketing mail or contact us to add an address to our suppression list.

You may lodge a complaint with your local data-protection authority.

10. International transfers

Our primary infrastructure is in the European Union. Some providers process data in other countries. Where required, we use appropriate transfer mechanisms, including standard contractual clauses and provider security commitments.

11. Children

The service is not directed to children under 16, and we do not knowingly collect personal data from them. If you believe a child has provided data, contact us and we will delete it.

12. Changes and contact

We may update this policy as the service or law changes. Material changes will be posted here with a new effective date and, where appropriate, additional notice.

Privacy questions, data-subject requests and DPA requests: [email protected]. Security reports: [email protected]. General support: [email protected].

This policy covers transmitly.io and the Transmitly API. It does not cover a customer’s own application, website or mailbox provider, which may have separate privacy terms.