Privacy Policy
This policy is based on the behavior identifiable in the supplied static artifact. It must be updated if production adds accounts, payments, analytics, marketing, AI, support tooling or other processors.
01 Controller
The controller is , . Contact: . The applicable supervisory authority is .
02 Data we may process
The reviewed landing page does not contain an account form, payment form, newsletter form, analytics tag, cookie banner, localStorage/sessionStorage usage or database code. If these exist elsewhere in production, this policy must be expanded.
- Technical request data: IP address, browser/device metadata, timestamps and server logs may be processed by hosting and network providers when a page is requested.
- Market-data requests: the page requests public 24-hour ticker data from Binance. The browser may disclose network metadata to that provider; no user account or trading journal data was observed in the request.
- Contact data: selecting the partner-program link opens a mailto address. Any information voluntarily included in that email is processed to respond.
- Potential product data: account, authentication, subscription, billing, journal, settings, support, affiliate, API or AI data is not implemented in the inspected artifact and must not be claimed as active here without verification.
03 Purposes and legal bases
Technical data may be processed to deliver pages, maintain security, diagnose errors and comply with legal obligations. Depending on the confirmed provider and jurisdiction, the legal basis may be performance of a contract, legitimate interests or legal obligation. Non-essential analytics, advertising, affiliate tracking or similar technologies require an appropriate consent mechanism where applicable.
04 Recipients and services
Identifiable third parties in the supplied artifact are:
- Google Fonts: font stylesheets are requested from Google’s domains.
- Font Awesome CDN: the page loads the Font Awesome stylesheet from cdnjs.cloudflare.com.
- Binance public API: the live ticker script requests public market data from api.binance.com.
- Affiliate script reference: /js/affiliate-tracking.js is referenced, but the file was not present in the inspected workspace; its behavior must be verified before launch.
No Stripe, authentication provider, hosting provider, newsletter provider, analytics vendor, advertising pixel, AI provider or payment processor was detected in the supplied artifact. Do not add those names until their actual implementation is audited.
05 Retention
The inspected static page provides no application retention schedule. Hosting/server logs and email communications may be retained according to the finalized provider contracts and legal obligations. Insert specific periods or criteria after the production architecture is confirmed.
06 Your rights
Where applicable, you may have rights of access, rectification, erasure, restriction, data portability, objection and withdrawal of consent. You may also lodge a complaint with a competent supervisory authority. Requests should be sent to ; identity verification may be required to protect against unauthorized disclosure.
07 International transfers
Google, Cloudflare/cdnjs and Binance may process information from infrastructure located in jurisdictions outside your country. The transfer mechanisms and supplementary measures must be confirmed against the final vendor configuration and applicable law.
08 Security
Reasonable technical and organizational measures should be applied to protect personal data. The static artifact alone does not establish production security controls, encryption, access controls, monitoring, incident response or deletion workflows. These must be documented after implementation.
10 Privacy settings
Necessary technical delivery cannot be disabled through this panel. The current artifact does not activate analytics or advertising technologies. Your preference is stored locally in this browser to remember your choice.