Privacy Policy

Effective October 31, 2026 · Development preview

1. Who this notice covers

HiMessage is a messaging application currently operated as a development project by the HiMessage development team. The legal operator name, postal address and applicable jurisdiction have not yet been provided. These details must be completed before public production launch. The website and app follow this notice.

2. Information we collect

• Account: international phone number, profile name, username, bio, links, profile image and creation time.
• Authentication: verification challenges, attempts, session identifiers, device names, expiry, revocation, IP addresses used for rate limiting and language preference.
• Conversations: membership, messages, attachments, delivery/read positions, reactions, saved/pinned states and timestamps.
• Contacts: contact names and phone numbers you permit us to sync, associated with your account to find registered users.
• Calls: participants, type, status and timestamps. We do not offer call recording. Call media is carried by WebRTC and may be relayed through our TURN service.
• Location: coordinates, place/address, update time and sharing expiry when you choose to send a place or share live location.
• Support and deletion requests: your supplied phone, email, request text, time, reference and a hash of the request IP for abuse prevention.

3. Why data is used

We process information to create sessions, route conversations, deliver messages and calls, sync contacts, display profiles, prevent abuse and handle support or deletion requests. We do not sell personal information or use it for third-party advertising. Where applicable law requires a legal basis, this includes providing the requested service, permission for optional device access, legitimate service-security interests and complying with legal duties. These bases depend on the law that applies to you.

4. Permissions and your choices

Contacts, microphone, camera, notifications, location and file access are requested for their related features. You may refuse or revoke them in device settings; the feature may then be unavailable. Sending your location is optional. Live location has a chosen duration and a Stop sharing control; Android may show an ongoing notification. Updates stop when sharing ends or the operating system stops the app. Downloaded or copied data on recipients' devices is outside our control.

5. Storage, service providers and sharing

Account data and conversation records are stored on our application server. Uploaded profile images and chat files are stored in MEGA S4 object storage. Profile image URLs may be accessible to anyone with the URL; chat attachments require authenticated conversation access. Firebase Cloud Messaging delivers push notifications and processes device push tokens. OpenStreetMap tiles and Photon geographic search receive map-area or coordinate requests when maps or address lookup are used. Our server and these providers may process data outside your country. We have not independently verified a complete list of all provider processing locations.

Conversation participants receive the content you send. Groups and channels may have multiple recipients. We may disclose information if legally required or necessary to address fraud, threats or service abuse. We do not claim that infrastructure providers cannot access server-processed data.

Administrative access and moderation

Authorized administrators can view account records, synced contact names and numbers, stored message text and attachment metadata to investigate abuse and support the service. Sensitive administrator views and actions are recorded in an audit trail. Administrators may restrict accounts and send service announcements. Messages are not end-to-end encrypted; this administrative access is possible in the current system.

6. Security

Network requests use HTTPS, authenticated APIs and session controls. WebRTC encrypts call transport; TURN can relay encrypted media. Messages and attachments are not currently end-to-end encrypted. Temporary shared-code sign-in is not production authentication and materially limits account protection.

7. Retention and deletion

Sessions expire or can be revoked. Expired verification records are cleaned after their expiry retention window (currently approximately 24 hours after expiry when new codes are requested). Contacts remain until replaced or removed. Messages, media, call records and profile data currently have no automatic general expiry. Deletion requests are recorded for identity verification; automated account deletion is not yet enabled. No fixed completion deadline or backup-erasure schedule has been implemented, so we do not claim immediate deletion.

When deletion is implemented and identity is verified, it should remove your account profile, synced contacts, sessions, push identifiers and owned data as applicable; shared content already delivered to others may remain with them. Legally required security records may need limited retention. Until this process is operational, request status is pending identity verification. See the deletion page for the active process.

8. Your rights

Depending on your location, you may request access, correction, erasure, restriction, portability or objection, and complain to your local data protection authority. Optional permissions can be withdrawn in device settings. Use the request form for an account-erasure request. Other requests may be submitted through Help and feedback in the signed-in app.

9. Age and changes

The service is intended for users aged 16 or older and any higher minimum age required locally. It is not directed to children. Material policy changes will be reflected here with a new effective date; in-app notices should be supplied when required.

10. Contact

Active channel: Help and feedback in the app, or the account deletion request form. Planned mailboxes: privacy@himessage.click and support@himessage.click. These mailboxes are being set up and must not yet be relied on for delivery.