[ Legal ]
Data Processing Agreement
Last updated: November 12, 2026
This Data Processing Agreement ("DPA") is part of the Terms of Service between Postatron and you, the customer. It applies whenever Postatron processes personal data on your behalf, which it does for any business that schedules posts, manages accounts or answers comments through Postatron.
It takes effect when you accept the Terms, so there is nothing to sign. If your organisation needs a signed copy for its records, email support@postatron.com and we will countersign one.
1. Who we are, and the words we use
"Postatron", "we" and "us" mean Henry Wallis, a sole trader in the United Kingdom, trading as Postatron. "You" means the person or organisation that holds the Postatron account.
- Data Protection Law means the UK GDPR and the Data Protection Act 2018, and the EU GDPR (Regulation 2016/679) where it applies to you.
- Customer Personal Data means the personal data Postatron processes on your behalf to provide the service, as Annex 1 describes.
- Subprocessor means a company Postatron uses to process Customer Personal Data, listed on our Subprocessors page.
- Controller, processor, data subject, processing and personal data breach mean what they mean in Data Protection Law.
2. Roles
You are the controller of Customer Personal Data, and Postatron is your processor. If you are an agency acting for your own clients, you are their processor and Postatron is your subprocessor, and you pass their instructions on to us through your use of Postatron.
Postatron is a controller in its own right for the data it needs to run your account: your name and email address, billing and plan, sign-in sessions and usage. Our Privacy Policy covers that data, not this DPA.
3. Your responsibilities
You are responsible for having a lawful basis for the personal data you put into Postatron, for telling the people concerned what you do with it, and for having permission to connect each social account you connect, including your clients' accounts. Your instructions to us must comply with Data Protection Law.
4. Our responsibilities
- Instructions. We process Customer Personal Data only on your documented instructions: the Terms, this DPA, and what you do in Postatron, through the dashboard, the API, the MCP server or the command-line tool. If the law requires us to process it otherwise, we tell you first, unless the law forbids that.
- Unlawful instructions. We tell you if we believe an instruction breaks Data Protection Law.
- Confidentiality. Postatron is run by one person, and nobody else has access to Customer Personal Data. Anyone we ever give access is bound to keep it confidential.
- Security. We protect Customer Personal Data with the technical and organisational measures in Annex 2, and keep them up to date.
- People's rights. The dashboard and the API let you find, change and delete Customer Personal Data yourself, which covers most requests from the people concerned. We help with anything they cannot cover, and pass on to you any request we receive directly, without answering it ourselves.
- Assessments. We give you the information you reasonably need for a data protection impact assessment or a consultation with a regulator about Postatron.
5. Subprocessors
You authorise us to use the subprocessors on our Subprocessors page. Each works under written terms that protect Customer Personal Data at least as well as this DPA, and we remain responsible to you for what they do with it.
Before we add or replace a subprocessor, we update that page and email your account's owner at least 30 days ahead. You can object within that time on reasonable data protection grounds by writing to support@postatron.com. We will then work with you on an alternative; if we cannot find one, you may stop using Postatron and delete your account, as section 8 describes.
6. Transfers outside the UK and the EU
Postatron is based in the United Kingdom, which the European Commission recognises as giving adequate protection, and Customer Personal Data is stored on Amazon Web Services in the United States. Transfers to subprocessors in the United States are made under the safeguards in each subprocessor's data processing terms: the EU Standard Contractual Clauses with the UK International Data Transfer Addendum, or the EU-US Data Privacy Framework and its UK Extension where the subprocessor is certified.
7. Personal data breaches
If we become aware of a personal data breach affecting Customer Personal Data, we tell your account's owner by email without undue delay, and within 48 hours. We say what happened, the kinds of data and roughly how many people are affected, the likely consequences and what we have done about it, and we send more as we learn it, so you can meet your own duty to report it.
8. When you leave
You can delete any Customer Personal Data at any time while you use Postatron, and the API returns your posts and the links to their media if you want a copy first. When you delete your account, we delete Customer Personal Data from our live systems within 30 days, most of it at once, as our Data Deletion page describes. Our database backups roll over within a further 35 days and our service logs within 30, so it is gone from those too, unless the law requires us to keep something.
9. Showing that we comply
We make available the information you need to show that we meet this DPA: this page and its annexes, the Subprocessors page, and answers to your reasonable security questionnaires, up to once a year. If that is not enough, or a regulator requires it, you may audit our compliance, at your own cost, with 30 days' notice, under a duty of confidentiality and at most once in 12 months. Our subprocessors' own facilities are covered by their audit reports, which they make available, rather than by your audit.
10. Changes, precedence and law
We may update this DPA to follow the law or changes to Postatron, but never to protect Customer Personal Data less, and we email your account's owner at least 30 days before a material change. If this DPA and the Terms disagree about personal data, this DPA wins. It is governed by the same law as the Terms.
Annex 1: Details of the processing
- Subject matter: providing Postatron: creating, scheduling and publishing posts, analytics, the Inbox, DM automations, queues, team workspaces, the API, MCP server and command-line tool, connect links and webhooks.
- Duration: while you have a Postatron account, and then until deleted as section 8 describes.
- Nature: receiving data from you and from the platforms you connect, storing and organising it, showing it to you and your team, sending it to the platforms and addresses you choose, and deleting it.
- Purpose: only to provide Postatron to you, as you instruct.
- People concerned: your team members; people who appear in your posts, captions and media; the owners of the social accounts you connect, including your clients' accounts connected through connect links; and people who comment on or message your connected accounts.
- Kinds of data: names, usernames, profile pictures and IDs of connected accounts and their access tokens; the text, images and video of your posts, with anything personal you put in them; the numbers platforms report about your accounts and posts; comments and messages, which are read from the platform when you open the Inbox and not stored; the IDs of comments your automations answer; team members' names, email addresses and activity; and logs of what happened in your account.
- Special category data: Postatron does not need any, and you should only put it in posts if you have a lawful basis for publishing it.
- How long each is kept: as our Privacy Policy and Data Deletion page set out, for example analytics for an hour, follower counts for 13 months (30 days for YouTube), post numbers for 60 days and logs for 90 days.
Annex 2: Security measures
Encryption
- Every connection to Postatron's website and API uses HTTPS, and the site tells browsers to use nothing else on any of its addresses (HSTS, for two years).
- Postatron talks to Amazon Web Services and to every platform over TLS.
- The database (Amazon DynamoDB) and file storage (Amazon S3) are encrypted at rest with AES-256.
Credentials
- API keys and AI assistant tokens are stored only as one-way SHA-256 hashes, and an API key is shown once, when it is made.
- Platforms are connected through their own sign-in (Bluesky through an app password you create for it), so Postatron never sees your password for them, and their access tokens are used only for what you ask.
- Card details go straight to Stripe and never reach Postatron.
Access
- Every request is signed in, through Amazon Cognito, an API key or an OAuth token, and every read and write is checked against the account it belongs to.
- Team members see and change only the profiles they are given, and a member's access ends within a minute of being removed.
- Each part of Postatron runs with its own permissions in AWS, limited to the data and actions it needs.
- Uploaded media sits at random, unguessable addresses, because platforms have to fetch it to publish it; files attached to support tickets sit in a private store and are deleted within a day.
Protection against misuse
- Webhooks are signed, and are sent only to public addresses, checked again each time.
- The API is rate limited, and the routes that connect AI assistants and open connect links are throttled.
- The website cannot be framed by another site.
Resilience and monitoring
- The database has continuous backups, kept for 35 days.
- Every background step that fails is kept and retried rather than lost, and alarms email us about errors and failing posts.
Keeping less
- Comments and messages are never stored; DM automations keep only the IDs of what they answered.
- Logs record each API call's path and result, never what was sent.
- Postatron never uses Customer Personal Data for advertising or to train AI models, and never sells it.