HearMeOut Privacy Policy
Last updated: 6 November 2026
This policy explains how HearMeOut handles information when you use its community, messaging, jobs, marketplace, events and reporting features. It covers the Android app (package com.labs28.hearmeout), earlier HearMeOut installations and the associated backend. HearMeOut is the app/service name; this policy does not identify it as an incorporated company.
For privacy questions, access or correction requests, or deletion assistance, contact the HearMeOut app support team at hearmeout410@gmail.com.
1. Information we collect
- Accounts and profiles: phone number, email address, full name, nickname and password at registration; optional biography, profile photo, location, organisation/role and verification information. Account IDs, creation dates, subscription status and preferences are stored. Server account passwords are stored as bcrypt hashes.
- Posts and community activity: post and comment text, photos/videos, categories, tags, hashtags, alerts, reports, likes/dislikes, follows, bookmarks, shares and viewing/activity records. Forum posts can use a generated name or alias. An alias does not prevent identification through the text you share.
- Messages: message content, attachments, sender and recipient IDs, timestamps, read status and reactions. Messages are stored on the server to provide delivery and conversation history; they are not end-to-end encrypted.
- Jobs and CVs: job-seeker contact information, location, photograph, skills, qualifications, certifications, experience, CVs and supporting documents; job listings, applications, cover messages, portfolio links, salary expectations, reviews and application status.
- Marketplace and events: listing descriptions, prices, photographs/videos, location and seller contacts; event and venue details, coordinates where supplied, organiser contacts, RSVPs, saves, comments and interaction records.
- Missing-person and alert reports: names, age, photographs, physical descriptions, last-seen details/coordinates, circumstances, reporter contacts/relationship, police case references and health information if supplied. Only provide another person's sensitive information when you have an appropriate basis to do so.
- Location: location text you enter and precise GPS coordinates when you choose a current-location feature and grant device permission. Coordinates may become part of a report you publish. The inspected app requests foreground location for these features, not continuous background location tracking.
- Notifications: device push tokens, platform, notification preferences, notification content, related record IDs and read status.
- Payments, when enabled: account phone number, selected mobile-money network, amount, currency, transaction/provider references, payment result, timestamps and subscription entitlement. The inspected release disables the subscription purchase UI; the backend supports test payments and a configurable Xyle mobile-money integration. HearMeOut's implemented payment flow does not ask you to enter a mobile-money PIN or card number into HearMeOut.
- Technical and usage information: IP address and user-agent for account sessions, device identifiers/names if supplied by the client, authentication/session records, search queries and categories, views and interactions, and operational/error logs. Optional connectivity diagnostics contact Cloudflare's 1.1.1.1 service, which receives normal connection information such as your IP address.
- Support: information you send to the support email, including account identifiers, correspondence and any attachments you choose to include.
2. Why we use information
We use information to register and authenticate accounts; show profiles and content; deliver messages and notifications; provide jobs, applications, marketplace listings, events and reports; personalise search and listing results; maintain preferences; manage subscriptions when enabled; respond to support/privacy requests; and operate, troubleshoot and protect the service.
3. What other people can see
Content you publish and profile information displayed by a feature can be visible to other users. Candidate profiles expose the contact details and documents you choose to include to users browsing candidates. Job applications are shared with the job poster. Seller and organiser contact information may be displayed through the relevant feature. Message content is delivered to your recipient.
Uploaded-file links: supported document downloads require sign-in. Application CVs are available to the applicant and job owner; CVs and supporting documents included in published candidate profiles are available to signed-in users browsing candidates. Image/video and other uploaded-media links can still be accessible without signing in, including message media. Do not upload secrets or media that require strict access control. Removing a listing or database record does not necessarily remove the underlying file.
Other users can download, copy, screenshot or share information they receive. We cannot remove copies held independently by those users. Anonymous forum posts have no stored account association in the current implementation; non-anonymous posts can contain an author ID. Anonymous posting is not a guarantee that content or connection records cannot identify you.
4. Service providers and external services
The service uses Railway-hosted infrastructure for the backend and database, Expo for app updates and push delivery, and Google/Firebase Cloud Messaging for Android push notifications. Push providers receive tokens and notification payloads, which can include actor names and activity descriptions. Updates involve normal device/network requests to Expo. Do not assume notifications shown on a lock screen are private.
When live mobile-money payments are enabled, Xyle and the selected MTN/Airtel network process the phone number and payment details required for that transaction. Test/mock payment processing does not initiate a live network charge. Support email is handled through Gmail. Optional connectivity checks contact Cloudflare. Providers may process information in countries other than your own under their own applicable terms and policies.
Links to maps, WhatsApp, LinkedIn, email, websites, ticketing services and device sharing tools open external services chosen by you. Information you send there is handled under those services' policies. HearMeOut does not sell personal information. Information may also be disclosed when required by applicable law or necessary to respond to abuse, security incidents or lawful requests.
5. Device permissions and local storage
Camera, media/file selection, location, microphone and notification permissions are used by the features that request them. You can decline or revoke permissions in device settings, although dependent features may stop working. Selecting a document or photograph uploads that item when you submit the relevant feature; it does not mean every file on your device is uploaded.
The app stores authentication tokens, cached account information, preferences and feature caches locally. Mobile authentication storage uses Expo SecureStore; other feature caches use app storage. If you save login details, your identifier and password are saved on the device for autofill. The web version uses browser storage for several of these functions. Local app-lock PINs use device storage; biometric authentication uses the operating system and does not send fingerprint or face templates to our backend. Downloads and files shared to another app can remain on your device independently of your account.
6. Security
The production service uses HTTPS for network communication and authenticated API requests for account operations. Password hashing and device secure storage help protect credentials. These protections do not constitute a guarantee of absolute security, do not make server-stored messages end-to-end encrypted, and do not restrict access to uploaded-file links as described above.
7. Retention and deletion
Account information and content generally remain in the service while your account or the relevant records exist, until removed through an available feature or a verified deletion request. Search/activity history and independently stored records do not currently have a universal automatic expiry. Hosting/provider logs and any backups follow the applicable infrastructure retention settings rather than an app-wide guaranteed expiry period. Contact us for questions about a specific record or retention requirement.
You can initiate account deletion through Profile → menu → Delete Account, or use the external account-deletion request page. In-app deletion checks your password and deletes the account and database records linked by cascading relations, such as sessions, settings, messages, notifications, job profiles/applications and other linked activity.
Current deletion limits: account deletion also removes owned marketplace and missing-person records, account-linked forum posts, viewing records, reset codes, blocks and reports you submitted. Uploaded files and anonymous forum posts are not automatically erased. If deletion fails or you need these remaining records removed, email us using the deletion-request page so the request can be verified and handled manually. For an anonymous forum post, include a link, screenshot or identifying details because it is not linked to an account. We do not claim that the in-app button alone removes all data.
Uninstalling the app does not delete the server account. Saved login entries and exported/downloaded files may need to be removed separately. Information retained by independent recipients or payment/support providers is subject to their responsibilities and retention rules. Any necessary retention for a legal obligation, security investigation or dispute will be explained when applicable; we do not specify an unverified fixed retention period.
8. Your choices and requests
You can edit available profile details, change notification preferences, revoke device permissions, remove content where a delete control is available, and request account deletion. Contact hearmeout410@gmail.com to request access, correction or deletion of other information, or to raise a privacy concern. We may need proportionate information to verify that a request relates to your account; do not send your password, mobile-money PIN or identity documents unless a justified secure verification process has been agreed. Applicable privacy rights depend on your location.
9. Children and information about others
HearMeOut records which version of the Terms and Community Rules users accept. The current app does not ask users to confirm their age. Accounts created or updated under the previous policy may still have a record of an earlier age confirmation. Contact us to report a child-safety concern.
Some features allow users to submit information about other people, including children in missing-person reports. Avoid unnecessary sensitive details and contact us to request correction or removal of such information. A public privacy policy does not replace the app's age/audience settings or the publisher's child-safety responsibilities.
10. Policy changes and contact
We update this page when data practices change and revise the date above. Material changes requiring additional notice or consent will need that notice or consent before the new use begins. Privacy and deletion contact: hearmeout410@gmail.com.