1. About this policy
This policy explains information handled through the Rakugaki Beast official website, browser demo, Steam version, and contact form.
2. Browser-demo information
When you choose “Turn into a Beast with AI” in the browser demo, your drawing (PNG), chosen nickname, language setting, and Turnstile token are sent to our evaluation service on Cloudflare Workers. The drawing is sent to the DeepSeek API for evaluation and content moderation; the chosen name and language setting are sent for evaluation.
The evaluation service does not cache or persist the image itself. Its hash is used when forming the response. To limit use, the service keeps a counter based on a hash of your IP address for up to 48 hours.
3. Information handled by the Steam version
When you register a beast, your drawing (PNG), chosen name, fill ratio and language setting are sent to our evaluation service on Cloudflare. Drawings are sent to the DeepSeek API for evaluation and content moderation; chosen names and language settings are sent for evaluation. When Ghost Sharing is used, each creature’s drawing, party text fields and the in-game display name are also sent to the DeepSeek API for content moderation. Evaluation results, including chosen names, are stored in a cache whose key includes the image hash, normalized name and language setting, among other values. Normal results have no automatic expiry; fallback results expire after 24 hours.
Online matches send a Steam authentication ticket and an identifier generated on your device to our service. We verify the ticket with Valve's Steam service. The Steam ID returned by that verification is used for authentication, match admission, reconnection and abuse prevention, and is included in the authentication token issued to your game and in our match rooms. Ban-status information returned by Valve is also used for authentication and match admission. Game authentication sessions expire after 6 hours. Your raw Steam ID and authentication ticket are not shown or delivered to your opponent. However, a hash identifier derived from your Steam ID and creature ID is delivered to your opponent to identify a stamp target.
When you enter a private friend match using a room code or Steam invite, your in-game display name, party drawings, creature names, stats, moves, actions and match result are processed by the match service on Cloudflare and shown to your opponent in that match. Matches using an existing party send each creature’s drawing, party text fields and the in-game display name to the DeepSeek API for content moderation. In an Instant match, newly submitted drawings are sent to the DeepSeek API for evaluation and content moderation, with names and language settings sent for evaluation. Instant-match evaluation results use the evaluation-cache retention described above. Entering a match does not by itself register your creatures for Ghost Sharing or the public ghost ranking.
Choosing Ghost Sharing stores your selected party's drawings, names, stats, moves and descriptive text, and your in-game display name on Cloudflare for asynchronous opponents and the stamp ranking. A device-generated identifier used to read and delete the shared party is also sent. You can choose a sharing period of 14 days, 90 days or one year (one year by default). Existing sharing periods are not extended automatically. Expired ghosts are excluded from new retrieval and ranking results. You can see the names and expiration dates of your live shared teams in your sharing history; drawings are fetched when you open a team. Withdrawing a shared party removes its payload and index entry. A truncated hash of the device identifier is also sent to other players as an encounter marker. When a valid Steam authentication session is available, its session token is also sent to link the authenticated owner’s match stamps to the shared ghost. These link records have no automatic deletion period and are not erased just because the ghost expires or is deleted.
Match artwork is scheduled for deletion 10 minutes after a match ends, and stored room data after 24 hours. Artwork cannot be newly retrieved from that room after its deadline. Reported artwork is separately retained for up to 90 days in private storage for review. This does not erase encounter records already saved on your opponent’s device. Queue and abuse-prevention records from earlier public-match tests include records without time-based expiry, which are trimmed during count- or date-based processing. Current real-time play is limited to private friend matches.
Sending a stamp transmits the target creature identifiers and stamp type. Match stamps also send the authentication session token and a device-generated player identifier. Receiving a stamp also creates records for the recipient’s creature. Match stamps store a target hash derived from Steam and creature IDs, Steam-derived hashed owner and voter scopes, the target creature ID, receipt records and totals. These stamp records currently have no automatic deletion period. Match-stamp targets start private. They contribute to a live ghost's public ranking only when their owner chooses to share the corresponding creature as a ghost.
Ghost stamps send a Steam authentication session token and store the ghost ID, creature ID, stamp type, a voter hash derived from the verified Steam ID, receipt time and totals. These records also have no automatic deletion period. The player who shared a party can view its received stamp counts. The hashes described here are identifiers; they are not guaranteed to be anonymous information that cannot be linked back to the original data.
Reporting an opponent’s drawing from a battle result stores a hash of the artwork, the Ghost or match reference, creature ID, report reason, receipt time, and a reporter identifier derived from the verified Steam ID using a server-held secret. The report record does not contain the reporter’s raw Steam ID, and the opponent does not see it. A private copy of reported artwork is retained for up to 90 days for review. Report records are scheduled for deletion after 90 days; an artwork hash and temporary quarantine status remain until an operator clears them. Three sexual-content reports from distinct authenticated accounts temporarily stop sharing of the artwork pending operator review. Reporting does not remove the creator’s local drawing.
An affirmative moderation decision may be reused for up to 24 hours only when the image, text, model and moderation rules are unchanged. This moderation cache contains an input hash, a pass indicator and expiry time, not the image or text itself. Rejections, review decisions and communication failures are not reused. Our expiry periods do not mean external providers’ stored data or backups are erased at the same instant.
4. Contact form
The contact form receives an optional name and email address, topic, message, referring page, and browser information. This information is stored in Cloudflare KV to handle your inquiry and is deleted automatically after 180 days. The name, email address, topic, message, referring page, receipt time, and record identifier are also sent through Cloudflare's email service to the operator's verified Gmail address. The emailed copy is not covered by Cloudflare KV's automatic deletion after 180 days.
IP addresses are used only for a submission rate-limit counter and are not stored with the message. That counter expires within one hour.
5. Abuse prevention and analytics
The browser demo uses Cloudflare Turnstile to prevent abuse. The evaluation service’s per-minute rate limit stores counters under keys containing IP addresses; these expire after 120 seconds. Demo usage limits also use IP-derived hash counters retained for up to 48 hours.
If daily limits for ghost registration or retrieval are enabled, they store the operation, date, IP-derived hash and request count. These daily records have no automatic deletion period. To limit evaluation registrations, the service also briefly stores a key derived from the verified Steam ID and daily request counts.
The official site uses Cloudflare Web Analytics to aggregate page visits, referrers, browser and device types, and loading performance. This analytics service does not track visitors using cookies or local storage. See Cloudflare’s data collection explanation for details.
To monitor AI service usage, operational logs record the model, operation type, success or failure, response time and token usage returned by the provider. These usage logs do not record drawings, input text, generated text or API keys.
When the client and server disagree on an online match calculation, operational logs record the match ID, player seat, turn and affected field. Drawings and full battle state are not sent. The client keeps a diagnostic log capped at 1 MiB.
6. Use and sharing of information
We use this information to evaluate creatures, authenticate players, run and reconnect matches, aggregate stamps, respond to inquiries, prevent abuse and operate the service safely. Entering a friend match shows your display name, party, actions and result to your opponent. Parties you separately choose to share as ghosts may appear as asynchronous opponents and in the stamp ranking.
Evaluation, sharing and match services use Cloudflare. Drawings are sent to the DeepSeek API for evaluation and content moderation; chosen names and language settings are sent for evaluation. Ghost Sharing and matches using an existing party also send drawings, party text fields and the in-game display name for moderation. Steam authentication tickets are verified with Valve’s Steam service.
7. Contact
For questions about this policy, please use the contact form.
Effective date: July 12, 2026 / Last revised: September 26, 2026