Security, in plain language

Current capabilities and limitations of text.gs.

Current chats are not end-to-end encrypted

The existing service uses server-managed message encryption. The service retains the ability to decrypt current messages. Do not treat text.gs as a channel where only the participants can access message content.

End-to-end encryption is in development

Device verification, recovery, encrypted message history and encrypted attachments still require integration and review. No customer E2EE switch is enabled. Old messages cannot retroactively become private from a server that already knew their keys.

Protect your account

Review signed-in sessions in the app, protect your email or phone account, and keep recovery codes private. Anyone with the credentials needed for account recovery may gain access to your account. Never give codes to someone claiming to be support.

Understand optional features

Translation, AI editing and speech features may process content outside your device depending on the selected feature and browser. Read the feature notice before using them with sensitive material. Location sharing is separate from the decorative globe on this page.

Reporting and emergencies

Use the in-app report controls to report content. Only include evidence you intend to disclose. text.gs is not an emergency communications service and does not promise immediate monitoring or response.