DOTWORLD

Public release is being prepared.

Privacy and encryption

Information and purposes

The operator is JongYun Kim. We process app account identifiers, Apple/Google service-specific identifiers, authentication attempts and sessions, public device authentication/encryption keys and identifiers, and protected provider tokens. These support sign-in, linking, recovery, deletion, delivery and abuse prevention.

Apple/Google authentication responses are processed for verification and interrupted sign-in recovery. Information included by a provider in an ID token may temporarily be held inside an encrypted recovery record. We do not use names or email addresses as account-ownership evidence, automatically populate a DotWorld profile from sign-in responses, or merge accounts because email addresses match.

We process the nickname, biography, selected continent/country, private age and display language supplied for your profile and settings. Registration requires age 16 or above. Age is self-declared; a profile or entered age is not verified identity or age assurance.

Conversation partners can see the public profile needed for conversations and friendships. Age and friend counts are not public, and only you can view your friend list. In-app friendships do not read your phone address book, and continent selection does not use precise GPS location.

We process friend requests/relationships, blocks, conversation region/topic/time/membership, booking/readiness/admission and participation-ticket records. Connection IP addresses are used in the network/security path; the distributed request limiter uses keyed pseudonymous identifiers. Request status, errors and timing information may support reliability and abuse prevention. We do not provide advertising tracking or combine activity with other companies’ apps/sites for tracking.

Cloudflare Workers provides API execution/delivery and service protection; Supabase provides PostgreSQL storage. The current primary database region and Workers placement configuration use the Seoul region (ap-northeast-2). This does not guarantee that network, authentication, support or all other processing stays in Korea. Apple provides Apple sign-in, supported device translation and app distribution. Google provides optional Google sign-in and email handling for the designated Gmail support address. Providers process information required for their services under their own terms and policies.

Messages and translation

New encrypted conversation content is encrypted and decrypted on participant devices. The server handles ciphertext and the membership, delivery and timing metadata needed for communication. The operator cannot erase a participant’s independently saved copy or screenshot.

Comparing safety codes through an independent channel checks whether keys match; it does not certify a person’s legal identity. A known key change blocks sending until explicitly acknowledged.

Supported Apple translation processes decrypted messages on the iPhone. DotWorld does not send conversation plaintext to its server for translation. Language-model downloads may be required; unsupported devices or languages display original text. Translation accuracy is not guaranteed.

Reports and support

After you preview the selected original message, author and time and consent to disclosure, that selection, your report reason and related identifiers are sent to the server. A report does not include the whole conversation or encryption keys. This is voluntary plaintext disclosure, separate from ordinary encrypted delivery.

Report evidence is a selection submitted by the reporting device, not independent proof of a whole conversation or authorship. JongYun Kim personally reviews reports and can impose or restore time-bounded participation restrictions with recorded reasons when warranted. Submitting a report does not guarantee automatic sanctions or an immediate emergency response.

Support email includes the address and information you choose to send. Questions, additional evidence and appeals can be sent to kimjyun0808@gmail.com. Do not send passwords, verification codes or encryption keys.

Retention and account deletion

Ordinary chat history and encrypted delivery content become eligible for server cleanup 24 hours after a conversation ends. Expired device history is removed on later launch, access or cleanup. Actual removal depends on subsequent maintenance runs and failure recovery. It does not erase other participants’ independent copies or screenshots.

Selected report evidence uses a cleanup threshold of 30 days from the original report. Related review records follow their defined retention rules; a late review does not extend the report-evidence period. Account deletion removes your authored messages and reports about those messages. Reports about another author may remain within the original period after removing the reporter link and reason.

Encrypted sign-in recovery responses are removed when the device acknowledges storage. Expiry is at most 24 hours, capped by session expiry; expired copies are removed by subsequent cleanup. Incomplete provider-exchange data follows authentication-request expiry. Authentication attempt/completion context is cleaned after 30 days once active-session and recovery-data references no longer require it.

Sessions are limited by a 30-day maximum, seven-day inactivity, logout or account deletion. Expired or revoked session records are cleaned separately. Account deletion revokes access first, clears or de-identifies profile information, and clears friendship/block relationships and participation state. It does not physically erase every minimal record at the same moment.

If Apple/Google authorization revocation is unresolved, protected provider tokens and job information are retained for retries. Tokens are removed once revocation succeeds or the provider confirms they are already invalid. Re-registration through that provider identity may be blocked in the meantime. These unfinished jobs currently have no universal automatic final expiry.

Limited security records can remain after account deletion, including hashes preventing reuse of deleted authentication keys, some authentication/revocation-completion history, and participation/ticket integrity records. They support replay, duplicate-processing and abuse prevention. A fixed automatic deletion deadline is not currently implemented for all of these records. You may ask the operator to review retention necessity or an access, correction or deletion request.

Where copies exist in infrastructure-provider-managed operation logs or backups, the provider’s storage and restoration processes also apply. Deleting data in the app does not guarantee immediate removal of every copy. Contact the operator about residual information and deletion handling. You can delete your account in Settings → Delete account.

Device keys and recovery

A guest proves ownership using a separate authentication key on this device. Losing that key without a linked Apple/Google sign-in method prevents recovery of the same guest account.

Recovering an account through Apple or Google does not restore lost conversation-encryption keys. Logout, app-data loss or a device change may make earlier encrypted conversations unrecoverable.