Privacy — Hit Engine

This notice describes the records created when you browse Hit Engine’s game catalogue or sign in to the private preview.

Visiting the site

Cloudflare delivers the pages and checks requests for security. It receives connection information such as your IP address and browser details. Its request logs can include the time, URL (including its query string) and response status. The site does not ask visitors to create a player account or use advertising or audience-tracking scripts.

If you confirm you are 18 or over, the site stores that choice in your browser. The flag has no built-in expiry, is not sent to us, and disappears if you clear this site’s browser data. See Cookies.

Signing in and editing

Cloudflare Access protects the private preview and staff console. It processes the sign-in identity, IP address, time and outcome of a sign-in attempt and uses a session cookie. The application session is set to 24 hours. Ending a session does not erase an access log.

Hit Engine keeps staff email addresses, roles and access status in its Supabase database in Canada (Central). It also keeps website content, uploaded artwork and its description, saved revisions, approved versions, and a record of who changed what and when. Removing access does not erase past activity or the staff record. The raffle setup editor can save an unfinished draft in the staff member’s browser until they create or discard it, or clear the site’s browser data.

We use a private GitHub repository for the site’s code. GitHub and Cloudflare Builds handle contributor and deployment history. We have not set an automatic expiry for our repository history.

How long we keep records

The provider log windows below apply to the preview’s current plans. They are not deadlines for deleting database records, backups or every security record held by a provider.

Cloudflare: Worker request and error logs are available for 3 days; Access authentication logs for 24 hours. These are separate logs on the current Workers and Zero Trust plans.
Supabase: API and database service logs are available for 1 day on the current Free plan. The data saved in the database does not expire after a day.
Staff and site records. Staff access history, website revisions, releases and artwork have no automatic expiry.
Recovery copies. Our existing manual staging exports are encrypted and expire 30 days after creation. Cleanup runs on the studio PC when it is available. New daily staging backups are paused. A restored copy is checked for holds and expired records before it is used.

Who handles the data and how to contact us

Hit Engine chooses what its site collects and publishes. Cloudflare hosts the preview, controls access and checks requests for security. Supabase hosts the application database. If you follow a game link to Stake, you are visiting Stake’s own service.

For questions about access, correction or deletion, see Terms. The studio’s legal identity and contact details on that page are still to be completed.