Privacy policy

1. Information collected and its purposes

Depending on the features you use, we collect and use the following:

• Account information: Discord user ID, username, display name, avatar, login and activity timestamps, client version and related information. Used for authentication, identifying and displaying users, retaining preferences and support. We do not receive your Discord password. The current login integration requests the identify scope, not permission to obtain your email address.
• Optional profile information: player name, date of birth, country of residence, input device and model, main/strong/weak characters, favorite players and games, biography and links. Used for profiles, player searches and aggregate statistics.
• Listings and connection information: IP addresses and ports, hosting/connection status, latency, tools such as Giuroll and AutoPunch, comments and stream URLs. Used for publishing listings, connecting players, UDP host checks, identifying opponents, preventing abusive/duplicate listings and diagnosing problems. A country may be inferred from an IP address.
• Match information: player identifiers, both players' IP addresses, in-game profile names, characters, results, scores, timestamps, ranks/ratings, match identifiers and replays. Used for recording and synchronizing results, matching reports, rank calculations, statistics and replay access.
• Messages and inquiries: chat and play/watch requests, author information, timestamps, feedback, bug reports and contact details. Used for communication, notifications, synchronization and support. Feedback contents, author information and versions may be sent to a Discord destination used for handling reports.
• Usage information: cookies and similar identifiers, access times, visited pages, browser/device information, access and error logs. Used for sessions, visitor counts, analytics, maintenance and security.

The client inspects running processes/modules, target game memory and replay files to detect Hisoutensoku and supported tools and automate listings and match records. Settings, logs and match records are also stored on your device; match information is synchronized with the server when logged in.

We may receive listing, match and related information from opponents' clients or integrations. An opponent may record your in-game name and results even if you do not use the asobby client yourself.

2. Visibility and dpalette integration

The lobby, lobby chat and player profile viewing/search generally require Discord login. Public profile information includes Discord identifiers, public profile fields, rank, the rating for Ph players, total matches and distinct opponent counts. Listings provide other users with the IP address and port needed to connect.

dpalette is operated by the same operator as asobby. Listing/chat synchronization uses display names, Discord user IDs, ranks/status, comments, stream URLs, chat text and timestamps. Connection addresses are included in the integration API only where the administrator has granted that permission.

Information posted to Discord is also sent to Discord and is visible to people with access to the destination server/channel. The audience can differ from the asobby lobby. Other API/webhook integrations operate within the information and permissions configured by the administrator. You can ask the contact below about actual destinations and shared fields.

Names and Discord IDs supplied by an integration may be claims made by that source, not identities verified through asobby login. A listing ending, a setting changing or information being deleted in asobby does not necessarily make the same change to Discord posts or copies already obtained by others.

3. Dates of birth, age and aggregate statistics

Your full date of birth is not exposed to other users in profile or search APIs. You can review it in your own profile editor.

We provide aggregate distributions and match/character statistics by age band, rank, country, device and similar categories. These aggregates include players whose individual character win rates are private. A secret date of birth does not exclude a player from statistics unrelated to age.

Statistical responses omit individual names, IDs and dates of birth. Groups of fewer than 5 players and some other totals/buckets that could reveal small counts by subtraction are suppressed. Making your individual win rates private does not hide public replay results or records held by your opponents.

4. Replay storage and publication

Clients send eligible match replays for server storage. Stored replays and their match times, names, characters and results can be searched and downloaded without login. Search results and replay filenames include in-game names.

You can limit new uploads using the replay-saving refusal setting in the client or other provided settings. New replays are not stored unless both players are identified as logged-in asobby users, and storage is blocked when the server confirms either player's refusal. Synchronizing a setting to the server requires a working connection.

Refusing replay saving, stopping use or uninstalling does not automatically delete or unpublish past replays. They remain stored and public together with in-game names and match information to maintain match history and provide replay viewing. Requests for deletion or restriction are handled through section 8 in accordance with applicable law and service terms.

asobby cannot directly delete files that other people have already downloaded.

5. Cookies, local storage and external services

Cookies maintain login sessions and visitor identifiers. Local storage retains language/display preferences and cached match records. Login and visitor cookies expire 30 days after issuance. You can delete or restrict browser storage, but some features may stop working.

Some web pages use Google Analytics, which sends information such as visited pages and browser/device details to Google using cookies and related technologies. See how Google uses information. Supported browsers can use the opt-out add-on. This policy page itself does not include analytics tags.

• Fly.io: server hosting and file storage.
• Neon: database storage of accounts, profiles, match records and replays.
• Discord: login, avatar display, listings, chat and support integrations.
• dpalette: listing/chat integration run by the same operator.
• Google Analytics: website usage analytics.
• GitHub: client update information and downloads. Update checks may connect to GitHub directly.

Country inference uses a server-side MaxMind GeoLite2 database rather than sending each user's IP address to MaxMind for lookup. Connection assistance such as AutoPunch exchanges necessary connection information with its corresponding relay service.

Opening the Stripe support link or a user-provided stream/social link also sends access information to that destination. Consult the destination service's policy for its information handling.

External services may process information outside Japan. You can contact us about the storage regions in use and security measures.

6. Retention and stopping use

There is no dedicated account-closure feature or procedure for stopping use. Exit the client and, if desired, remove its executable, settings and local match files. Removing only the executable may leave settings, logs and records on your device.

The server cannot detect uninstallation. Stopping use or logging out does not automatically delete or unpublish stored profiles, Discord identifiers, names, match records or replays. Removing your client also does not stop information received from an opponent's client, dpalette or another integration.

Account/profile information is retained for identification and continuity of settings and records on returning. Match records, in-game names and replays are retained for history, statistics and replay access. These categories currently have no uniform automatic age-based deletion deadline. This is not unconditional permanent retention: information no longer needed for its purposes, or requiring action under applicable law or terms, is subject to deletion or restriction.

IP addresses and logs are handled as needed for matching reports, troubleshooting and abuse prevention. Normal chat display covers up to 100 messages from the last hour, but disappearance from the display and removal from persistent storage may not occur together. A listing ending does not delete related match records, logs or integration copies.

Backups and copies in external services may not be deleted at the same time as primary records. When handling requests, we check the affected information, applicable law/terms and storage mechanisms. You can also ask about specific retention periods and the scope of processing.

7. Security

We use HTTPS for web/API communications, authentication and administrator/integration permissions to help prevent unauthorized access and disclosure. Game connections and UDP traffic use mechanisms separate from HTTPS. We do not guarantee that every item of information or connection is encrypted, or that all risks can be eliminated.

Information is handled as needed for operation and maintenance. If an incident occurs, we investigate, remediate and make necessary notifications in accordance with applicable law and terms.

8. Access, correction, deletion and restriction requests

You can edit your profile and visibility settings in the provided editor. For requests or complaints concerning access, correction, deletion, restriction or stopping third-party disclosure, use the contact below. No asobby login or post in a public channel is required.

Please provide information that identifies the affected data, such as your Discord user ID or profile/replay URL, and the action requested. We verify identity using the minimum information needed and handle requests according to applicable law and terms. Do not send passwords, session tokens or API keys.

Discord API data is deleted in accordance with Discord's developer terms when the relevant user requests deletion, when retention is no longer needed for the functionality, and in other required cases, except where retention is legally required. Requests requiring deletion or restriction of in-game names, replays or other information are also handled individually; we do not apply a blanket refusal.

If you cannot contact us through Discord, use email. The same contact accepts inquiries about operator information, purposes, retention and security measures.

9. Changes to this policy

Changes in information handling and their effective timing will be announced here or through other appropriate notices. Where law or external service terms require consent or other steps, those steps will be taken separately. Publication of this policy or continued use alone is not treated as obtaining every necessary consent.