Privacy Policy

Last updated: September 14, 2026

This Privacy Policy explains what information TipLink collects, how it's used, and how it's protected - for creators, their team members, and the contributors who pay through a TipLink page.

1. What we collect

Creators: name, email, phone, payout provider/number, country, bio and social links you choose to display, and KYC details (e.g. ID number) used to verify your account before connecting a live payment gateway.
Contributors: the name and phone number you provide when paying (name is optional and shown as "Anonymous supporter" if left blank), the amount, and an optional message to the creator.
Transaction data: every contribution attempt, its status, WaestaPay's own transaction reference, and the mobile money provider's transaction code (used solely to reconcile a specific payment if a contributor or creator raises a dispute).
System data: login timestamps, IP address and browser user-agent at login (for account security and audit purposes), and records of account actions (e.g. gateway connection, KYC status changes) in our audit log.

2. What we don't collect

TipLink never asks for or stores your mobile money PIN. We never see your card details, because TipLink does not process card payments. Each creator's WaestaPay API key and webhook secret are encrypted at rest (AES-256-GCM) the moment they're saved and are never displayed again in full.

3. How we use it

To operate the service: process contributions, show your dashboard and statements, and route payouts.
To keep the platform secure: detect suspicious login activity, enforce account lockout after repeated failed logins, and maintain an audit trail of sensitive actions.
To communicate with you about your account (e.g. a payout request being approved) - TipLink does not sell your data or use it for third-party advertising.

4. Sharing

Payment details are shared with WaestaPay to actually process a contribution - that's the only third party contributions pass through. We disclose information to law enforcement or regulators only where legally required, and never sell personal data to advertisers or data brokers.

5. Security

Passwords are hashed (never stored in plain text). Gateway credentials are encrypted at rest with authenticated encryption. All state-changing actions require a CSRF token, and every request runs through prepared SQL statements. Sessions use HttpOnly, SameSite cookies, sign out automatically after a period of inactivity, and are rotated on login. Repeated failed logins temporarily lock an account. No system is perfectly secure, and we keep improving these protections as the product grows.

6. Data retention

We keep contribution and audit records for as long as your account is active and for a reasonable period after, to satisfy financial record-keeping and dispute-resolution needs. You can request deletion of your creator account by contacting support, subject to records we're required to retain.

7. Your choices

You can update your profile information at any time from Settings, revoke API tokens, and review your own login history. Contributors are not required to create an account and can request that TipLink remove their name/message from a public receipt by contacting the creator or support directly.

8. Changes to this policy

We'll update the date at the top of this page when this policy changes materially.

9. Contact

Questions about this policy can be sent to the support address shown in your dashboard.

This is a template Privacy Policy for TipLink's current feature set. Have it reviewed by qualified legal counsel - including against applicable data-protection law in your operating countries - before relying on it for a live product handling real payments.