Privacy

Updated October 26, 2026 · Customer accounts

Account information

The application stores your account identifier, name, email, password hash, verification/reset records, access decisions and session records. Passwords are hashed rather than stored as readable passwords. Never include passwords or payment credentials in feedback.

Preferences and device storage

Watchlists, recent assets, language, research view, tips and onboarding preferences can sync through your account. Browser storage and the installed Progressive Web App (PWA) also keep interface preferences and cached application files. Signing out clears account-scoped local state; removing the PWA does not delete the server account.

Payments

When enabled, Stripe or PayPal processes checkout and recurring billing. The application stores provider identifiers, payment/subscription status, approved price, period dates and reconciliation events. Card details are entered with the provider rather than stored in the application account store. Manual payment requests store the method, reference and administrator review result. Payment providers and banks process information under their own policies.

Human verification and external sources

Cloudflare Turnstile is used when configured to help protect account forms. Your browser contacts Cloudflare and the server validates its response. Market-data and research providers receive requests needed to retrieve evidence. Public source links can take you to independent sites. Optional services are controlled by the operator configuration.

Security and diagnostics

The application uses session cookies, request limits, authorization checks and operational diagnostics. Hosting, mail, verification and payment services may process technical connection data such as IP addresses. Application Programming Interface (API) requests use Hypertext Transfer Protocol Secure (HTTPS) in production. Runtime diagnostics include in-memory aggregate route latency and status counts. Diagnostic summaries are intended to avoid provider secrets and customer credentials. No system can promise uninterrupted or risk-free service.

Access, deletion and retention

Use account controls or Send Feedback to request help with account information or deletion. An administrator can delete a customer account after resolving pending billing. Deletion removes the application account and sessions; payment-provider records, limited audit records and backups may remain where operationally or legally required. The operator must establish and disclose the applicable retention schedule and support process before commercial launch; this software does not assert a universal retention period.