MAINLAND Privacy Policy

Effective date: November 3, 2026

Joseph S Apps, LLC (JosephSApps) develops MAINLAND, including development builds named “Mainland AI Character.” This policy describes information processed by the current MAINLAND virtual reality prototype and our related support. It does not describe features that have only been proposed for future releases.

For privacy questions, corrections, deletion requests, or security reports, email itsjosephsapps@gmail.com with the subject “MAINLAND Privacy.”

Information used to run MAINLAND

VR movement and interaction. The app processes headset and controller positions, rotations, and controller inputs to move through the world, animate avatars, operate controls, and display mirrors. These are used during play. The current avatar integration does not request raw camera images, eye tracking, facial tracking, or microphone input for avatar animation.

Meta avatars and account access. MAINLAND includes official Meta avatar presets. Where personal Meta avatar access is available and you choose “Use my Meta avatar,” the app checks access to MAINLAND through Meta’s platform and requests your Meta user identifier and an access token to load your avatar. Meta may return profile information allowed by the approved permissions; MAINLAND currently uses the identifier to load the avatar, rather than building its own profile or friends database. Our integration keeps the identifier and token in running memory and does not deliberately write them into MAINLAND save files or logs. Meta’s SDKs and services handle their own account, avatar, network, and cache processing. MAINLAND does not ask you to give JosephSApps your Meta password. If Meta avatar access is unavailable, the Meta welcome shows that status; it does not switch to an AI avatar-creation service.

Local saves. App storage on your device can contain gameplay and comfort preferences, local world and test parcel records, and home-access preview records. Saved custom avatar appearances, avatar slots, generated-model files, and design/request records from earlier test builds may remain so updates preserve your existing data. Home preview codes are stored as salted derived verifiers, with local attempt-limit information, rather than as readable six-digit codes. These codes and parcel claims are local prototypes, not secure ownership or purchases. Verified-email code recovery is not active.

Optional network and website features

Nearby multiplayer. If you choose to host, find, or join a private nearby room, MAINLAND uses local-network addresses and room/session identifiers. The host and connected devices exchange game actions, results, seat/presence information, and avatar head/controller poses so participants can see shared activity. These private LAN prototypes are separate from an Internet-hosted world. Nearby room traffic is not encrypted in this prototype; use it only on a network you trust. Other participants can see shared actions and may retain information they receive. Internet hosting, Unity Authentication/Relay sessions, and in-app voice chat are not active in this build. Quest People calls and messages are managed by Meta, outside MAINLAND; the friend helper does not read your contacts, messages, or call audio.

In-world television. Turning on the supported cinema TV opens an Android WebView inside MAINLAND, with YouTube as its starting website. Sites you visit receive normal web requests, including your IP address, browser/device information, page addresses and interactions, and any information you enter or submit. Their privacy policies apply, including Google’s Privacy Policy for YouTube. Signing into a site sends account information to that site. The app does not provide a separate password manager or collect website credentials for a JosephSApps account.

The TV permits HTTPS navigation, enables JavaScript and website storage, and blocks third-party cookies in its WebView configuration. This does not prevent all third-party web requests or tracking. First-party cookies, website storage, cache, and history can remain on the device between sessions. Use the TV’s “Clear site data” control to clear its stored browsing data; turning the TV off is not the same as clearing it. Clearing local site data does not delete a website account or information already held by a website. The current TV denies website microphone/camera permission requests and does not offer file uploads or downloads. Website video audio is playback, not microphone recording.

Diagnostics, support, and service providers

Development testing can produce local application/engine logs, error and performance measurements, screenshots, diagnostic browser frames, and copies of save files. When a tester authorizes device diagnostics or shares information for support, the development team and its support tools may handle these records and backups to investigate problems and preserve test data. If you contact us, we receive your email address and the information you send. Do not send passwords, access tokens, or payment-card information.

Meta, Unity, the device platform, and websites may process technical or diagnostic information through their components under their own policies. MAINLAND’s current application code does not operate an advertising, billing, or general analytics service. This is not a promise that the device, SDKs, hosting providers, or websites make no network requests or collect no diagnostics. See Meta’s supplemental privacy policy and Unity’s game and app user privacy policy.

The current normal Meta-avatar flow has no live AI generation service or live voice integration, and MAINLAND has no real-money land, clothing, or in-game purchases. Websites visited on the TV may have their own terms, subscriptions, or charges. Earlier explicitly authorized AI pilot records can remain among preserved local test files. Future AI, voice, commerce, or Internet multiplayer services will need their own implementation and updated disclosures before use.

We do not sell, rent or trade Meta account or device user data, or use it for targeted advertising. Information is processed for the functions described above, support and applicable legal obligations. This public policy page is hosted by Google Firebase Hosting, which receives normal website-request information; hosting the page does not upload your MAINLAND headset saves.

Storage, requests, and your choices

Local data remains in app storage until it is removed, replaced through normal app operation, or cleared using the device’s available app-data controls. Device or operating-system backups may have separate retention behavior. Development/support copies and email records can remain separately from headset storage; there is no automatic synchronized deletion or fixed retention timer in this prototype. We use support and diagnostic records to resolve issues, maintain the prototype, and meet applicable obligations.

To ask about, correct, or delete information JosephSApps holds, email itsjosephsapps@gmail.com, subject “MAINLAND Privacy,” and describe your request and the app/build involved. We may ask for limited information needed to locate records or verify your authority. For information held only on your headset, we can explain the relevant local-data steps; we cannot remotely erase a headset through the current app. Meta account/avatar data and website account data must also be managed through those providers’ privacy controls. We will handle requests in accordance with applicable requirements, including removing data no longer needed where required.

Age and updates

MAINLAND is intended for people 13 and older, subject to platform age requirements and any higher age restrictions for particular content. It is not directed to children under 13. This statement does not mean the current prototype has implemented an independent age-verification system. Contact us if you believe a child under 13 has provided personal information to us.

We will update this policy when our practices change. The effective date identifies this version. Questions and security concerns can be sent to itsjosephsapps@gmail.com.