QUIETDATA← Back to Quiet Data

Privacy Policy

Effective date: 9 October 2026

This policy explains how Quiet Data, operated by Silas Tagoe, handles personal information when you use the Quiet Data website and app. It is intended to be read together with our Terms of Service.

Quiet Data’s checkout is handled by the payment provider shown at checkout. We do not ask you to send or store your Mobile Money PIN, full payment-card number, or card security code.

Information we handle

Why we use it

We use information to create and secure accounts, take and fulfil orders, process wallet and agent operations, send service notifications, answer support requests, prevent fraud or abuse, fix errors, and understand whether the site is working well. We do not sell personal information or use it to build advertising profiles.

Payment and service providers

Depending on the service you use, relevant information may be shared with KoraPay or Paystack to process hosted checkout; Inventorax to verify and fulfil data-bundle orders; our configured SMS provider (Nkomo SMS or SMS Online GH) to send requested service messages; Supabase for authentication and database hosting; and Cloudflare for hosting, security and, if enabled, Web Analytics; and Google for Google Analytics (GA4) site and campaign measurement. Push notifications also rely on the browser or device’s push service. Each provider handles information under its own terms and privacy notice.

The Quiet Data Supabase project is hosted in the EU region. Information may therefore be processed outside Ghana by the providers that support the service. We share only what is needed for the relevant function.

Analytics, errors and security

Quiet Data’s first-party analytics stores daily aggregate counts and short-lived hashes, not raw IP addresses or the random session ID. Client error reports are limited to a short, redacted message, route and technical detail; we do not intentionally send passwords, payment credentials or phone numbers in those reports. The Worker hashes network addresses before using them in short-window abuse counters.

If Cloudflare Web Analytics is enabled for the Pages project, Cloudflare’s beacon reports page-view and performance information. Cloudflare documents that Web Analytics does not use client-side cookies or local storage for its beacon metrics. Google Analytics (GA4) also processes page-view and browser/device information and allowlisted advertising campaign parameters to help us understand visits and campaigns. The tag removes the URL fragment and excludes arbitrary query parameters, such as checkout references, from its initial page-view URL; only recognized campaign parameters are retained. Google may use cookies or similar identifiers according to the Analytics setup and your browser settings; see Google’s Privacy Policy. Enhanced-measurement events depend on the web stream settings. Browser extensions and privacy settings may block analytics.

Retention and deletion

We keep account and order information while it is needed to operate the service, handle support, resolve disputes and meet applicable record-keeping duties. Daily visitor hashes are retained only for short-term counting; aggregate daily statistics may be kept longer. Diagnostic and security events older than 90 days are pruned when a new event is recorded or an administrator reads the event feed. Administrator account deletions record the administrator account ID for accountability; the deleted account is represented by a one-way hash in that audit event.

You can request account deletion from Profile, or an administrator can delete a duplicate account. A deletion request is allowed when the account wallet balance is zero. Deleting an account removes its sign-in and linked profile; limited payment or accounting records may remain without the account link where required, and external providers may retain their own records under their rules or legal obligations.

Your choices and rights

You may request access to, correction of, or deletion of personal information, or object to processing where applicable. To make a request, use the WhatsApp support link in the Quiet Data app or website and identify the account involved. We may need to verify that you control the account before acting. Ghana’s Data Protection Act, 2012 (Act 843) sets out data-protection principles and data-subject rights. The Act also requires data controllers intending to process personal data to register with the Data Protection Commission. Please contact the Commission for regulatory information or to raise a complaint.

Security and children

We use access controls and server-side checks to protect the service, but no online service can promise absolute security. Quiet Data is not designed for children under 18. If you believe a child has supplied account information, contact us through the in-app WhatsApp support link.

Changes and contact

We may update this policy when the service changes. The current version and effective date will appear here. For privacy requests or questions, open Quiet Data and choose Menu → Chat on WhatsApp. Do not send a password, Mobile Money PIN or full card details to support.

This notice is a practical service description, not legal advice. Quiet Data should confirm its data-controller contact details and registration status with Ghana’s Data Protection Commission before production publication.