Security approach

We are developing HelloMate with controls for account access, content sharing and private conversations. This page describes our approach during development and private testing.

Account access

Development builds include account verification and device-related safeguards for selected sensitive actions. During development, device-verification emails have been successfully sent and received in testing. Email verification helps confirm eligible requests. These protections do not mean that every login requires a new code or that every account action has the same restrictions.

Permissions and sharing

We use authenticated access and database permission rules to control access to application data. Some content is intended for its owner, some for a conversation or connection, and some may be shared publicly by choice. We are testing these boundaries, including blocking and changes to sharing settings.

Chat screen protection

Selected chat views include an optional screen-protection setting in supported builds. Its behavior depends on the device, operating system and screen being shown. It cannot prevent someone from photographing a display with another device, and should not be treated as a guarantee that content cannot be copied.

Cloud services and translation

HelloMate uses cloud services for accounts, storage and other enabled features. When cloud translation is used, the text to be translated is processed by an external AI service. Do not assume chats are end-to-end encrypted. See our privacy notice for the data categories and service providers involved.

Reporting a concern

If you find a potential security issue, contact [email protected] with a brief description and the affected page or feature. Please avoid sending passwords, verification codes or other people's private content. We may ask for further details to investigate.

This page is a product overview. It does not represent an independent security audit or certification.