Privacy

Solitaire Tavern is published by adrianmato.com. Questions or requests: hello@adrianmato.com.

Last updated: October 3, 2026.

Game saves stay on your device

Your current hand, preferences, and local game statistics are stored in your browser or plugin host when storage is available. The game does not upload card layouts or local saves. Clearing site data removes local saves.

Limited usage statistics

To understand how often the game is played and improve reliability, the deployed game sends usage events to our Supabase database. Events cover opening a session, successful or failed loading, starting or winning a hand, theme changes, and approximate active play time.

These events contain a random browser identifier, a random session identifier, a hand identifier, whether you play on the website or in an embedded host, theme, draw count, loading duration, active seconds, a fixed error category, and the server receipt time. The browser identifier is stored locally so we can estimate returning browsers. It is not your name or an OpenAI account ID. These identifiers are pseudonymous, not a guarantee of anonymity.

We do not include your name, email address, chat content, card layouts, page URLs, or raw error messages in usage rows. We use aggregate statistics to understand activity, engagement, theme preferences, and loading problems. We do not sell this usage data or use it for advertising.

Services that receive data

OpenAI Sites hosts the game assets and website. Vercel hosts the public plugin service and its publisher pages. Supabase stores the usage events. These providers receive network requests and may retain operational logs under their own policies. When the host requires sign-in, OpenAI handles that sign-in; this game does not request or store your password.

Your choices

The game respects browser Do Not Track and Global Privacy Control signals by disabling usage collection. Blocking the Supabase connection also prevents events from being submitted; gameplay does not depend on telemetry. Clearing site storage resets the browser identifier for future visits, but does not by itself delete events already received. Contact us for access or deletion requests; because events are not tied to an account, we may need information to identify the relevant records.

Retention and access

Local saves remain until you or your browser remove them. Usage events currently have no automatic expiry and are retained for the operation of the game unless deleted earlier following a request or cleanup. Database reads are restricted to the publisher and authorized service access. Other players cannot read individual usage records.

If you contact support, we receive the information you choose to send and use it to handle your request. We retain that correspondence as needed to resolve and keep a record of the request. We will update this page when our practices change.