1. Summary
Tranquiliva is designed to support private reflection, wellbeing education and moderated peer connection. We aim to collect only information needed to provide, protect and improve those services.
Your private account profile is kept separate from your anonymous community identity. Journal entries are not shown publicly. Payment card and mobile-money details are handled by the payment provider rather than stored directly by Tranquiliva.
2. Information we handle
Information you provide
- Account details such as name, email address, phone number and authentication identifiers.
- Profile settings, language, accessibility, notification and community-identity preferences.
- Private journals, mood check-ins, screening responses and saved resources.
- AI-chat messages and feedback when chat history is enabled.
- Community posts, replies, reactions, reports and appeal submissions.
- Contact requests, attachments and support correspondence.
Technical and transaction information
- Security logs, timestamps, approximate device and browser information, and abuse-prevention signals.
- Payment references, plan status, amount, currency, invoice and webhook-verification records.
3. How we use information
Information is used to authenticate accounts, provide requested features, synchronise private records, personalise preferences, process subscriptions, prevent abuse, moderate community content, respond to support requests and meet legal obligations.
We do not sell private journal text or use it for targeted advertising. Sensitive wellbeing information should not be used to determine employment, insurance, credit or similar eligibility.
4. AI-assisted support
When you use AI chat, messages are sent through Tranquiliva’s server safety layer to the configured AI provider. Automated responses may be inaccurate and are not diagnosis, treatment or emergency care.
Deterministic safety checks, contextual classification and conservative escalation rules may generate structured safety events separately from general conversation history. Retention and staff-access limits should be documented in the production retention schedule.
5. Anonymous community participation
Community members see an automatically generated identity rather than your personal profile. Authorised moderators may access account-linked audit information where necessary to investigate safety, abuse, legal or appeal matters.
Do not include real names, contact details, exact locations or other identifying information in public posts or live rooms.
7. Retention and deletion
Different records require different retention periods. Active account records remain while needed to provide the service. Deleted journals, mood records and AI history enter a controlled deletion workflow. Billing, moderation, security and legal records may need to be retained longer.
Account deletion should explain which records will be erased, anonymised or retained and the applicable reason. Offline drafts on a device may require separate removal.
8. Your choices and rights
Subject to applicable law, you may request access, correction, portability, restriction, objection or deletion. The Privacy & data screen provides self-service controls for exports, private records, AI history, community identity and account deletion.
We may need to verify your identity before completing a request. You may also contact Ghana’s Data Protection Commission where applicable.
9. Security
Security measures should include encrypted transport, restricted server credentials, role-based access, reviewed database rules, audit logging, payment-webhook verification, dependency updates and incident-response procedures. No service can guarantee absolute security.
10. Children and young people
Age eligibility, guardian consent and youth safeguards must be finalised before public launch. Community and AI experiences intended for young people require additional design and moderation controls.
11. Changes to this policy
Material changes will be communicated through the service or account contact details. The effective date and version will be updated at the top of this page.
12. Contact
Privacy questions and requests can be submitted through the contact form. The final policy should include the legal entity name, registered address, privacy contact and Data Protection Commission registration details.