Privacy policy

Last updated: 22 October 2026

Starting point

Flexdger Wallet is built so that your content does not need to reach us. The mockup is drawn wholly inside your browser.

The data behind each part of the service

• Account. We hold your email address and a password, and Supabase, our authentication provider, stores both. The password is kept hashed, so we can never read it. You need the pair to open your wallet and to get your access back when you sign in from another device. Suppose you create your account within 24 hours of opening an affiliate's link: the affiliate's code and the moment you opened the link are then stored with your account. The reason is that a purchase you make inside those 24 hours, from a different browser or device, can still be credited to that affiliate. Nothing else is done with these two items. If you pick Continue with Google, Google vouches for your email address in place of a code and passes us that address, your name and the link to your profile picture. Your email address goes to your account. We make no use of the name or the picture, and your Google password never comes anywhere near us.
• Purchase. Stripe, our payment provider, processes your email address and your billing details. On our side we retain your email and the transaction id, which lets us tie your access to your account and honour a refund. A payment through Whop works differently, and Whop, not Stripe, handles it. That covers lifetime access paid in crypto, and the backup checkout we may offer after a card payment is declined (for the monthly plan or lifetime access). To Whop we send your email address, your account id and, when you arrived through an affiliate link, that affiliate's code. In return Whop gives us the amount paid, the transaction id, and your Whop account's email address, user id and username. We look at that email only when the purchase does not already arrive with your address from our side, and then for two purposes: attaching the purchase to your account, and making sure the affiliate code in use is not yours. The user id and username end up in our logs alone, and only if nothing else identifies you, so that the purchase can be attached manually. The card, or the crypto wallet, that you pay with stays with Whop, and we never ask you for it. After a declined card payment we may send a single email to your account's address, about an hour later. For every declined card payment, a note goes into your account: the reason for the decline, whether we emailed you about it, and whether you paid in the end.
• Licence. It records the plan, the date it was created and, for a plan that ends, the expiry date. It hangs on your account, so there is no key to send and no code to type.
• Wallet configuration. This is written to two places: your browser's local storage, and your account at Supabase, so that the wallet can reopen on another device. It contains what you assembled: tokens, amounts, the account name, colours, plus any avatar or token icon you uploaded, which sits inside the configuration as image data.
• Audience measurement. Daily counters, covered in full in the section after this one.
• Session recordings. They run on some public pages and for visitors outside Europe only, through Microsoft Clarity. The "Session recordings" section below gives the whole picture.
• Price testing. This means the price group your browser was assigned to, a random identifier for that browser, and what you went on to do on the site. The "Price testing" section below gives the whole picture.
• Payment options test. It stores whether your browser and your account are shown the option of paying for lifetime access in crypto. See the "Payment options test" section below.

We do not process a demonstration wallet, so it is missing from the list above. Visit /demo and the wallet you build there, plus a tally of your edits, sit in your browser's local storage and in no other place. We receive none of it, it belongs to no account, and we cannot read it. On that page, where session recordings are active (see below), the wallet is masked inside your browser before any data leaves, so its content stays on your device that way too. Should you open an account later in the same browser, the wallet moves into it one time and the local copy is erased.

The free tools are outside the list as well. The quantities you enter in /tools/crypto-portfolio-calculator are saved in your browser's local storage, so they are waiting next time, and are saved nowhere else. Like all pages, it sends the anonymous counts described under Audience measurement below. Beyond those, it makes one request only, for public market prices, identical for every visitor and carrying no quantity. Press Clear and the quantities are deleted. Its "See it as a wallet on your phone" button copies your SOL, ETH, BTC, HYPE and USDC quantities into the demonstration wallet described above, within the same browser. In /tools/screenshot-size-calculator, your browser itself reads the screenshot you test, looking at its first bytes to find the size and format; nothing is uploaded. In /tools/if-it-hits-calculator and /tools/meme-coin-calculator, the numbers you enter remain in your browser and are never transmitted. To display live prices and supply, your browser contacts CoinGecko (api.coingecko.com) on its own for public market data. CoinGecko therefore sees that request and your IP address, as any website would when you load it, but the request holds nothing you typed.

Audience measurement

We count how the site gets read, since we need to choose what to write next. Below is the complete inventory of what a page transmits; nothing outside it is sent:

• The path of the page you are viewing (/blog, /login), without any query string and without anything after #.
• The domain of the site that sent you (google.com, reddit.com), or the word direct. The complete address of that page is excluded: a search query or a private thread does not belong in our statistics.
• A screen shape, one of three: mobile, tablet or desktop. We infer it from your window's size and ignore your browser's user agent.
• Your country, as a two-letter code (us, fr). Our host derives it from the request, and the IP address itself is not retained.
• Which button you clicked, taken from a fixed list of buttons defined in our code. A name outside that list is discarded.
• Your scroll depth, rounded to one of four marks: 25%, 50%, 75%, 100%.

We also count a visit once for each browsing session, and a visitor once for each browser each day. To avoid counting you twice, your browser holds two small values: a flag that lives while the tab stays open, and the current date. Everyone visiting today gets the same date, so it identifies no one, and it never leaves your device.

No cookie is set by these counters, and no identifier is kept. They record no IP address, and nothing in them can trail you to another site. The Microsoft Clarity cookies covered under "Session recordings" below are set only for visitors outside Europe. Apart from them, the single cookie on this site is the price-testing one explained in the "Price testing" section, which is a separate matter from these counters.

The counters stay out of the wallet itself and out of these legal pages. Price testing, explained below, does run there.

Affiliate links. If an affiliate's link (flexdger.com/r/…) brought you here, that affiliate's counter rises by one, no more than once a day for each browser. We keep alongside it, for each affiliate and each day, totals of the same kind as above: the platform you arrived 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 they open a link, so in that case we read the platform from the name the app gives its built-in browser, and store that platform name alone. On their dashboard the affiliate gets these totals and nothing besides: no address, no identifier, and nothing that reveals who clicked.

Prefer not to be counted at all? Open flexdger.com/?mesure=off a single time in this browser. That sets a flag which switches off every measurement on the site, on every page and session recordings included, until you open /?mesure=on. The flag remains on your device and we never receive it. A browser that blocks local storage cannot save the flag. In that case the address keeps ?mesure=off, which has the same effect for as long as it remains in the address bar.

On top of this, Vercel Web Analytics also counts page views. Its script is delivered from this domain, sets no cookie and builds no profile. Where the measurement above skips certain pages, this one runs on every page, wallet and legal pages included, and it logs the path where it was loaded. Your wallet lives at flexdger.com/your-name, so that address is the path it sees.

Session recordings

Microsoft Clarity helps us watch how some public pages get used: where visitors click, how deep they scroll and where they pause, through behavioural metrics, heatmaps and session replay. The aim is to spot what confuses people so we can fix it.

• Pages concerned. It runs 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 final pages, before anything is sent, your browser masks your email address, the sign-in and sign-up forms, the 6-digit code and the messages about your account. The card form belongs to Stripe and is never recorded. A page whose address holds a sign-in link or a one-time token is not recorded in any way. It does not run in your wallet, on the password reset page, in the clip library, on the affiliate pages, on the page displayed after a payment, on the free tools, or on these legal pages.
• Visitors concerned. If your device's time zone is in the European Economic Area, the United Kingdom or Switzerland, it does not load at all. For visits from those countries, Microsoft further holds back its cookies unless consent was given.
• Content recorded. Mouse movements, taps, clicks, scrolling and the page as it appears, along with technical details like screen size, browser and approximate location. Whatever you type into a form field is masked in your browser and never transmitted. On the demo, the wallet you assemble gets the same masking.
• Price group. Each recording carries the label of the price group your browser belongs to (see "Price testing"), which lets us compare how each group reads the pricing.
• Cookies. Clarity places two cookies on this domain: _clck, which holds one visitor id across visits, and _clsk, which stitches the pages of a single visit into one recording. Microsoft also places cookies on its own domains (CLID, MUID and related ones), and uses them as well for its own analytics and advertising.
• Retention. We can access recordings for 30 days from the moment they are made.

Microsoft handles this data in line with the Microsoft Privacy Statement. To switch it off in your browser, open flexdger.com/?mesure=off once, as explained earlier. Blocking cookies does not suffice by itself: Clarity keeps recording and merely loses the ability to join your pages into one visit.

Price testing

New customers take part in our price tests. On your first visit, your browser is drawn at random into one price group and remains in it, so the prices shown in that browser stay the same from one visit to the next. After you have an account and sign in, your account's prices show on every device. A different browser, an app's built-in browser, a private window, or a browser with cleared site data starts without that record. Where such a browser connects over the same network as one already placed in a group (your home Wi-Fi, say), it joins that group, which is why your devices at home show identical prices. On another network it may show different prices until you sign in. Groups are drawn at random, with one exception: a browser or an account that knew our prices before the test keeps them. Nothing else about you, your device or your location plays any part in choosing your group.

These items are stored to keep your prices steady:

• a cookie called flx_ab, set by our server, which holds your price group, a random identifier made for this browser, and the date it was made. It lasts up to 400 days;
• those same three values in your browser's local storage, together with your account's identifier once signed 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 latest visit;
• your price group, written onto your account when you create it, so every device where you are signed in shows the same prices;
• 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 the network portion of an IPv6 one), never the address itself, along with the price group first seen on that network and a count of the new browsers seen there. It is erased 30 days after the last visit from that network. A network on which many new browsers show up, like an office or a mobile carrier, is no longer used in this way;
• a cookie called flx_ab_r, lasting 15 minutes, which our server sets on the first page of a browser with no group yet, and which contains the group of its network.

Using that identifier, we log the following for this browser: the first page you opened, the domain of the site you came from, your screen shape, the type of browser (for example "Instagram's built-in browser"), your country as a two-letter code, the affiliate link you came through if there was one, the days you return, and steps from a fixed list: 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 happens on every page of the site, wallet included (logged as /app, never under your wallet's own address) and these legal pages included. Once you create an account, the records are linked to it. We use them for one purpose only, comparing price groups and choosing our prices. They are never shared, never sold, and never used to follow you onto another site.

Our legitimate interest in setting prices (Article 6(1)(f) GDPR) is the legal basis. Records not linked to an account are erased twelve months after the test finishes. Records linked to an account stay with it, and those linked to a payment stay with the billing records. You may object whenever you like by writing to contact@flexdger.com: we erase your records and retain only what we need to show you consistent prices. If you open flexdger.com/?mesure=off, these records stop for that browser: it is no longer registered, its network goes unnoted, and none of its steps are logged. The cookie that keeps your prices steady stays in place, and a checkout begun from your account is still logged against that account.

Payment options test

A second experiment checks whether the offer to pay for lifetime access in crypto changes what people buy. One half of browsers sees the crypto option (the "Card or crypto" label, the "Pay with crypto" button and the lines that mention it), while the other half sees it nowhere on the site. Prices do not differ between the halves. A browser's half derives from the random identifier explained under "Price testing", so a given browser always stays in the same half; nothing about you, your device or your location decides it. At sign-in, the version you saw first is saved on your account as a single character, and from then on every device where you are signed in shows you that version. Your browser holds the same character in its local storage, next to your account's identifier. To compare the halves we use the steps already logged for the price test and gather nothing else for it, and the legal basis and your right to object are those of the price test.

Payment form

The card form, Apple Pay and Google Pay on the payment screen come from Stripe, loaded from js.stripe.com within this page. Whatever you type there goes directly to Stripe, so your card number never reaches us. As a fraud-prevention measure, Stripe gathers information about your device and your visit, cookies and IP address among it, under its own privacy policy. It is not loaded on any other page of the site.

Things we do not do

• We run no advertising trackers, and no analytics that build a profile of you or trail you between sites.
• We do not sell data, nor share it for commercial ends.
• We never ask for a private key, a seed phrase or a wallet address, because the service has no use for them and never will.

How long we keep data

Licence data stays as long as the subscription is active, and for one year after cancellation, so that we can restore access if you return. Your wallet configuration stays with your account for the same length of time, and deleting your account deletes it. Accounting rules require us to keep billing records for ten years.

The notes on declined card payments stay with your account, and deleting the account deletes them.

An account created within 24 hours of opening an affiliate's link keeps that affiliate's code and the time of the opening. Deleting the account deletes both.

Records from price testing follow the rules in "Price testing" above.

We keep no copy at all of a demonstration wallet composed on /demo. It lives only in the browser that composed it, until it is carried into an account, that browser's data is cleared, or seven days go by. We hold nothing from which to restore it.

What you can ask of us

You are entitled to access, rectification, erasure and portability of your data. Send your request to contact@flexdger.com, from the address you used when you purchased. A complaint can also be lodged with the French data protection authority (CNIL).

Videos on the socials page and in some articles

Videos from our own YouTube channel appear on the socials page and in a few blog articles. Until you tap one, YouTube is asked for nothing: the image you see comes from this domain. Tapping a clip brings in YouTube's player. From then on YouTube receives your request and may set its own cookies, under its own policy. The address we use is youtube-nocookie.com, the strictest option they provide. Before you tap, no page of this site contacts them.

Third parties that process data

• Stripe: takes care of payments.
• Whop: handles crypto payments for lifetime access, and the backup card checkout for the monthly plan and lifetime access (it receives your email address and account id; it returns the amount, the transaction id, the state of a monthly plan, and your Whop account's email address, user id and username).
• Supabase: stores accounts, licences and wallet configurations, audience counters and price-testing records.
• Resend: delivers our emails (account confirmation, password reset, and the one-time email about a declined payment).
• Vercel: provides hosting.
• Microsoft (Clarity): session recordings and heatmaps, on certain public pages, for visitors outside Europe only.
• YouTube (Google): plays videos on the socials page and in some blog articles, only once you tap a video.
• Google: handles sign-in, solely if you choose Continue with Google.