Hosted
Use a server managed by an operator. If you have an invitation, use the account address and invite they supplied.
Availability, subscription terms and checkout come from the selected service.
Open hosted setupStart with your account
Account setup
Use the server your operator gave you, then keep a way to recover access.
Export or erase your signed-in account data
Choose your service
Hosted or self-hosted?
Already have an account on this server? Sign in and continue to your phones.
Account · create
Register an invited owner
Use the email address on your invitation. Your operator must allow registration and may require an invite token for that address.
After registration, verify your email below. If the request is interrupted, try again or ask your operator to confirm your invitation.
Account · verify
Verify your email
Enter the code from your ZROtext verification email together with the password you chose at sign-up. Keep the code out of links and URLs. If you did not sign up, ignore the email.
Request another code
Email verified? Sign in to connect your phone.
Keep access safe
Authenticator and recovery codes
Add an authenticator, confirm its code, then save your recovery codes. Keep them somewhere you can reach if you lose your phone. A recovery code is used only once.
Add this secret to your authenticator. It is shown only during setup and is cleared when you leave the page.
Provisioning URI for apps that accept manual import:
Save these recovery codes now. Each code works once. They are cleared when you leave this page.
Review where you are signed in under Security & sessions. Your SMS line approval key is managed separately on SMS lines.
Account · your data
Export or erase account data
Download the server takeout
Download private JSON parts to your own device. Each part contains the server's original responses, including message content and contacts where available. Keep every part somewhere safe.
Sealed content stays encrypted. This is not a key backup or a database backup. Retention may already have removed content; some sections contain only metadata. Line setup includes at most 16 registrations and 16 exchanges without further pages. Data can change between requests.
Each step reads at most eight pages, with an 8 MiB page limit and a 32 MiB part limit. Continue until all exposed pages have been retrieved. Responses may repeat completed families; parts are raw pages, not a deduplicated record list. Export stops at 4,096 distinct continuation cursors; contact the operator if that safety limit prevents completion. Leaving this page clears continuation and download links.
Download this JSON partErase this account on this server
This permanently deletes the account and its invited observer users in one transaction if the server permits it. Line identities, immutable trust or audit history and other retained references can block the whole request. Nothing is deleted when the server reports blockers.
Erasure does not cancel external subscriptions, release carrier identities, delete external copies, or rewrite backups, replicas or WAL archives. Export first if you need a copy.
An account-ID record may remain for the app's database lifetime to prevent identity reuse. It contains your account ID, deleted state, and a version counter. The receipt lists this retained identity record and shared request-budget counters when present.
Local template preview · Preview personalized text without sending or saving it.