Privacy policy
The data we process, why, for how long, and your rights.
Last updated: 20 September 2026
This English version is a translation provided for information only. Only the French version is legally binding.
In three sentences. We collect what is needed to operate your account and your page. We do not sell, rent out or exchange any data; no advertising, no advertising trackers. Your payment details never pass through our servers.
1. Who is responsible
The data controller is ONLINE NC, whose contact details are given in the legal notice. For any question about your data, contact: contact@qrazy.link
2. Which legal framework applies
Our company is established outside the European Union. The EU GDPR and the French Data Protection Act (known as the “Informatique et Libertés” Act) therefore do not automatically apply to our processing: their scope depends on the legislation itself, and on each user's situation.
Our position, and we stand by it: rather than wait for a definitive answer, we voluntarily apply the protective principles of the GDPR — collecting only what is necessary, for a specific purpose, for a limited period, with a right of access and deletion — as a quality standard, without prejudging whether they are mandatory in our case.
Any complaint relating to your data may be addressed to us directly, using the contact details above, without prejudice to the rights you have under the law of your country of residence. The courts designated in our general terms and conditions retain jurisdiction.
3. The data we process
3.1 Your customer data
| Data | Status |
|---|---|
| Display name | Mandatory |
| First name and surname | Optional |
| Email address | Mandatory — it is your login identifier |
| Password | Mandatory — stored hashed, we cannot read it |
| Profile photo | Optional |
| Two-factor authentication secret and backup codes | Optional — encrypted at rest |
| Country | Inferred from your IP address when you log in — the country only, never the city. Used to suggest a currency and to determine where the account is based. |
| Stripe customer ID | Created when you place your first order |
| Subscription history and invoices | Mandatory — management and accounting |
| Newsletter subscription | Optional — the date of your consent and the exact wording you agreed to, kept as proof of that consent |
What we do not hold: no card number, no expiry date, no security code. This information is entered directly with Stripe and never passes through our servers.
3.2 What you publish
Title, description, avatar, links, social networks, phone number, contact card, catalogue, images, and the address entered in a Map block.
This content is public by nature. Anyone who has the QR code or the page's web address can view and copy it; it may be indexed by search engines. Only publish what you are willing to make public, and only publish a third party's number or address with their permission.
3.3 Visitors to your page
We measure how pages are used, but we do not create any visitor account and do not seek to identify anyone. Here is everything an event contains, with nothing left out:
| Data | Example |
|---|---|
| The type of event | scan, page view, click on a block |
| The page concerned | the page's identifier |
| The date and time | — |
| The block clicked, where applicable | “call button” |
| The referring site | the address of the site the visitor came from, when their browser provides it |
| The type of device | computer, mobile or tablet — nothing more specific |
| The country | “NC” (New Caledonia), “FR” (France) — the country only, never the city or region |
No IP address is recorded, and the technical identification sent by the browser is not kept: it is used only, at the time of the visit, to determine whether the device is a computer, a mobile or a tablet, and is then discarded.
The country is determined in the same way: our server infers it from the visitor's IP address at the time of the request, using a database installed on the machine. This inference never leaves the server — no external service is queried, and the IP address itself is neither read by the site nor stored. Only the country code is kept, which is not enough either to locate a person or to recognise them from one visit to the next.
In practice: no visitor profile, no advertising identifier, no tracking from one page to another, and nothing that would allow two visits to be linked together. The customer sees numbers — “142 scans this month”, “37 clicks on the Phone button” — never who scanned.
The server's technical logs — kept for security and troubleshooting purposes, and separate from the events above — are retained for twelve months.
3.4 What we do not do — on the pages your visitors see
On the public pages your visitors scan:
- No selling, renting out or exchanging of data with third parties.
- No advertising on the pages.
- No advertising network or advertising tracker placed on our initiative.
- No third-party audience measurement, no profiling of your visitors, no automated decision-making.
3.5 On our own pages — audience measurement, with your consent
Sections 3.3 and 3.4 describe our customers' public pages, where no audience tracker is present. On our own pages — home page, pricing, sign-up, customer area, admin area — we use, with your consent, Google Analytics (traffic statistics) and Microsoft Clarity (recording of browsing sessions, for debugging).
These tools place their own cookies and send data to Google (United States) and to Microsoft. Nothing is loaded until you have given your consent in the banner provided for this purpose; you may refuse, and you can change your choice at any time. These tools are never present on our customers' public pages. Details are given in the cookie policy.
3.6 Messages sent through a contact form
Some pages carry a contact form. What the visitor writes in it — their name, email address, phone number if given, the subject and the message — is emailed to the customer who owns the page and kept by us: that is what allows a lost message to be sent again, and a failed delivery to be noticed.
The sender's IP address is not kept here either. Against automated submissions we use two means that retain nothing: a limit on the number of messages per page and per visitor, and a captcha (see 5.1). These messages are deleted along with the page that received them.
4. Why, and for how long
| Purpose | Retention period |
|---|---|
| Creating and managing your account, logging you in | For the entire duration of the subscription |
| Publishing and serving your page | For the entire duration of the subscription, then three years after expiry (to allow for a possible reactivation); once that period has elapsed, the page is deleted, after two email reminders |
| Securing access — two-factor authentication, logs | Twelve months |
| Invoicing and collecting payment | Ten years (accounting obligation) |
| Account after non-renewal | Your expired pages are deleted three years after their expiry date; your account remains accessible and can be deleted at any time at your request |
| Statistics on scans, views and clicks — including country | Kept visit by visit (date, device type, country, referring site), without any data identifying a visitor, until the page is deleted |
| Sending you our newsletter — only if you asked for it | Until you unsubscribe, in one click from your account or from the link at the bottom of every email; proof of your consent is then kept for three years, so that it can be shown it was indeed given |
| Passing on to the customer the messages received through their page's contact form | Until the page that received them is deleted |
| Correspondence with support | Three years |
5. Who has access to your data
5.1 Our service providers
- Hosting provider — Cloudways (États-Unis): hosts the application, the database and the public pages.
- Stripe — online payment. When you place your first order, it receives your display name, your email address and the handle of the page ordered — the latter so that your invoices show which page they relate to. Your payment details are entered directly with Stripe and never pass through our servers. Stripe is an international provider: the data may be processed in countries other than the one in which we are established.
- Email delivery provider — Elastic Email (États-Unis): delivers the service's emails (confirmations, notifications, password resets).
- OneSignal — delivery of our newsletter, and only if you are subscribed to it. It is then sent your email address, your language and your account identifier with us. OneSignal is an international provider: the data is processed in the United States. Unsubscribing removes you from its mailings.
- Google (reCAPTCHA) — protection of forms against automated submissions, at sign-up and on the contact forms of pages. The service analyses the browser's behaviour to tell a person from a program, and receives the visitor's IP address in the process. Data processed in the United States.
- Google (sign-in) — only if you choose to link your Google account in order to log in without a password. We then receive your email address and your name; we ask for nothing else, and the link can be removed from your account.
- Google (Analytics) and Microsoft (Clarity) — audience measurement on our own pages only, and only if you consent (see section 3.5). Data processed in the United States. Never present on customers' public pages.
5.2 Third-party services called from public pages
These are not our processors but independent third parties, called only when a customer adds the corresponding block. This content is displayed with the page — it is part of it — but visitors can refuse it using the icon at the bottom of the page. This refusal is enforced by our servers: the blocks concerned are then replaced by a placeholder and no request is sent to these services. The table below therefore describes what happens for a visitor who has not refused.
| Service | When | What happens |
|---|---|---|
| Google Maps | Map block | The browser connects to maps.google.com, which receives its IP address. Google is an advertising network: its trackers are also used for audience measurement and advertising |
| Nominatim / OpenStreetMap | Address search by customers | Queried from our servers to help our customers locate their address. The visitor's browser never contacts it |
| TikTok | TikTok block | The TikTok script places its own trackers |
| Spotify | Spotify block | The player places its own trackers |
| YouTube | Video block | Loaded in “nocookie” mode, which limits cookies without eliminating them |
| Vimeo, Facebook | Video block | Depending on the address pasted by the customer; they place their own trackers |
| Variable | HTML code block | Depends entirely on the code inserted by the customer, over which we have no control |
We have no control over what these companies collect once they have been contacted — hence the option, offered to every visitor, of refusing to let them be contacted. See the cookie policy.
5.3 Authorities
We may be required to disclose certain data in response to a lawful request from a competent authority. In that case, we strictly limit ourselves to what is requested.
6. Security
- Passwords are hashed — never stored in plain text, and not readable by us.
- Optional two-factor authentication, whose secret and backup codes are encrypted at rest.
- An anti-CSRF token protecting the actions performed from your account.
- Transmission over HTTPS.
- Regular backups, stored outside the web root.
No system is infallible. In the event of a breach likely to cause you harm, we will inform you without undue delay and tell you what steps to take.
7. Your rights
You have the right of access, the right to rectification, the right to erasure, the right to object, the right to restriction of processing and the right to data portability in respect of the data concerning you, as well as the right to withdraw your consent where it is the basis for processing.
To exercise these rights, write to contact@qrazy.link. We may ask for proof of identity where there is reasonable doubt. We will reply within a reasonable time, in principle within one month — including a copy of your data, if you request one.
As regards visitors: as we only record aggregated events, with no account or identifier, we are generally unable to retrieve the data of any particular visitor — there is nothing to retrieve.
8. Changes
This policy evolves with the service: opening of online payment, addition of a block that calls on a third-party service, change of provider. The date of the latest update appears at the top, and customers are informed by email of any significant change.