Published cards are saved.
Privacy
Scope and contact
This policy describes how my9template handles information when you use this service. The operator uses the my9template brand. For questions or a request about your information or a public card, use the email address on the contact page. Updated October 9, 2026.
Drafts in this browser
The editor uses localStorage on your device for your name, selected games, their order, notes and spoiler settings. It also stores a pending publication operation and its content so that you can retry after a refresh. These local items have no automatic expiry. They are not an account or a cross-device backup. Clearing browser site data removes them; clearing the editor empties the draft. Neither action deletes published cards.
Public cards
Publishing sends your name, nine game selections, notes and spoiler settings to our server. Cloudflare D1 stores a snapshot, publication time, public identifier and operation information used to prevent duplicate retries. Cards remain stored long term without a scheduled expiry. Names, game selections and notes are public to anyone who can access the link. A spoiler toggle hides text on screen; it is not a privacy or access restriction. Avoid publishing private or sensitive information.
Searches and service protection
Search queries are sent through our server to RAWG to find games. The RAWG API secret stays on the server. Queries and results are cached in D1: results for one hour, empty results for five minutes, and game details for 24 hours. Expired records are removed during later cache writes. Usage counters support upstream quotas and request limits. Where Cloudflare provides an IP address, publication protection stores a hash of it in a per-minute counter, not the original IP. These counters expire at the end of the minute and are cleaned during later requests; monthly upstream counters expire at the next month. Expiry does not promise immediate physical erasure.
Service providers and external links
Cloudflare processes requests and hosts the site and D1 storage; this can include technical request information such as IP addresses. RAWG receives server-side search queries and game requests. Available image requests also pass through our server to the image source. Opening X or Bluesky passes the chosen prefilled text and card URL to that platform; you decide whether to post. Email and external services have their own data practices and retention rules. We do not promise deletion of all provider logs, backups or copies made by other people.
Requests about public content
Use the email address on the contact page to send the full card URL and your reason for a request. Your email address, message and information you provide are used to review and respond to the request. The operator can restrict or remove public access after review. There is no account-based ownership verification or self-service deletion. Requests are considered according to applicable requirements, rights concerns and reasonable operational needs; not all requests are accepted and no fixed response time is promised. Restricted cards may remain in storage even when their public pages and images are unavailable.