Manage your identityGuidesBrowse
Identity guide

Manage your identity

Your Auris identity starts on your phone. Choose how to introduce yourself, who can find you, and when to use an invitation.

On this page

Your ID and display name

Your Auris ID is a random string generated on the device. It gives people a way to connect without your phone number or email. Your display name is separate and travels to contacts inside the encrypted conversation.

Share an introduction

  1. Choose who to connect with

    Share your ID, a QR code or an invitation link over a channel you trust.

  2. Start the conversation

    The first message establishes an encrypted session. Your private identity keys stay on your device.

  3. Verify the contact

    Compare safety numbers to check the identity keys introduced through that connection.

Choose invitation-only discovery

Standard allows lookup by Auris ID. Enhanced and Lockdown select invitation-only discovery. A lookup without the required invitation capability receives an unavailable response.

This gives you control over ordinary discovery. Your registration remains visible to the directory operator. For the service's full data view, see the observer ledger.

Block a contact

Blocking filters the contact's calls and messages and changes the capability used to access your presence. Auris sends no explicit blocking notification. The person may infer the change and can create another identity, so control who receives new invitations as well.

Moving to a new device

The released protocol keeps identity keys in device-bound Keychain storage and does not offer linked-device identity or account recovery. A replacement device creates a new identity that your contacts need to add and verify. Losing the original device can also mean losing locally held history.

Use the explicit reset flow when resetting an identity. Deleting and reinstalling an iOS app does not reliably remove every Keychain item.

How the directory supports your identity

The directory supplies public key bundles and routing information. It also stores protocol metadata, preferences and available push tokens. It does not need an uploaded address book or a plaintext display name to do those jobs.

Directory fields and retention →

Released beta · Reviewed · Review scope and versions