Privacy Protocol

We collect personal credentials and metadata you provide directly to the lab when signing up, purchasing products, or contacting the lead engineers. This includes:

• Account node parameters (name, email address, usernames).
• Unique cryptographically hashed credentials for account authentication.
• Active developer inquiries, feedback logs, and technical telemetry you submit.

We use the captured parameters to operate our AI lab infrastructure, specifically to:

• Authenticate user accounts and maintain active secure sessions.
• Verify active Whop subscription states to unlock dashboard modules and premium resources.
• Process developer payloads within interactive token calculators and playground nodes.
• Adapt lab configurations, optimize edge performance, and resolve debugging anomalies.

We deploy secure cookies, session storage tokens, and active browser identifiers to trace session telemetry.

These cookies allow us to identify your browser state and keep your premium account securely authenticated as you navigate through the laboratory pages. Disabling cookies will interrupt active sessions and block secure access to the developer dashboard.

Consistent with modern web scaling, we synchronize core actions with trusted third-party cloud engines. We never sell your telemetry. Your data syncs specifically with:

• Whop (Billing & Store): Handles all transactions and premium checkout sequences. Credit card details are processed entirely via Whop.com and never enter or reside on DecodesFuture servers.
• Supabase / Firebase (Identity & Database): Handles account registrations, metadata storage, and secure authentication tokens.
• Upstream AI Nodes (OpenAI / Anthropic): When using interactive sandbox models, payload prompts are securely transmitted to these partners for inference. They are bound by strict developer API policies not to use your prompt strings for model training.
• Infrastructure (Vercel & Analytics): Google Analytics, Ahrefs, and Vercel are deployed to capture page speeds, latency, and reader engagement levels.

Depending on your regional jurisdiction (such as the GDPR or CCPA frameworks), you maintain active rights over your record sets:

• The right to inspect what telemetry we hold.
• The right to request node correction or complete database purge.

To execute any of these directives, dispatch an authorized request to our support node listed below.

In alignment with our emphasis on local LLM configurations and data sovereignty, we implement industry-standard encryption, firewalls, and active edge proxy protections. We actively secure your records against leakage, breach, or unauthorized decryption.

If you have any questions about this Privacy Protocol, please contact the lead engineer at: thecodehaider@gmail.com.