Security at Lekkafy
Last updated: 10 October 2026
Your financial data is sensitive. We've built Lekkafy with security as a first-class concern, not an afterthought. Below is an overview of the safeguards currently in place, and where a claim depends on configuration we're still confirming against production, we've said so rather than overstating it.
No Bank Access
We never connect to your bank account. No credentials, no open banking, no third-party account aggregators. You enter what you choose.
No Passwords to Steal
Sign in with a magic link (web) or one-time code (mobile) — we never create, store, or transmit a password. This closes off password-reuse and credential-stuffing attacks, though email compromise and phishing still need their own precautions.
Encrypted at Rest
Your account and financial database is encrypted at rest using our infrastructure provider's industry-standard encryption, hosted on Supabase infrastructure in the EU (Ireland region).
Encrypted in Transit
All communication between your device and our servers is encrypted. Connections over plain HTTP are rejected.
Permission-Based Access Control
Our database enforces access policies based on your user and household permissions — you can only query data you or your household are permitted to see. Individual mode filters your own view; it does not hide your entries from other members of your household. This restricts unauthorised queries; it is one control among several, not a guarantee against every possible compromise.
Primary Data in the EU, Some Providers Process Elsewhere
Your account and financial database is stored on infrastructure in the EU (Ireland). AI-assisted features (Google Gemini) and transactional email (Resend) involve processing outside the EU/UK under appropriate safeguards — see the provider table and our Privacy Policy for exactly which providers and what safeguards.
Authentication & Session Security
- Magic links and one-time codes sent in the same sign-in email are both single-use. Their exact expiry windows are set in our authentication provider's configuration; contact support@lekkafy.com if you'd like the current configured values confirmed.
- Sessions are backed by signed, tamper-evident JWT access tokens, refreshed periodically using a separate refresh token. Revoking a refresh token (for example, on request to our support team) prevents new access tokens from being issued going forward; it does not necessarily invalidate an access token that was already issued and has not yet expired, so there can be a short window before revocation takes full effect.
- Authentication events (sign-in, sign-out, link/code requests) are logged with IP address and timestamp; retention of these logs is being confirmed against our current provider configuration.
- Signing out affects your current device/session. If you suspect unauthorised access, contact us immediately at support@lekkafy.com and we will help secure your account — see the point above for what "invalidating a session" does and does not guarantee immediately.
AI Processing (Receipt Scanning, Statement Parsing & Ask Lekka)
- Receipt images and statement files you upload are sent to Google's Gemini API over an encrypted connection to extract transaction data (date, merchant, amount, category) only.
- On our side: the raw image or file itself is not written to our storage or database — it exists only in memory for the duration of the request, then discarded. Only the extracted transaction data is saved to your account. This describes Lekkafy's own backend only — see the next point for what happens once the file reaches Google.
- On Google's side: we use a billing-enabled (paid) Gemini API configuration, so your prompts, uploaded content, and Google's responses are not used to improve Google's general-purpose products. Google separately 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 flagged content. This Google-side retention is not covered by, or removed by, Lekkafy's own "memory only" handling described above.
- Ask Lekka sends your question, along with the specific financial data needed to answer it (such as your budgets, recent transactions, or savings figures), to the same Gemini API, under the same Google-side handling described above. We do not save a transcript of your Ask Lekka conversations on our own servers.
- This processing may occur on Google infrastructure outside the EU/UK — see our Privacy Policy for the safeguards that apply.
Third-Party Subprocessors
We use a minimal set of trusted subprocessors, all operating under data processing agreements:
| Provider | Purpose | Data Region |
|---|---|---|
| Supabase | Database, authentication, and storage for user-uploaded profile/family avatars (not for AI-processed receipts or statements — see "AI Processing" above) | EU (Ireland) |
| Vercel | Hosts and serves our web application and backend API | Global edge network; our primary deployment region is the EU |
| Google (Gemini API) | Receipt scanning, statement parsing, Ask Lekka, budget suggestions | Global — Google's standard paid terms allow transient processing, storage, or caching in countries where Google or its agents operate, not limited to the EU/US |
| Resend | Transactional email (magic links, invitations), via Supabase Auth | United States — Resend stores email content and delivery logs in the US regardless of the sending region we've configured |
Infrastructure Security
- Production access is restricted to authorised personnel, with multi-factor authentication required on each provider account where it controls access to production systems.
- Environment variables and secrets are stored in our hosting provider's protected environment-variable configuration, never committed to source code.
- Dependencies are monitored for known vulnerabilities and updated regularly.
- Our database is automatically backed up daily by our infrastructure provider, and recent daily backups are retained. We do not currently offer point-in-time recovery, so a restore returns the database to the time of a daily backup rather than to an arbitrary moment. Files held in our infrastructure provider's file storage (see the provider table above) are covered by a separate recovery process from the database backup, since object storage and database backups are not the same mechanism.
Responsible Disclosure
We take vulnerability reports seriously. If you discover a security issue in Lekkafy, please disclose it responsibly:
Security contact: support@lekkafy.com
Please include: description of the issue, steps to reproduce, potential impact, and your contact details. Please do not include real passwords, sign-in links/codes, or other users' financial data in your report — a redacted example or screenshot is enough for us to investigate.
We aim to acknowledge reports within 72 hours, and will keep you updated on our remediation progress after that.
We ask that you do not publicly disclose the issue until we have had reasonable time to address it.
Your Security Controls
You have direct control over your security posture:
- Delete your account at any time from Settings → Security. What exactly is deleted depends on your role in your household — for example, a household admin's deletion also removes the household's shared records, while a regular member's deletion leaves their household's shared data intact. See our Terms of Service for the full breakdown, and our Privacy Policy for retention/backup timelines.
- Export all your data on request. Email support@lekkafy.com.
Coming soon: a self-service view of your active sessions, so you can review and revoke a session on a specific device yourself rather than contacting support.