Skip to content
Legal Document

Privacy
Policy.

We built privacy into the product, not just the policy. BYOC sends zero email content to our servers — by design, not by promise. Here's exactly what we collect, why, and what you can do about it.

Effective April 30, 2026
Last reviewed: September 17, 2026
BYOC privacy guarantee

On Starter and BYOC plans, email content — subject, body, recipient — is never written to our database. We send directly from your AWS SES account using your credentials. Only a monthly send counter is stored for Starter plan rate-limiting. This is an architectural constraint, not a policy choice.

BYOC = zero content stored
Email bodies, subjects, and recipients never touch our database on BYOC plans.
Keys are SHA-512 hashed
We store only a hash. The raw key is shown once and gone forever.
Never sold, never ads
We don't sell personal data or use email content for advertising.
01

Who We Are

SendFleet ("we", "us", "our") is a transactional email API service operated at sendfleet.net. We provide developers with infrastructure to send transactional email — either through your own AWS SES account (BYOC) or through our managed infrastructure (Managed plans).

This Privacy Policy explains what data we collect when you use SendFleet, how we use it, and the choices you have. By creating an account or using the API, you agree to this policy.

02

Data We Collect

We collect data in two contexts: directly from you at registration, and automatically when your application uses the API.

Account data

Field Why Required?
Email address Authentication, identity, service communications Yes
Display name Personalisation inside the dashboard No
Password (hashed) Authentication — never stored in plaintext Yes
Account creation date Audit trail and support Auto

Email usage data (Managed plans only)

Field Why
Sender name & email Forming the outbound From header
Subject line Passed through to email; stored in your log
Message body Passed through to email; stored in your log
Request timestamp Log ordering, usage calculation, rate-limit enforcement
Delivery status Displayed in your dashboard; used for retry logic
Message ID Returned in the API response for delivery tracking
BYOC plans: None of the above email fields are written to our database. Only a monthly aggregate send count is stored for Starter plan rate-limiting. Your email data never leaves your AWS account.

Technical / infrastructure data

API requests may generate standard HTTP metadata (IP address, User-Agent) used for rate-limiting, abuse prevention, and debugging. This is not linked to email content and is not retained beyond 30 days.

03

How We Use Your Data

  • Authenticate you and authorise API requests against your account.
  • Route and deliver transactional emails initiated via the API.
  • Maintain your email log — a history visible only to you in the dashboard.
  • Calculate monthly usage against your plan limit.
  • Send essential service communications — security alerts, policy updates. We do not send marketing email without opt-in.
  • Improve the reliability and performance of the service.
  • Place an account on a retention or security hold, and/or suspend API sending, at our sole discretion, when we reasonably believe the account is involved in abuse, fraud, or activity that may violate our Terms or applicable law, or when required by valid legal process. A retention hold preserves the account's email logs, domain configuration, API key metadata, and webhook configuration beyond the standard retention window until the hold is released. A sending suspension disables outbound API sending while the account's dashboard, logs, and billing remain accessible. We are not obligated to disclose the reason for a hold or suspension to any third party, and we may decline to confirm or deny whether a specific account is on hold except where compelled by lawful process or where the account holder is the requesting party.
  • We load web fonts from Google Fonts (fonts.googleapis.com) for typographic consistency. Google receives the requesting IP address as part of standard CDN operation. We do not control Google's data processing for this service.
We do not sell, rent, or trade your personal data or email content to any third party for marketing or advertising purposes. Ever.
04

API Key Security

API keys are your primary credentials for the send endpoint. We take their security seriously at the implementation level.

  • Keys are SHA-512 hashed before storage and are not retrievable after creation.
  • Lookup uses an 8-character prefix. The prefix alone cannot send emails — the full hash verification is always performed on every request.
  • Revoke any key instantly from the dashboard. Revocation propagates quickly through our cache layer.
  • Keys support expiry dates. Expired keys are automatically refused.
  • All actions under your API keys are your responsibility, whether or not you authorised them.
If you suspect a key has been compromised, revoke it immediately from the dashboard. Because we store only the hash, we cannot recover or reset a lost key.
05

Email Processing

SendFleet acts as a data processor for email content submitted through the API. You are the data controller and are responsible for the content and recipient data you submit.

Managed plans

Email content is delivered via AWS SES on our behalf, and written to your email log. Bounce and complaint events from SES are processed and written to your dashboard. Email logs are retained for 14 days and then purged automatically by a scheduled cleanup job, except where a retention or security hold is in place (see §6 below). If attachments are included, they are temporarily staged in AWS S3 for the duration of delivery and deleted immediately afterward — they are never written to our database.

BYOC plans (Starter / BYOC)

We access your IAM role using short-lived temporary credentials to send directly from your own AWS SES account. No email content is written anywhere on our infrastructure. Only a monthly send counter is incremented. Your SES logs and CloudWatch are the source of truth. Attachments on BYOC sends are also staged transiently in S3 (isolated per-request, deleted immediately after delivery) — no attachment data persists on our servers.

06

Data Retention

Data type Retention period
Account info Until account deleted, or 12 months after last login (inactive free accounts)
Email logs (Managed plans) Rolled off automatically after 14 days by a scheduled cleanup job. Exception: when an account is on a retention or security hold (see §3 and our Terms), its email logs and metadata are preserved beyond the standard 14-day window, for as long as the hold remains in place and any related investigation or legal obligation requires. End-users cannot delete individual logs — this is by design, so that bounce/complaint signals remain available for abuse detection and to respond to lawful requests.
API keys (hashed) Until revoked; revoked records purged after 30 days
Usage counters Monthly aggregates retained 24 months
HTTP request logs 30 days (rate-limiting / abuse only)
BYOC email content Never stored — zero retention by architecture
Email attachments Staged in S3 for delivery only; deleted immediately after successful dispatch (no persistent storage)

When you delete your account, all associated email logs, API keys, and usage records are scheduled for permanent deletion within 30 days. Exception: if the account is subject to a retention or legal hold, deletion is deferred until that hold is lifted.

07

Third-Party Services

We rely on a small number of trusted providers to operate SendFleet. These are the categories of data each provider processes:

Provider / purpose Data processed
Amazon Web Services — email delivery Sender, recipient, subject, body (Managed plans only)
Amazon Web Services — transient attachment handling Attachment content (deleted immediately after delivery; never written to our database)
Amazon Web Services — BYOC credential delegation IAM Role ARN (no email content)
Paddle — payments Email address, payment details
Managed cloud hosting & database All persisted data within our secured infrastructure
Managed cache service Rate-limit counters, usage counts, session cache
Google Fonts — typography User IP address on page load

We do not use advertising networks or third-party behavioural advertising systems.

08

Your Rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

  • Access — Request a copy of the personal data we hold about you.
  • Correction — Ask us to correct inaccurate or incomplete data.
  • Deletion — Request erasure of your account and associated data (also available self-serve in the dashboard).
  • Portability — Receive your email log data in a machine-readable format.
  • Objection / Restriction — Object to certain processing or request restriction while a dispute is resolved.
  • Withdrawal of consent — Where processing is based on consent, withdraw it at any time.

To exercise any of these rights, email [email protected]. We aim to respond within 14 days. We may need to verify your identity first. If you feel we haven't addressed your concern, you have the right to lodge a complaint with your local data protection authority.

09

Cookies & Tracking

Cookie Purpose Duration
sessionid Authenticated dashboard session Session / 2 weeks
csrftoken CSRF protection on form submissions 1 year (value rotated)

We may use analytics (e.g. Google Analytics) to understand aggregate product usage, diagnose issues, and improve the service. Analytics data is never used for personalised advertising. You can disable cookies in your browser settings, though doing so will prevent dashboard access.

10

Children's Privacy

SendFleet is a developer API service and is not directed at children under 16. We do not knowingly collect personal data from minors. If you believe a minor has registered an account, contact us immediately at [email protected] and we will delete the account promptly.

11

Changes to This Policy

We may update this Privacy Policy as SendFleet evolves. For material changes we will:

  • Update the "Last reviewed" date at the top of this page.
  • Email all registered accounts at least 14 days before changes take effect.
  • Where required by law, request your explicit re-acceptance.

Continued use of SendFleet after the effective date constitutes acceptance of the updated policy.

12

Contact Us

Questions about this Privacy Policy, data access requests, or concerns:

SendFleet Privacy Team
We aim to respond within 2 business days.
[email protected]