Privacy Policy.

1. Who is responsible

Matheria is a web-based mathematics and student productivity service operated by Ara Musayelyan from Armenia. Privacy questions and requests can be sent to matheria.contact@gmail.com. Matheria is not presented as a separate incorporated company or legal entity.

2. Information Matheria handles

Account and session information

If you create an account, Matheria sends your display name, email address, password credentials, email-verification status, password-recovery requests, and session information to Appwrite. Matheria does not receive your readable password from Appwrite.

Workspace information

Your workspace may contain subjects, classes, schedules, tasks, notes, documents, folders, saved graphs, sketches, profile settings, and task attachments. Verified accounts can synchronize a serialized copy of this workspace to a private Appwrite database row associated with the account.

Files and profile images

Images, PDFs, task attachments, and profile images that you choose to upload can be stored in an Appwrite storage bucket. The application also keeps browser-local copies where needed to support previews, offline continuity, and upload retry.

Support and operational information

When you submit a support, privacy, account-access, feedback, or legal request, Matheria stores the email, category, subject, message, source page, timestamps, status, priority, account association when signed in, reply history, and restricted internal support notes. Administrators can see operational account metadata and aggregate counts, but the Admin Panel does not expose passwords, tokens, private note contents, equations, or uploaded file contents by default.

Browser-local information

Matheria uses localStorage for settings and working state such as theme, calculator history, local workspace content, editor state, and navigation state. It uses IndexedDB for larger local files and blobs. A session fallback value may be stored in sessionStorage and localStorage when a browser blocks the normal Appwrite session cookie.

3. Why information is used

• To create and secure accounts, confirm email addresses, sign users in, and support password recovery.
• To provide calculators, planners, notes, sketches, graphs, file management, and private workspace synchronization.
• To respond to support, privacy, and deletion requests.
• To understand use of public pages and improve Matheria when analytics consent permits it.
• To meet security, abuse-prevention, legal, and service-integrity needs.

4. Service providers and processing locations

GitHub Pages hosts the public static website. Appwrite Cloud, configured through its Frankfurt endpoint, provides authentication, database, and file storage. Google Analytics 4 measures public-page use where the relevant consent permits it. Google AdSense provides site verification and Google's consent-management integration; Matheria does not currently place ad units. Google Fonts supplies web fonts and may receive normal connection data such as an IP address and browser request information.

These providers can process information outside Armenia under their own terms and infrastructure. Matheria does not sell your private workspace or uploaded files.

5. Analytics, advertising, and consent

Google Consent Mode is initialized with analytics and advertising storage denied. Google Analytics is included on public informational pages, not as custom tracking inside private application pages. Google signals and ad-personalization signals are disabled in Matheria's GA4 configuration. Where Google's consent message is available, your accept, reject, or manage choice is intended to control the relevant Google consent states. Details are in the Cookie Policy.

6. Security and access

Cloud workspace rows and files are requested through authenticated Appwrite sessions and account-specific permissions. Email verification is required before cloud workspace synchronization. No public website can promise absolute security, so use a unique password and protect access to your device and email account.

7. Retention and deletion

Browser-local information remains until you delete it in Matheria, clear site data, or the browser removes it. Cloud workspace information and uploaded files remain until they are deleted through the service, the associated account is deleted, or they must be removed for security or legal reasons. Support tickets and administrator audit records receive a three-year retention review date and may be retained longer only where an unresolved support, security, or legal need requires it. Rate-limiting fingerprints are hashed rather than stored as raw IP addresses and are scheduled to expire after 24 hours.

The current Appwrite Function removes expired rate-limit records during later submissions. Ticket and audit retention review is currently an explicit administrator process rather than an automated scheduled job. Google controls its own service logs and GA4 retention according to the settings of the connected Google property and Google's policies; Matheria does not state a fixed analytics-retention period because it can be changed in that property.

Removing a feature from the active interface does not automatically erase unrelated private workspace information. If data is moved to an inactive compatibility archive, it is kept with the workspace until the user deletes the workspace or account.

8. Your choices and rights

You may ask to access, correct, export, or delete personal information that Matheria controls, withdraw optional consent, or object to particular processing. Privacy requests are stored in a restricted support queue and Matheria may need to confirm that the requester controls the relevant account before taking a destructive action.

Browser settings can clear local site data. Google's consent message controls Google processing where it applies.

9. Updates and contact

This policy may change when Matheria's real implementation or legal obligations change. Material revisions will be published on this page with a new update date.