Skip to main content

Trust Centre

Data processing

This page summarises what data PayslipIQ processes, why, on what legal basis, who else touches it, and how long it stays.

What we process

  • Payslip image or manually-entered figures, while the analysis request runs.
  • An anonymised hashed IP for rate-limit counters; deletes within one hour.
  • Email address and consent state for newsletter or Pro Report sign-ups.
  • Anonymised analytics pageviews and device class (after consent).

Why

  • Performance of a service requested by you (Article 6(1)(b)).
  • Legitimate interest in service availability for abuse prevention (Article 6(1)(f)).
  • Consent for marketing (Article 6(1)(a)).

Sub-processors

  • Vercel — hosting and edge cache.
  • Anthropic — AI vision and analysis. Inputs not used for training. May retain inputs up to 30 days for trust-and-safety review.
  • Upstash — rate-limit Redis, abuse counters and web-vitals samples (hashed IP only, never an address).
  • Cloudflare — Turnstile challenge on forms. Sees the IP of a challenged visitor; no payslip content.
  • Stripe — payment processing, only on a Pro Report purchase. Never sees payslip data.
  • Resend — transactional email, only when you ask for one.
  • MailerLite — newsletter delivery (Ireland-resident processor).
  • GA4 and Microsoft Clarity — anonymised analytics, behind consent.

How long

  • Payslip content: not retained by PayslipIQ. Anthropic up to 30 days for safety review.
  • Hashed-IP rate-limit buckets: up to 1 hour.
  • Daily AI-call cap, and the per-hashed-caller tally that breaks it down: up to 26 hours.
  • First-party funnel counters (no identifier): 90 days.
  • Vitals telemetry: 30 days.
  • Newsletter email: until you unsubscribe.

Your rights

Under UK GDPR you have the right to access, rectify, erase, restrict, port and object. Email privacy@payslipiq.co.uk. PayslipIQ has not appointed a Data Protection Officer and is not required to under Article 37; that address reaches the person who runs the site.

Educational guidance only. Last reviewed . Written and reviewed by Rocco Clayfield, founder and editor. If anything here is wrong, the correction policy says how to report it and what happens next.