GodzillaBTC logoGodzillaBTC

Privacy & Cookies

How the terminal handles local notes, service requests, analytics, advertising and optional memberships.

Maintained by Fahad Farid · Updated 13 October 2026

Who maintains this site

GodzillaBTC is maintained by Fahad Farid. Use the contact page for privacy questions, corrections or a request about information you have sent to us.

Local watchlists and notes

The trade workspace saves watchlists, per-market notes and the Quick View preference in your browser's local storage. That feature does not upload those values to our server. They are not encrypted or synced. Anyone with access to this browser profile may be able to read them. Use Clear Saved Workspace to remove the stored values, or delete this site's storage in your browser. Downloaded trade plans remain on your device until you delete them separately.

Requests and embedded services

Loading pages and market endpoints sends normal network information, including your IP address and browser request headers, to the hosting service. Cloudflare hosts the site. Embedded TradingView charts and Google services may receive network information when loaded and apply their own policies. Server-side market providers supply quotes and calendar data. The public paper-signal ledger contains model publications and outcomes; it is not a record of your personal broker trades.

Analytics

Existing pages use Google Analytics. This package sets analytics and advertising storage to denied by default before the Google tag runs. Consent Mode can still send cookieless measurements; it does not mean no network data is transmitted. The site does not provide a cross-device personal trading journal; optional memberships manage delivery preferences only.

Advertising

The site is prepared for Google AdSense. A publisher verification tag or ads.txt entry does not mean advertising is approved or active. If Google ads are enabled, Google and its partners may use cookies or similar technologies to serve, personalize and measure ads, subject to your consent choices where required. Before serving ads to visitors in the EEA, UK or Switzerland, the publisher must configure a Google-certified consent platform. A local preference switch or this policy is not a substitute.

Read how Google uses information from partner sites, Google's privacy policy, TradingView's privacy policy and Cloudflare's privacy policy. Ad personalization controls are available through Google My Ad Center.

Contact and retention

If you contact us, the information you choose to send is used to respond and maintain correspondence. Do not include passwords, private trading credentials or unnecessary financial information. Local workspace data remains until you clear it or the browser removes it. Hosting, analytics and third-party retention follow the relevant service settings and policies; this page does not promise a retention period that has not been verified.

Updates

We will revise this notice when the implemented data practices change. The date above identifies this version.

Verified manual payment records

After independently verifying a transfer, the owner records the member ID, selected plan, actual credited amount and currency, payment method, transaction reference, receipt date and paid-through date. These records are restricted to the owner and used for reconciliation and preventing duplicate activation. Do not send passwords, private keys or wallet seed phrases.

Optional memberships

When membership signup opens, we store email, consent time, hashed member key, plan, payment-provider reference and expiry. Connecting Telegram stores your chat ID. Delivery records store event, status and retry count. Card details are handled by the approved payment provider, never this site. Turnstile checks signup abuse; Resend sends opted-in alerts; Telegram delivers linked-bot messages. These providers receive information needed for their function. You can stop email or unlink Telegram in the member area without cancelling billing; cancel recurring payments separately in the billing portal. Contact support to request access or deletion. Necessary billing records may need retention.

Private Pro workspace

Members may save a journal, plans, watchlist, notes and alert filters to their member-owned workspace. Access requires the member key; keys are hashed on the server. Cloud data is used to provide the workspace and filter requested notifications. It is not publicly listed and is not end-to-end encrypted. The owner can access server-stored data for operation and support. Never store passwords or API secrets. Demo mode keeps work in the tab only. Expired members retain read/export access; contact support for deletion. Export JSON or CSV from the workspace.

Username and password accounts

We store a normalized username, salted and peppered password hash, hashed recovery code and hashed seven-day session tokens. Passwords and recovery codes are not stored as plain text. A necessary Secure, HttpOnly, SameSite session cookie keeps you signed in. Hashed request limits help prevent repeated login attempts; raw IP addresses are not stored in the login rate-limit table. Password resets revoke existing sessions and legacy access keys. Your paid-through date determines which live markets you can access. Completed paper results remain public.