Trust Centre
Practical safeguards, explained in plain language before you upload anything.
Leakage Finder handles billing reconciliation data, not cybersecurity or data leak detection. This page explains exactly what the current product does with your CSVs and saved audit results — no compliance theater, just what actually happens.
The 10-second version
Raw CSVs not stored
Uploaded files are not kept as file storage. Only structured results are saved.
Parsed in your browser
CSV parsing and comparison run client-side before results are saved.
Runs scoped per account
Supabase row-level security ties every saved run to your signed-in user ID.
Stripe handles billing
Card details and payments are processed by Stripe, never stored on our servers.
Supabase Auth + RLS
Authentication and per-row access control run on Supabase's managed auth stack.
Where your data actually goes
A single reconciliation run moves through four steps. Nothing about this flow requires storing your raw billing file.
You export two CSVs
Vendor billing export + PSA billing export from tools you already use.
Parsed in your browser
Rows are normalized and compared client-side, not on a shared server queue.
Structured results saved
Client, product, quantity, and dollar-impact fields are stored, scoped to your account.
Raw file discarded
The original CSV upload is not retained as a file after the run completes.
How your data is handled, in detail
What you upload
Leakage Finder is built for vendor or distributor billing CSV exports and PSA/customer billing CSV exports. These files usually include client names, products or SKUs, quantities, and pricing fields.
How the app processes CSVs
The app parses each CSV in your browser and keeps only the normalized client, product, quantity, and pricing fields needed for the audit. Those fields are sent over TLS to an authenticated server endpoint for reconciliation and saved as structured results tied to your account. The raw CSV files are not stored as file uploads.
Workspace isolation
Saved audits, recovery notes, usage limits, and billing entitlements are accessed through authenticated server endpoints. Browser access to the underlying audit and billing tables is blocked, and every server query is scoped to the signed-in account.
Authentication and payments
Authentication is handled by Supabase Auth. Paid subscriptions and billing portal sessions are handled through Stripe.
What this product does not do
Said plainly, so there is no ambiguity about what you are and are not getting.
- Does not automatically write corrections back to your PSA — every fix is reviewed and applied by your team.
- Does not sell, rent, or share your data with third parties.
- Does not claim SOC 2, HIPAA, ISO 27001, or any other compliance certification.
- Does not monitor for cybersecurity incidents or data leaks — this is a billing reconciliation tool, not a DLP or security product.
Retention and deletion
Saved reconciliation results stay tied to your account until you delete your account or request removal. Raw CSV uploads are never retained as files — once a run is parsed and compared, only the structured, row-level results are kept.
Deletion requests and questions
To request deletion of your account data or ask a security/data-handling question, email support@leakagefinder.com. The security guide, setup guide, sample audit, and sample CSV templates are available before you upload any real customer billing exports.
This page reflects the current, actual behavior of the product. If something changes, this page changes with it.