Referral Policy
- Effective
- <date>
- Last updated
- <date>
How the invitation programme works: what a referral link does, what makes a referral qualify, why an invitation by itself earns nothing, and what happens when a referral does not stand up.
1. What the programme is
The referral programme lets you invite somebody to the platform. Your invitation carries a code that belongs to your account, and when the person you invited creates an account with that code, the platform records the connection between the two accounts.
Recording the connection is not the same as earning from it. That distinction is the programme’s central rule, and the rest of this policy is mostly about it.
2. The life of a referral
Every referral moves through the same steps. It can stop at any of them, and where it stops is visible to you in the app:
| Step | What happens | What it means for a reward |
|---|---|---|
| 1. You share | You send your link or your code to somebody. | Nothing. Sharing is not earning. |
| 2. They join | They open the link, install the app if they need to, and create an account with your code attached. | Nothing yet. An account has been created — the programme has a record, not a reward. |
| 3. Verification and activation, where required | Some activity, and every payout, depends on the account meeting a requirement — an identity the platform can rely on, or a method that can pay out. | Still nothing. A requirement that has not been met cannot be skipped by inviting somebody. |
| 4. Qualifying activity | The person you invited completes the activity the programme treats as qualifying. Which activity that is belongs to the programme’s current rules. | This is the step that matters. Nothing before it earns anything. |
| 5. Qualification | The platform assesses the referral: the activity confirmed, the accounts distinct and genuine, the arrangement a real invitation. | A qualified referral becomes eligible for the referral reward. |
| 6. Eligible reward | The reward is recorded against your account. It may be **pending** until the activity behind it is confirmed, and it may be reversed if that activity is withdrawn or turns out not to justify it. | A pending reward is not money you can spend — see the terms on reward states. |
3. What makes a referral qualify
- The invited person must be a real person who is not you, and their account must be distinct from yours.
- The qualifying activity must actually have been completed, by them, as the programme’s rules describe it at the time.
- Where the activity is confirmed by a partner, the partner’s confirmation is what the platform relies on.
- The invitation must be a genuine one. A referral engineered to produce a reward — rather than to invite somebody who then takes part — does not qualify, however the accounts were created.
Joining is not qualifying
An account created through your invitation does not, on its own, earn you anything. The programme pays for a qualified referral, and qualification depends on the invited person completing the qualifying activity. If you were told otherwise, you were told wrong.
4. What is not allowed
- **Referring yourself.** An account cannot be its own inviter, or the inviter of an account you also control. The platform checks this when a referral is applied rather than only in the interface.
- **Duplicate or fake accounts.** Creating a second account to invite, or to be invited by, breaches the terms.
- **Inviting somebody who does not exist**, or creating an identity to stand in for them.
- **Buying, selling or trading referrals**, or paying somebody to sign up through your link.
- **Automating any part of it** — bulk invitations, scripted registrations, or activity completed by a machine.
- **Publicly posting your code where the invitation is not genuine** — a code-farm, an incentivised signup site, or a page that rewards people for entering codes.
5. When a referral is refused, pending or reversed
A referral or its reward can be in one of several states, and each means something specific:
| State | What it means |
|---|---|
| Pending qualification | The invitation is recorded and the qualifying activity has not been confirmed — or has not happened yet. |
| Qualified | The activity was confirmed and the referral meets the programme’s rules. |
| Unqualified | The referral did not meet the rules — the activity was not completed, or was not the one that qualifies. |
| Refused | The referral was rejected for a reason the programme treats as a breach: a duplicate account, a self-referral, an engineered arrangement. A refused referral is not a pending one, and it does not become payable later. |
| Pending reward | The referral qualified and the reward is recorded but not yet confirmed. It is not part of a spendable balance. |
| Confirmed reward | The reward is yours and forms part of your available balance. |
| Reversed reward | A confirmed reward was taken back because the activity behind it was withdrawn or shown not to justify it. |
Why we do not always explain a refusal in detail
Where a referral is refused, we will tell you which rule it failed. We will not describe how the platform detects an engineered arrangement — the signals it looks at, the patterns that raise a case, or the thresholds involved. Publishing those would tell somebody exactly how to stay underneath them, and the programme would be worse for everybody honest who takes part in it.
6. The reward
The referral reward is one of the platform’s rewards, so it behaves like the others: it may be pending, it may be confirmed, and it may be reversed if what it rested on is undone. When confirmed, it forms part of your available balance and can be withdrawn under the withdrawal policy.
**We do not state a referral reward amount here, and the app does not show one.** The amount is configuration: it can differ between programmes, it can be changed, and no part of the platform publishes a single figure for it. If a number is to be published, it will be published from configuration, and it will be the number that applies.
- What a referral pays, when it pays, and what qualifies it may change. A change applies prospectively — to referrals made after it takes effect, not to a reward already confirmed.
- Rewards are credited in the platform’s own unit. Where a payout converts it, the conversion belongs to the payout method and is shown before you submit a request.
- A reward is not assignable. It belongs to the account that earned it.
7. Your code and your link
Your referral code is issued to your account, and your invitation link is built from it. The link opens the app if the app is installed, and shows the invitation on this website if it is not, so that somebody who has not installed the app yet can still see the code and use it when they create an account.
- A code is not a secret, and it is not a credential: it identifies who invited somebody, and it grants no access to your account.
- A code can be retired. A retired code no longer resolves, and a link built from it will say so rather than attaching a referral that will not qualify.
- The code is applied to the new account by the server when that account is created. Nothing the client sends can name an inviter — that is why a modified link cannot attribute a referral to somebody else.
What the platform records about an invitation is described in the privacy policy: the connection between the two accounts, its state, and the reward if there is one. It does not record who you sent the link to, and it cannot see that — it sees the code when it is used.
Contact
Questions about this policy go to [CONTACT EMAIL]. The help centre answers questions about how the platform works, and the app itself is where an account is managed.