Privacy Policy & Data Intent Rules
At QueryIntent Handbook, we believe database engineers deserve absolute transparency. This document details how we handle session-based interactive training, telemetry metadata, and browser caching preferences.
01. Data We Collect
Our primary mission is education on database query intent. When using our interactive tutorials, guides, and handbook code blocks, we capture minimal interaction data to optimize the training path.
- Session-based query inputs: Code snippets processed locally to analyze execution intent.
- Interface analytics: Device viewport sizes and interaction durations to improve code editor blocks.
- Preferences: Theme selections and IDE configuration overrides (e.g., DBeaver or pgAdmin guides).
02. Query Telemetry & Interpretation
We prioritize database security. Our tools are designed for simulated educational queries only. We do not access production databases, live schemas, or proprietary company tables.
Educational Sandbox Boundary
No query input is executed on active backends. Parser engines run in a virtual client sandbox, preventing any sensitive schema data from transferring outside your local machine.
04. Data Security Protocols
QueryIntent Handbook implements high-standard industry encryption (HTTPS/TLS) for transit. We actively clean local browser caches of any interactive mock data when sandbox sessions close to ensure your playground queries stay private.
05. Dynamic Consent Preference Settings
As a user, you hold complete control over your metadata. Below is the state tracker panel showing your active system permissions. Change them here or toggle individual parameters in the sidebar control card.
If you have queries or concerns regarding this policy, please visit our Contact Page to reach out directly to the database educational team. Updated last on August 11, 2026.