Security and data handling
Practical notes for MSPs before uploading billing exports.
Leakage Finder handles billing reconciliation data, not cybersecurity or data leak detection. This page explains what the current product does with your CSVs and saved audit results.
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 current app parses CSV files in the browser, compares the normalized rows, and stores saved reconciliation runs as structured audit results tied to your account. The app does not store the raw CSV files as file uploads.
Workspace isolation
Saved profiles and reconciliation runs are stored in Supabase tables with row-level security policies scoped to the signed-in user's ID.
Authentication and payments
Authentication is handled by Supabase Auth. Paid subscriptions and billing portal sessions are handled through Stripe.
Operational boundaries
- Leakage Finder shows reviewable billing mismatches and revenue impact.
- It does not automatically write corrections back to a PSA.
- It does not sell user data.
- It does not claim SOC 2, HIPAA, ISO, or other compliance certification.
Deletion and questions
To request deletion of your account data or ask a security/data-handling question, email support@leakagefinder.com. If you are evaluating the workflow first, use the sample audit and sample CSV templates before uploading real customer billing exports.