Privacy policy

1. Who is responsible

Adfluence (“we”, “us”) is responsible for this policy. It covers adfluence.ai (studio and marketing) and adfl.to (creator stores and buyer library).

Questions, access requests, and deletion requests go to support@adfluence.ai. We do not publish a street address on this page; write to that inbox and we will handle the request.

2. Roles

We are the controller for creator accounts, studio usage, our own billing (Pro and Studio subscriptions, platform-fee records), security logs, and visitors to the marketing site.

On a sale, the creator is the seller. Name, email, and what was bought exist so that creator can fulfil the order. We process that data to run checkout, delivery, the library link, and the sales list the creator sees. We do not use another creator's buyers to market Adfluence, and we do not sell lists.

3. What we collect

Creators

Name, email, password (stored hashed) or a Google sign-in id, the store you publish, handle, products, files you upload, pasted course content, booking hours, and the id of the payment account you connect — never that account's secret keys, and never a full card number. We also keep plan, subscription status, and the platform fees taken on your sales.

Buyers

Email, optional name, what they bought or claimed, payment status from the provider (succeeded, refunded, disputed) and a provider payment id. We do not store card numbers. On downloads we keep a coarse network prefix so we can see if one library link is being shared, not a marketing profile of the buyer.

Visitors

Technical data the host needs to serve the page (IP address at the edge, user agent). On adfl.to we set first-party click cookies so a creator can see which post sent a visit — see cookies. Stores also record how a visit went: pages and products opened, how far a page was scrolled, time on the page, which links and buttons were tapped, and whether checkout was started. That record carries the visit cookies, a country and region from the edge, and a device type, and never a name, an email, or anything typed. Visitors in the EEA, UK and Switzerland get the visit count only, without the scroll, time and tap measurement. We do not run advertising pixels.

4. Why we use it

• To run your store, sign you in, and keep the session on adfluence.ai.
• To take a payment on the account you connected and to record the sale.
• To deliver the file, course, booking, link, or tip, and to email the library link.
• To show you who bought, and to let you refund from Sales.
• To bill Pro and Studio, and to take the Starter platform fee at charge time.
• To keep the ledger honest, to prevent abuse, and to meet the law.
• To answer mail you send to support, including a buyer who cannot open a file.

We do not sell personal data. We do not use buyer lists from one store to advertise another store, or to advertise Adfluence to those buyers.

5. Legal bases

We handle personal data under the UAE Federal Decree-Law No. 45 of 2021 (Personal Data Protection Law) and, where a visitor or customer is in the EEA or UK, under GDPR / UK GDPR as well.

• Contract — creating an account, running a store, delivering a purchase.
• Legitimate interests — security, fraud, attributing a store visit to a campaign, improving the product without building an advertising profile.
• Legal obligation — tax, accounting, and responding to a lawful request.
• Consent — where a cookie is optional, or where Google sign-in is something you choose.

6. Who else sees it

We share data with the processors that actually run the product:

• Neon — database.
• Resend — transactional email (sign-in codes, delivery mail, sale notices).
• Cloudflare, including R2 — hosting, edge, and files you upload.
• Stripe — checkout on the account you connect, and our own subscription billing.
• Google — sign-in if you choose it, and Google Analytics for page visits on adfluence.ai. Stores do not load it. Analytics is not used for advertising.
• PostHog — product analytics for signed-in creators in Studio, with typed fields masked. Stores and buyers never load it.

A creator sees their own buyers, not anyone else's. Staff who operate Adfluence can see account data when they need to support you, bill you, or keep the platform safe — not to browse stores for fun. If you turn on staff access in Settings, a named operator can impersonate the studio session you allowed; you can turn that off.

We may disclose data if the law requires it, or to defend a claim. If we sell or reorganise the business, this data goes with it under the same promises.

7. International transfers

We are established in the United Arab Emirates. Processors above may store or access data in the United States, the EEA, or other places they operate. Where a transfer tool is required (standard contractual clauses, or the processor's own lawful mechanism), we rely on it. We do not invent a local-only copy of Stripe or Neon.

8. How long we keep it

Account and store data while the store exists, and for a short period after you close it so we can finish deletion and answer a dispute. Orders, entitlements, and fee records for as long as someone might need the library link and as long as the ledger and tax rules require — typically years, not weeks. Download logs keep a prefix, not a full address, and are not a permanent marketing file. Support mail is kept long enough to resolve the thread.

9. Your choices and rights

Creators can export sales and buyers from Settings, change the display name in Account, and close the account from that same page — the store goes offline and the login ends. For remaining personal data, or a buyer asking to be forgotten, email support@adfluence.ai.

Depending on where you live, you may have the right to access, correct, delete, restrict, or port personal data, to object to some processing, and to withdraw consent. We will not charge for a reasonable request. We may need to verify it is you. Some records (a paid sale, a fee we took, a dispute) we cannot erase while the law or the provider still requires them; we will say so.

You can complain to the UAE Data Office, or to a supervisory authority in the EEA or UK if those rules apply to you. We would rather fix it first — write to support@adfluence.ai.

10. Children

The service is not for children. Creator accounts are for people 18 or older. We do not knowingly collect data from children. If you believe a child has an account or appears in a listing, email support@adfluence.ai and we will take it down.

11. Security

Passwords are hashed. Sign-in codes are hashed. Creator sessions stay on adfluence.ai; store click cookies stay on adfl.to — the two hosts do not share login cookies. Card data never touches our servers. No setup is perfect; a breach that affects you will be mailed to the account email when the law says we must.

12. Cookies

The cookie policy lists what we set. Short version: a session on the studio, first-party click and visit cookies on adfl.to, Google Analytics on adfluence.ai, PostHog inside Studio, and whatever Stripe sets on its checkout form. No advertising pixels. Analytics does not load on a payment page.

13. Changes

We can change this policy. The date at the bottom is when the posted version took effect. A material change will be mailed to the account email or shown in Studio.

14. Contact

Email support@adfluence.ai.