You choose what is recorded, and readers can choose too.

Swarm runs in your own Cloudflare account, with no Swarm company in the middle. Turn tracking off for a publication, let readers opt out for themselves, limit how long history names a person, and answer data requests from one place.

  1. Step 1

    Switch tracking on or off for each publication

    When open tracking is on, each email carries a tiny image; when click tracking is on, links go through your link domain first. Either way Swarm records the time, the first part of the reader's network address, their network and browser family. No cookies are set, and privacy proxies and link scanners are labelled, never counted as people.

    All three switches are on for a new publication. Only admins and owners can change them, every change is in the audit log, and a switch turned off applies at once, also to emails already sent.

    Tracking settings for a publication: switches for Open tracking, Click tracking and Reader profiles, each saying what turning it off changes.
    The three tracking switches, under Sending and delivery.
    What each tracking switch does when it is off
    SwitchWhen it is off
    Open trackingNo image in emails. Send reports show "Not tracked" instead of an open rate. Reader profiles turn off too
    Click trackingLinks go straight to their address and nothing passes through Swarm. No clicks or click map, and automations can't wait for a click
    Reader profilesNo engagement scores and no best sending hour; existing ones are deleted. Best-time sending uses the time you chose, and the inactive-reader cleanup does not run
  2. Step 2

    Let each reader say no for themselves

    The settings page linked from every email has Don't track my opens and clicks. When a reader ticks it, their emails carry no image and plain links, and the opens and clicks recorded for them so far are deleted.

    • No score, no best hour, never unsubscribed as inactive, and never picked for "send again to people who didn't open".
    • Reports stay true: past send reports keep their numbers, and new ones leave them out of the open rate and say how many there were.
    • Unsubscribe links keep working, and the reader can untick it again whenever they like.
    Subscriber settings, with "Don't track my opens and clicks".
  3. Step 3

    Choose how long history names a person

    Under Settings, Privacy, Engagement history sets how long deliveries, opens, clicks and per-send copies of addresses stay tied to a person: 6 months, 13 months (the default), 2 years or 3 years. There is no "keep forever": nothing in Swarm looks back further than 90 days.

    Past the limit, every number on a send report stays the same. The person's activity no longer lists those emails, and unsubscribe links in emails that old stop working; readers can use a newer email or their settings page.

    Engagement history in Settings, Privacy: keep engagement history for 6 months, 13 months (the default), 2 years or 3 years. After that, records no longer name the person and send reports keep every number.
    How long engagement history names a person.
    What happens to history past the limit
    RecordWhat happens
    DeliveriesThe subscriber, the address, the message id and any error are removed; status and times stay
    Opens and clicksNetwork and browser details are removed; the row stays, so link counts stay
    Per-send copies of a postDeleted
    Soft-bounce recordsDeleted after 30 days whatever the setting
    Blocked addressesNever touched: they are how Swarm keeps not mailing someone
  4. Step 4

    Answer data requests from one place

    Readers ask for a copy of their data, or for its deletion, from their settings page. You can file a request for them too, when one arrives by email or letter. The Privacy Center lists every request with its due date: a copy within 24 hours, a deletion within 30 days.

    • A copy is a file of everything Swarm holds on that address in the workspace, sent as a download link that works for 7 days.
    • A deletion removes the address from every publication of the workspace with its history, and keeps only a hash so it is never added again.
    • Confirmed from the inbox: a deletion asked for from the settings page waits for a confirmation link, so someone holding a forwarded email can't erase a reader.
    The Privacy Center: requests for a copy of data or its deletion, exports due within 24 hours and erasures within 30 days; New request; filters; an export waiting for approval, due in 19 hours; an erasure waiting for approval, due in 26 days; and two done in time.
    The Privacy Center, with requests waiting and done. Sample data.
  5. Step 6

    Encrypt what is sensitive

    A profile field can be encrypted when stored, for a birthday, a phone number or anything you would rather not keep in plain text. Segments can then only test whether the field is set.

    • Only what is needed: network addresses are shortened to their first three parts everywhere Swarm keeps one, and sign-in links and session cookies are stored only as hashes.
    • Keep your keys: encrypted fields can only be read with the keys in the .swarm/ folder the installer makes. Back it up.
    Add a profile field: Date of birth, key date_of_birth, type Date, and Encrypt this field ticked: values are encrypted when stored, and segments can only test whether the field is set.
    A profile field encrypted when stored.
  6. Step 7

    A website that sets no tracking cookie

    Swarm's own website analytics use no cookies and store daily totals. Publication websites load nothing from other companies unless you add it under Cookies and code, where analytics and marketing tools wait for each reader's agreement in the cookie popup.

    If an owner marks a known tracking tool as strictly necessary, Swarm asks them to confirm and records it in the audit log. Most cookie rules say such tools must wait for the reader.

    Cookies and code: Show a cookie popup on my website, the message, Accept and Reject buttons shown just as prominently, the cookie policy link and where the popup sits.
    The cookie popup for code you add to a website.

Read the tracking and retention guide

The GDPR, in practice

Swarm is software you run yourself. Your data sits in your own Cloudflare account and goes only to the services you connect: your email service, and Stripe or PayPal if you sell. The GDPR guide explains who is responsible for what, with a record of processing to copy and a privacy notice checklist.

Read the GDPR guide

  • You are the controller for your subscribers. If you run Swarm for other people, you process their subscribers' data for them and need an agreement with each.
  • A list of subprocessors says what each service receives and where, and every publication website links to it.
  • Every data request step is written to the workspace's audit log, without the address.

What Swarm does not do for you: choose your lawful basis, write your privacy notice, sign agreements with your services, or delete data held by them: your email service's logs, Stripe records, files teammates downloaded, or your backups.

It does not keep data in the EU by itself either: where the database lives depends on how you set it up. This is practical help, not legal advice.

Privacy that starts with where the data lives.

Install Swarm on your own Cloudflare account, then choose for each publication what it records and for how long.

Install from a terminal
git clone https://github.com/jntegz/swarm-newsletter.git swarm
cd swarm && pnpm install
pnpm swarm

Want to look first? pnpm swarm --dry-run shows every step and changes nothing.