Privacy Policy
Last updated 16 November 2026
What personal data Postyard handles, why, where it is stored, how long we keep it, and how to use your rights.
Who we are
Postyard is operated by IHAR LITVINOVICH (sole proprietorship), Poland. NIP 7011083588.
Email support@postyard.dev about this policy or your data.
We are the controller for data about visitors to our website, people who request early access, and our customers' accounts, billing and use of the service.
The mail and other content an organization keeps in Postyard belongs to that organization. It decides what is stored and who can reach it, and we process it on its behalf, as its processor, under our Terms.
What we collect and why
Early-access requests
When you request access on postyard.dev we receive your email address, what you'll use
Postyard for (if you tell us), the campaign tags of the link that brought you
(utm_source, utm_medium and utm_campaign), the
origin of the website that sent you (such as https://news.ycombinator.com,
never the page address), and the time. To stop abuse we also keep a keyed hash of your
IP address, never the address itself.
The request is emailed to our support inbox. We use it to review your request, invite you, and see which campaigns bring requests. Until you have an account, your request isn't linked to the browser analytics described below. Once you sign up, our server events for your account and, if you allowed analytics, your browser's events share your account ID.
Legal basis: steps you ask us to take before a contract (GDPR Art. 6(1)(b)), and our legitimate interest in preventing abuse and knowing which campaigns work (Art. 6(1)(f)).
Your account
Clerk runs sign-in. It holds your name, email address and password or sign-in method. Postyard stores your Clerk user ID, the organizations you belong to, your role in each, and which mailboxes you can use.
Legal basis: our contract with you (Art. 6(1)(b)).
Your organization's mail and settings
The domains you add and their DNS check results; mailboxes, aliases and app passwords; every message and attachment, with its senders, recipients and subject; drafts, folders and read state; send, delivery and bounce history; API keys, which we store only as hashes; and webhook endpoints with their delivery history.
We store and process this only to run the service for your organization. API keys and AI agents act only on behalf of the organization that created or connected them. When an agent reads your mail, its own provider handles what it reads under that provider's terms.
Legal basis: our contract with your organization (Art. 6(1)(b)). For the personal data inside your mail, we act on your organization's instructions as its processor.
Support
What you send to support@postyard.dev or through the app's support form, and diagnostics if you choose to include them.
Legal basis: our contract with you, and our legitimate interest in answering questions (Art. 6(1)(b) and (f)).
Payments
Stripe handles payments, and we never see your full card number. We keep your Stripe customer ID, your billing period and whether you're a paying customer. Stripe sends us payment and invoice details.
Legal basis: our contract with you (Art. 6(1)(b)), and our duty to keep invoices and tax records (Art. 6(1)(c)).
Logs and security
For each API request we log the route (such as /v1/mailboxes/{id}), the
result, how long it took, and which API key or connection made it, but not your IP
address. Our mail server records connection details, such as the sending server's IP
address, to deliver mail and fight spam.
Legal basis: our legitimate interest in keeping the service secure and working (Art. 6(1)(f)).
Analytics in your browser (Amplitude, with your consent)
On postyard.dev and app.postyard.dev we'd like to measure how Postyard is used, with Amplitude in its EU data centre. We only do this if you choose Allow in the banner. If you choose No thanks, or don't choose, Amplitude isn't started and nothing is sent to it.
With your consent, Amplitude records:
-
the pages and screens you open, as a path such as
/privacyor a pattern such as/domains/$id, never the full address; -
your visits (sessions), the campaign you arrived from (
utm_source,utm_mediumandutm_campaign) and the domain of the site that sent you; - actions such as clicking a button, trying the price calculator, requesting access, adding a domain or sending a message, described with counts, yes-or-no values and fixed categories;
- your browser and operating system, device type and language (sent by your browser).
Amplitude keeps a random device ID in a cookie on postyard.dev, so a visit to the site and later use of the app count as the same device. In the app, events are linked to your Clerk user ID and organization ID.
We never send Amplitude your email address, name, domain names, mail addresses, message content or subjects, recipients, anything you type, or API keys. No location either: we blank the IP address in every event before it reaches Amplitude. We don't use session recording.
Legal basis: your consent (Art. 6(1)(a)). You can withdraw it at any time with Privacy settings at the bottom of every page of postyard.dev, or in the app. Withdrawing stops Amplitude and removes its cookies and storage from your browser.
Analytics from our servers (Amplitude)
Our servers also send Amplitude a short list of business milestones: an early-access request received or invited, an account or organization created, a domain verified or enabled for sending, a mailbox created, the first mail sent and received, a usage limit reached, sending paused, a subscription started or ended, a support request received, and, once a day, whether an organization used the API or MCP.
These carry your Clerk user ID and organization ID (before you sign up, an internal request number), plus counts and fixed categories such as the campaign code you arrived with. Nothing is read from or stored in your browser, so they are sent whether or not you choose Allow.
Legal basis: our legitimate interest in knowing whether customers get Postyard working and which campaigns bring them (Art. 6(1)(f)). You can object at any time by emailing support@postyard.dev; we'll stop sending these for your account within 30 days. We keep a record of your objection, so that it stays in force.
Error reports (Sentry)
When we enable error tracking, we'll use Sentry's EU (Germany) region. Our servers will then send reports of errors in Postyard's own code to Sentry, with user, request and host details, and anything that looks like an email address, removed before a report is sent.
Legal basis: our legitimate interest in finding and fixing faults (Art. 6(1)(f)).
What we never do
- Sell your personal data, or share it for advertising.
- Use the content of your mail for analytics or advertising, or to train AI models.
- Put advertising pixels or session recordings on postyard.dev or in the app.
- Send automatic emails from the early-access form. The only email it can lead to is our invitation, sent by a person.
Cookies and browser storage
postyard.dev sets nothing in your browser until you make a choice in the banner, and nothing beyond that choice unless you choose Allow.
| Name | What it's for | When and how long |
|---|---|---|
py_consent (cookie on postyard.dev and app.postyard.dev) |
Remembers whether you chose Allow or No thanks | Set when you choose; 12 months |
AMP_… (Amplitude cookies and local storage) |
A random device ID, the current visit, and events waiting to be sent | Only after Allow; up to 12 months. Removed when you withdraw consent |
py_first_touch (session storage, postyard.dev) |
The utm_source, utm_medium and utm_campaign
tags and the referring site of your first visit, so an early-access request still
names them after you've looked at other pages
|
Only after Allow; deleted when you close the tab, or when you withdraw consent |
| Clerk cookies (app.postyard.dev and its sign-in pages) | Keep you signed in to the app | Needed for the app; set when you sign in |
| App preferences (local storage, app.postyard.dev) | Interface choices, such as your setup checklist | Needed for the app; until you clear them |
Who processes your data, and where
| Provider | What it does for us | Where |
|---|---|---|
| OVHcloud | Runs our servers: the app, the API, the database and the mail server, with all mail content | Beauharnois, Canada |
| Amazon Web Services: SES | Delivers outgoing mail to external recipients, and reports bounces and complaints | United States (N. Virginia) |
| Amazon Web Services: S3 | Stores our encrypted daily database backups | United States (Oregon) |
| Clerk | Sign-in, accounts, organizations and invitations | United States |
| Stripe | Payments, invoices and billing records | European Union and United States |
| Amplitude | Product analytics, as described above | European Union (Amplitude's EU data centre) |
| Sentry | Error reports from our servers, once we enable error tracking | European Union (Sentry's EU region, Germany) |
Mail you send also passes through the recipients' own mail servers, and anything you send to a webhook or a connected agent goes where you point it.
Some of these places are outside the European Economic Area. Canada has an adequacy decision from the European Commission for commercial organizations. For providers in the United States, transfers rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses in the provider's data processing terms. Email us for details of the safeguard that applies.
How long we keep it
Cleanup jobs run regularly, so a record is removed shortly after its period ends, not to the second.
| Record | How long |
|---|---|
| Early-access requests we haven't invited | 180 days |
| Early-access requests we've invited | Kept with your customer record; deleted after 12 months if they never become an account |
| Account and customer records | While your organization uses Postyard |
| Invoices and billing records | For as long as Polish tax law requires (generally 5 years from the end of the year in which the tax became due) |
| Mail in your mailboxes | As long as you keep it. When an organization is deleted, its mailboxes are suspended at once and its mail is erased after 7 days |
| Send and delivery history of each message | 180 days |
| Amazon SES message IDs, to match late replies, bounces and complaints | 730 days |
| Counts of outbound recipients, for usage limits | 400 days |
| API request logs | 30 days |
| Webhook deliveries and their events | 30 days after the delivery finishes |
| Mailbox export files | 24 hours |
| Database backups | Taken daily; we keep the 14 most recent, and the files of older ones are deleted 30 days later, so about 44 days in all. Data you delete stays in backups until they expire |
| Server logs | Rotated by size, at most 30 MB for each service, so older lines are overwritten |
| Support emails | As long as we need them to help you and keep a record of what we agreed |
| Analytics events in Amplitude | Deleted after 12 months; a person's events sooner, on request |
| Your objection to server analytics | As long as it applies, so we keep honouring it |
The py_consent cookie | 12 months |
Your rights
Under the GDPR you can ask us to:
- give you a copy of your personal data (access), or a portable copy of what you gave us;
- correct it;
- delete it;
- restrict how we use it;
- stop using it where we rely on legitimate interest (objection); for server analytics we stop for your account within 30 days.
Where we rely on your consent you can withdraw it at any time, with Privacy settings; that doesn't affect what happened before.
Email support@postyard.dev from the address the request is about. We answer within one month. If your data is in another organization's mailboxes, that organization decides what happens to it, and we'll pass your request on.
You can also complain to the Polish data protection authority, UODO (Prezes Urzędu Ochrony Danych Osobowych), or to the authority where you live or work.
We don't make decisions about you by automated means that have legal or similar effects.
Changes to this policy
When this policy changes we update the date at the top. If a change matters to customers, we email them before it takes effect. A new use that needs consent is asked for separately.