Privacy Policy Framework
Review the comprehensive documentation detailing our client-side architecture, data isolation protocols, and localized state persistence engines.
Client-Side Sandbox Execution Policy
The core generation mechanisms of Math AI are engineered to process algorithmic matrices entirely within the user client interface. All calculation routines, grade calibrations, and custom template structuring are executed locally by your web browser engine. Because there is no middleware API or backend ingestion layer connected to these workflows, data transmission to external host servers is fundamentally blocked.
Localized Database Index and Persistence
The Performance Ledger Tracking functionality leverages the Web Storage API (specifically the LocalStorage protocol) to persist worksheet scores and student identifiers over time. This data is written into an isolated domain space on your hard disk. Math AI does not monitor, aggregate, or mirror these records. Users retain absolute structural command over this storage engine; clearing the cache memory or using the provided database reset switch inside the ledger will completely and permanently delete all history indexes.
User Identification and Pseudonymity
We do not collect personal identifiers such as email accounts, physical locations, or system hardware addresses. The application functions autonomously without requiring profile creation or third-party OAuth validation. For multi-user environments or educational deployments, we recommend utilizing random alphanumerical tags, room descriptors, or pseudonyms in the student input fields to maximize user privacy boundaries.
Behavioral Analysis and Advertising Cookies
Math AI strictly rejects the installation of cross-site marketing frameworks, behavioral analysis pixels, or tracking cookies. The workspace environment operates completely devoid of contextual advertising. This strategy ensures the technical infrastructure remains focused on raw speed, privacy compliance, and systematic academic utility.
Document Portability and Printed Formats
When executing the document render layout functions, all conversion processes are handled natively via CSS media queries and the integrated web browser printing system. Output files exported to portable formats such as PDF or direct physical prints remain contained within your hardware environment, preventing unapproved data duplication or unexpected leakage loops.