What Hearken collects
Account and invite details, Conversation setup data, participant replies, optional voice uploads where used, usage logs, wallet/billing events, and support messages.
This overview explains the customer-facing privacy basics for Hearken: what is collected, why it is used, who is involved, and how to ask a privacy question.
Account and invite details, Conversation setup data, participant replies, optional voice uploads where used, usage logs, wallet/billing events, and support messages.
To provide the Conversation workflow, invite people, ask follow-up questions, prepare individual reply summaries and Conversation reports, operate the service, prevent abuse, support customers, and meet legal obligations.
The creator organisation is normally the controller for its invited people. Hearken handles Conversation data for that organisation and is controller for its own account, billing, support, and service operations.
EU data subjects may have rights to information, access, rectification, erasure, restriction, portability, objection, and complaint to Malta's Information and Data Protection Commissioner.
After account deletion, Hearken may keep minimal records needed for accounting, legal obligations, privacy request handling, and preventing duplicate free signup credits. These records are not used as a marketing list.
For GDPR rights requests or privacy questions, contact Hearken at privacy@hearken.my.
Account deletion comes after you download the data you need and delete your Conversations. Signed-in creators can download and delete each Conversation from Conversation settings; then use Settings > Privacy to request account deletion or email privacy@hearken.my.
Deletion does not reset free-credit eligibility: Hearken keeps a minimal signup-credit record for emails that have already received welcome or First Listener credits, so the same address cannot receive those credits again by rejoining.
Trust and securityCookie notice