Flurry

Privacy policy

Last updated 13 October 2026

The short version

Who we are

Flurry is an iPhone app for keeping your loyalty cards in one place. It's made by Harry Drabwell, an individual developer in the United Kingdom, who is the "controller" of your information under UK data protection law (the UK GDPR and the Data Protection Act 2018).

Questions, requests or complaints: hdrabwell@getflurry.co.uk.

Using Flurry without an account

You don't need an account. Without one, your cards, stamp cards, photos and settings stay on your phone and nothing about them is sent to us. The only things that leave your phone are described under What happens with or without an account.

If you create an account

An account lets you back up your cards, use them on your other devices, and share a card with someone. When you have one, we store:

WhatWhy
Your email addressTo sign you in. We email you a one-time code instead of using a password.
Your first nameTo greet you in the app, and to show people you share a card with who it's from.
Your cards, encryptedTo back them up and sync them. Each card (its name, number, balance, stamps and history) is encrypted on your phone with a key that only your devices hold, before it's uploaded. We store scrambled data that we can't read. Photos of paper stamp cards aren't uploaded.
Your devicesTo show you which devices are signed in and let you sign them out: a random ID made by the app, the device type and iOS version (e.g. "iPhone · iOS 18.1"), the app version, and when each was first and last active.
A security logSo you can spot anything unusual: the type of event (for example "signed in", "recovery key viewed", "app lock turned on"), which of your devices it happened on, and when.

Your encryption key and recovery key

The key that encrypts your cards is kept in your Apple Keychain and syncs to your other Apple devices through iCloud Keychain, which Apple encrypts end to end. We never receive it. The app can show you a recovery key to save somewhere safe; without it or one of your devices, we can't recover your cards, because we can't read them.

Sharing a card

If you share a card with someone (for example, so a partner can collect your points), we store:

If you're the person a card is shared with: the person who shared it can see the name you enter and is told when you add, use, screenshot or remove their card. The app tells you this before you add it.

Stopping a share removes the card from the other person's app the next time it checks with our server. It can't undo a photo they may have taken of the code.

What happens with or without an account

Your location

If you turn on "Spot nearby shops" or arrival alerts, Flurry uses your location on your phone to work out whether you're at one of your shops. Your location is never sent to us. To find branches of your shops, the app searches Apple Maps, which means Apple receives the area being searched. Apple's handling is covered by Apple's privacy policy. You can turn location off at any time in the app or in iOS Settings.

Shop logos

To show shops' logos, your phone downloads each shop's icon directly from that shop's website, then keeps a copy. Like any website visit, the shop's server sees your phone's internet address. Nothing about you or your cards is sent, and no cookies are used.

Barcode format reports (off unless you turn them on)

If you switch on "Help improve Flurry", scanning a card for a shop in our list sends us the shop, the type of barcode, how long the number is, and its first few characters (at most 6, and never more than half the number), so Flurry can learn each shop's format. This never includes your full card number and isn't linked to you or your account.

"Didn't scan?" reports

If you report that a card didn't scan, we receive the shop (or, for a shop you added yourself, the name you gave it), what went wrong, the type of code and the app version. It isn't linked to you or your account. Please don't put personal details in a shop's name.

The list of shops that don't work

The app downloads a public list of shops whose cards can't work in Flurry. This sends nothing about you.

Notifications

Arrival alerts and sharing alerts are created on your phone. We don't use a push notification service.

Testing with TestFlight

If you're testing Flurry through Apple's TestFlight, Apple may share crash reports and any feedback or screenshots you choose to send with us, along with your device type. See Apple's privacy policy and the TestFlight app for details.

What we don't do

Our legal reasons for using your information

Who helps us run Flurry

These companies process information for us under contracts that require them to keep it secure and use it only to provide their service to us:

CompanyWhat they doWhere
SupabaseHosts our database and sign-in systemLondon, UK (on Amazon Web Services)
ResendSends sign-in code emails, so it receives your email addressUnited States
CloudflareRuns our website and domainGlobal network
AppleApp distribution, TestFlight, Apple Maps searches, iCloud KeychainGlobal

Where information is handled outside the UK, we rely on the protections the law requires, such as the UK's International Data Transfer Addendum to the EU Standard Contractual Clauses, or the UK–US "data bridge".

How long we keep it

Keeping it safe

No system is perfectly secure. If we ever discover a breach that puts your information at risk, we'll tell you and the Information Commissioner's Office as the law requires.

Your rights

You have the right to:

Email hdrabwell@getflurry.co.uk and we'll reply within one month. If you're unhappy with how we've handled your information, you can complain to the Information Commissioner's Office at ico.org.uk.

Children

Flurry isn't meant for children under 13, and we don't knowingly create accounts for them. If you think a child under 13 has an account, contact us and we'll delete it.

Changes to this policy

If we change how Flurry uses your information, we'll update this page and the date at the top. For significant changes, we'll also tell you in the app before they take effect.