Privacy Policy

Last updated: 10 October 2026

On this page

Lekkafy ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our service at lekkafy.com and our mobile applications. It also covers our obligations and your rights under the UK GDPR and EU GDPR.

This policy describes the processing we carry out and the lawful basis for each activity — see "Lawful Basis for Processing" below. Where we rely on your consent for a specific purpose (such as optional marketing communications), we will ask for it separately and you may withdraw it at any time; this policy alone is not a substitute for that consent.

1. Who We Are

Lekkafy Ltd is a family budgeting application and acts as the Data Controller for personal data you provide when using our service. We determine the purposes and means of processing your personal data. We are registered in England and Wales (Company No. 17378238) and with the Information Commissioner's Office (ICO Registration No. C1997472).

For data protection enquiries, contact us at support@lekkafy.com.

2. Information We Collect

2.1 Information you provide directly

  • Account information: Your email address (used for passwordless sign-in via magic link).
  • Display name: A name or alias of your choice — this does not need to be your real name. We do not ask for or verify your legal identity.
  • Financial data: Expense records, budget limits, income entries, savings balances, investment balances and contributions, commitments, loan and repayment records, and category labels that you manually enter or import.
  • Family data: A family name and display names for members you choose to add. These are aliases and do not need to reflect real names.
  • Information from other household members: If someone invites you to their household, or adds a record that names or concerns you (for example, a loan marked as owed to or by you), we hold that information as part of providing the service. See "Household Sharing" in section 6 below for how this is shared within a household.
  • Receipts and statements: Images or PDFs you upload for AI-assisted parsing. See the table below for exactly what happens to these — the original file, the extracted data, and what is sent to our AI provider are each handled differently.
  • AI conversation inputs: When you use Ask Lekka, the question you type and the underlying financial data needed to answer it (see section 3).
DataWhat happens to it
Original receipt image / statement PDF or CSV you uploadSent to our AI provider (Google Gemini) for extraction, and not written to our own database or file storage. It exists only for the duration of that processing request on our servers. Google's own handling of the uploaded content is described in section 6.
Extracted transactions (date, merchant, amount, category)Saved to your account (Supabase, EU/Ireland) once you confirm/import them, and retained per section 7 until you delete them or your account.
Identifiers printed on the document (sort code, account number, masked card number)Our extraction schema has no field for these, so they are never saved to your account. However, the full document — including any such identifiers printed on it — is sent to Google for processing before extraction happens; see section 6 for what Google does with it.
Server/application logs of an upload happeningMay record that a request occurred (timestamp, user, file size, success/failure) for debugging and security purposes, but not the document's contents.

2.2 Information collected automatically

  • Authentication logs: Our authentication infrastructure automatically logs sign-in event timestamps and IP addresses for security purposes. We do not read these logs as part of our normal operation of the service; our infrastructure provider (Supabase) processes and retains them on our behalf as a data processor under our agreement with them, and our own personnel may access them only for debugging, security investigation, or as required by law.
  • Hosting/traffic data: Our hosting provider, Vercel, processes technical information needed to deliver requests to and from our servers — for example IP address and basic request/system information. This is used to operate and secure the service, not for advertising or behavioural tracking. See section 6.

2.3 What we never ask for

  • We never connect to your bank account.
  • We never ask you for bank credentials or passwords, and do not have a form field or feature that requests them.
  • We never use open banking or third-party financial data aggregators.
  • We do not use analytics or tracking tools for advertising or behavioural profiling, and we do not use session recordings or ad tracking. We do use Vercel's privacy-focused page analytics and performance measurement on our website, described in section 11.
  • We do not sell your data to advertisers or third parties.

Note: bank statements or receipts you choose to upload may incidentally contain details such as a sort code, account number, or masked card number printed on the document. We don't ask for or require this information, and our AI extraction is constrained to return only transaction data (date, merchant, amount, category) — it has no field to output account numbers or similar identifiers, so they are never saved to your account even if present in the source document. This does not mean Google never receives that identifier — see the table above and section 6 for what is actually sent to our AI provider.

3. How We Use Your Information

  • To provide, operate, and maintain the Lekkafy service.
  • To authenticate your identity — via a magic link on the web, or a one-time code sent to your email on our mobile app.
  • To process AI-assisted features such as receipt scanning, statement parsing, and budget suggestions.
  • Ask Lekka: when you ask Lekka a question, it can query your recorded financial data — spending, budgets, transactions, commitments, savings, and your safety-net/runway figures — to compute an answer. Your question and the relevant data needed to answer it are sent to our AI provider to generate a response. We do not save a transcript of your conversations with Lekka on our servers.
  • To send transactional emails (magic links, family invitations, budget alerts). We never send unsolicited marketing without your consent.
  • To detect, investigate, and prevent fraudulent or unauthorised activity.
  • To comply with legal obligations.

4. Lawful Basis for Processing (UK GDPR / EU GDPR)

We process your data under the following lawful bases:

Processing ActivityLawful Basis
Account creation and authenticationContract (Art. 6(1)(b))
Storing financial records you enterContract (Art. 6(1)(b))
Sending magic links and invitationsContract (Art. 6(1)(b))
Receipt scanning, statement parsing, budget suggestions, and Ask Lekka (AI processing you actively use)Contract (Art. 6(1)(b)) — processing genuinely necessary to deliver the feature you've asked for
Sharing your records with other members of your householdContract (Art. 6(1)(b)) with the household member who added you — you agree to household visibility when you join or create a family; see section 6
Customer support enquiries and related correspondenceContract (Art. 6(1)(b)) where support relates to your use of the service, or Legitimate Interests (Art. 6(1)(f)) for general enquiries
Processing information about a non-user named in your records (e.g. a loan counterparty) or an inviteeLegitimate Interests (Art. 6(1)(f)) of the inviting/recording user and Lekkafy in providing the feature — this is not automatically covered by our contract with the user who added them
Security monitoring and fraud preventionLegitimate Interests (Art. 6(1)(f))
Measuring how the website and web app are used and how fast they load (Vercel Web Analytics and Speed Insights — aggregate, cookieless, not used for advertising or profiling; see section 11)Legitimate Interests (Art. 6(1)(f)) — keeping the service working and fast and understanding which pages are used. You can object at any time; see your rights below
Marketing communications (if opted in)Consent (Art. 6(1)(a))
Legal holds or regulatory requestsLegal Obligation (Art. 6(1)(c))

5. Data Storage and Security

Your primary application database — your account, financial records, and files — is hosted on Supabase infrastructure in the EU (Ireland) region. This does not, by itself, mean every operation on your data stays in Ireland: AI processing, vendor support access, and operational logs can involve other locations, as described in "International Data Transfers" (section 8) and "Data Sharing" (section 6).

We implement the following safeguards:

  • All data is encrypted in transit and at rest using industry-standard protocols.
  • Database-level security policies enforce access according to your user and household permissions: your own entries are visible only to you and, where you use Family mode or belong to a household, to that household's members. Individual mode is a personal view for decluttering your own entries — it is not a private space hidden from your household. Household membership, not the mode you have selected, determines who can see your records — switching between Individual and Family mode changes only what you see, not who else can see it. See section 6 for what household members can see, and "Family Features" in our Terms of Service for how household access works.
  • Passwordless authentication: no passwords are ever stored or transmitted.
  • Access to production systems is restricted to authorised personnel only.
  • Regular security reviews and dependency audits.

No system is 100% secure. If you discover a security vulnerability, please report it responsibly to support@lekkafy.com.

6. Data Sharing and Third Parties

6.1 Household sharing

If you create or join a household (Family mode), the other members of that household can see the financial records you and they add — this is core to how Lekkafy works as a shared household budgeting tool, not a third-party disclosure. Specifically:

  • Members can see each other's expenses, budgets, income, commitments, and other financial records added under that household — including entries added before a member joined, and entries added in Individual mode (which is a personal view for you, not a privacy boundary from your household — see section 5).
  • The household administrator has additional permissions, such as inviting or removing members; see "Family Features" in our Terms of Service for the full list.
  • If a member leaves or is removed, or deletes their own account, the records they added while a member generally remain visible to the household (they were shared household records, not that member's private data) unless deleted by whoever has permission to do so. If the household administrator deletes their own account, this can delete the household's shared data entirely — see "Family Features" in the Terms of Service for what happens in that case.

6.2 Third-party processors and providers

We do not sell, rent, or trade your personal data. We use the following providers to operate the service:

  • Infrastructure provider: Supabase — database, authentication, and file storage hosted in the EU (Ireland) (data processor).
  • Hosting provider: Vercel — hosts and serves our web application and backend API. As part of delivering your requests, Vercel processes end-user traffic information such as your IP address and basic request/system information (data processor). We use this to operate and secure the service; it is not used for advertising or to build a profile of you. We also use Vercel Web Analytics and Vercel Speed Insights on our website and web app to measure aggregate page views and page-load performance (see section 11); Vercel processes that measurement data on our behalf as our data processor, and it is not used for advertising or to build a profile of you.
  • AI processing provider: Google, via the paid tier of the Gemini Developer API. When you scan a receipt, import a statement, use Ask Lekka, or receive AI-generated budget suggestions, the relevant image, text, or financial data needed to answer your request is sent to Google's Gemini API for processing. Because we use a billing-enabled (paid) configuration:
    • Your prompts, uploaded content, and Google's responses are not used to improve Google's general-purpose products, under Google's applicable terms for paid use.
    • Google nonetheless retains certain request data — currently up to 55 days, per Google's published terms — for abuse and safety monitoring, and authorised Google staff may review content flagged by that monitoring. This is separate from, and not covered by, our own account-deletion timelines (section 7).
    • Google's terms also permit use of this data to improve its abuse-detection and policy-enforcement systems specifically, distinct from training general models. We do not claim your data is never used for any purpose at Google — only that it is not used to train Google's general models under our paid configuration.
    • This processing may occur on Google infrastructure outside the EU/UK, including in the US (see "International Data Transfers" below), and — for some operational and account-level functions — Google may act under its own separate controller terms rather than solely as our processor.
  • Email delivery provider: Resend, via Supabase's authentication email integration — sends transactional emails (magic links, family invitations). This necessarily includes the email content (such as your magic link), not only your email address.
  • Law enforcement or regulators: where required by applicable law or court order.

Our third-party processors are contractually bound to process your data only as instructed and to maintain appropriate security standards. Where a provider holds data on our behalf (such as authentication or hosting logs we do not routinely access ourselves), it remains part of our processing of your data, and we remain responsible for it — engaging a processor does not remove that responsibility.

7. Data Retention

We retain your data for as long as your account is active. The figures below describe our current configuration — where a figure is still being verified against our live provider settings, we have flagged it rather than state it as certain.

DataRetention
Account and profile dataUntil you delete your account.
Financial records (expenses, budgets, savings, investments, commitments, loans)Until you delete the record, or until you delete your account.
Active-database deletionRemoved from our active (live) database immediately on request/account deletion.
Backup copies of deleted dataPurged from backups within 30 days of deletion. Our database provider currently keeps daily backups for 7 days, so in practice deleted data leaves our backups within about a week.
Authentication logsRetained for 90 days for security purposes, then automatically purged [figure under verification against our current provider configuration].
Support emails and related correspondenceRetained for as long as reasonably needed to resolve your enquiry and for a limited period afterward for quality and dispute purposes, then deleted or anonymised.
Invitations (pending or expired)Retained until accepted, declined, expired, or for a limited period afterward for record-keeping.
Email-delivery records (via our email provider)Retained by our email delivery provider per its own operational retention period, primarily for deliverability and abuse prevention.
Technical/operational logs (hosting, application logs)Retained for a limited operational period for debugging and security, then rotated out; not used to reconstruct document content (see section 2).
AI-related data held by Google (Gemini API)Not covered by our own deletion timelines above — see section 6 for Google's separate abuse-monitoring retention (currently up to 55 days per Google's published terms).
Data subject to a legal holdRetained for as long as required by the applicable legal, regulatory, or dispute-resolution obligation, notwithstanding the periods above.

8. International Data Transfers

Your account data, financial records, and files are stored on Supabase infrastructure in the EU (Ireland) (see section 5 for what this Ireland-hosting claim does and doesn't cover). Processing through Google's Gemini API (receipt scanning, statement parsing, Ask Lekka, and budget suggestions) may involve Google infrastructure located outside the UK/EEA, including in the US. Our hosting provider, Vercel, may also process technical/traffic data in locations outside the UK/EEA as part of operating our infrastructure.

For a transfer outside the UK/EEA, we rely on the safeguard that actually applies to that transfer and that vendor, which — depending on the vendor and the applicable route — is one of:

  • The EU-US Data Privacy Framework and its UK Extension, where the receiving vendor is certified under that framework for the relevant data.
  • EU Standard Contractual Clauses (SCCs) for a transfer governed by EU GDPR.
  • The UK International Data Transfer Agreement (IDTA), or EU SCCs combined with the UK Addendum, for a transfer governed by UK GDPR — EU SCCs alone are not, on their own, a sufficient basis for a restricted UK transfer.

We do not list a specific safeguard against each named vendor here because it depends on that vendor's current certification status, which can change. You can request details of the safeguard applicable to a specific processor, verified at the time of your request, by emailing support@lekkafy.com.

9. Your Rights Under GDPR

As a data subject under UK GDPR and EU GDPR, you have the following rights, which we honour without charge within one calendar month of a verified request (extendable by up to two further months for complex requests, with notice):

Right of Access (Art. 15)

Request a copy of all personal data we hold about you, including how it is processed.

Right to Rectification (Art. 16)

Correct any inaccurate or incomplete personal data. You can update most data directly in the app.

Right to Erasure — 'Right to be Forgotten' (Art. 17)

Request deletion of your personal data. You can delete your account directly from Settings → Security → Delete Account. Your data is removed from our active database immediately and purged from backups within 30 days — see section 7 for the full retention schedule, including data our processors (such as Google) retain separately under their own terms.

Right to Restriction (Art. 18)

Request that we restrict processing of your data while a dispute is being resolved.

Right to Data Portability (Art. 20)

Receive a copy of your personal data in a structured, machine-readable format to transfer to another service. Submit your request by email and we will fulfil it within one calendar month.

Right to Object (Art. 21)

Object to processing based on legitimate interests. We will cease processing unless we can demonstrate compelling legitimate grounds.

Right to Withdraw Consent (Art. 7(3))

Withdraw consent for any consent-based processing at any time without affecting the lawfulness of prior processing.

Rights Related to Automated Decision-Making (Art. 22)

Lekkafy does not make solely automated decisions that produce legal effects concerning you or similarly significantly affect you. AI-generated insights (such as Ask Lekka's answers or budget suggestions) are informational only — you decide whether to act on them.

How to exercise your rights

Email support@lekkafy.com with your request. We may ask you to verify your identity before fulfilling the request. We will respond within one calendar month, as required by UK GDPR (extendable by up to two further months for complex requests, with notice).

10. Data Breach Notification

In the event of a personal data breach that poses a risk to your rights and freedoms, we will:

  • Notify the relevant supervisory authority (ICO for UK, applicable DPA for EU) within 72 hours of becoming aware.
  • Notify affected individuals without undue delay if the breach is likely to result in high risk.

11. Cookies and Local Storage

Lekkafy uses only essential cookies required for authentication (session tokens), on both our public website (lekkafy.com) and the authenticated app. We do not use advertising or tracking cookies.

Our website and web app load two measurement scripts from our hosting provider, Vercel: Vercel Web Analytics (aggregate page views, referrers, and broad device, browser and country information) and Vercel Speed Insights (page load and responsiveness timings). They are used only to understand how the site is used and to keep it fast. They do not set advertising or tracking cookies, do not follow you across other websites, and are not used to build a profile of you or for advertising. Vercel acts as our data processor for this. They run on public and authenticated pages alike, but they are not given your financial records, and we do not attach your account details to the measurements.

Our mobile app similarly stores only what is needed for the app to function — such as your session — using standard secure on-device storage, and does not use advertising or tracking SDKs.

12. Age Requirement

Lekkafy is intended for users aged 18 and over. We do not knowingly collect personal data from anyone under 18. If you believe a minor has provided us with personal data, contact us at support@lekkafy.com and we will delete it promptly.

13. Supervisory Authority

If you believe we have not handled your data in accordance with GDPR, you have the right to lodge a complaint with a supervisory authority:

We encourage you to contact us first at support@lekkafy.com. We will do our best to resolve any concern directly.

14. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in how we process your data or in applicable law. We will notify you of material changes by email or via an in-app notice at least 14 days before the change takes effect. Where a change requires your consent (for example, a new use of your data that relies on consent as its lawful basis), we will ask for that consent separately before relying on it.

15. Contact Us

For any privacy or data protection questions:

Lekkafy Ltd

Registered Office: 82A James Carter Road, Mildenhall, Bury Saint Edmunds, IP28 7DE, United Kingdom

Email: support@lekkafy.com

Website: lekkafy.com