Privacy policy
Last updated: 14 November 2026
Where your wallet lives
Larp Cards is built so that it can run without ever collecting what you create. You draw the wallet in the page, and whatever you place in it is kept solely in your browser.
The cards you design stay on your device. Your browser writes issuer names, cardholder names, the last four digits, balances and transactions into its own storage, so they are waiting for you when you return. Nothing is uploaded, nothing reaches us, and we have no way to read any of it. Your account does not hold them either: on a second device you draw the cards again, or you import a setup file yourself.
Data we handle
- Licence: your plan, the date it was created and, if the plan expires, its expiry date. It hangs off your account, so there is no key to send and nothing to type in.
- Account: an email address and a password, both held by Supabase, our authentication provider. The password is stored hashed and we never see it. They are needed to open the full version and to restore your access when you sign in on another device. If you create your account within 24 hours of opening an affiliate's link, that affiliate's code and the moment you opened the link are kept with your account, so that a purchase made within those 24 hours from a different browser or device is still credited to that affiliate. They serve no other purpose. If you pick Continue with Google, Google vouches for your email address in place of a code and passes us your email address, your name and a link to your profile picture. The email address becomes your account's; the name and the picture go unused, and your Google password never comes near us.
- Purchase: Stripe, our payment provider, processes your email address and billing details. We keep your email and the transaction id, to tie your access to your account and to honour a refund. Larp Cards is published and run by Larpea, which takes the payment: the name on your bank or card statement is Larpea's. Your card details go directly to Stripe and we never see them. When a bank declines a card payment, we may send one email to your account's address roughly an hour later. For every declined card payment we record, with your account, why it was declined, whether we emailed you, and whether you paid afterwards.
- Wallet settings: stored in your browser only, and they never reach us. That covers the clock on the status bar, the payment screen and the categories. Your cards, balances and transactions are held by your browser in the same manner and are never uploaded.
- Price testing: the price group your browser was placed in, a random identifier for this browser, and what you do on this site from then on. See the section "Price testing" below.
- Session recordings: made on certain public pages through Microsoft Clarity, for visitors outside Europe only. See the section "Session recordings" below.
- Audience measurement: counters kept per day, set out in full in the next section.
The contents of your wallet are missing from that list on purpose: we do not process them. The cards you design, the transactions you type and the settings you choose live in your browser's storage and nowhere else. We receive none of it, no account is linked to it, and we cannot read it. On public pages where session recordings run (see below), your browser masks the phone screen before anything is sent, so its content does not leave your device by that route either. Clearing your browser's site data erases it all, and we cannot get it back for you.
We serve the card library; we do not collect from it. Once you own the library, each design is fetched from our content delivery network through a link made for you and valid for a few minutes. What we keep is what you bought, never what you looked at.
Audience measurement
We count how the site is read, because we need to decide what to write next. The list below is everything a page sends. Nothing else leaves it:
- The path of the page you are on (
/blog,/login), never the query string and never what follows#. - The domain you came from (
google.com,reddit.com), or the word direct, but never the complete address of that page: a search query or a private thread has no place in our statistics. - One of three screen shapes: mobile, tablet or desktop. It comes from the size of your window, not from your browser's user agent.
- The country of your connection, as a two-letter code
(
us,fr). Our host derives it from the request, and the IP address itself is not kept. - Which button you clicked, out of a fixed list. That list is written into our code, and any name not on it is discarded.
- Scroll depth, rounded to one of four marks: 25%, 50%, 75%, 100%.
All six go into counters kept per day: how many views a page had, how many visits came from a domain. Nothing is stored per person. Two readers of the same page on the same day cannot be told apart once their visits are recorded, by us or by anyone else. No record exists to trace back.
We also count a visit once per browsing session and a visitor once per browser per day. To avoid counting you twice, your browser holds two small values: a flag that lasts while the tab stays open, and today's date. That date is the same for everybody visiting today, so it identifies nobody, and it never leaves your device.
Where these counters are concerned, no cookie is set and no identifier is kept, no IP address is recorded, and nothing can follow you to another site. The only cookies this site sets are the Microsoft Clarity ones described under "Session recordings" below (visitors outside Europe only) and the price-testing cookie described under "Price testing", which has nothing to do with these counters.
The counters are absent from the app itself and from these legal pages. Price testing, covered below, is not.
Affiliate links. If you arrive through an affiliate's link
(mylarpcards.com/r/…), that affiliate's counters rise by one,
at most once a day for each browser. We keep alongside it, per affiliate and per
day, the same sort of totals: the platform you came from (TikTok, YouTube,
Google, other or direct), your country as a two-letter code,
and your screen shape. Apps such as Instagram or TikTok usually conceal where a
visitor came from; when a link opens inside one, the platform is read from the
name the app gives its built-in browser, and only that platform name is kept. On
their dashboard the affiliate sees these totals and nothing beyond them: no
address, no identifier, nothing to show who clicked.
Prefer not to be counted at all? Open
mylarpcards.com/?mesure=off once in this browser. It
sets a flag that halts every measurement on the site, session recordings
included, on every page, until you open /?mesure=on. The flag stays
on your device and is never sent to us. If your browser blocks local storage, the
flag cannot be saved; the address then keeps ?mesure=off, which does
the same job for as long as it stays in the address bar.
Apart from all this, Vercel Web Analytics also counts page views. Its script comes from this domain, sets no cookie and builds no profile. Unlike the measurement above, it runs on every page, the app and these legal pages included, and records the path of the page it was loaded on.
Session recordings
On some of our public pages we use Microsoft Clarity to watch how they get used: where visitors click, how far they scroll and where they hesitate, by way of behavioural metrics, heatmaps and session replay. The aim is to spot what confuses people and fix it.
Where and for whom
Pages. Recordings run on the home page, About, Contact, the demo, the download page, the socials page, the blog, the guides, the comparison pages, the examples and "for" pages, and the sign-in, sign-up and payment pages. On those last ones, your email address, the sign-in and sign-up forms, the 6-digit code and the account messages are masked in your browser before anything is sent; the card form belongs to Stripe and is never recorded; and a page whose address carries a sign-in link or a one-time token is not recorded at all. Recordings do not run in the app, on the password reset page, in the card library, on the affiliate pages, on the page shown after a payment, or on these legal pages.
Visitors. Clarity is not loaded at all when your device is set to a time zone of the European Economic Area, the United Kingdom or Switzerland. Microsoft also holds back its cookies from visits coming from those countries unless consent has been given.
What is kept
- Captured: mouse movements, taps, clicks, scrolling and the page as displayed, with technical details such as screen size, browser and approximate location. Whatever you type into a form field is masked in your browser and never sent. On any page showing the phone screen, the cards on it are masked in the same way.
- Retention: we can access a recording for 30 days after it is made.
- Price group: every recording carries a label with the price group your browser was placed in (see "Price testing"), which lets us compare how each group reads the pricing.
- Cookies: on this domain Clarity sets
_clck(which keeps one visitor id across visits) and_clsk(which groups the pages of a single visit into one recording). Microsoft sets further cookies on its own domains (CLID,MUIDand related ones), which it also uses for its own analytics and advertising purposes.
Microsoft handles this data under the Microsoft Privacy Statement. To switch it off in your browser, open mylarpcards.com/?mesure=off once, as explained above. Blocking cookies is not enough by itself: Clarity still records, it just cannot join your pages into one visit.
Price testing
How the group is chosen
We run price tests on new customers. On your first visit, your browser is put at random into a single price group and stays there, so the prices you see in that browser hold steady from one visit to the next. After you have an account and sign in, you get your account's prices on every device. A different browser, an app's built-in browser, a private window, or a browser whose site data was cleared begins without that record. If it connects through the same network as a browser already placed in a group (the same home Wi-Fi, for instance), it joins that group, so your devices at home show the same prices; on another network it may show other prices until you sign in. The group is drawn at random. The single exception is a browser or an account that already knew our prices before the test began: it keeps them. Beyond that, nothing about you, your device or your location has any say in your group.
What we store to keep prices stable
- A cookie named
mlw_ab, set by our server. It holds your price group, a random identifier created for this browser and its creation date, and it lasts up to 400 days. - The same three values in your browser's local storage, along with your account's identifier once you sign in, a note of your first visit (the page, the domain you came from, your screen shape and the affiliate code of the link you used, if there was one) and the day of your last visit.
- Once you create an account, your price group is saved on the account, so the prices match on every device where you are signed in.
- A cookie named
mlw_ab_r, lasting 15 minutes, which our server sets on the first page seen from a browser with no group yet. It carries the group of that browser's network. - To give the other devices on your network the same prices, a one-way code computed from the network your visit came from (your public IP address, or its network part for IPv6), never the address itself. It is stored with the price group first seen on that network and a count of the new browsers seen there, and deleted 30 days after the last visit from that network. A network where many new browsers appear, such as an office or a mobile carrier, stops being used in this way.
What we record
Under that identifier, we record for this browser: the first page you opened,
the domain you came from, your screen shape, the kind of browser (for example
"Instagram's built-in browser"), your country as a two-letter code, the
affiliate link you came through, if any, the days you return, and a fixed list
of steps: seeing a price or an offer, opening the sign-up or payment screen,
clicking one of a fixed list of buttons, choosing a plan, starting a checkout,
paying. This takes place on every page of the site, the app included (logged as
/app) and these legal pages included. Once you create an account,
these records are attached to it. We use them for one thing only: comparing the
price groups to settle our prices. They are never shared, never sold, and never
used to follow you onto another site.
Legal basis, retention and objection
The legal basis is our legitimate interest in setting our prices (Article 6(1)(f) GDPR). Records not linked to an account are deleted twelve months after the test ends; those linked to an account are kept with it, and those linked to a payment are kept with the billing records. You can object whenever you like by writing to contact@mylarpcards.com: we delete your records and keep only what is needed to show you consistent prices. Opening mylarpcards.com/?mesure=off halts these records in that browser: it is no longer registered, its network is not noted, and none of its steps are recorded. The cookie that keeps your prices stable stays, and a checkout started from your account is still recorded with that account.
Payment form
Stripe supplies the card form, Apple Pay and Google Pay on the payment screen,
loading them from js.stripe.com within this page. Whatever you
type there goes directly to Stripe, and your card number never reaches us. To
guard against fraud, Stripe gathers information about your device and your
visit, cookies and your IP address among it, under
its own privacy policy.
No other page of this site loads it.
Our commitments
- We run no advertising trackers, and no analytics that profile you or trail you from one site to another.
- Your data is neither sold nor shared for commercial purposes.
- The service has no use for your camera, your microphone or your photo library, and never will, so it never touches them. A picture reaches it only when you pick the file yourself as a card background, and it stays on your device.
How long we keep data
We keep licence data while the subscription is active and for one year after cancellation, so we can restore your access should you return. We keep billing records for ten years, as accounting rules require. The notes about declined card payments stay with your account, and deleting the account deletes them. Your cards, transactions and settings are held by your browser, not by us, so there is nothing on our side to delete along with them.
Where you created your account within 24 hours of opening an affiliate's link, that affiliate's code and the time you opened the link stay with your account, and deleting the account deletes them. Price-testing records follow the rules given in "Price testing" above.
We hold none of what you type into the wallet: it exists only in the browser where you typed it, until you remove it or that browser's data is cleared. There is nothing here to restore it from.
Exercising your rights
You have rights of access, rectification, erasure and portability. To use them, write to contact@mylarpcards.com from the address you used at purchase. You may also lodge a complaint with the French data protection authority (CNIL).
Video clips on the socials page
Who processes data for us
| Vercel | hosting. |
| Supabase | account and licence storage, audience counters, and price-testing records. |
| Stripe | payment processing. |
| Resend | sending our emails (account confirmation, password reset, and the one-time email about a declined payment). |
| Bunny | delivery of the card library's files, when you own it (the link created for you, and nothing about your account). |
| sign-in, only if you choose Continue with Google. | |
| YouTube (Google) | video playback, only on the socials page and only after you tap a video. |
| Microsoft (Clarity) | session recordings and heatmaps, on some public pages and only for visitors outside Europe. |