Privacy policy

Who is responsible

Quivermark is run by one person, based in Moldova, who is the data controller for everything described here, except where we act for a customer (see “Alerts sent to someone else”). For any question or request, write to hello@quivermark.lol.

If you have an account

• Your name and email address
• If you connect them, a Slack or webhook address for a site’s alerts, the words you ask us to look for on its pages, and the times your scheduled jobs call their heartbeat link. Each is deleted when you remove it or the site
• If you add one, a second email address of your own for alerts. It is used only after you type back the code we send it, and you can remove it at any time
• Your password, stored only as a cryptographic hash — never as text
• If you turn on notifications, the address your browser’s push service gives us for each device, and a name like “Safari on iPhone”. It is deleted when you remove the device, or when the push service tells us it is gone
• If you sign in with Google or Apple instead, the name and email address they share with us, and an identifier for your account with them. We never see your Google or Apple password. If you choose Apple’s “Hide My Email”, we only ever know the relay address Apple gives us
• The websites you monitor and their settings: how often, the contact and product pages you nominate, how you proved you control the site, and whether a status page is on
• Every check result. These come from public web pages, and some include a short extract of a page’s code — a broken element, or the address of a script — so you can see what we found
• A record of each email we send — recipient, subject, and whether it was delivered
• A log of changes made on the account: what changed, which email address made the change, and when. Everyone on the account’s team can see it, and it is kept for 365 days
• If you turn on two-step sign-in, the key your authenticator app uses (encrypted) and scrambled copies of your recovery codes
• Your plan as Whop reports it: which plan, the price, its status and dates

Alerts sent to someone else

A customer can ask us to send a site’s alerts to someone else, usually their own client. If that is you, we store your email address and email you to ask; nothing else is sent unless you confirm, and ignoring it is enough. If you confirm, we store when, and send that site’s alerts to you. Here we act for the customer who added you, as their processor, and they are responsible for having your details.

If you follow a status page

A customer’s public status page lets visitors ask for email updates. If you do, we store your email address and email you once to confirm; if you do not confirm within 7 days it is deleted. Once confirmed, we email you when that page posts an incident or planned maintenance, and every email has a link that stops them at once. Here we act for the customer whose page it is.

If you are invited to a team

A customer can invite colleagues to their account. If that is you, we store your email address and the role you were given, and email you a link once. Nothing else happens unless you sign in with that address and accept. Either of you can end it at any time, and it is removed when either account is closed.

The inbox check

If a customer switches on the inbox check, their contact form sends a hidden copy of each enquiry to an address of ours. Resend, our email provider, receives it. We record only when it arrived: we never open the message, and never store who sent it, its subject or what it says. Here we act for the customer, as their processor. The arrival times are deleted after 90 days, or as soon as the check is switched off.

If you ask Q, the help character

Q answers in your browser; your questions are not sent anywhere to be answered. When Q has no answer, or you mark an answer as not helpful, we keep the question so we can write a better one: without your account, without your IP address, and with any email address, link or long number taken out first. When you mark an answer as helpful, we only count it.

If you only used the free check

You can run a check without an account. When you do, we store the address you entered, the result, and a salted hash of your IP address — never the address itself. The hash exists only so the same visitor cannot run unlimited checks; it cannot be turned back into an address.

If you ask us to email you the report, we store that address and the site it relates to, so we can send it and follow up once. Reply to any of our email and ask, and it goes.

Verifying a site by email

To prove you control a website, we can send a code to an address at that site’s own domain, or to one the site publishes. We store that address and a hash of the code until it is used or expires — thirty minutes. Signing up works the same way: we send a code to the email you give, and if that email is at the website’s domain or shown on the website, typing the code also proves the site is yours. To do that we read the site’s home and contact pages, as the checks do. If you receive one of these without having asked, someone tried to add your site: you receive that one email and nothing else, and ignoring it is enough. An owner can also ask us to email the steps to whoever looks after their site, at an address they give us: we send what to add and a link to confirm it, at most five times a day for a site, and keep a record of the send.

If we contacted your business

We look for businesses whose websites have a visible problem, such as a page that does not load or a broken link, and write to tell them. To do that we use the business’s website address and type from OpenStreetMap, the public map, and run the same kind of check on its public pages as our free check does. We keep the website address, what the check found, the contact details the website itself publishes, and when we wrote. We never buy lists or collect private addresses.

Reply to any message from us and ask, and we will not contact you again. We keep your website address on a do-not-contact list, so that request is never forgotten. What the check found and the contact details are deleted a year after we last wrote, or a year after the check if we never did; the website address stays, so we never write to the same business twice.

Why, and on what basis

• To provide the service you signed up for — your account, the checks, their results and the emails about them. This is necessary for our contract with you.
• Alerts to someone else — on the basis of their confirmation, which they can withdraw at any time by asking us or the customer who added them.
• Our legitimate interests — stopping one visitor running unlimited free checks, keeping records of the emails we sent so we can show what was delivered, keeping the service secure, and telling a business about a problem on its public website.
• Legal obligations — Whop keeps the records of what you paid that tax law requires.

How long we keep it

• Your account and everything attached to it: while you have a plan or use the account, and for a year after the last of those, so you can pick up where you left off. 30 days before that year is up we email you the date; signing in keeps the account, and otherwise we delete it and everything in it. Closing it yourself deletes all of it at once.
• Whop keeps its own records of what you paid after that, as tax law requires, under its privacy notice.
• The up-or-down samples taken every five minutes: 180 days.
• Records of the emails we sent: 365 days.
• When form emails arrived at the inbox check: 90 days.
• Free checks: 30 days.
• Questions Q could not answer well: 90 days.
• An address you gave us to receive a free report: 180 days.
• Verification codes, and the address they went to: until they expire.
• A sign-up whose email was never confirmed: 7 days, then deleted with everything in it.

Deleted data can survive for a short time in our database provider’s recovery history before it is gone for good.

Who else processes it

• Neon — the database, hosted in the EU (Frankfurt)
• Vercel — hosting and delivery of the website (United States)
• Resend — sending alerts and other email (United States)
• Hetzner — the server that runs the scheduled checks (Germany)
• GitHub — runs our own test jobs and the checks of businesses’ public websites described above (United States)
• Whop — payments, and the tax on them (United States). You pay on Whop’s own checkout page, so card details go to Whop and never reach us; Whop tells us only which account paid, for which plan, and whether it is still active.

Where data leaves the EU, it is protected by the safeguards these providers commit to, such as the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses. We do not sell your data, and we run no advertising or analytics tracking of our own.

What we do with it

We use it to run the checks you asked for and to tell you what they found. We do not use your monitoring data for anything else, and we do not email you about unrelated things.

Your rights

You can ask for a copy of what we hold, ask us to correct it, or ask us to delete it — including the account itself. Email hello@quivermark.lol and we will act within thirty days. We do not require a particular form of words.

You can also object to what we do with it, ask us to restrict it, and ask for what you gave us in a portable form. If you think we have handled your data badly you are entitled to complain to a data protection authority — in the EU, the one where you live or work; in Moldova, the National Center for Personal Data Protection — and you do not have to raise it with us first, though we would rather you did.

Cookies and your browser

We set one cookie, and only once you sign in: the one that keeps you signed in. It is strictly necessary for the service to work, it is not readable by scripts in your browser, and it is not used to follow you anywhere. Signing out removes it.

If you are on someone else’s team, a second cookie remembers which account you chose to work on. It holds only that choice, and is also not readable by scripts.

The dashboard also remembers, in your own browser, which suggestions you dismissed. That stays on your device and is never sent to us.

There are no advertising or analytics cookies, which is why you have not been asked to consent to any. Our fonts are served from our own servers, so visiting a page here does not hand your IP address to a third party. Checkout happens on Whop’s site, under its own privacy notice.

Changes

If what we store or who processes it changes materially, we will update this page and email account holders. The date at the top always reflects the current version.