Sub-processors
Last updated 16 November 2026
Peoplume relies on the services below, each with a narrow job. Email is sent through Resend for every company. Anthropic receives data only for a company whose administrator switches receipt reading or the AI assistant on in Settings; both are off by default. Push services are used only for devices where someone turns notifications on. This list changes when the software does — see Privacy for what is stored in the first place.
Always used
| Service | Purpose | What it receives |
|---|---|---|
| Railway | Application hosting and the database volume. | Everything, as the host — this is where the application and its database run. |
| Cloudflare | DNS and reverse proxy in front of the application; R2 object storage holding every uploaded file and the off-site database backups; Web Analytics, a cookieless page-view counter injected into our public and application pages. | Page views and referrers from the analytics beacon — no cookie, no profile, no cross-site tracking. Requests in transit; every file uploaded to Peoplume — employment contracts, identity documents, expense receipts, candidate CVs, company policies and logos — and backup copies of the database. R2 encrypts what it stores at rest; we do not encrypt it ourselves before it is sent, so Cloudflare holds it in a form it could read. |
| GitHub (Microsoft) | Runs the nightly database backup and a daily read-back of the newest off-site copy, and the support commands a Peoplume owner runs outside the product (clearing a sole Administrator's two-step verification, removing a login nobody ever used, deleting a company on request, giving or removing Peoplume staff access, and emailing every company's Administrators a notice we owe them), on GitHub-hosted runners. | Each night's full copy of the database, in transit, which it also keeps for 7 days as a build artifact; we do not encrypt it ourselves, so GitHub holds it in a form it could read. For each support command, its inputs and what it prints, kept with the run: an account's email, a company's name and id, the names of the people the command concerns, and the reason recorded. Each day, the newest off-site copy again, in transit, deleted when the check ends. For a notice to Administrators: the notice's name, and the names and ids of companies and counts, never an Administrator's address. |
| Resend | Delivers transactional email: the link that confirms a sign-up, notifications and the monthly digest, invitations, password reset links, links confirming a new sign-in address, security notices, service notices to Administrators, and messages to job candidates (including an offer's response link, and a self-scheduling link when a recruiter emails it). Sign-up cannot be completed without it, so it is used for every company. | Recipient address, the sender name (your company's name, followed by “via Peoplume”, on notification copies, the monthly digest and candidate emails; account and security emails are sent as Peoplume), the subject and the message body, and, where an email has one, the address a reply goes to. Each person can turn off email copies of their notifications (the notification still appears in the app); security notices, such as a password change or reset, ignore that setting. So do Peoplume's own service notices to a company's Administrators (a new sub-processor, a breach). |
Push notifications — only for devices that turn them on
| Service | Purpose | What it receives |
|---|---|---|
| Google, Apple and Mozilla push services | Relay a notification to a phone or browser where the person turned notifications on for that device. Which one depends on the browser: Chrome and Android use Google's, Safari and iPhone use Apple's, Firefox uses Mozilla's. | An encrypted message they cannot read — the content is encrypted to the device's own key — and the fact that a message was sent to that device. No name, no employee data, no account identifier beyond the device's own subscription address. |
| Expo (650 Industries, Inc.) | Delivers notifications to the Peoplume phone app, handing each one to Apple's or Google's push service. Used only for phones where the employee installed the app, signed in and allowed notifications. | The phone's push token and a deliberately generic alert: the word Peoplume, one line such as “Leave update” or “A payslip is ready”, and an in-app link. Unlike browser push this message is not encrypted to the device, so Expo, Apple and Google could read it — which is why it never carries a name, a date, an amount or anything anyone wrote, and why the link names the page only where that says nothing sensitive: for a one-to-one, an improvement plan or a probation the link is the app's own inbox, so the message does not say that someone is on a plan. The app fetches the detail, and the page it belongs to, from us after it is opened. |
Payments
| Service | Purpose | What it receives |
|---|---|---|
| Paddle | Takes subscription payments as merchant of record, which means Paddle sells to you, charges any sales tax due where you are, and remits it; its customer portal, opened from Billing, holds your invoices and payment method. | Your billing contact details and payment method, which go to Paddle directly — typed into Paddle's own checkout, which our payment page loads from Paddle — and never reach us; we hold a subscription status, the seats, price and interval it bills, and Paddle's own identifiers, and keep each payment notification Paddle sends as those facts and its dates only, never the card or billing details it also carries. Once a day we send Paddle any change in the number of seats: the employees who are not terminated (at least the minimum) — a count, never a name. No employee data is sent. |
Only for companies that switch a feature on
| Service | Purpose | What it receives | If switched off |
|---|---|---|---|
| Anthropic | Two features, each off until an administrator switches it on: reads a photographed expense receipt and suggests the total, date, merchant and category for the claim form — and, where the employer records tax on claims, the tax and the supplier's tax number; a total in another currency than the claim's is not filled in, and the person enters the amount themselves; and answers questions asked of the AI assistant. | For receipts: the receipt image and the company's list of expense category names (so the reader can suggest one of them), only when an administrator has switched receipt scanning on for the company (it is off by default, and not available during a free trial), and only when someone presses the button for that receipt. For the assistant: the question; the asker's name, the company's name and today's date; the earlier questions and answers of the same conversation (up to 20 messages, as text — rows looked up for an earlier question are not sent again); and the rows looked up to answer it, each lookup sending its whole fixed set of fields — which are only rows the asking person could already open in Peoplume — and only when an administrator has switched the assistant on for the company (it is off by default). Nothing is sent automatically. Anthropic handles it under its own Commercial Terms of Service and Data Processing Addendum, not terms Peoplume negotiated. Peoplume does not promise that Anthropic will not use it to train or improve its models, or keep what it uses for that. Anthropic's published policy for API customers is to delete what it receives within 30 days, except content its automated safety systems flag under its Usage Policy (kept for up to 2 years, with the safety classification scores for up to 7 years) and anything the law requires it to keep longer. Peoplume has no zero-data-retention arrangement with Anthropic. To reduce cost, each assistant request is cached for about five minutes after its last use (a receipt request is never cached); Anthropic says the cache holds an internal representation of the prompt in memory, not the question or the answer themselves. Peoplume stores no conversation. | The receipt button is not shown, and the assistant page says the assistant is switched off. Employees type receipt details in themselves. |
Whatever the receipt reader returns is treated as a suggestion and re-validated on our side before it reaches a field — the amount must be a plain positive number, the date cannot be in the future, a total in another currency than the claim's is never filled in (there is no conversion), and the category must be one of the company's own rather than whatever the model decided to call it. It fills in a form that a person still submits and an approver still approves. No amount reaches a payslip because a model read it.
The assistant is read-only by construction: it can call a fixed list of lookups, each of which runs the same permission and branch checks as the page for that data, and none of which can approve, file, pay or edit anything. During a free trial a company can ask it 20 questions in total.
What is not here
There is no advertising or marketing pixel, no session-recording tool, no error-reporting service and no third-party chat widget. Nothing about your employees is sent anywhere for our own purposes.
Analytics is the one exception, and it used to be on this list. Cloudflare Web Analytics counts page views and referrers; it is cookieless, builds no profile and cannot follow anyone to another site. It is injected by Cloudflare at the edge rather than added in our code, which is why it went unlisted until a content security policy blocked it and made it visible. It sees pages, not people: no employee record, name or document is involved.
Job boards and search engines that fetch a job feed or careers page an employer chooses to publish receive only the job details it publishes; they are not our sub-processors.
