Legal

Privacy Policy

What Dolinq collects, why we collect it, who we share it with, and the control you have over it.

Last updated: 14 July 2026

1. Who we are

Dolinq is a platform for paid audiences. Creators use Dolinq to publish a public profile, open paid channels, collect payments, keep records of their members, and publish updates that Dolinq delivers to those members on WhatsApp and by email.

This policy explains what we do with personal data. Where a member joins a creator’s channel, the creator is the controller of that member’s data and Dolinq acts as a processor on the creator’s behalf. For a creator’s own account data, Dolinq is the controller.

2. Data we collect

From creators, when you open an account and run channels on Dolinq:

  • Account data: name, email address, phone number, password hash, and profile details such as your slug, photo, bio and social links.
  • Channel data: your channels, their prices, and the updates you publish into them — including any images, files and voice notes you attach.
  • Payout data: the bank code, account number and resolved account name your earnings settle into.
  • Usage data: sign-ins, actions taken in the dashboard, and technical data such as IP address, browser and device type.

From members, when someone joins a creator’s channel:

  • Contact data: name, phone number and, if given, email address supplied when joining.
  • Notification preferences: the channels you asked to be reached on — WhatsApp, email, SMS or Telegram.
  • Payment data: what was joined, the amount, the payment reference, and the status of the payment and the membership.
  • Delivery data: a record of each message sent to you — which channel it went out on, when, and whether it was delivered or failed.

We do not collect or store full card numbers, CVVs or bank credentials. Card and bank details are entered directly with our payment provider and never reach Dolinq’s servers.

3. How we use data

  • To operate the service: create accounts, host creator profiles, process joins, take payments and open memberships.
  • To verify payments with our payment provider before access to a channel is opened.
  • To deliver a creator’s updates to their members on the channels each member asked to be reached on.
  • To send transactional messages on a creator’s behalf: welcome messages, payment receipts, renewal reminders and expiry notices.
  • To secure the platform: detect fraud and abuse, and enforce the expiry of a membership when it lapses.
  • To support creators, respond to enquiries and meet our legal and accounting obligations.

We do not sell personal data, and we do not use a member’s data to advertise to them.

4. Legal bases

Where data protection law requires a legal basis, we rely on: performance of a contract (to provide the service you or the creator asked for); legitimate interests (to secure, maintain and improve the platform); consent (where you have given it — for example, the notification channels you chose when joining); and legal obligation (for tax, accounting and compliance records).

5. Service providers we share data with

Dolinq uses a small number of processors, each for a specific purpose:

  • Paystack — payment collection and verification. Card and bank details are handled by Paystack, not Dolinq.
  • Evolution API — delivery of WhatsApp messages to members.
  • Brevo — transactional and channel email.
  • Cloudflare R2 — storage of profile images and the media attached to a creator’s updates.
  • Vercel — hosting of the application and its infrastructure logs.
  • Our database and queue providers — storage of account, member, payment and delivery data, and the job queue that sends messages.

We share only what a provider needs to perform its function. We may also disclose data where we are legally required to, or to establish, exercise or defend legal claims.

6. Your private channel feed

When you join a channel, Dolinq issues you a private link containing a long, randomly generated token. That link is your key to the channel’s updates on the web, and anyone who has the link can open it. Treat it like a password: do not forward it, and do not post it publicly.

Media attached to an update — an image, a voice note, a team sheet — is stored at a long, randomly generated address so that WhatsApp is able to fetch and deliver it to you. That address is not listed or indexed anywhere, but it is not individually password-protected either. The paywall protects the channel; it does not encrypt each file.

7. Retention

We keep account, channel, member, payment and delivery data for as long as the creator’s account is active, and afterwards for as long as we need it to meet legal, tax and accounting obligations or to resolve disputes.

When a creator deletes an update, the delivery records for that update are deleted with it. Messages already sent to a member’s phone or inbox have left our systems and cannot be recalled.

A membership that expires is retained as a record of the payment that was made; it simply stops receiving new updates.

8. Security

Data is transmitted over TLS. Passwords are stored hashed, never in plain text. One-time codes and reset links are stored only as a hash, so a leaked database row cannot be used to sign in as you. Access to production data is restricted to the people who need it to run the service.

No system is perfectly secure. If a breach affects your personal data, we will notify you and the relevant authority where the law requires it.

9. Your rights

Depending on where you live, you may have the right to access, correct, delete, port or restrict the use of your personal data, and to object to processing based on legitimate interests. You may also withdraw consent at any time where processing is based on consent.

You can change which channels you are contacted on, or ask to be contacted on none, at any time by contacting the creator or us.

Creators can exercise these rights from the dashboard or by contacting us. Members should contact the creator they joined first, as that creator controls the member record; if you contact us instead, we will pass the request on and assist them in fulfilling it.

10. Cookies

Dolinq sets a session cookie so you stay signed in, and stores your theme preference in your browser. We do not use advertising cookies or third-party tracking cookies. We use privacy-preserving analytics to measure aggregate traffic and performance.

11. Children

Dolinq is not intended for anyone under 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it.

12. Changes to this policy

We may update this policy as the product and the law change. When we make a material change, we will update the date at the top of this page and, where appropriate, notify creators by email.

13. Contact us

Questions about this policy or about your data can be sent to support@dolinq.com and we will respond within a reasonable time.