Privacy Policy

This notice covers Earth 256D on the web and in the Android app. References to “Earth”, “we”, and “us” mean the operator of this service. The operator’s legal name, country, and privacy contact still need to be confirmed before this draft becomes the final policy.

Account and profile information. Your sign-in email, account identifiers, information supplied by your sign-in provider, display name, username, bio, and chosen avatar or profile photo.

Conversations and activity. Messages and associated information, such as sender, conversation, dimension, timestamps, replies, delivery or read state, and dimension-specific interactions. We also store invitations, chat requests, blocks, privacy preferences, and dimension visits needed for the features you use.

Devices and service operation. Linked-device and session information, notification tokens or browser push subscriptions, notification preferences, and app presence. Hosting and delivery systems may also process IP addresses, browser or device details, request timestamps, and operational logs.

Website usage. The website includes Vercel Web Analytics to measure visits and usage. Provider settings, log retention, and the complete production data inventory must be verified before publication.

Yes. Messages are not end-to-end encrypted. Message content is stored in a form that Earth’s backend systems can read. Earth personnel with privileged database access can read stored message content.

The app uses account and conversation access checks to restrict ordinary users to conversations they are authorized to access. These checks do not prevent privileged database administrators or backend credentials from accessing message content. They do not mean that every member of the Earth team has database access.

Encryption of connections, underlying storage, or local caches does not change this limitation. Do not assume that a dimension’s name or visual behavior gives a conversation additional encryption.

People in your conversation can see the messages and conversation information that its dimension makes available to them. They may copy, photograph, or otherwise keep information they receive. Earth cannot remove copies kept outside the service.

Privacy settings let you control exact-username discovery and public profile link visibility. Turning these off does not remove information already shared with conversation members or copies another person has kept. Treat invitation links and QR codes as access information and share them carefully.

Earth uses account and conversation information to sign you in, display profiles, deliver and synchronize conversations, apply dimension mechanics, and maintain your preferences. Device and notification information supports device linking, session management, presence, and notifications you enable.

Technical information supports troubleshooting, reliability, security, and prevention of misuse. Website analytics helps us understand use of the website. Any additional use of message content for advertising, AI training, or human moderation must be separately confirmed and described before publication; this draft makes no promise about an unverified practice.

The current integration uses Supabase for accounts, databases, storage, and realtime conversation delivery; Vercel Web Analytics for website usage measurement; and Expo’s push service for Android notifications. Browser push services and operating-system notification providers also participate in notification delivery. If you use a third-party sign-in provider, that provider processes the sign-in under its own policies.

Notification delivery involves sharing device delivery identifiers and notification payloads with the relevant providers. Notifications may appear on your lock screen or other visible surfaces according to your device settings.

The production hosting and email providers, processing locations, international-transfer arrangements, and provider retention settings remain to be confirmed. Providers’ own policies explain their processing; Earth remains responsible for describing the processing it directs.

If you choose a profile photo, the selected image is uploaded to provide your avatar. Photo-library access supports selecting that image. Where QR scanning is available, camera access supports reading a code; it is not permission to publish your camera feed.

You can manage notification preferences in Earth and revoke device permissions through your browser or operating system. Turning notifications off does not delete your account or message history.

Earth uses browser cookies, local storage, and app storage for sign-in, theme and other preferences, and cached information that supports loading and synchronization. Web and Android clients include encrypted local conversation caches. These caches do not make server-stored messages end-to-end encrypted. Signing out or uninstalling the app must not be treated as a request to delete server data.

A message fading, expiring, being hidden, or becoming unavailable in a dimension does not establish that all copies have been erased. Dimension behavior can affect visibility or history separately from cleanup of database records, local caches, logs, and backups.

Account and ordinary conversation information is stored to support the service. This draft does not promise a fixed deletion period. Retention periods and the cleanup of expired messages, operational records, and backups still need to be verified and documented before publication.

Any final retention policy must explain what is removed, when removal happens, and what may be retained for a specific legal or security reason.

You can edit your profile, change discovery and public-profile settings, manage notifications, block people, and manage linked devices through the available settings.

The current Account settings do not provide self-service account deletion or a downloadable data export. Signing out does not delete your account. A working request contact and deletion process must be added before this policy is finalized.

Depending on the law that applies to you, you may have rights to access, correct, delete, or obtain a copy of personal information, object to certain processing, withdraw consent where processing relies on consent, or complain to a data protection authority. The final policy must identify the request route, relevant legal grounds, and any applicable exceptions.

The minimum age and any parental-consent requirements are still being decided. This draft does not establish a children’s service or claim that an age-verification system is in place. Eligibility rules and the handling of information from underage users must be confirmed before publication.

Updates will carry a revised date. Material changes should be explained through the service before they take effect where required by applicable law. The final policy will include a working privacy contact for questions and requests.