Skip to main content

Privacy & Data Protection

Privacy Policy

Your privacy and data security are our top priorities. Learn how we protect and handle your information.

Last updated: 9 October 2026

Privacy at a Glance

Secure by Design

HTTPS (TLS) between your browser and our servers; passwords hashed with bcrypt; sessions in httpOnly cookies

A named specialist

When you buy a fix, a person on our team reads your statements, payslips and P60s and checks the pack before it reaches you

Full Transparency

Clear information about data collection and use

Your Control

Manage your privacy settings and data access

Introduction

Kelmoss Ltd ("we", "us", or "our"), a company incorporated in England (company number 15629688), operates Remedy, our public-sector pension platform (including the free pension check). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website and services.

Kelmoss Ltd, registered in England and Wales (company number 15629688). Registered office: 124 City Road, London, EC1V 2NX. VAT number GB489325742. ICO registration ZB775702. We are the data controller for the personal data described here.

We take your privacy seriously and have appropriate technical and organisational measures in place to protect your personal information while providing a service for finding, fixing and managing your public-sector pension tax position and financial documents.

Who sees your records

When you ask us to fix a year, a specialist on our team opens your case and reads the documents and figures behind it — your pension savings statements, payslips, P60s and the position we have worked out — before the pack reaches you. That check is carried out by named members of our own team, not by a third party. The notice that a pack is waiting includes your email address so they can find your case.

If you invite an accountant or adviser, they see only the files you consent to share. Scheme administrators and employers hear from us only when you ask us to contact them.

Jurisdiction and Governing Law

This Privacy Policy is governed by English law. Any disputes arising from or related to this policy will be subject to the exclusive jurisdiction of the courts of England and Wales. We comply with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Information We Collect

Personal Information

  • Name and contact information
  • Public-sector employment details: your pension scheme (for example NHS, Teachers', Civil Service, Armed Forces, Police, Fire, Judicial or Local Government (LGPS)), your role, and service history
  • Email address
  • Password (hashed with bcrypt; not stored in plain text)
  • Payment information (processed securely by Stripe)
  • Professional registration numbers (where applicable)
  • Employment history and workplace details
  • Pension and pay records you upload, or that we obtain with your authorisation (for example pension statements, payslips, and Annual Allowance or remedy statements)

Usage Information

  • Log data and device information
  • Usage patterns and preferences
  • Uploaded documents and analysis results
  • Communication preferences
  • IP addresses and browser information
  • Session duration and interaction data

Free pension check (without an account)

Our free check lets you answer a short questionnaire and receive a triage-only result (red, amber, or green). It does not calculate a personalised tax charge for your situation. That requires your documents and our deterministic calculator after you create an account.

What we collect

  • Your pension scheme choice and questionnaire answers (income band, McCloud-related factors, and similar triage inputs)
  • Your email address, if you choose to submit it (with an explicit consent checkbox at the point of capture). We send a confirmation link. Your email is not used for updates until you click it (double opt-in).
  • A timestamp of when you gave consent (email_consent_at)
  • An anonymous session identifier stored in an httpOnly cookie (remedy_check_session) so you can return to your result on the same device
  • Product analytics events (for example check started, scheme selected, verdict shown) when analytics cookies are enabled

Lawful basis

  • Consent (UK GDPR Article 6(1)(a)): for storing your email and sending your result or occasional updates. You can withdraw consent by contacting us or using unsubscribe links in our emails.
  • Legitimate interests (Article 6(1)(f)): to operate the anonymous check, deliver your triage result, prevent abuse (rate limiting), and improve the funnel. We balance this against your rights; the data is limited and time-bound.

Retention for check sessions

  • Anonymous sessions (no linked account): deleted automatically after 90 days from when the session was created, unless you register and link the session to an account before then.
  • Linked sessions (after you create an account): kept while your account is active and deleted when your account is deleted.
  • Email + consent: subject to the same retention window unless converted to a registered account; we record when consent was given.

If you only use the check without registering, your email and answers will not be kept indefinitely. They are purged on this schedule even if you opted in to updates.

Cookies and Tracking

This section is our cookie policy. We use cookies and similar technologies (including local storage where noted) to provide and improve our service. You have full control over non-essential cookies through our cookie consent banner and settings.

Essential Cookies (Always Active)

These cookies are strictly necessary for the operation of our website. They enable core functionality such as security, network management, and accessibility.

  • Authentication: Session tokens, login status, cross-site request controls (SameSite cookie policy)
  • Free check session: remedy_check_session, an httpOnly cookie binding your anonymous check to your browser (see Free pension check section above)
  • Security: Secure connection management, fraud prevention
  • Functionality: Language preferences, accessibility settings
  • Cookie Consent: Your cookie preference choices

Legal Basis: Legitimate interest - These cookies are essential for the website to function properly.

Functional Cookies

These cookies allow the website to remember choices you make and provide enhanced, more personal features.

  • Remembering your calculator preferences and settings
  • Storing your display preferences (dark mode, layout)
  • Personalising content based on your professional role

Legal Basis: Consent - You can enable or disable these cookies through our cookie settings.

Analytics Cookies

We use reliability and performance telemetry to improve the service and diagnose issues. Where optional analytics is in use, we request consent through cookie preferences.

  • Sentry: Error tracking, performance traces, and (where enabled) Session Replay. Replays may capture interactions on the site with text and media masked; sampling depends on configuration
  • PostHog (browser): Page views and in-browser product events when you accept analytics cookies. We use the EU-hosted endpoint when configured, limit automatic capture, and rely on explicit events
  • PostHog (server): After you create an account, or confirm the email on a check, our API records product events that measure whether core features work (for example documents arriving, connector sessions completing, checkout, and purchases). These events use your account id. Your email is stored on that profile, with the latest step you reached, so we can see which member an event belongs to and help you if you get stuck. They carry no document contents, chat messages, or passwords, and are not gated by the cookie banner
  • Page views, session duration, and user journeys
  • Feature usage and engagement metrics
  • Performance and load time measurements

Legal Basis: Consent for browser analytics cookies; legitimate interests (Article 6(1)(f)) for server-side product analytics needed to operate and improve the signed-in service, balanced against your rights and limited to operational metrics.
Retention: Retention varies by system and provider configuration.

Marketing Cookies

We currently do not use marketing cookies.

Currently, we do not use marketing cookies. If we introduce them in the future, we will update this policy and require your explicit consent.

Managing Your Cookie Preferences

You have several options to control or limit cookie usage:

  • Cookie Banner: When you first visit our site, you can choose to accept all, reject all, or customise your preferences
  • Change preferences later: Use in the footer on any page, or the button below. The banner then stays hidden unless you open settings again.
  • Browser Settings: Most browsers allow you to refuse or delete cookies through their settings

Note: Blocking all cookies may affect your ability to use certain features of our website.

Third-Party Cookies

We use the following third-party services that may set cookies:

  • Stripe (Payment Processing): Essential for secure payment processing and fraud prevention
  • Sentry (Monitoring): When analytics consent is on: errors, performance, and optional Session Replay
  • PostHog (Product Analytics): Browser cookies and local storage when analytics consent is on; server-side product events for signed-in accounts as described under Analytics Cookies (EU-hosted when configured)

These services have their own privacy policies and may collect information as described in their respective policies.

How We Use Your Information

We use your information to:

  • Provide and maintain our services
  • Process your payments and subscriptions
  • Send you important updates and notifications
  • Improve our services and user experience
  • Analyse document contents for pension and financial insights
  • Check your scheme's figures against your payslips and other records, and work out your pension tax position
  • Have a specialist on our team check the pack for a year you have asked us to fix, before the pack reaches you
  • Check how a document of yours was read, for accuracy, as part of providing the service to you
  • Check and improve how accurately we read documents and calculate for every member, using the figures members and their accountants correct (see Improving how we read documents and calculate)
  • Where you ask us to handle your case, contact your pension scheme, administrator or employer on your behalf to obtain your records or correct errors in your record
  • Where you ask us to, prepare your reconciled position for review or sign-off by a qualified accountant or independent financial adviser. An introduction is not access until you grant consent
  • Respond to your inquiries and support requests
  • Comply with legal obligations
  • Prevent fraud and abuse
  • Enforce our terms of service

Lawful basis for the paid service

Performance of a contract (UK GDPR Article 6(1)(b)): once you buy the fix, we process your pension and tax records to produce your position, your action plan and your specialist-checked pack. The free check above has its own bases (consent and legitimate interests). We also rely on legitimate interests (Article 6(1)(f)) to keep the service secure, to tell a specialist that a pack is waiting, and to improve how we read documents as described below.

How We Share Your Information

We do not sell your personal information. We share it only in these ways:

  • Specialists on our own team: as described under Who sees your records. They receive your data so they can check the pack (UK GDPR Article 13(1)(e)). They are not listed as subprocessors because they act for us, the controller, as our own staff.
  • Service providers (processors): the organisations in our subprocessor register below process data on our behalf under contract.
  • Your pension scheme, administrator or employer: where you ask us to handle your case and with your authorisation, we may contact them on your behalf to obtain your records or correct errors in your record. We share only what is needed for that purpose.
  • A qualified accountant or independent financial adviser (IFA): where you ask us to arrange professional review, sign-off, or an introduction, we share your reconciled position and supporting documents with the professional you choose or we introduce. That professional acts as a separate data controller, responsible for their own use of your data. If you invite an accountant or adviser yourself, they see only the files you consent to share.
  • Legal and safety: where required by law, to enforce our terms, or to prevent fraud or harm.

We ask for your consent or instruction before contacting a scheme, employer or professional about your case.

If you work with an accountant or financial adviser through Remedy

You can invite an accountant or independent financial adviser (IFA), or accept an invitation from their firm. The firm sees nothing until you grant consent in your account, and then only what you choose to share. You can revoke that access at any time in Settings.

Who is responsible for what

  • Your account is ours to look after. We stay the controller of the data in your account: your documents, the figures we read, your position and your pack. Everything else in this policy still applies to it.
  • The firm is a separate controller. The firm is responsible for its own use of what you share with it, under its own privacy notice and professional rules. We and each firm sign a data sharing agreement that sets out what passes between us, why, and how each of us deals with your rights and with any security incident.
  • The firm's own records. When the firm works on your case in Remedy, it creates records of its own: its notes, its review and filing records, the status of its work, and papers its team writes. For those records we act for the firm, as its processor, under a data processing agreement. The firm decides what they are for and how long they are kept.

If you revoke access or delete your account

  • Revoking access stops the firm seeing your account from that moment. The records the firm has already made stay with the firm.
  • Deleting your account erases the data we hold as your controller, as described under Data Retention and Deletion below.
  • The firm's own records are not ours to delete. We keep them for the firm, under its instructions and its retention period, because a firm may need them for its professional and legal duties, for example if HMRC opens an enquiry or to meet its anti-money-laundering record keeping. We tell the firm that you have deleted your account.
  • To see, correct or delete the firm's records, ask the firm, which is their controller. If you send that request to us, we pass it to the firm.

Artificial intelligence and other processors

Core features use third-party AI and infrastructure providers. Depending on how you use the service, we may send content to these providers for processing (for example prompts, chat messages, document text or excerpts, and related context). Providers act as processors under their own terms and privacy policies.

AI providers

  • OpenAI (OpenAI API): document analysis, chat, embeddings, and (where applicable) web-augmented or search responses. This is our primary AI provider. OpenAI keeps API inputs for up to 30 days for abuse monitoring and does not train on them; see OpenAI's data usage policy (opens in a new tab).
  • Anthropic (Claude API): document reading, reading scanned pages, chat, and as a second, independent reader that checks the first. Each task uses whichever provider's model reads most accurately in our tests. Processing runs in the United States. Anthropic deletes API inputs and outputs within 30 days (content its safety systems flag may be kept for up to two years) and does not train on them; see Anthropic's API data retention (opens in a new tab).
  • Perplexity AI: used as a fallback for real-time or web-grounded answers when configured (for example when OpenAI search is unavailable or times out).

Before sending text to external AI services, we apply best-effort automated redaction of common personal-identifier patterns (for example styles of NI numbers, NHS numbers, dates of birth, email addresses, phone numbers, and postcodes) where that pipeline is enabled. A scanned document or a photo is also read from its page images, so that tables print reliably; the same kinds of identifiers are blacked out on each image before it is sent. This is not a guarantee that all sensitive or special-category data will be removed. Only upload or enter what you need for your use.

AI processing may involve transfer and storage outside the UK (including the United States), depending on the provider’s infrastructure and configuration. Several of the providers below are United States companies, including Neon, OpenAI, Anthropic, Stripe, Resend, Sentry, PostHog and Browserbase. Our database and file storage are in London. We make those transfers under the UK International Data Transfer Addendum to the EU standard contractual clauses, or the UK Extension to the EU-US Data Privacy Framework, as applicable to each provider.

Subprocessor register

The table below lists organisations that process personal data on our behalf or provide material parts of our infrastructure. We may update this list as our suppliers change; check this page for the latest version.

SubprocessorRole
OpenAIAI processing (document analysis, chat, embeddings, search-augmented responses where configured)
AnthropicAI processing (document reading, reading scanned pages, chat, and independent checking of readings)
Perplexity AIAI processing (fallback for real-time or web-grounded answers when configured)
BrowserbaseRuns the guided browser session when you choose to connect a pension or payroll portal (see Data Retention below); a United States processor, used only when you start a connection and closed when it ends
StripePayment processing, billing, and subscription management
ResendTransactional email delivery (e.g. account, subscription, notifications), and receiving documents you forward to your own document-forwarding address when you use it
Sentry (Functional Software Inc.)Error and performance monitoring; optional Session Replay when you consent to analytics cookies
PostHogProduct analytics when you consent (we typically use the EU-hosted instance when configured)
DigitalOceanCloud hosting for our application in London; DigitalOcean Spaces (S3-compatible object storage, London) stores uploaded documents and encrypted backups
NeonManaged PostgreSQL database for application and account data, hosted in London (AWS eu-west-2); Neon is a United States company
RedisCaching, rate limiting, and coordination of background jobs, hosted in London (AWS eu-west-2) by Redis Ltd (Redis Cloud)

Software libraries and frameworks we run on our own infrastructure (for example our web application stack) are not listed here unless they receive personal data as a separate cloud service on their own terms.

Improving how we read documents and calculate

Everything we work out for you starts with the figures we read from your pension statements, payslips and P60s. When you or your accountant correct a figure we read, that correction shows us where our reading went wrong. We use corrections to check and improve how accurately we read documents and calculate, for every member. This is a standard part of how our service works, not something we ask you to consent to, and you can object to it at any time (see below).

What we use

  • The figure we read and the figure it was corrected to
  • The type of document (for example an annual allowance pension savings statement), which figure it was (for example the pension input amount), and which version of our software and which AI model read it
  • Whether the correction was made by you or by your accountant (not who they are)
  • A short excerpt of the page around the figure, with your personal details removed: your name, address, National Insurance and NHS numbers, member, payroll and other reference numbers, date of birth, email address, phone number and bank details
  • Any line that could reveal more sensitive information is taken out completely, figures included: for example union subscriptions (which show trade union membership), sick pay, medical, ill-health, disability or maternity lines (which show health), payroll giving to a religious organisation, and deductions made under a court order

Removing these details is automated and cannot be perfect, so a member of our team reads every excerpt before it is used and takes out anything that still identifies you. We never use your whole document for this, and we only use corrections made on or after 30 September 2026, when this section was added.

How we use it, and who sees it

  • Only Remedy staff review corrections. They are never sold and never shared outside Remedy.
  • Staff use them to write internal test cases that check future readings. The test cases we keep are written by our team with made-up names, references and figures, and contain no text from your document.
  • They are never used by our AI providers to train their models. When we test our reading, test cases are sent to our AI providers under the same terms as your documents: as described under Artificial intelligence and other processors above, OpenAI and Anthropic keep API inputs for up to 30 days and do not train on them.
  • It makes no difference to your own results.

Lawful basis

Legitimate interests (UK GDPR Article 6(1)(f)): our interest, and every member's, is that the figures we read from documents are right, because a misread figure can mean a wrong tax position. We have weighed that against your rights. We use only the corrected figure and a small excerpt with your personal details and sensitive lines removed, never your whole document; only our own staff see it; the test cases we keep contain nothing from your document; it has no effect on your own results; and you can object at any time without it affecting the service you get.

How long we keep it

  • Corrections are read from your record when we review them, so they last only as long as your record does. When you delete your account, they are deleted with it.
  • The copy of an excerpt that staff review is a working copy. It is deleted when the review is finished and is never kept for more than 30 days. Before each review we remove the corrections of anyone who has objected or deleted their account.
  • The test cases we keep contain nothing from your document. We review them at least once a year and delete those that are no longer useful.

Your right to object

You can object at any time, without giving a reason (UK GDPR Article 21). Turn off Use my corrections to improve reading in Settings → Privacy, or email support@remedy.tax. From then on, your corrections, and your accountant's corrections to your documents, are not used for this, and we remove them from any review copy before it is used again. Objecting does not affect your results or the service you get. You can turn it back on in Settings whenever you like.

What is separate from this

  • Checking your own readings: our team may check how a document of yours was read, for accuracy, as part of providing the service to you. That is part of running the service, not improvement use, so it continues if you object.
  • Counting corrections: each week we count how often each kind of figure is corrected, across all members, so we notice quickly if our reading gets worse. The counts contain no figures, names or document text, and include every member's documents, because they are how we monitor the service you receive. When a figure our software was highly confident about is corrected, the weekly report identifies that document so our team can check the reading.

Data Security

We implement technical measures to protect your personal information, including:

  • HTTPS (TLS): encrypts data between your device and our website and APIs
  • Passwords: stored as bcrypt hashes, not plain text
  • Sessions: signed JWTs in httpOnly cookies
  • Database: PostgreSQL; our application requires TLS to the database in production (sslmode=require)
  • Access control: authentication required for account data; role-based controls for administrative features
  • Logging: selected actions (e.g. document sharing, subscription and security events) are logged for support and security review
  • Payments: card data handled by Stripe under their standards; we do not store full card numbers on our servers
  • Encryption at rest: provided by our hosting and database providers where they offer it. We do not operate a separate "end-to-end" encryption layer for file contents

We review and improve security as the service evolves. We do not list specific audit or penetration-test schedules here; ask us if you need detail for procurement or risk assessment.

Data Retention and Deletion

We retain your personal information for as long as necessary to provide our services and comply with legal obligations. Specific retention periods apply to certain features:

  • Free pension check (no account): anonymous session data (answers, email if captured) is deleted after 90 days. See the Free pension check section above.
  • Registered accounts: data is kept while your account is active.
  • Corrections used to improve reading: review copies of redacted excerpts are deleted when the review is finished and within 30 days at most; the test cases we keep contain nothing from your documents. See Improving how we read documents and calculate.
  • Connecting a pension or payroll account: when you choose to connect an account (for example My NHS Pension or the Electronic Staff Record), you sign in on the real page shown live from a browser we run. What you type goes straight into that page and is never stored, logged or sent anywhere else by us; the browser is closed when the session ends and cannot sign in again without you. We keep the records the portal gave us (statements, payslips and the figures behind them) while your account is active, because your calculation cites them. The page images and screenshots taken during the session, which exist only so we can check the collection worked, are deleted automatically after 90 days. All of it is deleted with your account.

You can request deletion of your account and associated data at any time. Upon deletion request:

  • Your account will be deactivated immediately
  • Personal data will be deleted within 30 days
  • Linked free-check sessions are removed with your account (database cascade)
  • Your rows leave the live database immediately. We keep encrypted database backups for 90 days, so your data leaves the backups as they expire
  • Anonymised analytics data may be retained
  • An accountant's or adviser's own records about your case are kept for their firm, and the firm is told: see If you work with an accountant or financial adviser

Your Rights Under GDPR

Under the UK GDPR, you have the right to:

  • Access your personal information
  • Correct inaccurate information
  • Request deletion of your information
  • Object to processing of your information, including our use of your corrections to improve reading: turn it off in Settings → Privacy
  • Receive a copy of your information: download it from Settings → Privacy at any time
  • Withdraw consent at any time
  • Complain to the Information Commissioner's Office (ICO)
  • Request restriction of processing
  • Data portability: the Settings download is one JSON file you can take elsewhere

To exercise any of these rights, email our data protection lead at support@remedy.tax. We will respond within 30 days. We are a small company and are not required to appoint a statutory Data Protection Officer, so the lead is a director of the company.

If you are unhappy with how we handle your personal data, you can complain to the Information Commissioner's Office (ICO), the United Kingdom's data protection regulator, at ico.org.uk/make-a-complaint (opens in a new tab). We would welcome the chance to put it right first: see how to complain.

Updates to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Last updated" date. This policy tells you how we use your information; it is not a request for your consent. Where we rely on your consent, we ask for it separately.

Questions About Privacy?

If you have any questions about this privacy policy or how we handle your data, please contact us.