Privacy

Last updated November 14, 2026

Signing in with Google

The Sign in button uses Google's sign-in. Google asks you to share your name, email address and profile picture with tickcli.com. Nothing else is requested.

We keep your Google account id, email and name on our server so you can manage your API keys and deployments. Your picture stays in your own browser. Google's sign-in token is checked once and then discarded. We never share or sell this data.

Sign out ends your session. "Delete my account and data" on the API keys page removes your account, keys and deployments at once. You can also remove tickcli from your Google Account, under Security, "Your connections to third-party apps and services".

API keys and deployments

API keys are stored only as a one-way hash; we show each key once and cannot show it again. For a deployment we keep its name and the list of sites you allow. Games using a deployment connect to our room server; it keeps rooms in memory and the saves a game asks for, and no player accounts.

Everything else

tickcli.com sets one cookie, only after you sign in (your session). It runs no analytics or ads and does not track you across sites. Google's sign-in script is loaded only when you reach for the Sign in button. The web server does not keep access logs for tickcli.com.

Google's handling of your account is covered by the Google Privacy Policy.

Questions

Open an issue on GitHub.