Effective date: September 10, 2026
1. About This Privacy Policy
This Privacy Policy explains how TikiPay collects, uses, transmits, stores and protects information when merchants, administrators, developers or authorized business users use the TikiPay website, merchant dashboard, APIs, plugins, modules and the TikiPay Android payment automation application.
2. Information We Collect
Depending on the service you use, TikiPay may process account information such as name, business details, email address, phone number, subscription information, API credentials, device identifiers, IP address, technical logs, transaction references and payment-status data.
3. SMS Access for TikiPay Direct Payment Automation
The TikiPay Android payment automation app may request access to SMS messages on a business-controlled device when SMS-based payment verification is enabled. This functionality is intended for supported mobile financial service payment notifications used by the merchant or authorized business operator.
When a supported payment notification is received, the app may read and process the transaction-related SMS content required to identify payment information such as the payment provider or sender identifier, transaction/reference ID, amount, timestamp, payment/account reference and other text needed to determine whether the message represents a supported payment event.
Relevant transaction SMS data may be transmitted securely to TikiPay servers so the merchant's website or application can match a customer-submitted transaction/reference ID, amount and payment session and determine whether the payment should be verified. The SMS functionality is not intended for advertising, marketing, contact profiling or sale of personal message data.
4. Online and Offline Delivery of Payment Notifications
For TikiPay Direct, the configured phone must remain powered on and the payment SIM must have mobile network coverage. When an internet connection is available, supported transaction information can be delivered to the TikiPay server through the internet connection. Where the merchant has enabled the supported SMS fallback, the app may use the SIM network and available SMS package or mobile balance to forward the required payment notification when internet connectivity is unavailable.
If no supported delivery path is temporarily available, eligible payment-event data may be retained in a local pending queue and retried when a configured connection becomes available. The underlying customer payment is processed by the relevant MFS/payment provider; TikiPay's role is to automate receipt, matching and verification of supported payment notifications.
5. Official Merchant API Connections
Where a merchant uses provider-issued official API credentials, TikiPay may communicate with the configured payment provider through server-side API requests. These official API workflows are separate from Android SMS-based TikiPay Direct connections and are subject to the provider's own rules and privacy practices.
6. How We Use Information
- To create and manage payment sessions, invoices and payment links.
- To match and verify supported payment transactions.
- To provide merchant dashboards, transaction history and reconciliation information.
- To deliver webhook, callback and API responses.
- To prevent duplicate fulfillment, fraud, abuse and unauthorized access.
- To provide customer support, troubleshooting and service communications.
- To comply with applicable legal, security and payment-provider requirements.
7. Data Sharing
TikiPay does not sell personal SMS content or transaction data to advertisers. Information may be shared only as needed to operate the service, with authorized service providers, infrastructure providers, payment providers, or when required by law. Service providers must only process data for the services they provide to TikiPay.
8. Data Retention
Transaction, verification and technical records may be retained for as long as reasonably necessary for service operation, reconciliation, fraud prevention, dispute handling, security, accounting and legal obligations. Merchants should not configure TikiPay to collect unrelated SMS or information that is not required for payment automation.
9. Security
TikiPay uses reasonable administrative and technical safeguards designed to protect information in transit and at rest. Merchants are responsible for securing their dashboard accounts, Brand API Keys, Device Keys, websites and authorized Android devices. No electronic system can guarantee absolute security.
10. User Choice and Permission Control
SMS access must be enabled only by an authorized user on a device used for the supported TikiPay Direct payment automation purpose. Android permissions can be reviewed or revoked from the device settings. Revoking a required permission may stop SMS-based automatic verification from working.
11. Data Access, Correction and Deletion Requests
Authorized account holders may contact TikiPay to request access, correction or deletion of eligible personal information, subject to legal, fraud-prevention, accounting and transaction-record retention requirements.
12. Children
TikiPay is a business payment automation service and is not directed to children. Users must have the legal authority to operate the business account and connected payment devices.
13. Third-Party Services
TikiPay may link to or integrate with banks, mobile financial services, cloud infrastructure, social platforms, plugins and other third-party services. Their own privacy policies apply to information processed directly by those providers.
14. Changes to This Policy
We may update this Privacy Policy when our products, permissions, integrations, legal obligations or data practices change. The updated version will be posted on this page with a revised effective date.
15. Contact
For privacy or data-related questions, use the contact information published on the TikiPay Contact page.