Skip to content
Legal Document

Privacy
Policy.

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

Effective April 30, 2026
Last reviewed: May 18, 2026
BYOC privacy guarantee

On Starter and BYOC plans, email content - subject, body, recipient - is never written to our database. We assume your IAM role with temporary 15-minute credentials and dispatch directly to your SES. Only a monthly send counter is stored for Starter rate-limiting. This is an architectural constraint, not a policy choice.

BYOC = zero content stored
Email bodies, subjects, and recipients never touch our DB 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 (Growth/Pro).

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

FieldWhyRequired?
Email addressAuthentication, identity, service communicationsYes
Display namePersonalisation inside the dashboardNo
Password (hashed)Authentication - never stored in plaintextYes
Account creation dateAudit trail and supportAuto

API usage data (Shared SES only)

FieldWhy
Sender name & emailForming the outbound From header
Subject linePassed through to email; stored in your log
Message bodyPassed through to email; stored in your log
Request timestampLog ordering, usage calculation, rate-limit enforcement
Delivery statusDisplayed in your dashboard; used for retry logic
Message IDReturned 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.
  • 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 within 2 minutes via Redis cache.
  • 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.

Shared SES path (Growth / Pro)

Email content is queued in AWS SQS, delivered via our managed SES account, and written to your email log. Bounce and complaint events from SES SNS are processed and written to your dashboard. All content is stored for 90 days and then purged. 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 path (Starter / BYOC plan)

we assumes your IAM role using temporary STS credentials (15-minute session) with your ExternalId. It dispatches directly to your SES. 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 typeRetention period
Account infoUntil account deleted, or 12 months after last login (inactive free)
Email logs (Shared SES)Rolling 90 days; deletable on request
API keys (hashed)Until revoked; revoked records purged after 30 days
Usage countersMonthly aggregates retained 24 months
HTTP request logs30 days (rate-limiting / abuse only)
BYOC email contentNever stored - zero retention by architecture
Email attachmentsStaged 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.

07

Third-Party Services

ProviderPurposeData shared
AWS SESEmail delivery (Shared SES path)Sender, recipient, subject, body
AWS S3Transient attachment staging during deliveryAttachment content (deleted immediately after delivery; never written to our DB)
AWS SQS + LambdaAsync email queueing and processingFull email payload (Shared path only)
AWS STSTemporary credential issuance for BYOCIAM Role ARN, ExternalId (no email content)
PaddlePayment processing and subscription managementEmail address, payment details
Cloud host (Render/Railway)Infrastructure and database hostingAll persisted data within our secured DB
Redis (Upstash)Rate-limiting, usage caching, session cacheRate limit counters, usage counts
Google FontsFont deliveryUser 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

CookiePurposeDuration
sessionidAuthenticated dashboard sessionSession / 2 weeks
csrftokenCSRF protection on form submissions1 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]