CORNERLOCK Privacy Policy
Effective July 5, 2026
CORNERLOCK is a strategy game available at cornerlock.io and as an iOS app. This page explains what we collect and why. The short version: we collect the minimum needed to run online games, we don't sell or share your data, and you can delete everything yourself at any time.
What we collect
Playing as a guest requires no account and collects no personal information. A random client identifier is stored on your device so you can reconnect to games in progress.
If you create an account, we store your email address (used only to sign in and for password-reset emails), a securely hashed password (PBKDF2 — we never see or store the password itself), your chosen display name, your list of games, your rating and win/loss record, and the display names of recent opponents.
If you enable turn notifications, we store the push token or subscription your device provides so we can tell you when it's your move. Notification content is limited to game events (whose turn it is, invites).
What we don't do
We don't sell your data, show ads, use third-party trackers, or share your information with anyone except the infrastructure providers that host the game (Cloudflare for game servers, Vercel for the website, Apple/Google/Mozilla push services for notifications you opt into, and Resend for password-reset emails you request).
Analytics
The website uses privacy-friendly, cookie-less page analytics (Vercel Analytics) to count visits. It doesn't identify you or track you across sites.
Data retention & deletion
Finished games are automatically deleted from the game servers after 30 days. You can permanently delete your entire account — login, games list, rating, record, opponents, and push subscriptions — at any time from the menu: sign in, then choose Delete account. Deletion is immediate and irreversible.
Children
CORNERLOCK doesn't knowingly collect personal information from children. Guest play requires no personal information at all.
Contact
Questions or requests: help@cornerlock.io
We'll update this page if our practices change; the effective date above always reflects the current version.