Skip to content

Data regions

PostStack runs in one region: the EU. Your email content, contacts and logs are processed and stored in Helsinki, Finland — there is no other region to pick and no transfer to configure.

Where your data lives#

Region codeLocationAPI base URLStatus
euHelsinki, Finlandhttps://api.poststack.devActive (default)

Servers, storage, networking and backups are provided by Hetzner Online GmbH in its Helsinki (hel1) data centre. Outbound and inbound email, contacts, templates, attachments, delivery events, webhook delivery logs and audit logs all stay there. The API, the SMTP relay (smtp.poststack.dev) and the dashboard use the same infrastructure, so there is no regional endpoint to choose and no setting to get wrong.

Two services outside that infrastructure see limited data, and neither receives email content, recipient lists or message metadata:

  • Stripe (Ireland) processes payments for paid plans and receives billing contact details.
  • GitHub (United States) is involved only if a user chooses Sign in with GitHub, and receives that user's profile data.

The authoritative list is on the sub-processors page; the contractual terms are in the DPA.

Why only the EU#

PostStack is run by MICCI, a company in Vejle, Denmark. Operating entirely inside the EU gives a single, simple answer to data-residency, GDPR and cross-border transfer questions: your mail data is not transferred out of the EU. One region, done well, instead of a choice you would have to get right for every team.

Mail you send is, by its nature, delivered to your recipients' mail servers, wherever those are. Residency covers what PostStack stores and processes, not the inboxes you send to.

What stays where#

The same answer for every kind of data, with the one difference that matters in a review: how long each is kept.

DataWhereHow long
Sent email records: recipients, subject, body, delivery eventsHelsinkiYour plan's log retention: 14 days on Free and Starter, 30 on Pro, 90 on Scale, unlimited on Enterprise
Contacts, segments, subscription topics, templatesHelsinkiUntil you delete them
Mailboxes and the mail in themHelsinkiUntil deleted
Suppression listHelsinkiUntil removed — see Suppressions
Database backupsHelsinkiDaily, GPG-encrypted (AES-256), integrity-checked before the previous one is pruned

Deleting a contact or closing a team removes the rows from the live database; backups age out on their own schedule. The full description of technical and organisational measures is in section 6 of the DPA.

Point your code at the EU region#

There is nothing to configure: the SDKs, the SMTP relay and the dashboard all default to the only region. If your compliance notes have to show where traffic goes, make the endpoint explicit in configuration instead of relying on the default — the behaviour is identical.

import { PostStack } from '@poststack.dev/sdk';

// No region option: every request goes to https://api.poststack.dev,
// which is served from Helsinki.
const poststack = new PostStack(process.env.POSTSTACK_API_KEY!);

Mail you receive follows the same path: a domain whose MX points at inbound.poststack.dev is received, filtered and stored in Helsinki, and inbound webhooks are sent from there to your endpoint.

Discover regions over the API#

List regions#

The public region catalogue. No authentication. Also served at https://poststack.dev/api/public/regions.

GEThttps://api.poststack.dev/public/regions
Request
curl https://api.poststack.dev/public/regions
{
  "regions": [
    {
      "code": "eu",
      "name": "Europe",
      "location": "Helsinki, Finland",
      "apiUrl": "https://api.poststack.dev",
      "status": "active",
      "isDefault": true
    }
  ]
}

Response fields

regions[].codestring
Region identifier.
regions[].namestring
Display name.
regions[].locationstring
Data-centre location.
regions[].apiUrlstring
API base URL for the region.
regions[].status"active" | "draining" | "disabled"
active: serving and accepting signups; draining: serving existing teams, no new signups; disabled: offline.
regions[].isDefaultboolean
The region new accounts are created in.

Status codes

StatusMeaning
200The catalogue. Cached for up to 60 seconds.
429More than 30 requests per minute from your IP address.
500The catalogue could not be loaded.

Check the region in CI#

A data-residency claim in a record of processing is only true while nothing changes underneath it. Because the catalogue is public, a ten-line check in your pipeline can turn a silent change into a failed build:

typescript
// Fail a deploy if the region catalogue ever stops matching what your
// records of processing say. No API key needed.
const res = await fetch('https://api.poststack.dev/public/regions');
const { regions } = (await res.json()) as {
  regions: { code: string; location: string; isDefault: boolean }[];
};

const current = regions.find((r) => r.isDefault);
if (current?.code !== 'eu' || !current.location.endsWith('Finland')) {
  throw new Error(`Unexpected PostStack region: ${JSON.stringify(current)}`);
}

The check is a backstop, not the notice: section 10 of the DPA commits PostStack to telling you in advance before personal data is processed anywhere outside the EEA.

Questions from data-protection reviews#

Can I choose a region outside the EU?

No. There is one region, and new teams are created in it. If you need mail processed in another jurisdiction, PostStack is not the right fit for that traffic.

Is delivering to a US mailbox provider a transfer?

Delivery to the recipient's own mail server is the purpose of sending the message, so it happens wherever that server is. What PostStack stores — the copy of the message, its events, the logs — stays in Helsinki.

Are open and click tracking served from the EU?

Yes. Tracking pixels and click redirects are served by the same Helsinki infrastructure, and the IP address and user agent they record are stored there. You can turn tracking off for a domain, or per message on API sends — see Tracking.

What do I sign?

The Data Processing Agreement applies to every team on acceptance of the terms; the current list of sub-processors and what each receives is on the sub-processors page. The security page covers encryption and access control.

Next steps

Was this page helpful?

Related

Background reading