OASYN is a Windows game launcher and private game platform operated by Diego Huhn in California. For privacy questions, account deletion, data access, corrections, or safety reports, contact inquiries@oasyn.online. The beta is intended for invited United States residents age 13 or older. People under 13 may not participate. If you believe an account belongs to a child under 13, contact us so we can investigate and take appropriate action. We do not treat an age declaration as verified age assurance.
We use account email and authentication identifiers to sign you in and control access. Google sign-in is optional; email/password sign-in uses Supabase. We process your display name, declared age band, country and policy acceptance to administer beta eligibility. We process your library, favorites, ratings, reports, game sessions and supported save files to provide game access, progress synchronization and support. Technical services may process connection information and logs to deliver and secure the service.
The launcher stores downloaded games, settings, account session information and game saves on your PC. Supported cloud saves are associated with your account. A save conflict requires you to choose a version. Copies on your PC are separate from server copies; deleting your account does not automatically erase downloaded files from your computer.
Supabase provides authentication, Google provides optional Google sign-in, Render is the planned API/storage host, Resend sends account emails, and Hostinger provides the domain and support mailbox. These providers process information necessary to deliver their services. Support messages are visible to the operator. Creator and reviewer accounts are currently controlled by the same operator; their review is not independent human review. Player profiles and save files are not intended as public content.
The catalog shows creator display names, game descriptions, releases and aggregate ratings to admitted players. Reports and account-linked play records are available to authorized administrative functions. Hosting and authentication providers may process network addresses and security logs when you connect. We do not ask for precise location, a full birth date, government identification or payment details in the beta onboarding flow. Avoid including sensitive personal information in display names, game content or support messages.
The limited beta has no advertising, currency, payments, public chat or trading. OASYN does not use beta account data for targeted advertising or sell it. New uses will require an updated notice and any applicable consent before introduction.
Storage and requests
Account information, library records and current saves are stored to operate your account. The save service limits historical revisions by count; it does not implement a general time-based retention schedule. The current prototype has no self-service account-deletion or data-export interface and no automatic expiry for account, report or audit records. Contact inquiries@oasyn.online to request access, correction or deletion. These requests require a verified manual process before external beta admission; the prototype must not be represented as already providing automated deletion.
The launcher uses local session storage for sign-in and browser-based authentication pages use their own service storage. OASYN does not implement cross-site advertising tracking or a special response to browser Do Not Track signals in this beta. Authentication and hosting providers operate their own pages under their privacy notices. Review the deployed website separately before applying this statement to additional web pages or analytics.
We will date revisions to this notice and present material changes through the app or account email before applying them where required. You can ask to review or correct account information by contacting the support address above. Privacy requests will not by themselves result in punishment; deletion can make an account or cloud saves unavailable because those records are needed to provide them.
Access and deletion requests must be verified without asking for passwords or recovery codes. Explain any lawful retention exception to the requester. Security measures reduce risk but cannot guarantee that all incidents or data loss will be prevented. If practices materially change, provide notice before applying the change where required.