PRIVACY & TRUST
Trust starts with a clear explanation.
You should understand how your conversations work before you bring someone into them.
Who can see a conversation?
Across restricts chat access to authorised conversation members. Direct chats and groups have membership checks. New group members can see the group’s existing history. Someone who leaves or is removed may still have copies of messages they previously saw.
How translation works.
Message text is sent to DeepL for translation. Original messages and generated translations are stored so members can read the conversation and revisit earlier messages. Across does not provide end-to-end encryption.
Your account and preferences.
Across uses SpacetimeAuth for email sign-in and SpacetimeDB for application data. Your profile, language preferences, contacts, conversation membership, and messages support the experience. Administrators have tools for pilot access, usage, and moderation; don’t assume that membership controls mean the service operator has no administrative access.
Notifications and presence.
If you enable notifications, Across stores a browser push subscription for that device. Notification previews contain sender and group information rather than message text. Presence and typing indicators help conversation participants know when someone may be available; typing indicators do not send or store your draft text.
Your choices.
Choose your reading language, manage notification permission on each device, and use blocking and reporting controls when needed. For an account-data or deletion request, contact the pilot administrator who invited you. This website does not offer an automated deletion process or promise a retention period.
Keep private details out of feedback.
Share only what is necessary to describe a problem. Remove message content, email addresses, invitation links, and identifying details from screenshots before you share them.
Prepare a safe report →