Wish Board

1. Privacy Policy

1.1 Data we collect and store

• Wish text — Stored on our server (Firebase Firestore) and shown to others. The board resets at Sunday 24:00 (Monday 0:00 JST). Removed from the server each Sunday at 22:00 JST (purification); this time may change in the future.
• Icons — Display icons for wishes are stored on the server.
• User identifier — An ID generated in your browser is used to link your posts, deletes, and claps. We do not collect name, email, or phone.
• Delete token — A hashed value is stored so only you can delete your wish (the raw token is not stored).
• Claps — Your identifier is stored to know which wishes you clapped.
• Browser storage — Post history, clapped wish IDs, consent state, and similar data are stored in your browser’s local storage until you clear it.

1.2 Purpose of use

Data is used only to display wishes, manage your posts and claps, and operate the service.

1.3 Personal information

We do not collect personal information (name, email, phone). The user identifier is a browser-generated UUID and cannot identify you by itself. You can delete your own wish from the detail page (see 1.5).

1.4 Weekly purification

The board resets at Sunday 24:00 (Monday 0:00 JST). At Sunday 22:00 JST, last week’s wishes are removed from the server (purification); this time may change in the future. Wish text is not kept on the server. Data in your browser remains until you clear it.

1.5 Data deletion

• By you — You can delete your wish from the detail page. After deletion it is removed from the server and cannot be restored.
• Weekly purification — Board resets at Sunday 24:00; server data is removed at Sunday 22:00 JST (this time may change in the future).
• Browser data — Clearing site data (local storage) in your browser removes your post history, claps, and consent state. We cannot delete it remotely.
• Service end — If we end the service, we will delete or anonymize server data as appropriate and announce it where possible.

1.6 Service suspension and data loss

The service may become unavailable or data may be lost due to maintenance, outages, funding, or other reasons. We do not guarantee availability or data retention. Please keep important content elsewhere.

1.7 Security

We use Firebase App Check (reCAPTCHA v3) to reduce bots and abuse. All writes go through our APIs; direct database writes are disabled. Delete tokens are stored as hashes.

1.8 Third-party services

We use Firebase (Google) for the database. Those services may use cookies and collect usage data. See their privacy policies for details.

1.9 Consent

Use of posting and clapping is only for users who have agreed to the consent text (data storage, purification, deletion, possible service suspension, entertainment nature) and to this Privacy & Disclaimer.

1.10 Changes

We may update this policy. Significant changes will be announced on this page.

2. Disclaimer

• Entertainment — This service is for entertainment. We do not guarantee fortune-telling results, outcomes, or any “Miko feedback” content.
• Availability and data — We are not liable for unavailability, suspension, or data loss due to maintenance, outages, funding, or other reasons.
• Miko feedback — Any such text may be auto-generated. We do not guarantee its accuracy or suitability.
• Your posts — You are responsible for not infringing others’ rights. We may remove content we deem inappropriate.