1. What this policy covers
This policy describes cookies and similar browser technologies used by Matheria. Cookies are small values a website or service stores through a browser. localStorage, sessionStorage, and IndexedDB are not cookies, but they can also remember information on a device and are covered here for clarity.
2. Necessary session technology
Appwrite uses session technology to keep signed-in accounts authenticated. Matheria sends Appwrite requests with browser credentials. If the browser blocks the normal session cookie, Appwrite can return an X-Fallback-Cookies value that Matheria stores in sessionStorage and localStorage so subsequent account requests can remain authenticated. This fallback is removed when Matheria signs the user out.
3. Browser storage used by Matheria
- localStorage: theme choice, calculator state and history, workspace data, navigation and editor state, sketch/document references, and a session fallback when needed.
- sessionStorage: the Appwrite fallback session value when required by the browser.
- IndexedDB: uploaded files, images, PDFs, task attachments, and other larger local blobs used for previews, local continuity, and cloud-upload retry.
These technologies support core functionality. Clearing them can remove unsynchronized work and local files from that browser.
4. Google Analytics 4
Matheria loads GA4 on public informational pages using measurement ID G-HC9E6G3657. Analytics storage starts as denied through Google Consent Mode. Google signals and ad-personalization signals are disabled in Matheria's GA4 configuration. If the applicable Google consent message records analytics consent, Google can use analytics cookies or identifiers according to that choice and Google's policies. Custom analytics tracking is not included inside private workspace pages.
5. Google AdSense and the Google consent message
The Google AdSense script is present for site ownership, service readiness, and Google's consent-management integration. Matheria does not currently include ad units. Advertising storage, ad-user-data, and ad-personalization consent states start as denied. In locations where Google's Privacy & messaging consent interface applies, Google's CMP is intended to communicate the user's accept, reject, or manage choice to the relevant Google consent states. Matheria does not display a separate custom consent banner.
6. Google Fonts
Public pages request font files and stylesheets from Google Fonts. Google can receive ordinary technical request information, such as IP address, browser details, and the requested resource.
7. Managing your choices
Use the options shown in Google's consent message when it appears. Matheria uses the real Google privacy control rather than a second competing banner. If Google does not make the control available in your region, the button explains that limitation.
You can also block or delete cookies and site storage in browser settings. Blocking necessary session or browser storage can prevent sign-in, file previews, local saving, or synchronization from working correctly. Withdrawing optional Google consent does not remove the workspace data needed to provide the service.
8. Contact
Questions about cookies or consent can be sent to matheria.contact@gmail.com. The responsible person is Ara Musayelyan in Armenia.