PocketReceipt

Privacy Policy
Last updated: 9 October 2026

PocketReceipt Privacy Policy

This Privacy Policy explains what data PocketReceipt collects, how it’s used, where it’s stored, and the choices and rights available to you.

Quick summary (expand)
Local-first by default, optional cloud backup, optional AI scanning, and how to delete
  • Local-first: by default your records stay on your device.
  • Optional cloud backup: if enabled, your data is stored using Google Firebase services.
  • Optional AI receipt scanning: if enabled, receipt images are sent to a third-party AI provider for extraction.
  • Mileage tracking: if enabled, location data may be used to calculate trip distance.
  • Deletion: you can delete your account and associated data in the app, or request deletion by email.
  • Accountant sharing: if you choose, and you have a paid Professional plan, you can share your expense data with a linked accountant. You control access via the accountant access toggle and can pause or unlink at any time.
1. Who we are
Controller, contact, and where we operate

Controller: PocketReceipt (United Kingdom)

Contact (privacy): hello@pocketreceipt.co.uk

ICO registration: PocketReceipt is registered with the Information Commissioner's Office (ICO). Registration reference: C1899958.

PocketReceipt is operated from the United Kingdom and complies with UK GDPR (the UK General Data Protection Regulation) and the Data Protection Act 2018.

Data Protection Officer (DPO): PocketReceipt does not appoint a DPO, as we do not meet the threshold for mandatory DPO appointment under UK GDPR Article 37. For privacy requests, contact us at the email above.
2. Information we collect
What you provide and what’s collected when features are used

2.1 Data you provide App

  • Expense and receipt data: receipt photos/images (if you take or attach them), supplier/store name, date, amounts, VAT details, categories, and notes/business purpose.
  • Mileage data: journey distance, purpose, vehicle, start/end addresses, and (for GPS-recorded trips) start/end coordinates plus the GPS polyline of the trip. Stored on your device. See Section 11 for details.
  • Support: email address and message contents if you contact support.
  • Payment method per receipt: card, cash, bank transfer, or other.
  • Business type classification: sole trader, limited company, partnership, or LLP.
  • VAT registration status and VAT number: if voluntarily provided by you.
  • Capital item designation: whether an expense is capital expenditure or a revenue expense.
  • Vehicle information: name, registration, fuel type (petrol, diesel, electric, hybrid), and mileage cost method (AMAP or actual vehicle costs).
  • Receipt entry method indicator: whether the receipt was scanned via AI or entered manually.
  • CIS payment data: if you are a construction worker using the CIS feature, contractor names, gross payment amounts, materials amounts, CIS deduction rates, net payments, and statement references.
  • Invoicing data: if you use the invoicing feature, the invoices you create, invoice numbers, issue/supply/due dates, line descriptions, quantities, unit prices, discounts, VAT and CIS details, totals, status, payment terms, and notes, together with your invoice settings (numbering format, default payment terms, and the business contact details shown on your invoices). Stored on your device and, if you use cloud backup, included in your cloud backup. Your bank details and logo are never included in backups, they stay on your device only.
  • Your customers' contact details (invoicing): if you save clients for invoicing, their business name, contact name, email address, phone number, and postal address. These are stored on your device, appear on the invoices you generate, and are included in your cloud backup if you use cloud backup. As the issuer of your invoices, you are responsible for your customers' details; PocketReceipt stores them on your device on your behalf.
  • Bank details (invoicing): if you choose to add your account name, sort code, and account number so they appear on your invoices, they are held on your device in encrypted secure storage. They are never transmitted to PocketReceipt servers and appear only on the invoice PDFs you generate and choose to share.
  • Business logo (invoicing): if you upload a logo, the image file is stored on your device and embedded in your invoice PDFs.
  • Onboarding situation data: employment status (also employed via PAYE), whether you receive cash payments, whether you use a mixed personal/business bank account, vehicle ownership status, and whether you started self-employment in the current tax year. This data is collected during onboarding and stored locally.
  • Secure document transfer data: if you choose to send financial documents (such as bank statements, platform earnings reports, or phone bills) to your linked accountant, the document image, document type, month/year, and any notes you add.
  • Accountant messages: if you are linked to an accountant, your accountant may send you messages through the Dashboard. These messages (including text, category, priority, and timestamps) are stored in your account and visible in your Messages screen. You can acknowledge messages from within the app.
  • Accountant corrections: if you are linked to an accountant, your accountant may correct certain fields in your records (such as expense categories and mileage purposes). These corrections are stored temporarily and applied to your local data when you next refresh your records.

2.2 Data collected via the website Website

  • Email address (lead capture): if you submit the email capture form on the PocketReceipt website, your email address and the page you submitted it from are stored in our database. This is used solely to send you the requested guide or information.
  • Analytics data (Google Analytics 4): our website uses Google Analytics 4 (GA4) to collect usage data including pages visited, scroll depth, button clicks, session duration, referral source, device type, browser, approximate location (city-level), and language. Google Analytics sets cookies on your device. Data is processed by Google LLC.
  • Session recording data (Microsoft Clarity): our website uses Microsoft Clarity to record session replays and heatmaps including mouse movements, clicks, scrolls, and page interactions. Clarity may set cookies on your device. Form inputs are masked by default. Data is processed by Microsoft Corporation.

2.3 Data collected when app features are enabled App

  • Diagnostics: limited technical data for reliability and security (e.g., crash reports), if enabled in your device/app settings.
  • Authentication data: account identifiers (e.g., user ID) used to sign in and (if enabled) access cloud features. For accountants using the Accountant Dashboard, WebAuthn credential IDs are stored when a passkey is registered for login. Biometric data (fingerprint, face) is processed solely on your device by the operating system and is never transmitted to PocketReceipt servers.
  • Scan usage data: number of AI receipt scans used per calendar month, for the purpose of enforcing plan limits. This data is stored locally and, if you use cloud features, synced to our servers.
  • Usage statistics (App version 2.3.2 and later, on unless you switch them off). To understand which PocketReceipt features are useful and to improve the App, the App records which features are used, for example that a scanned receipt was saved, a mileage journey was saved, an invoice was marked as sent or paid, a trial offer was shown, or a step of scanning failed and at which stage. Each record holds only the name of the step and a few fixed values (such as the scan source, the platform and the App version), the time, and your account identifier. It never includes receipt images or contents, merchant names, amounts, invoice amounts, mileage locations or addresses, names, email addresses, notes or anything you type. The individual records are deleted automatically after 10 days; before then they are turned into anonymous totals (for example how many new users saved a second receipt in a week) that do not identify anyone and are kept. So that a feature is never counted twice, your account also keeps a few markers: which features you have started using regularly (receipt scanning, mileage, invoicing, accountant review), two small counts (up to 5 saved scanned receipts and up to 2 saved journeys), and, for a limited time, the dates needed to work out the anonymous totals (see Data retention). Usage statistics are never used for advertising or to choose who receives marketing, and never change what you see in the App. You can switch them off at any time in the App under More, Privacy, App usage statistics: collection stops straight away, unsent records are deleted from your phone, your records are deleted from our servers, and only your choice is kept. Anonymous totals already produced cannot be linked back to you and are not changed.
  • Anti-abuse signals: SHA-256 hashes of recent receipt images (stored at user_scans/{uid}.recentHashes for up to 30 days, used to detect duplicate-receipt scans), and per-hour rate-limit counters (hourlyCount and hourlyWindowStart). These are anti-abuse signals only and are not used for any other purpose. The hashes are one-way cryptographic digests and do not reveal the content of the original receipt.
  • Subscription and trial state: your current plan, subscription start/end timestamps, trial start and end timestamps, eligibility flags (whether you have used the 7-day Professional trial, whether you are eligible for the KEEP3 promotional offer, whether your account has legacy free-plan grandfathering), invitation status, and drip-progress markers indicating which trial-related notifications you have already received. Stored at subscriptions/{uid}. This data is used solely to enforce subscription entitlements, determine eligibility for time-bound offers, and avoid sending duplicate notifications.
  • Accounting preferences: accounting basis (cash or accruals), business type, and VAT registration status, stored locally and synced to your linked accountant if applicable.
  • Precise location (optional): if you enable mileage tracking with location permissions, location data is processed to calculate trip distance, recorded as a GPS polyline for the journey, and the start/end coordinates are sent to your device's platform geocoder to resolve a human-readable address. All resulting data is stored on your device. See Section 11.

2.4 Data collected via the Accountant Dashboard Dashboard

  • Passkey credentials: if you register a WebAuthn passkey for Dashboard login, the credential ID and associated public key are stored in Firestore at accountants/{uid}/passkeys/{credId}. Recovery codes are stored as SHA-256 hashes. Biometric data never leaves your device.
  • Audit log: every accountant action taken within the Dashboard is recorded, including: viewed client, edited receipt, sent message, marked quarter reviewed, requested document, and exported CSV. Each entry records the action type, affected client ID, detail, timestamp, and accountant email. Audit log entries are immutable, they cannot be edited or deleted by the accountant. Stored at accountants/{uid}/auditLog/{entryId}.
  • AML Customer Due Diligence (CDD) records: where an accountant records client identity verification data in compliance with the Money Laundering Regulations 2017 (MLR 2017), the following data is stored: identity verification status, document type (Passport or Driving Licence), verification date, risk rating (Low, Standard, or High), PEP (Politically Exposed Person) check status, and source of funds declaration. Stored at accountants/{uid}/clientCompliance/{clientId}.
  • Practice compliance information: ICO registration number, professional indemnity insurance details, and professional body membership, stored on the accountant's profile.
Sensitive information: receipt images and expense records may reveal sensitive details (for example, financial transactions or merchant information). PocketReceipt processes this information only to provide app functionality you choose to use.
3. How we use your information
Core features, AI scanning, backup, support
  • Provide core record-keeping features (expenses, mileage, reports, exports).
  • Provide optional AI receipt scanning (if you choose to use it).
  • Provide optional cloud backup/restore (if enabled).
  • Respond to support requests.
  • Maintain security and reliability (diagnostics where applicable).
  • Analyse website usage patterns to improve our website and marketing (Google Analytics 4, Microsoft Clarity).
  • Send requested guides or information to email addresses submitted via the website lead capture form.
4. Legal bases (UK GDPR)
Why we can process data
  • Contract: to provide app functionality you request.
  • Consent: for optional features such as AI scanning, cloud backup, and location-based mileage tracking.
  • Legitimate interests: app security and diagnostics.
  • Legitimate interests (usage statistics): understanding how PocketReceipt is used so that we can improve it (UK GDPR Article 6(1)(f)). For the small amount of information the App stores on your phone for this purpose, we rely on the exception in the Privacy and Electronic Communications Regulations for storage used only to collect statistics about how our service is used, with a view to improving it; you can object at any time in More, Privacy, App usage statistics, free of charge.
  • Advert measurement: the App (from version 2.3.2) does no advert measurement, so no consent for it is asked.
  • Legitimate interests (audit logging): the Accountant Dashboard audit log is processed on the basis of legitimate interests under UK GDPR Article 6(1)(f), specifically: compliance with MLR 2017 record-keeping obligations and fraud prevention. The audit log is immutable to preserve the integrity of these records.
  • Legal obligation (AML CDD): Customer Due Diligence data collected via the Dashboard is processed on the basis of a legal obligation under UK GDPR Article 6(1)(c), specifically the accountant's obligations under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017 (MLR 2017).
  • Consent (website analytics): Google Analytics 4 and Microsoft Clarity cookies are set only after you accept analytics cookies via the cookie consent banner on our website. If you reject cookies, these services are disabled.
  • Consent (email capture): if you submit your email via the website form, processing is based on your explicit action of submitting the form.
5. Where your data is stored
Local storage by default, optional cloud

5.1 Local storage (default) App

By default, your data is stored locally on your device. We do not access data that remains only on your device.

5.2 Cloud backup (optional) App Dashboard

  • If you enable cloud backup, data may be stored using Google Firebase services (e.g., Authentication, Firestore, Storage).
  • Data is protected using encryption in transit and at rest by the provider.
  • Access is linked to your authenticated account.
  • Cloud backup of records and receipt images is available to Professional subscribers and to existing Essential subscribers (Essential is a legacy plan as of 16 May 2026 and is no longer offered to new subscribers). Linking an accountant does not give you cloud backup; your own plan decides. For long-term HMRC record-keeping (up to 6 years), users may purchase a personal Storage Pack add-on to keep their receipt images retained. If the subscription or add-on that provides image backup expires, backed-up receipt images are retained for a 30-day grace period before being permanently deleted from the server.
  • If you link to an accountant and enable access, a summary of your expense and mileage data is stored in Google Firestore and is accessible to the linked accountant while your Professional plan is active. Receipt images are stored in Google Firebase Storage and made accessible to your accountant through secure links that expire after 15 minutes. Your accountant can view and download receipt images from the Dashboard.

5.4 AI receipt scanning (optional) App

  • If you use AI scanning, receipt images are transmitted securely for extraction.
  • We use a third-party AI provider to process the image and return extracted fields.
  • You should review and confirm extracted results before saving.

5.5 Cookies and local storage (website) Website

The PocketReceipt website uses the following cookies and local storage:

  • Google Analytics 4 cookies (_ga, _ga_*): used to distinguish users and sessions for website analytics. Set only after you accept analytics cookies. Duration: up to 2 years. Third-party (Google LLC).
  • Microsoft Clarity cookies (_clck, _clsk, MUID, CLID): used for session recording and heatmaps. Set only after you accept analytics cookies. Duration: up to 1 year. Third-party (Microsoft Corporation).
  • Cookie consent preference (cookie_consent): stores your accept/reject choice for analytics cookies. First-party localStorage. No expiry (until cleared).
  • Theme preference (theme): stores your light/dark mode choice. First-party localStorage. No expiry (until cleared).
  • Chat history (pr_chat_history, pr_chat_session_id, pr_chat_saved_at): keeps your conversation with the website chat assistant, and any reply from our team, on your device. Set only when you use the chat. First-party localStorage. Removed automatically after 30 days without use, or when you clear your browser data.

You can manage cookies at any time by clearing your browser data. Rejecting analytics cookies does not affect the functionality of the website.

6. Sharing with third parties
Service providers we use, and what we don’t do

We use service providers to operate certain features:

  • Google Firebase (authentication, optional cloud backup, accountant syncing, app diagnostics where enabled, and Firebase Cloud Messaging for push notifications such as accountant messages, scan-period reminders, and document-request alerts; you can disable push notifications in your device settings at any time).
  • Google Analytics for Firebase (App). Not used by the App from version 2.3.2: Google Analytics is permanently switched off in the App, so it sends no events, no advertising identifier and no install data to Google Analytics. App versions before 2.3.2 sent usage events to Google Analytics; updating the App stops this. Google Privacy Policy.
  • Sign in with Apple (optional authentication method). If you choose to sign in with your Apple ID, Apple receives a request that you are authenticating to PocketReceipt and returns a Sign in with Apple identifier we use to recognise your account. Apple's private email relay may be used to forward emails to you without revealing your real address. Apple Privacy Policy.
  • Google Sign-In (optional authentication method). If you choose to sign in with your Google account, Google receives a request that you are authenticating to PocketReceipt and returns your Google account identifier and email address, which we use to recognise your account. Google Privacy Policy.
  • Google Play Billing (subscription processing on Android devices).
  • Apple App Store (subscription processing on iOS devices).
  • OpenAI (receipt image text extraction via AI scanning, if you use this feature). Images are sent through OpenAI's API, are not used to train OpenAI's models, and may be kept by OpenAI for up to 30 days for abuse monitoring before being deleted.
  • Stripe (payment processing for past Accountant Dashboard subscriptions, which ended on 26 September 2026; no new payments are taken). Stripe holds the accountant email and payment details from those subscriptions as an independent controller for that payment data.
  • Google Analytics 4 (website analytics). Collects usage data including pages visited, button clicks, scroll depth, session duration, device type, and approximate location. Google may transfer data to the United States. Google Privacy Policy.
  • Apple Search Ads. From App version 2.3.2 the App does not request Apple attribution tokens and does not update Apple's install measurement (SKAdNetwork). App versions before 2.3.2 read an Apple Search Ads attribution token at first launch. Apple Advertising Privacy Policy.
  • Google Play install source. From App version 2.3.2 the App does not read or send the Google Play install source or any advertising click identifier. App versions before 2.3.2 read the install source at first launch.
  • Guest use before sign in (Android and iOS, from app version 2.2.10). You can scan and save up to two receipts before creating an account. Until you sign in, those receipts stay on your phone and the App uses a temporary anonymous identifier (a Firebase anonymous account) so that receipt reading and the usage statistics described in section 2.3 can work; no name, email or other personal information is attached to it. When you sign in, that identifier becomes your account, so nothing is copied elsewhere; if you never sign in, the identifier and its usage records are kept under the same retention rules as an account and can be removed by deleting the App.
  • No advert measurement in the App (from App version 2.3.2). PocketReceipt uses Google Ads and Apple Search Ads to find new users, but the App does not measure advertising: it asks no advert question, has no advertising tracking and uses no advertising identifier. Our usage statistics (section 2.3) are never used for advertising.
  • Google Ads (App). From App version 2.3.2 no purchase made in the App is reported to Google Ads. Before 2.3.2, a paid subscription bought on Android after a Google Ads click could be reported to Google Ads with the click identifier and the purchase value only. Google Privacy Policy.
  • Microsoft Clarity (website session recording and heatmaps). Records user interactions on our website including mouse movements, clicks, and scrolls. Form inputs are masked. Microsoft may transfer data to the United States. Microsoft Privacy Statement.
  • OpenStreetMap Foundation (map tiles for Mileage Logbook Pro PDFs). When a Pro user generates a logbook PDF online, the App fetches map tiles directly from OpenStreetMap covering the area of each trip. Tile URLs include the tile coordinates of the area being shown. No account or polyline data is sent. OSM Foundation Privacy Policy.
  • Google reCAPTCHA Enterprise (spam and abuse prevention on website forms). Collects IP addresses, browser fingerprints, and behavioural signals to assess whether form submissions are genuine. Google may transfer data to the United States. Google Privacy Policy.
  • ipapi.co (IP geolocation for country-level access control on website forms). Receives the visitor's IP address to determine country of origin. No personal data beyond the IP address is shared. ipapi.co Privacy Policy.
  • Anthropic (AI chat assistant on the website). Messages you send through the website chat widget are processed by Anthropic's AI services to generate responses. Conversations are processed in real time. To answer you, we also keep your latest message, the page you were on and a short session code on our servers, and any reply from our team until it has been shown to you. Each message you send and each answer from the assistant is also forwarded to our team through Telegram, a messaging service, so that a person can follow up. If you type your email address in the chat, we keep it with your message and the page you were on so that we can reply. Your browser keeps your chat history on your device for 30 days, so that if our team replies to your question you can still see the reply when you come back to the website. You can remove it at any time by clearing this website's data in your browser. Anthropic may process data in the United States. Anthropic Privacy Policy.
No sale of personal data: PocketReceipt does not sell your personal data.

Some privacy laws use the term “share” to include disclosure for cross-context behavioural advertising. PocketReceipt does not share personal data for cross-context behavioural advertising.

6A. Accountant data sharing App Dashboard
Optional consent-based sharing with a linked accountant

PocketReceipt allows you to optionally share your expense data with a registered accountant through the Accountant Dashboard feature. This feature is entirely consent-based.

Who can link: linking an accountant is part of the paid Professional plan (or VIP access we grant). It is not available during the Professional free trial or on the Free or Essential plans. The Accountant Dashboard has no charge for accountants. Linking gives you nothing beyond your own plan: your scans, backup, Storage Pack and other features always follow your own subscription.

How linking works: Only you can start a link. You generate a 6-digit code in the app. Your accountant enters this code on their dashboard. You must explicitly approve the connection before any data is shared. You control what is shared and can revoke access at any time.

Data shared when you approve a link:

  • Your name and email address.
  • Your business type and VAT registration status (including VAT number if provided).
  • Receipt summaries including store name, date, amount (net, VAT, and gross), category, VAT details, business use percentage, payment method, capital item status, and notes.
  • Mileage journey logs including date, locations, purpose, vehicle details, and miles.
  • Vehicle information including name, registration, fuel type, and mileage cost method.
  • Aggregate totals by quarter, year, and category.
  • CIS payment details (if applicable), including contractor names, amounts, deductions, and net payments.
  • Income records including amounts, dates, source labels, references, notes, and linked quarter. If you create an income record by marking an invoice as paid, the source label and reference will typically contain your customer's name and the invoice number.
  • Quarter review status data including client status, accountant status, and review timestamps.

What your accountant can do: When you approve a link, your accountant can view your records and receipt images, download receipt images, correct expense categories and mileage purposes, send you structured messages (such as deadline reminders, action requests, and queries), and request financial documents. Corrections your accountant makes are delivered to your app and preserved during your subsequent data updates.

Quarterly review workflow: You can send quarterly records to your accountant for review. Your accountant can review the quarter, request corrections, or mark it as reviewed. Once reviewed, you can lock the quarter to finalise your records for that period.

Messages from your accountant: Your accountant can send you messages through the Dashboard. These messages are stored in your PocketReceipt account and appear in your Messages screen. Each message includes the message text, category, priority, and timestamps. You can acknowledge messages from within the app.

Accountant access control (your own switch): You can pause access at any time using the accountant access toggle in My Accountant. When access is paused, no new data is shared, no new corrections are applied, and no new documents can be sent or downloaded. Messages from your accountant may still be delivered while the link is active. You can also fully unlink the accountant, which ends all future interaction.

If your Professional plan ends (payment pause): this is separate from your own switch above. When your paid Professional subscription ends (at the end of the billing period, after any grace period your app store gives for a failed payment) or your VIP access expires, the link is paused automatically. While paused, your accountant has no access at all to your records, receipt images, documents, messages, requests, corrections, exports or HMRC actions. They only see your name or email address and a message that your subscription is in a grace period of up to 30 days. If you return to paid Professional within those 30 days, the link resumes by itself with no new code. After 30 days paused, the link ends and your accountant's copy of your records is deleted from our servers, including any HMRC manual records they made for you. You can still use your own switch and unlink at any time while paused. If you turn off auto renew in the App Store or Google Play while linked, we send you a notification saying when your accountant's access will pause.

Unlinking: You may unlink your accountant at any time from My Accountant. When you unlink, your accountant immediately loses the ability to view your data through PocketReceipt. Synced data stored for the accountant, including any HMRC manual records they made for you, is deleted from our servers. Data already downloaded by the accountant is outside PocketReceipt’s control. Your local data in the app is not affected.

Legal basis: Accountant data sharing is based on your explicit consent under UK GDPR Article 6(1)(a). You provide this consent by approving the link request. You can withdraw consent at any time by revoking access.
Controller relationship: Your accountant acts as an independent data controller for any personal data they access, download, or process through PocketReceipt. PocketReceipt provides the technical platform for data sharing but does not control how your accountant uses the data once accessed. Your accountant is responsible for their own compliance with UK GDPR, including any obligations under their professional regulatory body.
6B. Secure document transfer App Dashboard
Optional upload of financial documents to your linked accountant

PocketReceipt allows you to securely send financial documents (such as bank statements, platform earnings reports, or phone bills) to your linked accountant. This feature is entirely optional and only available when you are linked to an accountant.

How it works: You capture a photo of the document in the app. When you tap "Send to accountant", the image is uploaded to Firebase Storage in a secure, isolated folder. Metadata (document type, month, year, notes) is written to Firestore. Your accountant can download the document via a time-limited secure URL (valid for 30 minutes) generated by our servers.

Storage and deletion:

  • Uploaded documents are automatically deleted from our servers after 30 days.
  • A local copy remains on your device (for your own tax records) and is not affected by the server deletion.
  • Maximum file size: 2 MB per document. Images only.
  • Maximum 5 documents per month.

Security: Your documents are stored in Firebase Storage with strict access rules. Only you can upload to your own folder. No one (including your accountant) can read the files directly. Downloads are only possible through authenticated Cloud Function signed URLs that verify your accountant link is active.

Legal basis: Document transfer is based on your explicit action (uploading the document) under UK GDPR Article 6(1)(b), processing necessary for the performance of a contract (your accountancy service). You can choose not to use this feature at any time.
7. International transfers
Processing outside the UK/EEA

Some of our service providers process data outside the UK/EEA. The following transfers occur:

  • Google LLC (Firebase, Google Analytics, reCAPTCHA Enterprise), United States. Covered by the UK-US Data Bridge and Google's Standard Contractual Clauses (SCCs).
  • Anthropic, PBC (AI chat assistant on the website), United States.
  • Telegram (forwarding website chat messages to our team). Telegram may process data outside the United Kingdom.
  • OpenAI (AI receipt scanning), United States. Covered by Standard Contractual Clauses (SCCs). Receipt images are not used to train OpenAI's models and may be kept by OpenAI for up to 30 days for abuse monitoring before being deleted.
  • Microsoft Corporation (Clarity), United States. Covered by the UK-US Data Bridge and Microsoft's Standard Contractual Clauses (SCCs).

You can request a copy of the relevant transfer safeguards by contacting hello@pocketreceipt.co.uk.

8. Data retention
How long data is kept

Retention periods:

  • Local app data: retained on your device until you delete individual records or delete your account.
  • Cloud-backed data: retained while your account is active and a valid subscription provides cloud access. Deleted within 48 hours of account deletion.
  • Your accountant's copy of your records: kept while the link is active. Deleted when you unlink, when you delete your account, or 30 days after a payment pause starts if you do not return to paid Professional.
  • HMRC submission records: if your accountant submitted updates to HMRC for you through the Accountant Dashboard, the record of each submission (what was sent, the HMRC reply and reference, and when) is kept for at least 7 years, so the submission can be shown if it is ever queried. These records are not deleted when a link pauses, ends or is unlinked.
  • Receipt images (cloud): retained while the subscription or add-on that provides image backup is active. If the subscription or add-on that provides image backup expires, images are retained for a 30-day grace period before permanent deletion.
  • Secure documents: automatically deleted from our servers after 30 days.
  • Email capture data (website): retained until you request deletion by emailing hello@pocketreceipt.co.uk.
  • Website chat records on our servers (your latest message, the page you were on, any email address you typed in the chat, and team replies waiting to be shown): retained until you request deletion by emailing hello@pocketreceipt.co.uk. Copies forwarded to our team through Telegram are kept in that service until we delete them.
  • Founding Partner application data: the Founding Partners programme closed on 26 September 2026. Applications received before then are deleted as part of closing it.
  • Website analytics data: retained by Google Analytics for 14 months and by Microsoft Clarity for 30 days, as per their respective retention policies.
  • Usage statistics (App): individual usage records are deleted automatically 10 days after they reach our servers. The dates used to work out the anonymous totals are deleted as soon as each total is final: the time of your first saved scanned receipt after your fifth saved receipt or 90 days, the time of your first saved journey after 8 days, and the dates on which you started using a feature and your first such feature about 120 days after you joined (plus up to 8 days while that week's totals are completed), or 120 days after that feature if you started it later. If you have an annual subscription, only your first such feature and your starting device type are kept until 14 months after your first annual payment, to see whether annual subscriptions renew; then they are deleted too. The feature markers and the two small counts described in section 2.3 are kept while your account exists, so a feature is never counted twice. Anonymous totals are kept. Everything linked to your account is deleted when you switch usage statistics off or delete your account.
  • Advertising records from App versions before 2.3.2: install source and attribution records made by earlier App versions are kept until you delete your account, and are deleted with it.
  • Crash logs: stored on your device only. Never sent unless you explicitly choose to via Settings.
  • Accountant audit log entries: kept for at least 5 years after the accountant's account closes, so the record of who viewed or changed client records remains available, in line with the record keeping requirements of the Money Laundering Regulations 2017 (MLR 2017). Audit log entries are immutable and cannot be edited or deleted by the accountant. They are not deleted automatically. After that period, the accountant, or a client named in an entry, can ask us to delete them by emailing hello@pocketreceipt.co.uk.
  • AML CDD records (clientCompliance): these are the accountant's records under MLR 2017, which requires them to be kept for 5 years after the business relationship with the client ends. The accountant can update them in the Dashboard. They are not deleted automatically, including when a link ends or an accountant account closes. After that period, the accountant, or the client they are about, can ask us to delete them by emailing hello@pocketreceipt.co.uk.
  • Passkey credentials: retained while registered by the accountant. Deleted immediately when the accountant removes the passkey or deletes their Dashboard account.

HMRC record retention: UK tax law requires business records to be kept for at least 5 years after the 31 January Self Assessment deadline for the relevant tax year (longer if HMRC opens an enquiry). PocketReceipt uses soft-delete for individual receipt and mileage deletions: when you delete an individual entry, it is hidden from your view but preserved in the local database. You remain responsible for maintaining records in accordance with HMRC requirements, consult HMRC guidance or your accountant for current retention periods.

Account deletion: When you delete your account using the in-app option, PocketReceipt processes your data as follows:

  • All local data (receipts, mileage, vehicles, CIS records, messages, documents, settings) is permanently deleted from your device immediately.
  • Cloud backups in Firebase Storage are permanently deleted.
  • Your Firebase Authentication account is permanently deleted (or queued for automated deletion if re-authentication is required).
  • Any active accountant links are severed and synced data is deleted from accountant views.
  • Any documents uploaded via the secure document transfer feature are deleted from Firebase Storage.
  • CIS payment records, pending accountant requests, and message history are deleted.
  • Some server-side items may require up to 48 hours for automatic cleanup.

If you previously shared data with an accountant, copies they already downloaded are outside PocketReceipt's control.

Crash logs: PocketReceipt includes a local crash logging system. All crash logs are automatically sanitised before storage: personally identifiable information including store names, email addresses, GPS coordinates, postcodes, vehicle registrations, and monetary amounts are automatically redacted. Crash logs are stored only on your device and are shared only when you explicitly choose to send them via Settings > Send Crash Log.
9. Your rights
UK GDPR + additional regional rights

UK GDPR (UK/EEA)

  • Access, correction, deletion, restriction, and objection (where applicable).
  • Data portability (where applicable).

Right to complain (UK/EEA)

You can lodge a complaint with the UK supervisory authority, the Information Commissioner’s Office (ICO), or your local supervisory authority (EEA) if applicable.

United States (where applicable)

  • Right to know/access the categories of personal data collected and disclosed.
  • Right to delete personal data (subject to legal exceptions).
  • Right to correct (in some states, where applicable).
  • Right to opt-out of “sale” or “sharing” (as defined by applicable law). PocketReceipt does not sell personal data and does not share personal data for cross-context behavioural advertising.
  • Non-discrimination for exercising privacy rights.

Brazil (LGPD) (where applicable)

  • Confirmation of processing, access, correction, anonymisation, portability, deletion, and information about sharing (where applicable).
To exercise rights, contact hello@pocketreceipt.co.uk.
10. Deleting your account and data App Dashboard
In-app deletion + request by email

You can delete your PocketReceipt account and associated data using the in-app option Delete Account & Data.

If you cannot access the app, you can request deletion by emailing hello@pocketreceipt.co.uk.

11. Location data (mileage tracking) App
Optional, only if enabled
  • Location is used to calculate trip distance for mileage journeys you start, if you enable tracking and grant permission.
  • You can deny location permission and use manual mileage instead.
  • Foreground service usage may be required by Android while a journey is actively being tracked (if enabled).
  • What is stored on your device: for each GPS-recorded journey, PocketReceipt stores your start and end coordinates, the GPS path of the trip (a list of latitude/longitude points sampled approximately every 10 metres while tracking), the duration, the distance, and any address that was resolved at the end of the trip. This data is stored only in the local database on your device.
  • Reverse geocoding (address lookup): when you stop a trip, the start and end coordinates may be sent to your device's platform geocoding service, Apple Location Services on iOS, or Android's Geocoder (which on most devices uses Google Play Services), to obtain a human-readable address (such as "Tesco, Reading, RG1 2DH") for inclusion in your journey log. PocketReceipt does not operate this service. We do not transmit your coordinates or polyline to PocketReceipt servers. If geocoding fails (for example, you are offline), your trip is still saved with its coordinates; the address remains blank.
  • Mileage Logbook PDF: at your request, PocketReceipt can generate a PDF logbook of your saved journeys (including the fields HMRC requires, date, start, end, distance, purpose, vehicle, AMAP allowance) for a date range you choose. The PDF is rendered on your device using the journey data already stored locally. The resulting PDF is saved to your app documents and shared only when you tap your device's share sheet.
  • Route maps (Pro PDF only): if you have Mileage Logbook Pro entitlement (paid subscription, VIP, or active 30-day free trial) and you generate the PDF while online, PocketReceipt fetches map tiles from OpenStreetMap (openstreetmap.org) covering the area of each trip, and overlays your stored GPS polyline on top. The fetch is direct from the OSM Foundation tile servers; tile URLs include the tile coordinates of the area being viewed (which approximate the location of your trips). Standard HTTP request metadata (your device's IP address, timestamp) is visible to OSM during the fetch. PocketReceipt does not transmit your trip identity, account, or polyline to OSM. If you are offline or the fetch fails for any reason, the Pro PDF falls back to a self-drawn route diagram with no third-party request.
  • Cloud backup: if you are subscribed to Essential or Professional, mileage journey records may be included in your encrypted cloud backup as described elsewhere in this policy. The cloud backup includes the same fields stored locally (date, miles, addresses, coordinates, polyline, purpose, vehicle).
12. Automated decision-making App
AI scanning and profiling

PocketReceipt uses AI (via OpenAI) to extract text from receipt images when you use the AI scanning feature. This is automated processing of your receipt image to extract structured data (store name, date, amount, VAT, category).

No automated decisions are made about you based on this processing. The AI extracts data from your receipt, it does not make decisions about your tax liability, creditworthiness, or any other matter. You review and confirm all extracted data before saving.

PocketReceipt does not use profiling or automated decision-making that produces legal or similarly significant effects on you, as defined under UK GDPR Article 22.

13. Children’s privacy
Adults only

PocketReceipt is intended for adults. We do not knowingly collect data from children.

14. Changes to this Privacy Policy
Updates

We may update this Privacy Policy from time to time. If we make material changes that affect how your personal data is processed, we will notify you via email (if we have your email address) or via an in-app notification before the changes take effect. The "Last updated" date at the top of this policy will always reflect the most recent revision. We encourage you to review this page periodically.

15. Contact
Privacy requests

Email: hello@pocketreceipt.co.uk

Developer: PocketReceipt (United Kingdom)

Report a security issue: If you discover a security vulnerability or data protection concern, please report it immediately to hello@pocketreceipt.co.uk with the subject "Security Issue Report". We aim to acknowledge all security reports within 24 hours and resolve critical issues within 72 hours.