Your usage is yours.

Last updated 9 November 2026. This covers the Glyphi desktop app and glyphi.xyz.

Local by default

The desktop app keeps its database in your user profile, on your computer. It contains daily totals, per-hour buckets, model keys, provider ids, timestamps, your time zone and estimated cost. It never contains prompts, completions, source code, file paths or project names, because Glyphi reads counters rather than conversations.

Local tracking needs no account and no network. Everything below only applies if you choose to sign in.

Cloud save, if you turn it on

When you sign in, Glyphi stores on its server:

Your email address and a password hash held by Supabase Auth. Glyphi never sees your password.
A hash of your session token, so a database dump cannot be replayed as a login.
Per uploaded day and tool: token totals, hourly buckets, model keys, estimated cost and time zone.
If you create one: your handle, display name and avatar URL.

Nothing is uploaded while you are signed out, and signing out of the app stops uploads immediately.

Public profiles

A profile is private until you publish it. Published profiles show your handle, display name, avatar, saved token totals and a daily activity graph, and are ranked on the leaderboard. Unpublishing hides the page and removes you from the leaderboard.

This website

glyphi.xyz sets one cookie, glyphi_session, and only after you sign in. It is httpOnly, so scripts on the page cannot read it. There is no analytics, no advertising pixel and no third-party script on this site.

Where it runs

The website is served by Vercel; the API and database run on Supabase in the European Union (Paris). Both process requests on Glyphi's behalf and do not receive data beyond what the features above describe.

Deleting your data

Deleting the app's data folder removes everything held locally. To delete a cloud account and every row attached to it, ask through the project on GitHub — deletion is permanent and immediate.

Questions

Open an issue on GitHub, or read PRIVACY.md in the repository. Security issues should go through the contact described in SECURITY.md, never a public issue.