Privacy
What we hold, and how to make us stop.
We work from secondary, publicly available sources. Recentriq LLC is the controller of this data.
Make a request
This reaches us directly and does not go through a person first. We answer within 30 days.
What we collect about a business
Business contact details and public listing information — name, website,
address, phone number, category — from public directories and from the
business's own website. Snapshots of public pages of that website. Public
reviews. None of it is behind a login, and our crawler obeys
robots.txt (details).
Where a published business address happens to be a person's name — a sole trader, a named practitioner — it is personal data and everything below applies to it.
What we never collect
We work from secondary, publicly available sources and nothing else. We do not buy personal data. We do not use private or customer-supplied datasets. We ask for access to no system you run — not your booking software, not your CRM, not your inbox, not your analytics — and there is no version of this product in which we would.
Everything a report is built from is something any member of the public could have opened. That is a constraint on the product, and it is the reason the product can say what it says.
What we collect about a subscriber
What you typed into the signup form: your business name, its website, its postal address, your name and your email address. Which reports we produced and sent you, and whether you opened the billing page.
What we collect when you write to us
If you use the contact form: your name, your email address, the business you named if you named one, and what you wrote. It is stored so that a person can answer it and so that we can find the conversation later. It is used for that and nothing else — it does not join a mailing list, and writing to us is not consent to be marketed to.
Your password is stored as a scrypt hash. We cannot read it, which is why we cannot tell it back to you.
Stripe holds your card details and we never see them. We keep the customer and subscription identifiers Stripe gives us, so we know what you are owed.
Why we are allowed to
For subscribers: to perform the contract you entered into. For business contact data before that: our legitimate interest in offering a relevant business service to a business, balanced against the interest of the person whose address it is — which is why every message carries a one-click opt-out that works without a reply, and why opting out is permanent.
Where AI comes into it
A language model does the reading. Public text about a business — reviews, listings, the pages of its own website — is sent to a model provider, which extracts what was said and where. That is the whole of its job.
Every number is then computed in our own code over what it returned: how often a theme was raised, on how many separate platforms, whether it is worsening. The model is never asked how often something happens, and it cannot add a fact to a report.
Your account details, your card, your password and what you write to us are not sent to a model. Nothing we send is used to train anybody's model.
Who else sees it
Stripe, for payments. Our email provider, to deliver messages. Our model provider, for the reading described above. Our hosting provider. Nobody else: we do not sell, rent or share this data, and we do not use one customer's evidence to write another customer's report.
How long
Enquiries sent through the contact form are kept for two years, so that a conversation can be picked back up. Reports and the evidence behind them are kept while you are a subscriber and for one year after, so a finding stays traceable. Suppression records — the list of addresses that asked not to be contacted — are kept permanently and deliberately: deleting one is how somebody gets emailed again after asking us not to.
Your rights
Access, correction, deletion, restriction, objection, and portability, and the right to complain to your data protection authority. Use the form above, or write to us.
Cookies
This site sets no cookies and runs no analytics or advertising script. The only place a cookie is set is the operator's own dashboard, which is not part of the public site.