Offerwall Privacy Policy Clause: Copy-Ready Wording

What should an offerwall privacy policy clause say?

An offerwall privacy policy clause tells your users that your Earn page uses an offerwall run by another company, what that company receives, what it uses the data for, what it sends back to you, and how users can contact it. For the Moonetix offerwall, that means naming Moonetix, saying that it gets your pseudonymous user ID and the details any browser sends, describing its fraud and VPN checks, and linking to Moonetix’s Privacy Policy. Below is a clause you can adapt, followed by what each sentence is for.

The broader GDPR picture, such as pseudonymous IDs, consent banners, and deletion requests, is covered in Offerwalls and GDPR. This page focuses on the wording itself.

Why your policy needs an offerwall section

Three sources point the same way.

• Moonetix’s Terms. Section 7 of the Terms of Service makes you responsible for “your own terms of service and privacy notice, obtaining any consent your end users’ jurisdictions require before their data reaches us”. Section 16 adds that publishers that send end user data “must have a lawful basis to do so and must reflect our processing in their own privacy notice.”
• Moonetix’s Privacy Policy. Section 5 says the publisher is responsible for its own privacy notice, “including telling you that the offerwall is provided by Moonetix”. Moonetix decides on its own how offer activity is recorded, attributed, and checked for fraud, so it is a separate controller for that processing, not just a tool you run.
• The law. Under Article 13 of the GDPR, when you collect personal data from a user you must tell them, among other things, the purposes and legal basis, “the recipients or categories of recipients of the personal data, if any”, and how long you keep it. The full official text is on EUR-Lex. In California, the Attorney General’s CCPA page says a notice at collection must list the categories of personal information and the purposes they are used for, and be given “at or before the point” of collection.

Your users accept your rules, not Moonetix’s, so your policy is where they learn about the wall. A privacy section also belongs next to the rest of your rules; Rewards site terms of service covers the terms side.

The copy-ready clause

Replace the parts in square brackets. Delete optional sentences you do not need, and keep the rest as one section of your policy, for example under “Partners” or “Rewards”. The sentences are numbered so you can match them to the explanation below; remove the numbers when you paste.

Every sentence about Moonetix above restates the Moonetix Privacy Policy as it stood when this page was checked on November 5, 2026. Policies change, so compare your copy with the live policy when you publish and at least once a year after.

What each sentence is for

If you shorten the clause, this table shows what you lose. “Required” here is a drafting judgment, not a legal ruling.

Sentences 1 and 2: who and under what policy

Naming Moonetix and linking its policy answers “who else sees my data” in one line. Saying Moonetix is a separate controller is accurate for the processing Moonetix decides on, and it tells users that some requests go to Moonetix, not to you.

Sentences 3 to 5: what you send

The offerwall link docs say the link carries your user ID and a hash, plus optional sub1 to sub5 values. If your link follows the advice to use a random ID rather than an email or username, sentence 3 is true. If it does not, fix the link before you publish the sentence. The offerwall link builder shows what a signed link contains. Keep personal data out of sub IDs too, or drop sentence 4.

Sentences 6 to 12: what the wall collects and why

These mirror the “End users” part of the Moonetix policy and its fraud section. A user who sees “VPN detected” and finds the reason in your policy is less likely to open a ticket. VPN or proxy detected on an offerwall explains the block to users. Sentence 10 covers the GDPR point on automated decisions and the human review Moonetix offers. Do not name the companies behind the fraud checks; the Moonetix policy does not name them publicly either, and gives them on request.

Sentences 16 to 18: your own side

This is the part only you can write, because you choose which postback fields to receive. The postback reference lists them, including {country}, {device}, {ip}, and {offer_name}. If your postback URL does not request {ip}, delete “IP address” from sentence 16. If you keep postback logs for 12 months, write 12 months. The legal basis in sentence 18 is your decision to make with advice; the example is a common pairing, not a recommendation for your case.

Adding wording for California and other US states

The CCPA applies only to businesses that meet its thresholds, which the California Attorney General lists as revenue, data volume, and data sales tests. Many small rewards sites fall below them, but other US states have their own laws, so check with your lawyer.

If you do need CCPA wording, the offerwall section mostly reuses what you already have. In your categories list, the offerwall touches identifiers (user ID, IP address, device identifier), internet activity (offers viewed and completed), and approximate location. Sentence 21 reflects Moonetix’s own statement; whether you sell or share personal information depends on your whole site, including ad networks and pixels, not on the offerwall alone.

Common mistakes in offerwall privacy sections

• “We never share your data with third parties.” Once the wall is live, this is false.
• Copying another network’s clause. Different providers collect different things and describe their role differently. A clause written for one wall can be wrong for another.
• Promising what the wall does not do. For example, saying the wall uses no device identifiers at all. Moonetix’s wall sets no cookies of its own, but it does keep a device identifier in local storage for fraud prevention.
• Describing data you do not store, or hiding data you do. Your postback handler is the source of truth for sentences 16 and 17.
• Sending users to the wrong place. Balance and payout questions belong with you. Moonetix’s policy says so, and users who write to the wrong address wait longer.
• Forgetting apps. If you run the wall in an app through an SDK, your store listing has its own privacy questions. Answer them for the SDK as well, using the privacy section of the Moonetix SDK docs.

Where to put it and how to keep it current

• Add the clause to your main privacy policy, and list Moonetix wherever your policy lists recipients or partners.
• Put a short notice and a link to that section on the Earn page itself, near the wall, so users see it before they open offers. The Moonetix wall already shows a note that offers come from third-party advertisers, with links to Moonetix’s Terms and Privacy Policy, but that does not replace your own notice.
• Keep the Earn page behind an age check that matches sentence 22. Offerwalls in kids’ apps and COPPA explains why the wall does not belong in products aimed at children.
• Review the clause when you change your postback fields, add or remove a wall, or when Moonetix emails you about policy changes. Moonetix’s policy says material changes are announced to account holders by email or in the dashboard before they take effect.
• Tell your support team where users find their user ID, so they can pass it on for requests to privacy@moonetix.com.

Frequently asked questions