Cookies and analytics
There's no cookie banner on Ormly, and that's deliberate. There's nothing to consent to.
What's stored on your device
Two things of ours, both in your own browser and neither sent anywhere.
If you sign a card, your browser keeps a token so you can edit your message until the card sends, and remove it whenever you like. Without it, your message wouldn't be yours to change.
It also remembers the name you signed with and the pen you chose, so the next card you sign doesn't ask again. It never leaves your device, and clearing your browser's data for ormly.uk removes it.
Both exist only to do something you asked for, which is why neither needs consent.
On the pay screen, Stripe, who take the payment, set cookies of their own to spot fraud. They're part of taking a payment safely, so they don't need consent either, and Stripe's own privacy policy covers them.
We don't use advertising cookies, we don't track you from site to site, and we don't let anyone else do it on our pages.
Counting visits
We count how many people visit a page and which page they came from. We do it ourselves: each visit adds one to a tally for that page and that day, in our own database in London. Nothing is stored on your device, no cookie is set, no IP address is kept, and nothing builds a profile of you. We can see that sign pages were opened 30 times on a Tuesday. We can't see who by, or which card.
We don't run any of that on the page where a card is read. That page is for one person, and it isn't a thing to be measured.
We record whether each email was delivered or bounced, because a card that doesn't arrive is the worst thing that can happen here and we need to know when it does.
We don't track opens and we don't track clicks. No invisible pixels.
What we measure and why
To keep the thing reliable, we watch numbers that are about us, not about you: how many cards sent on time, how many bounced, how many failed and had to be retried, how long pages take to load, and how often something errors.