Privacy

Browser and room data

No account is required. Your browser stores information used to reconnect to a room, and may retain pending room cleanup information until removal or absence is confirmed. A five-minute reconnect window controls automatic restoration; it is not a server data-retention deadline.

Solo preferences, candidates, swipe progress and the chosen anime are stored in the tab’s session storage, with a five-minute activity window. Exit Solo clears that session. Recent anime history is stored separately in the browser to reduce repeats. Landing artwork selection also uses session storage.

Rooms in Together Mode use Supabase to store room details, nicknames, membership, saved preferences, votes, rounds and the selected anime. Leaving removes your membership through the application; confirmed last-member departure removes the room. This does not establish a retention period for inactive rooms, backups or logs.

Anime information is requested from AniList through the app’s catalogue endpoint. Your browser also requests artwork from AniList’s image service. Sharing through WhatsApp or Telegram opens that external service only when selected. Copy actions write the public invitation to your clipboard.

ISSHONIME uses Vercel Web Analytics to understand page visits and website usage. Hosting providers may also keep technical request logs according to their settings.

Android app storage

The Android app stores Solo preferences, progress, recent selections, language and cached anime information on your device. Room credentials and pending entry-recovery records are also stored locally. They support room entry, retry and recovery; the random credential is not a permanent installation identifier.

In Android version 1.0.15 and later, leaving offline keeps only the room code and credential needed to retry departure when the app is open and connected. Failed or uncertain exits remain pending until departure or absence is confirmed. Clearing app data removes local progress and retry records; it does not send a deletion request to the room service and may prevent a pending exit from completing.

Android 1.0.29 uses Google Mobile Ads SDK 25.5.0 and User Messaging Platform (UMP) 4.0.0. UMP checks consent eligibility before Mobile Ads initializes or requests a banner. Required privacy choices can be reopened in Settings; declining consent does not block anime discovery.

This closed-test build uses official Google test banners, with production ads disabled. Test ads still contact Google and do not mean that no data is processed. Google describes automatic processing of IP addresses, device or account identifiers, app and ad interactions, and diagnostics for advertising, analytics and fraud prevention. Actual processing depends on consent, device and SDK settings.

Website pages opened from Android use the website services described here. Catalogue and image providers may receive technical request information, including your IP address.

Together processes the nickname you choose, a random room credential, room identifiers, preferences and votes on the server, including when you use Android. Room members can see your nickname and shared room results. Creating an account is not required, but this does not mean that no personal or pseudonymous data is processed.

Hosting and contact services

The public website is served through Vercel. Supabase provides the application’s backend, database and room operations. Their technical request logs and operational settings are separate from application-level analytics.

ISSHONIME has configured Cloudflare Email Routing for contact@isshonime.com. Messages are forwarded to a private inbox. This email setup does not establish whether Cloudflare proxies website traffic.

Retention and recovery

The room service records authenticated room activity. Automatic cleanup of inactive rooms is currently not enabled or scheduled. A five-minute session timeout and a proposed 24-hour inactivity policy are not promises that server records will be deleted after those periods.

Room-creation recovery receipts prevent a lost response from creating another room. These receipts may retain the request credential, nickname and room association after departure or room removal. Receipt minimization is not currently active.

We have not established fixed retention periods for provider logs, backups or support correspondence. Application-level departure does not establish when those copies are removed. Contacting us is not a guarantee of immediate or complete deletion.

Data may be retained as needed to operate, secure and troubleshoot the beta. We do not specify a fixed retention period. Room and Solo recovery timeouts are not data-retention or deletion guarantees.

Technical logs may exist according to hosting, backend and network provider behavior and settings. This page does not promise automatic deletion, a deletion guarantee or a self-service deletion process.

Contact

For privacy questions, contact ISSHONIME at contact@isshonime.com.