What we store, who else sees it, and how long it stays

Checkout has two boxes to fill in: a name and an email address. The rest of the order is already decided: the package step, the quantity, and the public link or username you pasted for each item.

None of that is a credential. There is no account to open here, no password to set, no login code and no permission for an app, so none of those reaches us and there is no password of ours to lose.

One row for the order and one row per item on it. The order row carries the order ID, the random token that forms the address of your order page, the name and email you typed, the currency you were shown, that total and the US dollar total, and where payment stands. Each item row carries the product, the quantity, the address you pasted and the price of that line.

Two technical fields sit beside them for fraud checks. One is a SHA-256 hash of the IP address the order arrived from, so we can see that two orders came from the same place without the address itself sitting in the table. The other is the first 180 characters of the identification string your browser sends with every request anyway.

Google Analytics runs on the site to measure which pages are read and where orders come from; your answer to the cookie banner decides whether it may set cookies or must run cookieless. No measurement script, no tag manager, no advertising pixel, no session recording, nothing that carries a profile of you from page to page. Open your browser's network tab: the only requests leaving these pages are the ones the shop needs.

We also never see how you pay. Picking a coin and sending it happens away from here, so no wallet key and no recovery phrase passes through this site. Past the name and the email there is no field for a postal address, a phone number or a date of birth. No part of an order would use one.

Five entries, held in local storage rather than in cookies, all written by this site and readable by no other: mrfollows_cart, mrfollows_currency, mrfollows_geo_currency, mrfollows_cookie_consent and mrfollows_pending_order.

The cart entry holds what you picked, so a reload does not lose it. The currency entry holds the one you set in the footer. The suggestion entry holds a currency and nothing else: the site asks once which of the four fits the country a request came from, and applies it only if you have not chosen. The consent entry holds your answer to the notice at the bottom of the screen, and the last holds the ID of the order you are paying, so the cart empties when that order is paid and not before.

Clearing site data removes all five, and the shop still works without them. More sits on the cookie preferences page.

The database holding orders and the text of this site runs on Supabase, and the site is hosted on Vercel. Order confirmations and the reply to a contact form go out through Resend. A confirmation carries the whole order, so Resend sees your email address, what you bought, the quantity, the price, the link you pasted and the link to your order page. A contact message reaches it with whatever you wrote in it.

Payment runs through our card provider, Zbooni, or through one of two crypto payment services, Cryptomus and NowPayments. Whichever of the two makes your invoice is given the order ID, the amount, your email address and the link to your own order page, which is where it sends you back to after payment, and the payment status comes back the same way.

The delivery request is the narrowest of the lot: a service number, the quantity, the link you pasted and an internal reference, plus your comment lines when you wrote some. Your name, your email address and the amount you paid are not in it.

The link check sends the handle or ID read out of your address to an outside lookup that reads the public page, on the eight platforms where the target is resolved. On Facebook, LinkedIn, Twitch and Kick nothing leaves this site, because nothing is fetched there. A short health row is written either way: the platform, whether it worked, how long it took. Your link is not in it and neither are you.

Our own operations screen is told the order ID, what happened and when, and nothing about who placed it. None of this is sold, and none goes out for advertising.

Order records stay. They are what a refill claim inside 30 days is checked against, and what a question months later is answered from. No deletion job runs across that table today, so a record sits there until you ask for it to go.

The counter that stops one address from hammering checkout, the contact form or the review form is keyed on that address and dies with its window: a minute for the first two, an hour for the third. A link check result is held in memory and never reaches the database. The finished preview sits there for five minutes, so two people checking the same profile do not both cause a lookup, and the account or video id read out of your address sits there for a day.

A message sent through the contact form is not in the shop database at all. It is email, and it lives in the support mailbox.

The review form takes a name, a rating, the service it is about, and the text. A submission is saved unpublished and stays invisible until a person approves it, because a form that publishes on submit is one anyone can write our site with. If one is ever published, the name given with it stands next to it, so put in a name you are content to see there.

You can ask for a copy of what is stored against your order, for a correction, or for deletion. Write to support@mrfollows.com, where a reply comes within 24 hours. Include the order ID if you have it, since that is what the record is filed under.

If you are in the EU or the UK, the GDPR page sets out which rights apply and how to use them. For MrFollows the governing law and the place of jurisdiction is the United Arab Emirates.