Privacy Policy

Last updated: June 12, 2026

Overview

3DX Phone is built as a companion overlay for 3DXChat. The core phone experience is local-first where possible, but some services are online and need server-side data to work. This page explains what is stored locally, what is sent to 3DX Phone or DX-ID servers, and why.

Data stored only on your device

Built-in offline apps such as Calendar, Notes, Reminders, Photos, Calculator, and local Settings may store their content on your own device. This local content is not automatically uploaded to 3DX Phone servers unless a specific online feature or account feature explicitly sends data.

Website visit analytics

The website stores basic aggregate visit data: visited path, referrer host, broad device category such as desktop/mobile/tablet, request time, and a daily hashed visitor identifier derived from IP address and user agent. Raw IP addresses are not stored in the website visit table.

Downloads, updates, and device check-ins

The app may contact the server for release metadata, downloads, app status, notifications, and device check-ins. Device check-ins may store an app-generated device ID, app version, platform, and last-seen time. Server requests also create normal operational metadata such as IP address, user agent, timestamps, and error or access logs.

DX-ID account data

If you create or use a DX-ID account, the server stores your DX-ID user ID, username, normalized username key, account status, password hash, recovery hash, optional public key, refresh-token hashes, account timestamps, roles such as admin or moderator where applicable, linked devices, app links, and app access entitlements.

DX-ID profile media

If you upload a DX-ID avatar, the server stores the uploaded image as processed WebP variants such as avatar, profile, and original-size versions, plus image metadata such as width, height, byte size, media type, owner user ID, and creation time.

Friends and presence

DX-ID friends features store friend requests, accepted friendships, blocked relationships, linked user IDs, request and acceptance timestamps, online presence state, optional status text, and last-seen or updated timestamps. Presence data is used to show friend status in supported apps.

3DGRAM posts and activity

3DGRAM stores posts, captions, visibility setting, author user ID, uploaded image variants, dimensions and byte size, likes, comments, exact @username mentions resolved server-side, activity notifications for mentions/likes/comments, read status, timestamps, and soft-delete or moderation state. Friends-only posts and media are checked server-side before they are shown or served.

Reports and moderation

If you report a 3DGRAM post or comment, the server stores your reporter user ID, target type, target ID, reason, status, and report time. Admin and moderator actions may store who hid content and when. Regular users should not receive reporter identity through normal user-facing APIs.

Admin services and Discord OAuth

The website includes admin tools for managing releases, notifications, apps, prompts, games, visits, downloads, and device check-ins. Admin authentication may use Discord OAuth, which can provide Discord account identifiers, username, and avatar data and is also subject to Discord's own privacy practices.

Third-party and online app features

Some apps or integrations may contact their own online services, including weather, music, Xinder, games, app submissions, and future community features. These features may send the data needed to provide that feature, such as account identifiers, app-specific profile data, room or lobby information, messages or submissions, and technical request metadata.

No 3DXChat modification

3DX Phone is a separate companion application. It does not require your 3DXChat login, does not modify 3DXChat files, and does not intentionally inspect or intercept 3DXChat network traffic.

Security and access controls

Passwords and refresh tokens are stored as hashes, not as plaintext. Security-sensitive visibility decisions for DX-ID and 3DGRAM are enforced server-side. Media URLs may include short-lived signed tokens so normal image tags can load protected media while the server still checks whether the viewer is allowed to access it.

Retention and deletion

Server-side records are kept as long as needed to run the service, troubleshoot issues, secure the platform, enforce moderation, and maintain release or account history. Some actions use soft deletion so content can be hidden from users while moderation or abuse-prevention records remain available. Local app data remains under your control on your own device.

Contact

Questions about privacy, access, or deletion requests can be sent to the project owner through the contact channel listed on the 3DX Phone website or community page.