Security and data handling
What we hold, where it sits, and who can reach it.
Written for the person deciding whether to trust this with their pipeline, and for the business owner who found us holding their address and wants to know how carefully.
There is no password on your account
Sign in goes through Google or LinkedIn, so we never hold a credential to leak and there is no reset flow to attack.
Nothing sensitive reaches the browser
Provider keys and the service role stay on the server. The only key the browser sees is a publishable one, and every metered action is decided server side.
Your rows are yours at the database level
Row level security means one account cannot read another account rows, enforced under the data rather than in the interface on top of it.
Contact data ages out
Enriched contact details are held on a clock and purged, rather than kept forever because storage is cheap.
A removal survives the next run
Suppression is checked on every ingestion, so a removed business is not quietly re-added the next time our reader sees it.
Payments never touch our servers
The card is entered on the provider page. There is no card field anywhere in this product and there never will be.