Privacy
Two separate things are covered here. What this website collects from anyone who visits it, and what happens to a claim file a brand sends us for an audit. The commitments are different, so they are written out separately.
This website
We run Google Analytics to see how many people reach the site and which pages they read. It puts a cookie in your browser holding a random ID, and it reports to Google which pages you opened and what kind of device you are on. Your approximate location, usually the city, is worked out from your IP address. Google does not store the full IP address alongside that data, but the random ID still counts as an identifier under UK and EU law, so we treat the whole record as personal data rather than as anonymous.
If you are in the EEA, the UK or Switzerland, those cookies stay off until you press Accept on the banner, and consent is the only legal basis we rely on for them. Elsewhere they are on by default and Decline turns them off. Your choice is stored in your own browser, and you can change it by clearing the site data. Google processes this data in the United States.
There are no advertising pixels on the site and no session recording. The typefaces are served from our own domain, so nothing leaves your browser to load them. One call does go to Google on every page: the tag that loads Google Analytics. It runs even if you decline, though in that case it sends no cookie and no identifier.
The contact form
The form asks for your name, email address, brand name and website, your rough monthly claim volume and the kind of claim you deal with, plus anything you write in the message box. It reaches our inbox through a relay called FormSubmit. FormSubmit says it does not store submissions, and we cannot verify that from the outside, so treat the form as a message passing through a service we do not control. Email us directly if you would rather it did not.
We use what you send to answer you and to scope an audit. We do not add you to a mailing list and we do not pass it to anyone else. The message sits in our inbox for as long as we are talking and a while after, and it goes when you ask us to delete it.
A claim file sent for an audit
This is the part that matters if you send us work.
You share a folder. We read from it and we do not upload it anywhere else. Working copies live on a single machine with full disk encryption, and they are deleted within fourteen days of us sending your report. If you want them gone sooner, say so and we delete them within one business day. Either way we confirm the deletion in writing.
We do not ask for customer email addresses, names, phone numbers or payment details, and our template has no column for them. A claim can be examined without any of it. If your export contains those fields, we delete them before we start and tell you we did.
After that fourteen day window nothing from your file stays with us. We do not reuse it for another brand or put it in any shared database or index. It is never published and never used to train a model. Your report is written only from your own claims.
We do not connect to your store and we have no access to anything outside the folder you share.
If we ever become aware that your file was exposed, we tell you in writing within 24 hours of finding out, with whatever we know at that point.
Your rights
Ask us what we hold about you and we will tell you. Ask us to delete it and we will, then confirm it. You can also ask for a copy of what you sent us, or tell us to stop using it. One email is enough, and we answer within 30 days. If you are in the EEA or the UK these rights come from the GDPR, and if you are in California they come from the CCPA, but you do not need to cite either one to use them.
We have never sold or shared personal information for money or for advertising, and we do not intend to.
If you think we have handled your data badly, tell us first. You can also complain to your national data protection authority, or to the ICO if you are in the UK.
Contact
Karimer LLC, trading as VerifyReturns, is the controller of the data described here.
[email protected]