Privacy notice

Controller

Privacy contact: [email protected]. You can also write to the postal address above. See the legal notice for editorial responsibility.

Page delivery and security

This edition uses Cloudflare Pages, provided through Cloudflare, Inc. When you request HTML, an image, a font or a script, the hosting infrastructure receives connection information such as your IP address, the requested resource, request time, browser and protocol details. This information supports delivery, fault diagnosis and protection against abuse.

For this essential operation, our basis is Article 6(1)(f) GDPR: the legitimate interest in an accessible and secure publication. The connection information is necessary to deliver the requested resource. We do not run a separate visitor-log database in the website application.

Cloudflare’s Self-Serve Subscription Agreement incorporates its Data Processing Addendum. For customer logs and content processed on our behalf, Cloudflare acts as a processor. Its privacy policy also describes network information it handles under its own responsibility.

International processing

Cloudflare operates internationally. Processing may occur outside the European Economic Area, including in the United States. Its addendum describes the EU–US Data Privacy Framework where applicable and standard contractual clauses for restricted transfers. The subprocessor list identifies service providers and locations; it does not mean that every listed provider receives each visitor’s information. You can request information about the safeguards applicable to your data through the publisher’s contact.

Signing in to the protected preview

This section applies only when you use the separate, restricted testing preview. Cloudflare Access processes the sign-in email address, authentication result, IP address and technical request data to verify access and protect the preview. This is separate from reader registration: the magazine offers no reader account.

Access uses authentication and security cookies, including CF_Authorization. Cookie lifetimes depend on the configured session and cookie type; a cookie's expiry is separate from the retention of a login log. See Cloudflare's Access cookie documentation. We rely on Article 6(1)(f) GDPR for access protection. Necessary device storage for this requested sign-in is covered by Section 25(2)(2) TDDDG. Optional analytics would require a separate choice.

Search and device storage

The archive filters a downloaded index in your browser; there is no separate search-company request. The search term is also written into the page address as a query parameter. Reloading, opening or sharing that address sends the query with the page request to the host, and same-site navigation may include it in referrer information. Your browser history may retain it. Avoid entering sensitive information in search. Downloading the index is itself a normal hosting request.

This edition does not load Google Analytics or create advertising cookies, analytics cookies or visitor identifiers. Its inactive preference control does not save a choice on your device. Fonts, images, styles and scripts are delivered with the site. The preview authentication cookies described above are a separate hosting feature. Following an ordinary external link opens a different provider's service under its own privacy information.

Visitor measurement is not active

A separate Google Analytics 4 property and local measurement controls have been prepared for BitByteDaily. The Google tag is not loaded by this edition. Preparing these controls does not send page views, searches or tool actions to Google Analytics. The Analytics preferences control shows the current status.

Any later activation requires an updated notice, verified processing arrangements and a separate release decision. No analytics consent is requested by the current edition.

Market tools and asset requests

The Bitcoin page and other coin pages request a reference price and sampled price history when you choose Load price and history. The coin finder sends your submitted search to this site. Listed names and symbols are matched against a shared provider directory; contract searches use the provider's token index. Selecting a listed identity requests its provider profile. These requests are separate from reading an article.

The crypto price converter sends the ticker, token name or contract address you enter to this site only when you choose Search assets. Hosting functions fetch the requested provider data from CoinMarketCap using a server-side key. Choosing Load rates and convert sends the selected asset identities to this site for a price request. The browser performs the calculation locally and does not contact CoinMarketCap or Kraken directly. Avoid entering personal or confidential information in an asset search.

Tool availability is shown when you request data. Without available reference prices, the converter shows no estimate. Request limits protect the shared service; reaching a limit does not trigger an automatic purchase or an automatic retry.

Asset-search results and profiles have a configured shared-cache lifetime of 60 minutes; quote entries and sampled history have a lifetime of 5 minutes. Search-cache keys may contain the submitted asset search; price-cache keys contain asset identities and the chosen period. These are cache expiry settings, not guaranteed deletion periods for hosting logs or the provider's records. Our budget database stores aggregate request counters, without a visitor identifier. We rely on Article 6(1)(f) GDPR to provide requested lookups efficiently and protect the service against excessive requests.

Messages to the publisher

A mail link opens your own email application; the website does not send the message. If you choose to write, your reply address, message, optional name and attachments are processed to handle the enquiry. Supply only what is needed to explain the issue. Never send recovery words, private keys, passwords or identity documents.

Ordinary editorial correspondence is handled under Article 6(1)(f) GDPR, based on our interest in responding to readers and correcting content. Article 6(1)(c) applies where processing is required to fulfil a legal obligation, such as an applicable data-rights request. Contract-related correspondence is assessed under Article 6(1)(b) where relevant.

The mailbox at [email protected] uses Migadu-Mail GmbH, Switzerland. Migadu processes correspondence on our behalf. Its Privacy Policy and Data Processing Agreement describes its processing arrangements, subprocessors and deletion safeguards. Switzerland has an EU adequacy decision; international processing by a subprocessor is subject to the applicable transfer safeguards. A mail link does not give the website access to your email account.

Retention and recipients

Delivery and security data are processed by the hosting provider and its applicable subprocessors for delivery, abuse prevention and troubleshooting. Their retention depends on the service and security purpose. We do not export a separate permanent copy of visitor logs. You can contact us to ask about the records relevant to a specific request.

We keep correspondence while an enquiry, correction or rights request is being handled. Once it is resolved, the remaining messages and attachments are reviewed and removed when no longer needed. Further retention is limited to an applicable statutory duty or a specific legal claim; those records are kept for the relevant duty or claim. This is a purpose-based review, not a blanket retention period for every email. Deletion from a working mailbox does not necessarily remove a provider backup immediately; backup copies follow the provider's recovery and deletion cycle.

Your choices and rights

Depending on the applicable conditions, you may request access, correction, deletion, restriction or portability. Where processing relies on consent, you may withdraw it for the future. Where we rely on legitimate interests, you may object for reasons relating to your situation; applicable exceptions for overriding grounds or legal claims remain. This version does not conduct direct marketing or automated decisions with legal or similarly significant effects.

You are not required to send an enquiry or disclose optional message details. Without enough information to locate the matter and reply, we may be unable to handle it. Technical connection data is necessary for delivery; refusing it prevents the requested connection. We do not sell your correspondence or use it for mailing lists.

Use the contact above for requests; postal requests are also possible. You may complain to a competent supervisory authority, including the Bavarian State Office for Data Protection Supervision. The GDPR sets out the conditions and scope of these rights.

About this edition · Return to the archive