CHRADE · PRIVACY
Privacy Policy
How personal data are handled when you visit our website or contact CHRADE.
1. Who is responsible
The controller responsible for this website is Christian Lademann, trading as CHRADE Forex, Grenzbachstrasse 4, 22177 Hamburg, Germany.
You can contact us about privacy at contactus@chradeforex.com.
2. Scope and current website
This notice explains the processing of personal data when you visit chradeforex.com or contact CHRADE through the channels linked from the website. Personal data means information relating to an identified or identifiable person.
The website is publicly accessible without a CHRADE account or ChatGPT login. It provides product information, historical performance information and browser-local configuration demonstrations. There is currently no purchase checkout, customer registration, licence activation or MT5 account authorisation on this website. We do not collect payment details or MT5 account identifiers through it.
3. Website delivery and security
When your device requests a page or asset, the hosting and security infrastructure processes technical request data. This can include your IP address, request time, requested URL and query parameters, browser and operating-system information, referrer information where transmitted, response status and security-related signals. These data are used to deliver content, detect and mitigate malicious traffic, diagnose faults and maintain availability.
The website is published through OpenAI Sites and delivered using Cloudflare Workers and Cloudflare network infrastructure. The domain and www-to-apex redirect are managed through Cloudflare. Cloudflare, Inc. is based at 101 Townsend Street, San Francisco, CA 94107, USA. The account-specific OpenAI contracting entity and contractual allocation of responsibility for website visitor data have not yet been verified. We do not claim that a particular OpenAI entity is our contracted processor.
For processing for which CHRADE is responsible, the legal basis is Article 6(1)(f) GDPR: our legitimate interests in providing a reliable public website and protecting it and its visitors against misuse. Processing is limited to what is necessary and must be balanced against visitors' rights. Where a provider acts independently as a controller, its own privacy notice and legal bases also apply.
We have not configured a website visitor database or Logpush export in the domain account. This does not mean that infrastructure providers keep no logs. Provider-specific log categories, retention settings and contractual roles are still being verified; no fixed deletion period is asserted here. See OpenAI's privacy information and Cloudflare's privacy information.
4. Cookies and information on your device
The inspected website code contains no advertising cookies, analytics tags, tracking pixels or third-party social-media embeds. It does not write its demonstration settings to local storage, session storage or a browser database.
The delivery infrastructure sets Cloudflare's __cf_bm security cookie. It supports automated-traffic detection and contains security-related information, including an encrypted bot score and, in some configurations, a session identifier. Cloudflare states that it expires after 30 minutes of continuous inactivity. It is not a CHRADE advertising identifier. Cloudflare may use additional security cookies when a challenge is presented. Their use was not established by the available passive checks; we have not verified all provider-side browser behaviour.
Strictly necessary storage or access used solely to transmit communications or provide the expressly requested service may fall within the exceptions in section 25(2) TDDDG. Any associated personal-data processing still requires a GDPR legal basis. For necessary website security processing, we rely on the interests described above, subject to a documented necessity assessment. The current inspection identified no optional CHRADE analytics or advertising technologies. Cloudflare describes this cookie as necessary for its bot-protection service; the account-specific necessity assessment and full provider-side verification remain open.
You can manage cookies through your browser. Blocking necessary security cookies may affect access. We will obtain prior consent before introducing non-essential device storage or access that requires consent. See Cloudflare's cookie documentation.
5. Interactive examples, fonts and graphics
Chart controls, risk-to-reward switches, navigation and performance accordions operate locally in the page. Their selections are not sent to a broker, EA, CHRADE API or licensing server. They are not saved after the page session by our application code.
The inspected pages use locally served styles, scripts, SVG graphics and inline illustrations. Fonts are selected from fonts available on your device; no external font service is loaded. Normal requests for these website assets are processed as described in section 3.
6. Email enquiries
Both the displayed address and the email button use a mailto link. Opening the link starts your chosen email application; it does not submit a contact form to this website. If you send us an email, we process your email address, name where provided, message, attachments and correspondence metadata to answer and handle the enquiry.
For enquiries about entering into or performing a contract with you, the legal basis is Article 6(1)(b) GDPR. For general questions, feedback or partnership correspondence, it is Article 6(1)(f) GDPR, based on our interest in communicating with people who contact us. Legally required recordkeeping is based on Article 6(1)(c) GDPR.
We use Google Workspace for contactus@chradeforex.com. Google processes email content and related metadata to provide, secure and maintain the email service. Account-specific contractual documents, the Google contracting entity, any additional forwarding and mailbox retention settings are still being verified. Google's Cloud Data Processing Addendum and subprocessor information describe its published framework; their account-specific application has not yet been confirmed. We do not use enquiry messages for unrelated marketing without an applicable legal basis. Please avoid sending unnecessary sensitive information, account credentials or licence secrets.
7. Telegram and Instagram links
Our Telegram and Instagram buttons are ordinary external links, not embedded feeds, social login or tracking pixels. Website assets do not automatically load from those services merely because you view the contact page.
If you follow a link, your device connects to Telegram or Instagram. The provider may process IP addresses, device information, account information and interactions under its own terms. The extent of that processing can depend on whether you are logged in. These services may process data outside the EEA. Their privacy notices are available at Telegram and Instagram / Meta.
If you communicate with us on a channel that supports messages or comments, we process the information visible to us to respond or manage that communication, on the same enquiry bases described in section 6. Do not post confidential information publicly. Linking to a public Telegram channel does not imply that it offers an open discussion group.
8. Recipients and international processing
Personal data may be available to authorised people handling CHRADE enquiries and to providers involved in website delivery, security and email. We may disclose necessary information where legally required or where justified to establish, exercise or defend legal claims. We do not operate a sale of website visitor data.
Where a provider processes data on our instructions, an appropriate Article 28 GDPR arrangement is required. Publicly available provider addenda alone do not establish that a particular agreement has been concluded for our account.
The infrastructure is not confirmed to be restricted to the EEA. Processing or access in the United States and other countries may occur. A lawful transfer mechanism must be identified for each relevant transfer, such as an applicable adequacy decision or Article 46 safeguards, including standard contractual clauses and supplementary measures where needed. The applicable account-specific transfer mechanisms for OpenAI Sites, Cloudflare and Google Workspace have not yet been verified. We therefore do not assert that a particular adequacy decision, certification or set of contractual clauses covers these website and email data flows. You can request information about safeguards at our privacy email address.
9. Retention and deletion
Personal data must be kept only as long as necessary for the relevant purpose, subject to applicable legal retention requirements and justified retention for legal claims. Technical request and security records are subject to the providers' applicable retention and deletion arrangements. Their exact account-specific periods have not yet been confirmed. Relevant criteria include whether records remain needed to investigate a security incident, identify recurring abuse, diagnose a delivery fault or comply with a legal preservation obligation. This is not a representation that every provider follows a fixed or identical schedule.
Enquiry correspondence is retained for handling and follow-up and removed when no longer needed, unless legal duties or an actual need to retain evidence require further retention. Retention depends on whether an enquiry is resolved, follow-up remains necessary, the correspondence forms part of an actual contract or legally required business record, or it is needed for a specific legal claim. The mailbox archive and backup settings have not yet been verified. Statutory retention applies only to records actually falling within the relevant requirement, not automatically to every enquiry.
Browser-local demonstration selections are not persistently stored by our application code. The observed security cookie expires as described in section 4.
10. Your rights
Subject to the conditions in the GDPR, you may request access to your personal data, correction, erasure, restriction of processing and data portability. Where processing is based on consent, you may withdraw it at any time without affecting the lawfulness of earlier processing.
You may object, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR. We must then stop that processing unless the applicable legal conditions permit it to continue. You can object to direct marketing at any time.
Send requests to contactus@chradeforex.com. We may request proportionate information needed to confirm identity. We generally respond within one month; where a lawful extension is necessary, we will inform you within that month. We do not require you to waive rights to use the website.
You may complain to a data protection supervisory authority, particularly in the EU member state of your habitual residence, place of work or the alleged infringement. For our establishment in Hamburg, the relevant authority is Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit, Ludwig-Erhard-Strasse 22, 20459 Hamburg, Germany.
11. Providing data and automated decisions
You do not have to provide enquiry details, but we may be unable to respond without a reply address and information relevant to your request. Technical transmission data are needed for the website to load.
CHRADE does not use this public website to make solely automated decisions about visitors that have legal or similarly significant effects. Infrastructure security services may automatically assess traffic to detect misuse; this is separate from the illustrative trading charts and from an actual EA trading account.
12. Changes to this notice
We will review this notice when the website or its data processing changes. Before customer accounts, Stripe subscriptions, licence management or MT5 authorisation are activated, we will describe their actual purposes, data categories, recipients, legal bases, safeguards and retention. These planned functions are not described here as currently operating.
Last updated: 12 October 2026. This notice reflects confirmed information and expressly identifies remaining provider-related verification gaps. It will be updated when those details are established.