BTC Cycle CockpitBTC Cycle Cockpit

Privacy Policy

Effective: October 26, 2026

Privacy · Web · iOS · iPadOS · Android
This Privacy Policy applies to BTC Cycle Cockpit on the website and in the mobile apps for iOS, iPadOS and Android. It provides the information required by Articles 13 and 14 GDPR about the categories and sources of personal data, purposes, legal bases, recipients, international transfers, retention and your rights. Storage of, and access to, information on an end device is additionally governed by applicable ePrivacy rules, including the German TDDDG where applicable.

Important: research model, not investment advice

BTC Cycle Cockpit processes market and research data for general analysis. It does not create a personal financial or portfolio profile or make investment decisions for you. Full research and risk information is available under Risk & Methodology.

Read the full Risk & Methodology notice →

Controller

Chingo LabsChingo Labs

Inhaber: Tobias Leluschko

c/o IP-Management #11513

Ludwig-Erhard-Straße 18

20459 Hamburg

Deutschland

contact@chingolabs.com

Scope and data minimisation

We process data for service delivery, sign-in, access rights, security, billing and support. We also keep anonymous daily request totals. Account-linked statistics about visible cards and active time spent on the website and in the apps are optional and off by default. BTC Cycle Cockpit does not access contacts, photos, microphone, camera or precise location and does not use advertising SDKs. Functions are provided without additional identification wherever possible.

Sources of personal data

We receive personal data directly from you when you register, sign in, edit a profile, subscribe, send feedback or request support. Other data arise technically when you use the service, particularly session, security, log and usage data. Authentication providers, payment providers and app stores transmit the information needed for identity, payment and entitlement. Market, macro, technical and on-chain data come from public or licensed sources and are not linked to your account unless an account-specific feature expressly states otherwise.

Accounts, sign-in and entitlements

When you register or sign in, we process in particular your email address, internal user ID, optional display name, provider and identity references, authentication and session information, MFA metadata where applicable, and your assigned Free/Pro entitlement. Passwords are handled by Supabase Auth and are not stored by BTC Cycle Cockpit in plain text. If you expressly choose GitHub sign-in or account linking, the identity and account information required for that process is exchanged between GitHub, Supabase and BTC Cycle Cockpit. An optional display name or nickname is a private account label for you and authorised administrators, is not a sign-in identifier, does not affect permissions and is not currently displayed publicly. If chat or comments are introduced, public name use will be explained before you choose to use that function. The legal basis is Article 6(1)(b) GDPR, supplemented by Article 6(1)(f) GDPR for security and abuse prevention.

Local settings, cookies and device storage

Required HttpOnly cookies bcc_sb_access, bcc_sb_refresh and bcc_sb_expires maintain web sign-in; refresh and expiry cookies last no more than 30 days, and the access token lasts until its expiry. Language and theme preferences may be stored for up to one year. Short-lived OAuth/PKCE and entitlement hints protect sign-in and access. Local Storage, Session Storage and local caches retain requested preferences, navigation, cockpit state and learning progress. Native apps keep sign-in credentials in protected operating-system storage; other preferences and learning caches use local app storage. Strictly necessary access for an expressly requested function relies on section 25(2)(2) TDDDG where applicable. Optional usage analysis on the website and in the apps begins only after express consent under section 25(1) TDDDG; random session identifiers are created only afterwards and held only in memory. Anonymous request counting uses no additional device storage. There are no advertising cookies or tracking across other providers’ websites or apps.

Anonymous daily request totals

On the server, we count web document requests and permitted GET requests for mobile app startup configuration. Only the UTC calendar day, source (web or mobile startup configuration) and a total count are stored. These totals contain no user, account, session, device or network identifier, IP address, user-agent or precise event timestamps. They require no additional cookies or device identifiers. They provide a broad view of request volume and remain for 90 days with daily cleanup. Counts represent requests; repeat requests, technical retries and automated traffic may be included. They therefore represent neither unique visitors nor unique app opens. Required processing of incoming server requests is described in the hosting section.

Optional statistics about cards and active time spent

Only if you expressly enable optional usage statistics in the menu do we record your internal user ID, random pseudonymous session identifier, start and last activity, visible card or broad cockpit section, active time spent and view counts. We measure visible time after opening, resuming or recently interacting; timing pauses after 90 seconds without interaction and in the background. This does not measure whether content was actually read. Statistics serve product improvement and operational analysis. Authorised administrators can associate these data with your account, email address and optional private display name. The legal basis is Article 6(1)(a) GDPR. Consent applies across the website and apps for your account, is off by default and can be withdrawn in the menu at any time. The service remains available without consent. Withdrawal stops collection on this device immediately. Once saved successfully, the server rejects further analytics and deletes previous personal usage statistics. Other open devices check the choice on their next contact with the statistics function. Later consent covers only new usage and does not restore deleted statistics. Your current decision, its timestamp and notice version are stored as evidence of your choice. There is no screen recording, mouse-path tracking or storage of input contents. Necessary security logs and anonymous daily request totals remain independent.

Knowledge check, learning progress and daily poll

For the requested knowledge check, we store question or learning content, difficulty, correctness, answer time, daily rounds and compact learning progress. This supports progress, repetition and daily limits. The optional daily poll stores the answer, date and a pseudonymous value generated on the server with a secret key. The poll table contains no email address, user ID or IP address; a separate server-only mapping enables deletion of your votes when you delete your account. Only aggregate votes are displayed. Public comments, chat contributions and public user profiles are disabled. The legal bases are Article 6(1)(b) GDPR for the requested learning function and Article 6(1)(f) GDPR for reliable polls and protection against duplicate votes.

Contact, feedback and diagnostics

If you send feedback or a support request, we process the selected category and area, message content, optional email address, locale, Free/Pro status, relevant page, data status, app version, case reference, time received and the technically transmitted user agent. Processing is used to handle the request and, where needed, investigate errors; the legal basis is Article 6(1)(b) or (f) GDPR depending on the request. Do not submit passwords, payment details or authentication tokens.

Subscriptions and payments

Web subscriptions are processed through Stripe. Stripe receives payment and transaction data needed for payment, invoicing, authentication and fraud prevention and acts as a processor or an independent controller depending on the processing. We store customer, subscription, product, event, status and term references, not full card details. Native in-app subscriptions currently use Apple StoreKit; we receive product, transaction and status information to verify entitlements. Android in-app purchases are currently unavailable. The legal bases are Article 6(1)(b) GDPR and Article 6(1)(c) GDPR for required records.

Market, macro and on-chain data

BTC Cycle Cockpit obtains market, macro, technical, institutional and on-chain information from external data sources. These data are used for display, calculation, quality assurance and calibration of research models. Provider requests are generally made server-side. Data providers ordinarily receive no user ID, email address, payment details or personal financial information; technically unavoidable server connection data may arise at the relevant provider.

Hosting and delivery by Vercel

The website, web app, APIs and parts of mobile backend communication are delivered through Vercel. This may involve IP address, date and time, requested URL and route, referrer where transmitted, HTTP status, request ID, device/browser information, user agent, error and security events, and technically required headers. The purposes are delivery, operation, troubleshooting, scaling and attack prevention. The legal bases are Article 6(1)(b) and (f) GDPR; the legitimate interest is secure and available delivery. Optional usage-statistics content is processed only on the basis of your specific consent.

Abuse prevention with Upstash

We use Upstash, Inc. to protect sign-in and APIs. The server derives a purpose-specific cryptographic value from the IP address or internal user ID; the original IP address or user ID is not sent to the rate-limit service. Upstash processes that pseudonymous key, request count and expiry, plus technical server-connection data. Keys expire with the respective limit window, no later than 24 hours. The legal basis is Article 6(1)(f) GDPR and our interest in service availability and protection against automated attacks.

Authentication and database through Supabase

Supabase is used for authentication, sessions, profiles, entitlements and the server-side database. The connected project is hosted in the EU West region (Ireland). Depending on use, data include email address, user and identity ID, password hash within the authentication service, session and refresh tokens, MFA and OAuth metadata, profile, entitlement and subscription references, account-specific snapshots, and usage and security data. Depending on a table’s purpose, access is restricted through server-side keys, database roles, permissions and Row Level Security. The legal basis depends on the function: Article 6(1)(b) or (f) GDPR; optional usage statistics rely exclusively on consent under Article 6(1)(a).

Email delivery and support mailbox

Resend (Plus Five Five, Inc., United States) delivers contact, security and account-deletion messages. It processes sender and recipient addresses, subject, content, delivery status and delivery logs. Support messages to contact@chingolabs.com are delivered to the controller’s Gmail mailbox at Google. Google therefore also receives content and communication metadata; its own privacy terms apply to the consumer Gmail service. Processing serves inquiry handling and necessary account communication, under Article 6(1)(b) or (f) GDPR depending on the message. Resend retains email and delivery-log data for 30 days on its standard plans; correspondence in the support mailbox is separate.

Apple App Store, TestFlight and Google Play

When you install the app, use TestFlight, make an in-app purchase or subscribe, Apple or Google processes data under its own responsibility, particularly store account, device, diagnostic, transaction and payment information. BTC Cycle Cockpit receives only information needed for distribution, troubleshooting, and entitlement verification and assignment. The relevant store provider’s privacy notice additionally applies to that independent processing.

Service providers and recipients

Recipients are authorised internal personnel, Vercel for hosting, Supabase for authentication and database, Upstash for abuse prevention, Resend for email delivery and Google for the Gmail support mailbox. Stripe processes web payments; Apple and Google process store activity as independent controllers. GitHub receives identity data only when GitHub sign-in or linking is expressly selected. Processing on our behalf is governed by the respective Article 28 GDPR agreements; independent processing by payment, store, GitHub and Gmail providers is additionally governed by their privacy notices. Authorities and courts receive data where legally required or for legal proceedings. No data are shared for third-party advertising.

Purposes and legal bases

Article 6(1)(b) GDPR applies to accounts, sign-in, entitlements, requested learning functions, subscriptions, payments and contractual support. Point (c) applies to statutory retention and evidence duties. Point (f) applies to secure delivery, troubleshooting, technical logs, abuse prevention and reliable daily polls; legitimate interests are availability, integrity and protection against attacks and duplicate votes. Additional personal usage statistics on the website and in the apps rely exclusively on consent under point (a). Consent can be withdrawn at any time for the future without affecting other use of the service. Anonymous daily totals contain no personal records; required processing of the underlying server requests follows the hosting section.

Requirement to provide data

An email address and authentication data are contractually required for registration, sign-in and account functions. Without them, an account cannot be provided; publicly accessible research functions remain available without an account where offered. Optional feedback details are voluntary, while message content is required to handle a request. Payment data is required only for a paid subscription.

No automated individual decisions

We do not make decisions based solely on automated processing within the meaning of Article 22 GDPR that produce legal effects concerning you or similarly significantly affect you. The research models analyse market data and do not make decisions about individuals.

Processing outside the EU/EEA

The Supabase database is in Ireland. Supabase also identifies Singapore and the United States for support and subprocessor access, covered by EU Standard Contractual Clauses in its DPA. Vercel, Resend and Upstash are US providers whose published DPAs include EU Standard Contractual Clauses. Resend stores delivery data in the United States even when an EU sending region is selected. Google/Gmail, Stripe, Apple and GitHub may also process data in the United States. The EU-US adequacy decision applies to certified US recipients only within the scope of their valid certification; otherwise appropriate safeguards are required. Provider notices, subprocessor lists and contractual sources are linked below. Copies of safeguards applicable to the actual contractual relationship can be requested through the contact address.

Server logs, security and abuse prevention

For account management and abuse prevention, authorised administrators can see account creation, last sign-in and the count of successful sign-ins in the last 30 days. This count uses existing authentication audit logs; it does not record card visits or time spent. Unavailable audit data are not presented as actual sign-ins. For secure and reliable operation we process technically necessary log data, particularly IP address or network identifier, timestamp, route, HTTP status, request ID, user agent, error, authentication, rate-limit and security information. Security events may be emailed to a designated recipient for attack detection. The legal basis is Article 6(1)(f) GDPR. The data are not used for advertising or personal market profiles.

No advertising and no sale of personal data

BTC Cycle Cockpit does not sell or rent personal data. Personal data is not shared with advertising networks and we do not track users across third-party apps and websites for advertising or profiling. If these practices were ever to change, this policy would be updated before such processing and any legally required consent would be obtained.

Retention

Account profile, authentication identity, entitlements and the current privacy preference remain until account deletion. Anonymous daily request totals are cleaned up daily after 90 calendar days. Detailed quiz answers, completed rounds and pseudonymous daily polls are automatically deleted after 120 days on the server; cleanup runs daily. Local daily details are removed after 120 days at the next use and on account deletion. Compact learning progress remains until account deletion. Optional session records are removed 30 days from session start and daily aggregates after 30 calendar days in the daily cleanup; withdrawal deletes the account-linked usage records. Expired rate-limit records are removed by the next daily cleanup; Upstash keys expire automatically with the respective limit window. Resend retains email and delivery-log data for 30 days on standard plans. Vercel runtime logs accessible to us remain available for at most 30 days depending on plan; Supabase Pro diagnostic logs normally last 7 days and standard daily backups 7 days. Separate authentication audit records in the database are cleaned up daily after 30 days. Completed support correspondence without pending follow-up is intended to be deleted within 90 days of the last substantive handling, except for legal retention and specific disputes. Our accounting records subject to statutory retention normally remain for 8 years, and commercial or business correspondence for 6 years, from the end of the relevant calendar year. Tax or legal proceedings may extend statutory periods. Necessary exceptions are purpose-limited and access-restricted. Backups are used only for recovery; deletions must be reapplied after restoration.

Withdrawal, account deletion and deletion requests

Account settings provide directly accessible account deletion. It removes the authentication identity, profiles, entitlements, personal startup state, snapshots, learning progress, attributable daily poll responses, privacy preference and usage data. Local personal learning and history storage is cleared on the device performing deletion; copies on other devices may remain until sign-out there or manual deletion of website/app data. Local daily details also follow the 120-day period above. Server-side account deletion is independent of this. A linked Stripe web customer is deleted and an active web subscription ended; legally required payment records may remain with Stripe. Apple subscriptions must also be cancelled in store settings but do not prevent account deletion. Support correspondence, backups and legally required records follow the periods and exceptions above. Further deletion requests can be sent by email.

Your privacy rights and right to complain

Under Articles 15 to 21 GDPR, you have rights of access, rectification, erasure, restriction, data portability and objection. You may withdraw consent at any time for the future without affecting the lawfulness of earlier processing. Under Article 77 GDPR, you may also complain to a data-protection authority. Requests can be sent to the controller; reasonable identity verification may be required to prevent unauthorised disclosure. Requests are generally answered within one month.

Specific notice of the right to object

Where we process personal data under Article 6(1)(f) GDPR, you may object at any time on grounds relating to your particular situation. We will then cease that processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or the processing is required to establish, exercise or defend legal claims. You could object to direct marketing at any time without giving specific grounds; BTC Cycle Cockpit currently conducts no personalised direct marketing.

Data-protection authorities and complaints

Under Article 77 GDPR, you may contact a supervisory authority, particularly in the country of your habitual residence, workplace or the alleged infringement. One contact is the Hamburg Commissioner for Data Protection and Freedom of Information, Ludwig-Erhard-Straße 22, 20459 Hamburg, Germany, datenschutz-hamburg.de.

Data security

We use risk-appropriate technical and organisational measures, including TLS-encrypted transport, HttpOnly/Secure cookies, protected device storage, server-side secrets, role- and user-based access controls, Row Level Security, input and origin checks, rate limits, logging, backups and controlled account deletion. Measures are reviewed and adapted to the state of the art. No internet-based service can guarantee absolute security. A personal-data breach requiring notification will be reported and communicated under Articles 33 and 34 GDPR.

Changes to this Privacy Policy

This Privacy Policy will be updated when functions, providers, legal requirements or data-processing practices materially change. The current version remains available at btccyclecockpit.com/privacy and btccyclecockpit.com/datenschutz. Material changes will also be highlighted within the service where required.

Provider privacy notices and contractual sources

These links lead to the providers’ published terms, including their own processing and subprocessors. Contact us for information about our specific contractual documents.

  • Vercel · DPA
  • Supabase · DPA
  • Supabase · Data residency & transfers
  • Upstash · DPA
  • Resend · DPA
  • Resend · Security & retention
  • Google · Privacy
  • Stripe · Privacy
  • Apple · Privacy
  • GitHub · Privacy
Back to CockpitRisk & MethodologyLegal Notice