Privacy Policy

This policy describes the data used to provide Hush Messenger and this website.

Data and storage

Hush uses backend services to store account records, connections, access codes, messages, media and subscription status. The app also uses local storage and caches. This website sets no cookies and runs no trackers; the app uses usage and subscription analytics.

Account and connection information

The current default signup does not require a phone number or email. It creates an authentication account, then requires a username. The service holds account identifiers, connections, requests, notification preferences and custom contact names where used. Phone-based signup also remains implemented for clients that use that route.

Six-digit chat and Private Space codes are stored in readable form by the backend. There is no in-app forgotten-code recovery or master unlock; that access policy does not mean the server cannot read the codes. Do not assume an account without recovery credentials can be restored after losing its session, reinstalling or changing devices.

Messages and chat media

Messages and supported chat media use server storage as well as device storage or caches. Messages expire in the conversation, with expired placeholders possible; server cleanup occurs later. Expiry is not deletion on read and does not remove copies another person saved or photographed. We do not promise a deadline for erasure from every backup or provider record.

Private Spaces and imported media

Private Spaces hold your own photos and videos in backend storage and use a local media cache for access. Space items do not use the chat expiry timer; they normally remain until you delete them, subject to service availability. Forgetting a code makes contents inaccessible through the app and does not delete stored bytes.

Importing from Photos makes a copy: the original remains in Photos. Private Spaces uploads can preserve embedded photo or video metadata, including location information. The absence of a location permission does not mean that uploaded media contains no location data.

Hush is not end-to-end encrypted. Codes control app access; they are not encryption keys. Private storage access controls do not provide a guarantee against server access, device examination or independently saved copies.

Private Spaces are advertised in the iPhone listing. Android release availability of this feature has not been established here; check the features in your released app.

Notifications and app analytics

Hush uses Firebase Cloud Messaging for push notifications and Firebase Analytics for app usage events. Account, app-instance, device and interaction information can be processed by these services. Message pushes use generic new-message text, but can show the sender's name by default. Per-contact controls let you show the name, hide it or mute message notifications. Requests and other alerts can show identities.

The website's no-cookies/no-trackers statement applies to this static website, not to the app's analytics, hosting access or security logs, or linked app stores and other services.

Subscriptions and payments

Apple or Google handles in-app checkout and payment methods. Hush does not directly collect card details for that checkout. RevenueCat manages offerings and subscription status, using purchase and customer records; the backend stores the Plus entitlement state. Payment-related records exist even though the store handles the payment method.

See current prices, billing periods and any eligible trial in the app and store checkout. Manage or cancel the subscription through the store used to purchase. Deleting the app or account does not cancel a subscription.

Service providers and support

Hush uses Supabase for authentication, database, media storage and backend operations; Firebase for configuration, push delivery and app usage analytics; RevenueCat for subscription status; Apple and Google for distribution and in-app purchases; and Firebase Hosting for this website. Those services process information needed for their respective roles and have their own data practices.

If you contact support, we receive the information you choose to send and the contact details needed to reply. Avoid including private message content or access codes unless you intend to disclose them.

Deleting your data

Use the in-app account-deletion flow or the linked account-deletion instructions to request removal of account data. Private Spaces and their items also have deletion controls. Cleanup can involve backend jobs; we do not promise instant erasure of every copy, backup or billing record. Cancel subscriptions separately in Apple or Google account settings.

Updates To Our Privacy Policy

We may amend or update our Privacy Policy. We will provide you notice of amendments to this Privacy Policy, as appropriate. Please review our Privacy Policy from time to time.

Contact Us

If you have questions or issues about our Privacy Policy, please contact us at hm_support@myriadloop.com.

MYRIADLOOP PTE. LTD.
20 Collyer Quay, #09-01
Singapore 049319

Related