Privacy notice
The short version
Nothing you do with the chart leaves your browser. Market data passes through our relay on its way to you and is never recorded there, and no market data is ever tied to a person. We do publish market-wide liquidation, open interest and funding figures on a free page, but those describe the market, not anybody in it. What we hold about you is an account record, a subscription record, page view counts — and, if you asked to hear from us by email, that address and the record of the consent.
A few things measure how the site is used. Cloudflare Web Analytics counts page views without cookies and without identifying anyone, and it runs for every visitor. Google Analytics is the one that needs your agreement, and it stays switched off until you give it — from the bar that appears on your first visit, or later from Cookie settings in the footer of any page. Declining changes nothing about how the product works. Our own server also counts the pages it delivers, with no cookie and nothing running in your browser, and keeps only hourly totals that cannot tell one visitor from another.
Who is responsible
Sven Güttner, Walter-Hohmann-Str. 19, 45128 Essen, Germany, is the controller for the processing described here. Questions, and any of the requests under Your rights below, go to [email protected].
What is collected
- Account. Email address and authentication metadata, held by Clerk, plus an internal user id in our database.
- Subscription. Stripe customer and subscription identifiers, plan, status and period end. Card details are held by Stripe and never reach this app.
- Saved workspaces. Layout settings you choose to store server side, attached to your user id.
- Support messages. What you write in the contact form, the reply address you give, and the plan you were on, kept as the record of the correspondence.
- Cancellations. If you cancel from Verträge hier kündigen: the name and contract reference you enter, the type of termination, any grounds you give, and the time your declaration arrived. We have to be able to prove that it arrived and that we confirmed it, so this is kept as evidence rather than as a convenience.
- Usage measurement. Which pages are opened, roughly where in the world from, how quickly they render, and which sections of a page were on screen and for how long. Described in full in the next section.
- Contact consent. If you ask on the homepage to hear from us by email: the address, the wording you saw when you asked, the page you asked on, when you asked and when you confirmed — or withdrew — from the link in the mail. Until the confirmation link is followed, the address is a request and not a consent, and nothing further is sent.
- Operational logs. Standard request logs at the edge and on our server, including IP address and user agent, retained for a short period for security and debugging.
Measurement
Two tags, and no others. Both measure. There is no remarketing, no audience built out of you and sold on, no data broker, and no third party that receives anything about you in order to sell you something of its own.
- Cloudflare Web Analytics reports page views and page speed per hostname. It sets no cookies, writes nothing to your device, reads nothing from it, and builds no identifier that could follow you between sessions or between sites. Because nothing is stored on or read from your equipment, it does not require consent under s25 TDDDG, and it runs on our legitimate interest in knowing whether the site works (Art 6(1)(f) GDPR). You can stop it with any content blocker; nothing on the site depends on it.
- Page counts on our own server (Zählwerk) tell us how often each page is opened, how people find the site (a search engine, a site linking to us, one of our campaigns, an AI assistant) and which pages search engines and AI crawlers read. Nothing runs in your browser for this and nothing is stored on or read from your device: no cookie, no script, no pixel. Only what your browser sends anyway when it asks our server for a whole page is used — not images, scripts or the data the app loads afterwards, and moving around inside the app once it is open is not counted at all. For each page our server passes to Zählwerk, a statistics service we run ourselves: the page address without its query string, except campaign tags such as
utm_source; whether it carried an advertising click id (the fact, never the id); the response status; the site you came from, reduced to its domain; your browser's user agent; your first preferred language; and your IP address, shortened before it leaves our server — the last of its four numbers removed for IPv4 (203.0.113.57 becomes 203.0.113.0), everything after the first 48 bits for IPv6. The full address is passed on only for a request that declares itself a crawler of Google, Microsoft (Bing) or OpenAI, so it can be checked against the ranges they publish. Zählwerk derives a country (from the shortened address, with DB-IP's database on our own server), a device type, a browser and system family and a language, adds one to a counter for that hour — "page /pricing, from google.com, Germany, mobile, Safari: one more" — and discards the rest. It keeps no IP address, no user agent, no identifier and no record of a single visit, so nobody is recognised on a later page or visit and nothing is tied to an account. Separately, our server adds one to a counter in Zählwerk when certain steps happen on it: an account is created, the terminal opens a market or refuses one the plan does not include (with the plan and the exchange), a checkout is started, a trial starts, a subscription is paid for, cancelled or ends (with the plan and the billing interval), a support message is sent (with its topic), or an email consent is confirmed. These counts carry no account, address or identifier, so nothing in them can tie two steps to the same person. It runs on our legitimate interest in knowing how much the site is used and how people find it (Art 6(1)(f) GDPR); because nothing touches your device, s25 TDDDG does not apply. If your browser sends Global Privacy Control, its page views are not counted; you can also object by writing to [email protected]. Because nothing is kept that relates to you, there is nothing we could later look up, hand over or delete (Art 11 GDPR). - Google Analytics 4 counts page views per route. It sets its own cookies, assigns your browser a random identifier, and processes data on Google's infrastructure including in the United States. It runs only on your consent (Art 6(1)(a) GDPR, and s25(1) TDDDG for the cookies), which you give and withdraw on the consent bar. Google Consent Mode is set to deny everything by default, and the advertising signals — ad storage, ad user data and ad personalisation — are denied permanently and never granted, as are Google Signals and ad personalisation in the property itself. So the property measures pages; it cannot be used to advertise to you.
- The attention beacons report, per section of a page, how long it was on screen and how far down the page was read. They set no cookie, write nothing to your device, and carry no identifier: one row is a page path, a section name, a duration or a depth, and two rows cannot be proven to have come from the same visit. Like the Cloudflare measurement above, they run on our legitimate interest in knowing whether the site holds attention (Art 6(1)(f) GDPR); any content blocker stops them, and nothing on the site depends on them.
Withdrawing consent takes effect at once: no further events are sent, and the Google cookies we set are deleted from your browser. The Google library that has already loaded into the open page cannot be unloaded from it, so it stays in memory, idle, until you reload — and is not loaded at all on any later visit. Clarity is told the answer has changed as well, and its contract for that is the one that ends the session, deletes its cookies and stops recording until consent returns.
Cookies and local storage
The complete list, with what sets each one and how long it lasts.
| Name | Set by | Purpose | Lasts |
|---|---|---|---|
__session, __client_uat | Clerk | Keeps you signed in, and tells the app whether a session exists before it asks Clerk. Strictly necessary: without them there is no signed in terminal. | Session token, short lived and refreshed while you are signed in |
_ga, _ga_G2M26YBCGL | Google Analytics | A random browser identifier and the session state behind the page view count. Set only after you consent, and deleted when you withdraw. | Up to 2 years, or until withdrawal |
sonartape.consent.v2 | This site (local storage) | Your answer to the consent bar, so it is not asked again. Strictly necessary — it is the record of the choice itself. | 12 months, then asked again |
depth.* | This site (local storage) | Your exchange and symbol, toolbar and colour settings, panel sizes, alert rules, last seen price, and whether you have seen the walkthrough. Never sent anywhere. | Until you clear your browser storage |
__stripe_mid, __stripe_sid | Stripe | Fraud prevention during checkout and in the billing portal. Set on Stripe's own pages, which is where payment happens; they are not set by this site. | Set by Stripe, up to 1 year |
No cookie on this list is used for advertising, profiling or cross-site tracking, and the Cloudflare measurement and the attention beacons described above use no cookie at all.
What stays in your browser
Toolbar settings, the selected exchange and symbol, the last seen price and the sensitivity you chose are kept in local storage on your device. The order book, the prints and everything derived from them live in memory in the tab and are discarded when you close it.
Market data reaches your browser through our relay, so the exchange sees the relay's connection rather than your IP address, and the relay sees which exchange and symbol you subscribe to. The relay holds one upstream connection per exchange and market while terminals are open, and records none of what passes through it.
Separately from the relay, and not connected to it, a collector of ours subscribes to the public liquidation feeds of several exchanges and records market-wide totals — how much was liquidated, in which minute, on which exchange, and on which side — along with open interest and funding rates. That is what the free liquidations page is built from. It runs on a schedule of its own rather than in response to anybody, it is tied to no session and no account, and it records nothing about what any visitor looked at. Nothing in it is personal data, and it would hold exactly the same figures if nobody ever opened this site.
Legal bases
- Performing the contract (Art 6(1)(b) GDPR) — the account, the subscription, the saved workspaces and the session cookie that holds the whole thing together.
- Consent (Art 6(1)(a) GDPR, s25(1) TDDDG) — Google Analytics, each asked separately, and the contact consent for email, all of it opt in and nothing else.
- Legitimate interest (Art 6(1)(f) GDPR) — cookieless page view and page speed measurement, the page counts on our own server, the aggregate attention beacons (which sections were read and for how long, carrying no identifier), edge request logs, and keeping the service secure and available.
- Legal obligation (Art 6(1)(c) GDPR) — the invoice trail tax and accounting law requires us to keep.
Processors
- Cloudflare. The network in front of the site — DNS, encryption, edge caching and protection against attacks — and the cookieless page view measurement.
- Railway. Hosting of our server: the website, the API and the database. Zählwerk, the page counter described under Measurement, runs there too, in Railway's EU region (the Netherlands).
- Resend. The email sending that carries the confirmations and acknowledgements.
- Clerk. Authentication and the account record.
- Stripe. Payment, invoicing and the billing portal.
- Google. Google Analytics 4, on your consent only.
Transfers outside the EEA
Clerk, Stripe, Cloudflare and Google are US headquartered, and processing can reach the United States. Those transfers rest on the European Commission's adequacy decision for the EU–US Data Privacy Framework where the recipient is certified under it, and on the standard contractual clauses otherwise. In the case of Google Analytics the transfer is additionally covered by the consent you give, and declining it means no data about you goes to Google at all. Railway and Resend are US headquartered as well, and processing by them can reach the United States; those transfers rest on the standard contractual clauses in their data processing agreements.
Retention
Account and subscription records are kept while the account exists, and afterwards only where tax or accounting law requires an invoice trail. Saved workspaces are deleted with the account. Support messages are kept as long as the correspondence is live and then for as long as a related claim could be brought, and a cancellation record for as long as the contract it ended could be disputed. Google Analytics data expires on the retention period set in the property, at most 14 months. Clarity keeps what it records for the retention period set in the project. The attention beacons are kept for 30 days, then deleted. Zählwerk's hourly page counts are deleted after 25 months. A contact consent is kept for as long as the consent could still be in dispute — three years from the last request about that address — then deleted with it.
Your rights
You can ask for a copy of your data, correction of it, restriction or erasure, or the transfer of it to someone else. You can object to processing that rests on our legitimate interest, and you can withdraw consent at any time — for the analytics consent, from Cookie settings in the footer, with no need to write to anyone. Withdrawal does not affect what was lawful before it. The email consent can be withdrawn with the unsubscribe link in any mail, or by writing to [email protected]. Write to [email protected] for anything else and it will be handled within the period the applicable law sets, which is one month under the GDPR.
You also have the right to complain to a supervisory authority. For us that is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, and you may equally approach the authority where you live.
Contact
Sven Güttner, [email protected]. See also the terms of service and the imprint.