Data and privacy

Privacy policy

Last updated:

This policy covers creative, image, activity and game tools on wwwne1198.party: data processing, services used, and how to manage or delete your data. No account is required.

  • Settings, scores and selected images are initially stored in your current browser.
  • Settings and images are saved to the cloud when you create a cloud code or use custom images to create a match room or join matchmaking.
  • The production site uses GA4 analytics; cloud operations use Cloudflare verification.

Activity tool data

Names, weights, assignments and results for the picker and team maker are processed in your browser, not uploaded or sent as GA4 event content. Names are not saved by default. Enabling the remember option stores settings and names in localStorage, shared across four languages. Turn it off, use Clear all tool data, or clear site data to remove the local copy. Draw history and team results not saved in My activities last only for the current page; exported JSON/CSV files are yours to keep or delete.

Settings, members and scores stay in your browser. Transfers use this tab’s sessionStorage, are deleted after use and expire after two hours. There is no cloud sync. Scoreboard and timer settings can optionally be kept in localStorage; turn remembering off or clear tool data to remove them.

Activities and images stay in this browser. Clearing site data removes them. Export backups; there is no automatic sync to other devices.

In-person tools and audience windows process data in the browser. Online rooms send names, questions, pictures, answers and scores to the service and share them with participants. Room data is kept for up to 90 minutes.

These seven tools process images, names and content locally. Settings stay in this browser only after saving; clearing site data removes them. Export backups. Memory cloud sharing and PK follow the game’s own guide.

Solo and shared-device games run in your browser. Save settings manually; reloading clears the run. Materials use this device’s IndexedDB across all languages and can be exported or deleted.

Online rooms send names, prompts, answers, strokes and scores to the service and share them with participants. Room data is kept for at most 90 minutes. Avoid private content.

Local settings, images and scores

The site uses localStorage for game settings, your manually selected language, saved scores and cloud-code management credentials, and IndexedDB for custom images. These retain your choices and records. All four languages share this data within the same site and browser.

Score saving is on by default and keeps up to 500 records. Selected fields may include nickname, time and flips, alongside required identifiers and the rules used. The session leaderboard exists only in page memory and is cleared when you reload or leave the game page. Saved scores can be viewed or exported as CSV in Scores.

Local data has no fixed automatic expiry. It remains until you delete it, newer records replace it, or the browser clears it. Clearing site data, closing private windows, storage limits or switching devices may remove or make it unavailable. Turning off score saving stops new records; it does not delete existing ones.

Custom images and cloud codes

When you select an image, your browser resizes it, converts it to WebP, removes source metadata and compresses it on your device. Selecting images or playing solo does not upload them.

Cloud codes upload the current draft. Creating a room or joining matchmaking with custom images saves the applied settings and images. Cloudflare Workers receives the data; D1 stores codes and management information, and R2 stores settings and images. Each profile allows up to 15 images and 4 MiB. Profiles exclude nicknames, rankings and detailed results, but include any information placed in titles, image names or images.

The 12-digit code is a sharing and retrieval method, not a private account or password. Anyone who knows it can retrieve the settings and images after verification. Save only content you have permission to use and are comfortable sharing; avoid private photos or personal information.

Cloud profiles last 30 days from creation. A successful code load or using that profile to create a room or join matchmaking renews the 30-day period. Unused profiles expire and are cleaned up in hourly batches; deletion may follow expiry. Solo play does not extend retention.

The browser that creates a code stores a deletion credential. You can delete its cloud profile under Codes created in this browser. Clearing site data also removes the credential, so that deletion control will no longer manage the profile. Cloud deletion does not remove local copies already downloaded on other devices.

GA4 analytics and cookies

The production site uses Google Analytics 4 (GA4) to understand visits and usage. Analytics starts when a production page loads. Google may use cookies or similar technologies to process page URLs, referrers, browser, device, approximate location and interaction information. The site does not intentionally send game nicknames, score details or custom image contents as GA4 event parameters.

Analytics retention and processing depend on GA4 account settings and Google policies. Deleting cookies does not delete previously collected analytics, and private browsing does not guarantee that analytics stops. You can adjust browser cookie settings or use Google’s Analytics opt-out tool; some restrictions may also affect site features.

AdSense ads are currently disabled. If advertising services are introduced, this policy will be updated before activation to explain the providers’ data use and add applicable cookie and consent management.

Cloudflare verification and service providers

Cloudflare Turnstile loads when you create, load or delete a cloud code, or establish a match connection. Cloudflare processes IP addresses, browser information, connection characteristics and site origins to detect bots and prevent abuse.

To control capacity and traffic, the cloud API processes the request IP, creates a daily-changing hashed identifier and counts operations. The site’s rate-limit table does not store raw IP addresses. Older daily counters are removed in scheduled batches. Cloud profiles also retain codes, creation and last-retrieval times, expiry, file size and required management hashes.

GitHub Pages serves the static pages, and cloud features use Cloudflare Workers, D1 and R2. Providers may process IP, browser and request information to deliver connections, storage and security. Data may be processed through infrastructure in different countries or regions; provider retention and use follow their policies and service settings.

Online matches and room data

During a match, your match nickname, settings, images, moves and scores are sent to Cloudflare and shared with that opponent. This does not automatically upload your solo game data.

Rooms and connection credentials are temporarily stored in Cloudflare Durable Objects. Rooms wait for 3 minutes; matches last up to 10 minutes and are cleaned up about 1 minute after ending. Connection data lasts up to 20 minutes. Usage counters and daily IP hashes limit abuse; old counters are replaced on the next day’s activity. Outages may delay cleanup.

Custom images use cloud profiles that expire after 30 days without use. Leaving a match does not immediately delete the profile. Manage or delete it in the browser that created its code. Match results are excluded from solo rankings and are not stored in a public results database.

How to manage and delete data

  1. In Scores, export a CSV or delete saved records. Turn off score saving in Settings to stop adding records.
  2. To delete a cloud profile, first open Cloud codes in the browser that created it and use the deletion control under Codes created in this browser.
  3. Clear this site’s data in your browser to remove local settings, images, scores, language preference and management credentials. Delete any cloud profiles you want removed first; clearing local data does not delete cloud content.

You may request access, correction, deletion or restriction of processing under applicable law. Email us with the issue; where necessary, we will verify your connection to the data to avoid deleting someone else’s information. The site operator cannot directly access or delete data stored only in your browser.

Contact and policy updates

If you contact us by email, the site operator uses your email address, message and attachments to handle the issue or data request. Avoid sending unnecessary private information. Correspondence is retained for handling the request and any necessary retention period.

For privacy questions, contact: [email protected]

This policy may be updated when site features or third-party services change. The date appears at the top. You can always find the latest version through Privacy policy in the footer.

All tools