Privacy

Last updated 16 November 2026

Peoplume is HR software sold to employers. Almost everything in it is personal data about someone’s staff, so this page sets out exactly what is stored, who else can see it, and how it leaves again.

Who is who. Under GDPR-style terminology, the employer using Peoplume is the data controller — they decide what to record about their people. Peoplume is a processor, acting on the employer’s instructions. If you are an employee and want your record corrected or removed, ask your employer’s HR team; they hold the controls, not us.

What is stored

Only what the employer enters or the product generates. Nothing is collected from third parties, bought from data brokers, or inferred about anyone.

CategoryFields
Identity & contactName, employee number, work email, phone, address, date of birth, gender, nationality, marital status, emergency contact name and phone. Every one of these except name and employee number is optional.
EmploymentHire date, probation end and the decision recorded when a probation ends (confirmed, extended to a new end date, or not confirmed, with a note and who recorded it), a direct manager's recommendation on a probation before it is decided (confirm, extend to a date, or do not confirm, with an optional note for HR, which the employee is not shown), employment type, department (and who heads each department), job title, branch, shift, an own work week (the weekly days off) where the employer sets one instead of the branch's, reporting manager, status and termination date, a dated record of each change of branch, job title and employment type (from what, to what and the day it took effect), free-text notes.
PayBasic salary or hourly rate, allowances and deductions (with the months they are paid in), loans, bank name and IBAN, payslips, a history of salary changes, and pay holds (the months an employee's pay is kept out of payroll, the reason HR gives and who set and released the hold). Approved payroll runs are immutable snapshots by design.
TimeAttendance records (date, check-in and check-out as times of day), leave requests (with the notes approvers and HR write on them), stated leave figures (the days an employee carried over from the employer's earlier records, extra days HR adds to or takes off a year's allowance, and, for a leave type tracked from part-way through a year, the days carried into that year and used in it before Peoplume began tracking it, each with the reason HR gives for the figure and who recorded it), timesheets and project hours (with the activity booked and the actions recorded on each timesheet: who, when and any comment). Portal and phone-app check-ins may include the device's location when the employee's device allows it (the punch is never blocked if it does not), and then the punch's distance from the branch's location as set at that moment, where the branch has one.
ExpensesExpense claims: title, category, amount, date, notes and a receipt, and optionally a project the claim is for; where the employer records tax, the tax inside the amount and the supplier's tax number; for a mileage claim, the distance entered on the claim (by the employee, or by HR filing it on their behalf) and the employer's rate it was priced at. Trip reports that group claims: title, dates and purpose. Travel advances: the amount asked for and approved, the reason given, when and how the money was handed over, and how it was settled. A claim in a trip report that has not been sent goes to no approver: it is on no approval page, list or queue and in no expenses export — at most counted — and nobody decides it until the report is sent. The employer can still see it: in the company's full data archive and in a data export of that employee, both marking it as not sent; in the audit log, which records its title and amount when someone files it on the employee's behalf or the employee moves it into or out of a report; and, on a trip report HR set up on the employee's behalf, on that report's page, receipts included, to the employer's staff who can view expenses for that employee.
DocumentsFiles the employer or the employee uploads: contracts, IDs, certificates, expense receipts (uploaded in the portal or photographed in the phone app), candidate CVs, company policies, and a company logo.
FamilyDependents the employer records for sponsorship and benefits: name, relationship, optional date of birth and nationality, whether the company sponsors them, and one identity document's type, number and expiry. These are people who are not users and cannot sign in; the employee sees the list on their own profile.
Performance & developmentGoals (with notes, progress, the review cycle they belong to, and goals an employee proposes), review cycles and who each one covers (with the words a cycle gives each point of its rating scale), reviews and ratings (with the answers and scores given to each of the cycle's questions, and the employee's own comment on a review they have been shown), self-assessments (with a self-rating and answers to the cycle's questions), peer feedback, suggestions of colleagues to give peer feedback (made by the employee or their manager, with the reason given and what HR decided), one-to-ones a manager records with a direct report (the date, notes shared with the employee, the manager's private notes, which the employee is never shown, and action items), performance improvement plans (dates, objectives, the goals tied to them, dated check-ins and the outcome), training enrolments, the sessions booked and the attendance recorded, certificate files, the reason an employee gives when asking for a course or for a certificate to be renewed (and the day HR declined a renewal request, when it did), and succession plans (with the appointments made and the month a successor is expected to be ready).
RecruitmentJob openings: title, department, branch, positions, the monthly salary range and its currency, why the seat is needed, and the employee a hire replaces, if any; for the careers page, a closing date, a city and whether the range is shown. Job requisitions: each request to open an opening or to change its salary range, positions, branch or department — what it asked for, who sent and decided it, when, and the reason given for a decline. Hiring teams: each opening's hiring manager and team members, and who added them and when. Applicants — including applications submitted through an employer's public careers page: name, email, phone, CV, where they heard of the role (source — typed by the employer, or the channel the careers link was made for, such as LinkedIn), the recruiter's notes, whether an applicant is an internal candidate (the employee record they already are), which employee referred them, and which earlier application they were put forward from; whether and when the candidate asked to be kept for future roles, until when, and when that request was withdrawn at their request; and a dated history of the application (stage moves, why an application ended — withdrew, declined the offer, not a fit, position filled or other — recorded when it is rejected, with any later correction, notes added to it, corrections to the candidate's details before and after, interviews scheduled and their changes, offer changes, who made each, and when a rejection email was sent). The hiring manager's recommendation on a candidate — advance to a stage, make an offer, or reject with a reason — with an optional note for HR, who made it and when.
Interviews & offersInterviews: date, time, the time zone they are read in, place, the interview panel (up to six colleagues, one the lead) and status; each panelist's own notes, overall rating and scorecard ratings, against the criteria fixed when the interview was scheduled (the role's own or the employer's). A self-scheduling link's note, the panel offered, who created it, the times offered and the time booked, and whether it was emailed to the candidate. Offers: position, salary and its currency, start date, branch, notes, status, who sent and approved it, the letter wording approved and its respond-by date; and the candidate's online response link — when it was issued and until when it works — and whether and when they accepted or declined it online, with any reason they typed, never their IP address or device. Accepting online is a record of the answer, not an electronic signature. A self-scheduling link and an offer's response link are themselves stored only as a hash.
Candidate emailsEmails a recruiter writes to a candidate from Peoplume: subject, text, the address it went to, who sent it and when; the history records that an email was sent, with its subject. The employer's own wording for its candidate emails and offer letter, and the snippets its recruiters start emails from. Emails to candidates name the employer; a reply goes to the recruiting contact address the employer sets, and with none set the email asks the candidate to contact the employer's hiring team instead of replying — except an email a recruiter writes, whose reply then goes to the recruiter's own login email, which the recruiter is shown before sending.
Account & securityLogin email, a bcrypt hash of the password (never the password), last login time and the last sign-in through the company's identity provider; when and how each sign-in was made (never a network address or device); counts of wrong passwords and of wrong two-step codes typed when signing in, with when counting began and when the latest was typed — counting goes on until 30 days pass without a failure, and the next failure after that starts it again; a requested change of sign-in address (the new address, who asked and when), kept until it is confirmed, cancelled or replaced, or the login is removed — its link works for 24 hours; and an append-only audit log of sensitive changes and sign-ins recording who made them. For the company: which version of the Terms of Service and Data Processing Agreement was accepted at sign-up, when and from which email address; when an Administrator asks for the company to be deleted, who asked and when; and the details it chooses to print on payslips and letters (legal name, address, registration and tax numbers, and the name and title of the person who signs its letters), which an approved payroll run keeps as its payslips printed them, without the signatory.

Engagement survey responses are deliberately anonymous. A response row carries no employee reference and no timestamp, and the record of who responded is kept in a separate table that is never joined to it and keeps only the day someone answered, never the time. Responses are not stored in the order people answered: after every answer the survey’s responses are rewritten in a random order, and comments are shown in an order unrelated to when they arrived. Results — the score, the spread and the comments — appear only once the survey is closed and at least the minimum number of people have answered; while it runs, only how many have responded is shown, so no single answer can be watched arriving, and a survey whose results were shown cannot be reopened. Within the product, the one thing we cannot anonymise is a free-text comment, and the portal says so before you type one. A copy of the database holds no order or time that ties an answer to a person: each response keeps one storage key, fixed by its random identifier, through every rewrite, so anything the database engine leaves in unused space only repeats an answer under that same key, and that space is cleared every night; when the responses are rewritten, the space the old rows used is overwritten, and backups copy the current rows only. Two copies taken at different times — two nightly backups, say, or an image of the disk, which can also hold the temporary file the database writes while an answer is being saved — can narrow it, because they show which answers arrived between them and who answered in between, so when only one person answered in that interval, their answer can be told apart. Only someone with access to the database, its disk or its backups could do that. One thing the product itself shows: while a survey is open, the count of people who could still answer is kept up to date, and when someone comes off the list of people who can answer — they leave, or their portal login is removed — it drops only if they had not answered, so someone watching it across such a change can tell whether that person took part, though never what they answered.

A survey can ask a few more statements beside its main question, answered on the same terms: each answer is stored on its own, with no name, no time and nothing linking it to the person’s other answers. When an employer creates a survey it can choose to break the results down by branch or department, and a breakdown narrows anonymity, which the survey form says before it is chosen. An answer to such a survey is stored with the respondent’s branch or department — a group, never the person — but only for a group large enough to stand apart when the survey was created: at least the survey’s minimum number of people who could answer it then. Every other group’s answers are pooled together and stored with no group — groups too small then, a larger group pooled beside them when they alone would be too few (and, when no group is too small, the smallest group anyway, so the pool is never empty), and any group created later. Which groups are which is decided once, when the survey is created, and does not change while it runs, so a group’s answers are never split between its own name and the pool by when they were given. A group’s results are shown only once the survey is closed and at least its minimum number of people in that group have answered, and groups are held back until those not shown together hold at least the survey’s minimum, so the survey’s total cannot be used to work them out. A breakdown names only the groups it shows, followed by one line for all the others whatever was answered: a group not shown is never named, counted or given a figure, and comments are never broken down. The archive export follows the same rule. The group stored with an answer is the one thing a breakdown adds to a copy of the database: someone holding that copy can tie the answers stored under a group, the pooled ones included, to that group’s people who answered, and so, when only one of them did, to that person — and a group large enough when the survey was created, the pool included, can still hold few answers, if its members have left or did not answer.

Praise is meant to be seen, on the recipient’s profile and by whoever writes their next review. Its notification carries no text and no author’s name — only that praise was received, in the email copy too — and is deleted with the praise when it is retracted, removed or erased, or when the author’s or the recipient’s record is deleted, so no copy of the words outlives them in anyone’s notifications. One record does keep some of the words: when an administrator removes someone else’s praise, the audit log records the removal with the praise’s author and its opening words, and keeps that entry, as it keeps every entry.

One-to-ones and improvement plans. A manager’s record of a one-to-one with a direct report has two kinds of notes: notes shared with the employee, who sees them with the date and the action items agreed, and the manager’s private notes, which are shown only to that manager and to people the employer allows to manage performance — in the company’s full data archive too, only to an administrator who may also manage performance — and never reach the employee they are about, by any channel: no page, no download (their own, or the company archive, whose one-to-ones file leaves out every one-to-one about whoever downloads it, and whose audit log records only that a one-to-one was recorded or edited, with names and the date, never the notes), no notification and no screen of the phone app. An improvement plan, its check-ins and its outcome are shown to the employee it is about. Notifications about either say only that something was recorded, and carry none of the notes; on the phone app, the link such a notification carries is the app’s own inbox, so the push service is not told which page it was about.

A manager’s recommendation on a probation can carry a note for HR. The employee it is about is not shown that note — not on their own profile and not in their own data download — and the form the manager writes it in says so.

Who sees a candidate. An opening’s hiring manager and team see its candidates in the employee portal — stage, source, CV, interviews, submitted interview feedback and an offer’s status (with the start date once accepted) — never offer figures, recruiter notes, contact details, the salary range or an opening they applied for; while the opening is open (a change to it awaiting approval included) and for 90 days after it closes, and only while they work here. Only the hiring manager is notified, by title, of new applicants, submitted feedback and an online answer to an offer. An internal candidate’s accepted offer updates their existing employee record — job title and department on the day it is completed, basic salary from the offer’s start date through salary history — and is recorded in the audit log; no second employee record is created. The audit log records which of a candidate’s details changed, with the names and source before and after, never the email address or phone number; that a recruiter emailed a candidate, never the subject or the text; and edits to an opening by the fields changed, never the reason a seat is needed or a decline note.

Careers pages. An employer’s careers pages show the employer’s own privacy notice for candidates, or a neutral default naming the employer. They ask search engines not to index them unless the employer turns on job-board publishing, which is not available during a free trial; publishing makes the careers pages indexable and publishes job details only — title, description, place, closing date, employment type, and the salary range only for roles the employer chooses — as structured data on each job page and in a job feed. Job boards and search engines that fetch them receive no candidate data. The employer’s logo is shown on the careers pages without sign-in.

Who else processes it

A short list, each with a narrow job. The current list, and what each one receives, is on the sub-processors page.

Email goes out through one of them, Resend, for every company. The receipt-reading feature and the AI assistant are each off until an administrator of the employer switches them on, because each sends data to Anthropic: reading a receipt sends that receipt’s image, with the employer’s list of expense category names, and only when someone presses the button for it; answering a question sends the question, with the asker’s name, the company’s name, the earlier questions and answers of the same conversation, and the rows looked up to answer it. Anthropic handles that data under its own terms: Peoplume does not promise that it will not use it to train or improve its models, and its published policy is to delete it within 30 days, with the exceptions the sub-processors page lists. A photo picked in the portal or the console is re-encoded in the browser before it is sent for reading; the receipt stored with the claim is still the file as it was uploaded. Peoplume does not sell data and does not share it for advertising.

The phone app’s camera and photos. The Peoplume phone app uses the camera, the photo library and the phone’s files only to attach a receipt to an expense claim, and only when the employee chooses to. A photo is re-encoded on the phone before it is sent; a PDF, and any file uploaded in the portal, is stored as it was sent. A receipt reaches Anthropic only when someone presses “Read the receipt” while the employer has receipt reading switched on — in the app exactly as in the portal. The app adds no new service to the list above.

Two third-party scripts run on our pages: Cloudflare Web Analytics on every page, and Paddle.js only on the payment page, when someone pays. Cloudflare Web Analytics counts page views and referrers so we can see which parts of the site are used. It sets no cookie, builds no profile and cannot follow anyone to another site. We would rather name it than let “no tracking scripts” stand, which is what this page said until the content security policy we added caught it — Cloudflare injects the script at the edge, so it never appeared in our own source. Paddle.js is Paddle’s own checkout, loaded from Paddle on the one page where a subscription is paid for; the card or other payment details are typed into Paddle’s checkout and go to Paddle, never to us. There is no advertising or cross-site tracking of any kind.

How long it is kept

Mostly, for as long as the employer keeps it. Three things are deleted on a schedule. A leaver’s portal and app login is removed the day after their last day — not before, because someone serving notice still needs their payslips, leave and clock-in. (A console account — HR or administrator — is not removed: its access ends on a date set on the account and it is suspended from the next day, kept and restorable; restoring it signs it out of every browser and device, so its holder signs in afresh.) A sign-up that was never confirmed is deleted once its 24-hour link has expired. And, only if an employer switches it on, rejected job applicants are deleted with their CV after a period the employer sets — with their interviews, feedback, offer (with its response links), history, the hiring manager’s recommendation, the emails written to them and the staff notifications that link to their application — except an applicant who ticked “Keep my details for future roles” on the careers form, who is kept until that request runs out: never longer than the form said, sooner if the employer shortens or switches off its talent pool, and no longer once the employer withdraws the request at the candidate’s request. An interviewer’s notice of an interview with them, notification emails already delivered and audit log entries naming them remain. Applicants never rejected — still in the process on a closed role, or hired — are not deleted on a timer. When an employer puts a candidate forward to another opening, the CV is copied into a separate file that belongs to the new application and is deleted with it; the candidate’s request to be kept for future roles is never copied to the new application. Nothing else in Peoplume is removed on a timer, and no default period is assumed — how long to keep a record is a statement about the employer’s own obligations, not ours to guess.

Erasing a person. An administrator can erase a former employee’s personal data once they have left — from the day after their last day, judged on their own local day (their branch’s timezone), never while they are still serving notice and being paid. It also waits while any of their expense claims or air-ticket cash-outs is still awaiting a decision or approved but not yet paid (erasure removes the bank details that money would be paid into), while a travel advance of theirs is still requested, approved, handed over or being settled (money is in flight either way), and while a console (HR or administrator) account tied to the record — linked to it, or signing in with its email — still has access: that access is ended in Settings first, because the record is what shows that someone who has left still holds the console, and erasure blanks the email that ties them. It is permanent. What goes:

  • Their name (the record becomes “Erased” and the employee number), email, phone, address, emergency contact, gender (unless the employer has a leave type limited by gender — see what stays, below), date of birth, nationality, marital status, bank details and HR notes.
  • Every document on their file, with its file; their family members; custom field values; praise written by or about them, with the notifications of it; their portal login and any invitation sent to their address.
  • Their places as a successor on other people’s succession plans, and the notes and the flight-risk judgement on the succession plan covering their own role. The plan itself stays — the role still needs a successor — but a judgement about whether someone who has left might resign has no further use. Their place as the head of a department is cleared.
  • The certificate files uploaded to their training records (the records themselves stay), the note typed on each probation decision about them (the decision, its dates and who recorded it stay with the employment record), and the name of whoever created each of their goals — on a goal they proposed themselves, their own name and login email.
  • Their one-to-ones — the meetings a manager recorded with them, with the shared and private notes and the action items: informal working notes, not a decision on record (a goal an action item became stays with their goals). Suggestions of colleagues to give peer feedback on their review, or naming them as one. The note on a manager’s recommendation on their probation (the recommendation stays with the probation history, like the decision).
  • The job application they were hired from — the one their record was made from or, where no record is tied to it, a hired application under the email on their record, when no other record not yet erased carries that email (whether that person still works there or has left) — and any application on which they were an internal candidate: name, email, phone and CV file, their request to be kept for future roles, their name wherever the application’s history shows them as the one who applied, the staff notifications that link to it, the offer’s response links, the emails written to them from Peoplume (the history keeps that one was sent, without its subject), and the free text written about them while hiring — recruiter notes, notes and detail corrections in the application’s history, interview and feedback notes, notes on the offer and on a self-scheduling link, and the note on a hiring manager’s recommendation (its kind and reason stay). An online answer to the offer stays, with any reason they typed cut back to “declined online”. Its stage, dates, source, outcome reason, ratings, interview times and places and offer terms stay, unnamed, so hiring figures still add up. Other applications under the same email are not touched by erasure; they follow the applicant retention period above. A link between an anonymised application and one that stays named — one put forward from the other — is cut, with the opening each application’s history names for the other.
  • Their places on hiring teams, and interview feedback drafts they never submitted. Interview feedback they submitted about candidates and recommendations they made as a hiring manager stay, under the erased record’s label (each recommendation’s entry in the application’s history keeps the name it was recorded with, as staff names on records they acted on do), as does an application’s record that they referred the candidate. Openings and requisitions naming them as the person a hire replaces keep the record, which then reads “Erased” and the employee number; their free text — why the seat was needed and a decision note — is blanked.
  • Receipt files on expense claims that were never paid (rejected, including an approval later withdrawn, or sent back for correction and not resubmitted). Erasure waits while any of their claims is still pending, and while an expense claim or air-ticket cash-out of theirs is approved but not yet paid, so a claim that may yet be paid never loses its receipt.
  • Expense claims they never sent — claims in a trip report that was not sent, which nothing paid — with their receipts, and trip reports they never sent, together with any declined or cancelled travel advance on them. On the trip reports and travel advances that stay, the free text goes: a report’s purpose, the reason HR gave for sending it on their behalf, and the reason and decision note on an advance. Titles, dates and amounts stay, with the record of money handed over and paid back.
  • Their name on checklist steps they ticked themselves; steps ticked by HR keep the HR person’s name. Their name and login email on reviews they submitted about colleagues: those reviews stay, with their rating and text, and are credited to the erased record instead — a review they finished that its cycle still holds back for calibration included, so it is released under the erased record’s label. A review counts as theirs when it was submitted from a login tied to their record — their portal login, or a console account linked to the record or, linked to none, signing in with its email. The same goes for what they recorded about colleagues as a manager — one-to-ones, recommendations on a probation and improvement-plan check-ins — and for colleagues they suggested to give peer feedback: the records stay, with their text, credited to the erased record. Each is found by the employee record it was written from, so it is relabelled even after their login has been removed.
  • The reason HR typed on a stated leave figure (the days carried over from a previous system, extra days for a year, or the days carried into and used in the year Peoplume began tracking a leave type). The figure itself stays, like the rest of their leave, so balances and settlements do not move.
  • The reason HR typed on a pay hold. The months held, and who set and released the hold, stay with the payroll record: they are why a payroll month left the person out.
  • The notes approvers and HR wrote on their leave requests (with an approval, a rejection or a cancellation). The requests, their dates and days and the reason they gave stay, like the rest of their leave.

What stays is the employment and payroll record, under the employee number: hire and termination dates, payslips, salary history, attendance, leave — with their gender while the employer has a leave type limited by gender (women only or men only, an archived one included), because it decides which leave they had, so their balances and settlement do not move —, the trip reports they sent and their other travel advances, and expense claims — including the receipts of claims that were reimbursed, which are the evidence for money that was paid and are kept for the same reason payslips are. Their review, self-assessment, 360° feedback, goal and training records stay too, text included: they are evidence in employment disputes — a dismissal for performance, a claim about a missed promotion or a certificate that was not renewed — which is why they are kept. Their text can still name or describe the person. Improvement plans about them stay too, with their check-ins, objectives and outcome, text included: a plan is a formal performance record, kept for the same reason as a review. The same goes for their own comment on a review they were shown, their self-ratings and answers to a cycle’s questions, and the reasons they gave when asking for training or for a certificate to be renewed: they stay with the records they belong to. The names of staff recorded on the records those staff acted on — who added someone to a review cycle, returned a review to its writer, recorded a probation decision, appointed a successor or created a colleague’s goal, and who approved leave brought in from a previous system, as the import recorded it — stay too, as the audit log keeps the names it recorded. Everything else on the record stays with it too and is not rewritten: timesheets, loans, the reasons typed on leave requests, and the reasons and notes typed on attendance and expense entries. The actions recorded on a timesheet — who submitted, changed, approved or sent it back, when, and any comment — stay with it too; the erased person’s name is removed from the actions they recorded. The audit log keeps the name in its entry recording the erasure, so the employer can still answer “did you action my request?”, and its other entries keep the names they recorded at the time — an administrator’s removal of a praise, for one, quotes the praise’s author and opening words. That split is deliberate. A right-to-erasure request does not entitle anyone to rewrite what a company reported it paid, and a system that deleted payslips to honour one would change the accounting record months after the fact.

What else the employer can delete, and what happens when they do:

  • Deleting an employee removes their record and their employee portal login in the same transaction (an administrator’s own account linked to the record is unlinked, never deleted). It is refused if they have ever been paid — a payslip, an expense claim reimbursed to them, or a travel advance handed over to them, is an accounting record, and the answer there is to mark them terminated instead. It is refused for the same reason while they have a submitted review, submitted 360° feedback about a colleague, or a training enrollment with a cost — a final appraisal, someone else’s review and money spent are records too; a review its writer has finished counts even while its cycle holds it back for calibration. It is refused too while an improvement plan about them exists, in any state: erasure keeps a plan as evidence, so a delete must not be the way to lose one. It is refused while they hold interview feedback they submitted about candidates, a hiring record; their unsent feedback drafts are deleted with the record. Their one-to-ones, a manager’s recommendations on their probation and suggestions of peer reviewers about or naming them go with the record. Deleting a terminated employee’s record is also refused, like erasure, while a console account tied to it still has access. Praise they gave or received goes with the record, with its notifications.
  • Deleting a document, receipt, training certificate or CV — or the employee record they belong to — also removes the underlying file from storage.
  • Webhook delivery logs keep only the most recent 20 per endpoint.
  • The audit log is append-only on purpose: it exists to record who changed a salary or approved a payment, and an audit trail that can be edited is not one.

Deleting the whole company. One of the company’s Administrators can ask for the company to be deleted from the Billing page, once its subscription no longer renews and the payment provider is no longer collecting; its other Administrators are told. We delete every record of the company and every file it uploaded from the live database and file storage no sooner than seven days after the request (any Administrator can withdraw it until then), and keep only a record that we did so: the company’s name and id, who asked and when, the reason recorded and who at Peoplume carried it out, and when and how much was deleted. A deletion asked for in writing instead is also carried out no sooner than seven days after that request, and once a request is withdrawn on the Billing page we act only on a new one, made there or in writing on or after the day of the withdrawal. Backups holding the company rotate out afterwards. Deleting a company is never automatic. Neither deleting a company nor erasing a person reaches what receipt reading or the AI assistant had already sent to Anthropic, which keeps or deletes it under its own terms (see “Who else processes it” above).

Getting data out

Without asking us and without an export request: employees, attendance, leave, payroll, expenses, job applicants and reports each export to CSV, as do a review cycle’s results and the audit log (as filtered on its page); a report builder lets you choose your own columns; and a read-only API serves scoped keys.

One archive holds the company’s core records: employees (number, name, email, status, branch, department, job title, manager, their department's head, hire and leaving dates, basic salary with its currency, pay basis and hourly rate, IBAN, nationality and gender), employment terms (each dated change of an employee's branch, job title or employment type), salary history with its currency, attendance, timesheets (customers, projects and the activities each uses, each timesheet with its status and who decided it, the hours booked with their project, activity and note, and the actions recorded on each timesheet with their comments), leave requests and stated leave figures (opening carryover, extra days, go-live year), payslips, expenses (claims, trip reports, travel advances, expense categories and mileage rates), training (courses, sessions, requirements, learning paths, budgets and enrolments), performance (review cycles and who each covers, reviews with their answers, self-assessments, 360° feedback, goals, suggested peer reviewers, one-to-ones and improvement plans), praise, probation decisions and managers’ recommendations, succession plans, survey results, recruitment records when the person downloading may view recruitment (job openings with their salary ranges and closing dates, job requisitions and their decisions, hiring teams and hiring managers’ recommendations, applications with their history, outcome reasons, talent-pool requests and internal, referral and put-forward links, interviews with their panels and the criteria fixed for them, submitted interview feedback and scorecards, the company’s and each opening’s scorecard criteria, offers with the letter wording approved and when the candidate answered online, self-scheduling links with their panels and the times offered, emails written to candidates (subject, text, address, sender and date) and the company’s own wording for candidate emails, the offer letter and the snippets recruiters start emails from — never a link itself, never a feedback draft and never the downloader’s own applications; CV files listed, not included) and the audit log. Downloading it needs permission to manage settings, and parts of it follow the permissions of the person downloading it. Salaries, their currency, pay basis, hourly rates, salary history and bank details need permission to view salaries; the full IBAN needs permission to change them (with permission only to view them, the archive holds its first two and last four characters). Payslips also need permission to view payroll. The audit log needs permission to view it, and its pay figures need permission to view salaries. An offer’s salary, once the candidate became an employee, needs permission to view salaries. Who signed a timesheet off on an employee’s behalf and why, and why HR entered one for them, need permission to view salaries too; without it the timesheet still says that HR did so. Anything withheld is not in the download, and the archive’s README names it with the permission it needs. Every rating carries the words its cycle gave that point of the scale. A manager’s private notes on one-to-ones, and the columns saying what HR decided on each suggested peer reviewer, are filled in only when the administrator downloading it may also manage performance — the notes in a column marked as never shown to the employee; for anyone else those columns are empty, and the archive’s own README says why. The files of one-to-ones and of suggested peer reviewers leave out the rows about the person downloading it — one-to-ones about them and suggestions of peer reviewers for their own review — and the note for HR on a manager’s recommendation about them is left empty. When it is included, the archive’s audit log is the company’s audit log and keeps every entry, as the audit log page does: it still records each suggestion of a peer reviewer, each decision on one, each nomination and each one-to-one recorded or edited — about anyone, the person downloading included — with names and dates, never the notes or the reasons. No self-assessment or 360° feedback that was never submitted is in the archive: a draft is its writer’s own. Expense claims in a trip report not sent yet are in it, though, each marked as not sent, and the log entry for the download says how many. Survey results leave as the surveys page shows them — a survey’s score, spread (an eNPS survey’s as promoters, passives and detractors) and comments only once its results are shown, and never who answered; its extra statements and its branch or department breakdown as figures only, naming only the groups shown. Anything not named in that list is not in the archive — among it the rest of each employee’s profile (phone, address, date of birth, emergency contact and the like), custom field values, the records of documents on employees’ files, uploaded files (a record that names a file lists it; the files themselves come in the separate uploaded-files download), dependents, recurring allowances and deductions, pay holds, loans, air-ticket benefits and requests, leave encashments and leave salary advances, the reasons and notes typed on leave requests, compensation review cycles and proposals, shift swaps, checklists, letter requests, policy acknowledgements and most settings. Recruitment records are in it only when the person downloading may view recruitment; their own applications (and everything on them), the job requisitions naming them as the person a hire replaces and their own places on hiring teams are left out, an opening naming them is listed without that name or the reason given for the seat, interview feedback that was never submitted is never in it, and a candidate’s offer or scheduling link never is — only when each was made, used or answered. Anyone who may view recruitment can also download the applicants as a spreadsheet — one row per application, without recruiter notes, CVs or interview feedback; the salary of an offer that became someone’s employment needs permission to view salaries, and the downloader’s own applications are left out.

Uploaded files — documents on employees’ files, expense receipts, CVs, training certificates, policy files and the logo — download separately from Settings, in parts of up to 200 files, each part with a manifest saying which record each file belongs to. It needs permission to manage settings; documents, receipts, CVs and certificates each also need the permission of the page that shows them, and the downloader’s own job applications’ CVs are never in it. A file no record points at any more is not in it.

Answering a job applicant. From any of their applications an employer can export everything held under the applicant’s email address — every application with its history, interviews, submitted interview feedback and scores, offers and online answers, scheduling links, the emails written to them and the hiring manager’s recommendation; CV files are listed, not included — or delete every application under it at once, with CVs, interviews, feedback, offers, messages and notifications. Deletion is refused while one of the applications was hired (erasing that employee’s record anonymises it) or holds a sent or accepted offer. Interviewers of an interview still to come are told it is off, never who the candidate was. The export and the deletion are recorded in the audit log with the applicant’s name, never their email address.

Answering a request about one person is one click. An employer can download the records held about a single employee — profile (with their shift and work week), the dated changes of their branch, job title and employment type, attendance (with a punch’s location, where the device gave it, and its recorded distance from the branch’s location), leave, timesheets with the hours booked and the actions recorded on each, payslips, expenses (with their trip reports and travel advances), training, reviews with their answers, self-assessments, the 360° feedback they gave and that colleagues gave about them, goals, praise, probation decisions and a manager’s recommendations, one-to-ones, improvement plans, suggested peer reviewers, succession plan entries, the job applications they were hired from or were an internal candidate on, interview feedback they wrote and the hiring teams they are on — as one set of spreadsheets from that person’s profile; uploaded files are listed rather than included. It is not everything held about them: among what it leaves out are loans, leave encashment and leave salary advance requests, bank details and an hourly rate, compensation review proposals, the free-text notes HR keeps on the profile, shift swaps, checklists, letter requests, policy acknowledgements and the sign-in account and the audit log, which stay on the pages that show them. Each sensitive part — pay, reviews, self-assessments and 360° feedback, one-to-ones, improvement plans, suggested peer reviewers, leave, attendance, timesheets, expenses, training costs, certificates and requests, succession, and job applications and hiring — is included only if the person downloading it is allowed to see that information, and the file names anything withheld rather than leaving a silent gap. Self-assessments and 360° feedback need permission to write reviews — permission to view performance results is not enough, because only the page a review is written on shows them; one-to-ones and suggested peer reviewers need permission to manage performance, and improvement plans permission to view it; job applications and hiring need permission to view recruitment. Timesheets need permission to view attendance; who signed one off on the person’s behalf, and the reasons HR gave for that or for entering one for them, need permission to edit attendance or to view salaries — without it the file still says that HR did so. Rows about the person downloading a colleague’s file are never in it — 360° feedback the colleague gave about them, suggestions of peer reviewers for their own review or naming them, and interview feedback the colleague wrote, or recommendations they made, on the reader’s own job application — and the file says so in the same words whether or not any exist. Someone downloading their own record from the console with an account linked to it gets the employee’s own download described below, not anyone else’s. A console user whose sign-in email is on a record they are not linked to gets only what their own permissions allow, and never the seven things the employee’s own download holds back — and that download is logged like any other export of someone’s record.

Employees can download their own, without asking. The same bundle is on every employee’s own profile in the portal, with seven things held back, which the file names as held and not given: 360° feedback colleagues wrote about them, which is written for whoever writes their review and is never shown to the person it is about; succession plan entries naming them, which are the employer’s planning record; suggestions of colleagues to give peer feedback on their review, or naming them as one, with what HR decided — who is asked to give feedback is not shown to the person it is about; the private notes their manager wrote on their one-to-ones, which are never shown to them; the note a manager wrote for HR with a recommendation on their probation; the assessment from their job applications — interviewers’ feedback, ratings and scorecards, the hiring manager’s recommendation and the recruiter’s and interviewers’ notes, with an offer’s terms until it is sent to them (and again from a change to a sent offer until it is sent again) and every change of its terms and its approval steps, written for the people deciding on a hire and never shown to the person it is about; and job openings and requisitions naming them as the person a new hire replaces, which are the employer’s hiring plan. Their own job applications are included — the application, its history, interviews, an offer while it stands sent to them, the answer and any reason they gave online, and the emails written to them. Colleagues they suggested themselves are included, without what HR decided: for their own review they are never told who gives feedback, and for a review they write as a manager, the colleagues HR asks are listed on that review. Every employee’s file says this in the same words, so it tells nobody whether such an entry exists. A subject-access right that can only be exercised by asking your employer is a right with a gatekeeper, so there isn’t one — and we deliberately do not log people reading their own record through their own portal login or an account linked to it.

Where it runs

Peoplume is hosted on Railway, with Cloudflare in front of it. Uploaded files — contracts, identity documents, receipts, CVs — and the off-site database backups are stored in Cloudflare R2, which encrypts them at rest; we do not add a further layer of our own before they are sent. The nightly database backup runs on GitHub’s hosted runners, and GitHub keeps each night’s copy for 7 days. Each day a job there also reads the newest off-site copy back to check it, and keeps nothing. If your organisation has a data-residency requirement, ask before you commit — the hosting region is a deployment decision and we would rather agree it up front than discover it during your review.

Who to ask

Peoplume is operated by Plumeware LLC. Data protection questions — what is held, access and erasure requests, our sub-processors — go to [email protected].

If you are an employee rather than an employer, ask your own HR team first: they decide what is recorded about you and hold the controls to change it. We act on their instructions and cannot alter their records for them.

Changes to this page

The date at the top is the last change. Because this page describes how the software behaves rather than what we intend, it changes when the software does.