Tingraph · Indonesia

Cookie & Browser Storage Policy

Necessary sign-in cookies, browser state and the third-party storage used outside Tingraph.

Effective October 5, 2026 · Version 2026-10-05

At a glance

  • Tingraph uses account and OAuth cookies needed for authentication.
  • Browser storage synchronizes sign-in changes; it does not hold a password or session credential.
  • The current application does not use advertising or optional analytics trackers.

This summary helps you navigate. Read the full policy below for the details and qualifications.

Necessary cookies

The production account cookie is normally named __Host-tingraph_session; development deployments may use tingraph_session. It contains an opaque session credential, not your password. It is HttpOnly, SameSite=Lax and Secure in the production configuration. Its maximum configured lifetime is 30 days; server-side expiry, revocation or seven days of inactivity can invalidate it earlier.

Google sign-in temporarily uses __Host-tingraph_oauth (or tingraph_oauth in development) to bind the OAuth transaction to your browser. It is HttpOnly, lasts up to ten minutes and is cleared after the callback. Blocking it can prevent Google sign-in.

These cookies support the service you request rather than advertising. We do not describe your agreement to the Terms as consent to unrelated tracking.

Local storage and in-memory state

The local-storage key tingraph:session stores a timestamp to notify other tabs that account state changed. It is overwritten on sign-in/sign-out changes and remains until your browser removes it or you clear storage. It does not store the authentication token, password or diagram content.

Source, canvas state and the current AI conversation live in browser memory for the current editor session. Saved account diagrams are fetched from the backend. Standard browser caches may also hold static application files or publicly cacheable profile images; those are different from a guaranteed saved-diagram backup.

Third-party storage

Google authentication and external payment pages can use their own cookies or storage when you visit them. ChatGPT, Gemini or Claude can also do so if you open their websites yourself. Their policies govern storage on their own services.

The application's current code does not embed advertising trackers or optional analytics. If we add a storage purpose that legally requires consent, we will disclose it and obtain that consent before enabling it where required.

Your controls

Use browser settings to inspect, delete or block cookies and site storage. Signing out revokes the current session and clears its cookie. Clearing or blocking necessary storage can sign you out, prevent Google sign-in or stop cross-tab updates.

Download or save work before clearing site data or closing the editor; unsaved work can be lost. See the Privacy Policy for retention and data-rights requests, or contact support@tingraph.com with a storage question.

Questions about this policy?

support@tingraph.com