Acceptable use policy

AESHA Technology Services Limited · Last revised 7 October 2026 · All legal documents

This policy applies to everyone with an account and to the traffic they send. It sits on top of the terms of service. Breaking it is grounds for suspension without notice.

1. Incentivised traffic must be honest

Rewarded advertising works because the advertiser knows the user was rewarded. What they are paying for is a real person choosing to complete a real offer.

• Do not misrepresent what an offer requires in order to get a user to start it.
• Do not promise a reward we do not pay, or a larger one than the wall shows.
• Do not present an offer as free when it requires a purchase, a deposit or a subscription.
• Do not place the wall where a user does not know they are looking at advertising.

2. No fabricated completions

Specifically, and any of these ends an account:

• Bots, emulators, scripted clicks, click farms or automated form filling.
• Incentivising users to abandon offers part-way to farm partial credit.
• Multiple accounts run by one person to complete the same offer repeatedly.
• Proxies, VPNs or SDK spoofing used to appear in a country you are not in.
• Manipulating the user id in a wall URL to credit a different user.

The platform screens for the obvious cases before a click is recorded — automated user agents, blocked addresses, and an hourly click ceiling per user — and networks run their own checks afterwards. Passing ours is not a finding that traffic was genuine.

3. Where the wall may appear

Do not place the offerwall on, or send traffic from, anything that:

• is unlawful where it operates, or promotes unlawful activity;
• contains sexual content involving minors, or content sexualising minors in any way;
• infringes copyright or trade marks, including piracy and cracking sites;
• promotes hatred or violence against people for who they are;
• distributes malware, or bundles our wall with software a user did not choose to install;
• targets children below the age at which they can consent to processing where they live.

A placement lives on a site you control: your own registered domain or its www., or your app's page in an app store. We do not accept addresses on free hosting subdomains, free domain endings, or IP addresses.

Before a new placement on a website goes live, you show us you control that site, once per domain: a meta tag on its home page, an offerwall.txt file at its root, or a DNS TXT record, each carrying a code we give you. App store placements are confirmed by a person instead.

We check the address of every placement automatically, once: after you have shown the site is yours, or when you add an app store listing, and again only if you change the address. A placement that is already live is not checked again. The check looks at the domain, at whether public security services list it as unsafe or as adult content, and at the visible text of its front page or store listing, which we send to OpenAI to be classified. It never downloads images. A check can approve a placement, hold it for a person to review, or decline it, and a person can review any automatic decision.

Where a check indicates sexual content involving minors, the account is suspended at once, nothing from the site is kept, and we may report the site to child-protection hotlines and the authorities.

4. Technical conduct

• Do not attempt to read or modify another account's data. Every id in a URL is checked against the account that owns it.
• Do not forge, replay or tamper with a postback. Conversions are deduplicated on the network's transaction id and signed with your own secret.
• Do not scrape the catalogue beyond the published rate limits. The API exists; use it.
• Do not attempt to bypass a rate limit, a block, or a signature check.
• Keep your secret key server-side. If it reaches a browser, rotate it.

5. Advertisers

• The offer must be completable as described. If a requirement changes, change the campaign.
• Do not reject conversions that met the stated requirement in order to reduce spend.
• Do not collect more from a rewarded user than the offer needed, and do not repurpose what you collect.
• Landing pages must not deceive, and must not install anything the user did not ask for.

What a campaign may promote, and how, is set out in the advertiser content guidelines.

6. What happens when this is broken

Depending on what we find, and roughly in this order:

1. We ask. Most problems are a misconfiguration, and a question resolves them.
2. We block the source. An end user, an address, a country or a device can be stopped from earning on one placement without touching the rest of your traffic.
3. We reverse affected conversions. A reversal is a negative ledger entry with a reason on it, visible to you, not a silent deletion.
4. We suspend the account. The wall stops serving and payouts stop.

Balances. Earnings from traffic that breached this policy are not payable, and a payout already requested against them can be refused while it is investigated. Earnings unconnected to the breach remain yours. Where we cannot separate the two, we will say so and explain the basis of the decision rather than simply withholding.

Chargebacks. A network reversing a conversion weeks later is normal and is not by itself a breach of this policy. It reverses the ledger entry; it does not put your account at risk.

7. Reporting abuse

If you find an offer that misrepresents itself, a placement that hides what it is, or a user gaming your traffic, tell us at [email protected]. Include the offer name or the placement key — a report we cannot trace is one we cannot act on. Content you believe is illegal goes through the illegal content reporting page. A security problem goes through the vulnerability disclosure policy.

8. Appeals

If your account was suspended and you think we got it wrong, reply to the notice or write to [email protected]. We keep the click, conversion and postback records behind the decision, and we will look at them again.