What a referral code is
A referral code is a short string a reader shares with another adult player. The reading-room desk's note is that referral codes usually come with conditions on both sides: the referrer receives a small credit when the referee signs up and meets the conditions, and the referee receives a small credit on first deposit.
This page describes what referral codes usually mean, what they usually require, and the things an adult reader checks before sharing one. The reader who has read this note has read the most useful referral note.
What the referrer usually receives
Most apps credit the referrer with a small amount after the referee signs up, completes KYC and meets a minimum deposit. The credit is usually released after the referee has met the conditions; the credit is usually subject to a playthrough multiple before it can be withdrawn.
Three things the referrer should check
- The minimum deposit the referee must make
- The playthrough multiple on the credit
- The expiry window on the credit
The reading-room reader who has checked all three has read the most useful referrer note.
What the referee usually receives
Most apps credit the referee with a small amount on first deposit. The reading-room desk's note is that the referee's credit is usually subject to the same playthrough multiple the bonus code is subject to. The reader who has read the bonus-code page has read the most useful description of the conditions.
Sharing a referral code
The desk's note on sharing a referral code is that the reader should share it only with another adult player who has already decided to open an account. Sharing a referral code by posting it publicly is generally not allowed by the publisher; the reader who has read the publisher's terms has read the most useful sharing note.
What to read next
The routes that pair well with this one are the bonus-code note, the responsible-play guide and the safety explainer. The reading-room reader who has read all four has read the full referral spine.
Why a referral code is a short piece of writing
A referral code is a short string the reader shares with another adult player. The reading-room desk's note is that the short string comes with a longer paper trail: the conditions the publisher publishes, the credit the referrer receives, and the credit the referee receives. A careful reader reads the longer paper trail before sharing the short string.
The reader who has read the conditions has read the most useful referral-code note.
Three things to share, three things to keep
- Share: the code, the app, the publisher's published terms
- Keep: the referee's registered mobile number, the deposit record, the credit record
When to share
The desk recommends sharing a referral code only with another adult player who has already decided to open an account. The reader who has shared a referral code with a player who is still deciding has read the least useful sharing moment. The reader who has shared with a player who has decided has read the most useful one.
What to read next
The routes that pair well with this one are the bonus-code note, the responsible-play guide and the safety explainer. The reading-room reader who has read all four has read the full referral spine.
What does not change when a code is shared
The rules do not change when a referral code is shared. The KYC requirements do not change. The responsible-play tools do not change. The reading-room desk's note is that a referral code is a small piece of writing, not a content change. The reader who has read this note has read the most useful description of what does not change when a code is shared.
The desk's read is that the credit conditions also do not change between the referrer and the referee. The reader who has read both sides of the conditions has read the most useful referral-code note.
- The rules do not change when a code is shared
- The KYC requirements do not change when a code is shared
- The responsible-play tools do not change when a code is shared
- The credit conditions apply equally to referrer and referee
The reading-room reader who has read this list has read the most useful description of what does not change when a code is shared.
What the reader checks before sharing
Before sharing, the reader checks the publisher's published terms for public sharing. Most apps prohibit public sharing of referral codes. The reader who has read the publisher's terms has read the most useful sharing note.
What to read next
The routes that pair well with this one are the bonus-code note, the responsible-play guide and the safety explainer. The reading-room reader who has read all four has read the full referral spine.
A short reading-room reading list
The reading-room routes that pair well with the referral-code note are the bonus-code note, the responsible-play guide and the safety explainer. The reader who reads all four has read the full referral spine. The referral-code reader who has not visited the bonus-code note is the reader who has skipped the foundation.
The desk's read is that the referral-code reader revisits the referral-code note when a code is to be shared. The reader who has done both has read the most useful version of both.
Three reading habits worth practising
- Re-read the referral-code note before sharing a code
- Re-read the bonus-code note before entering a code
- Re-read the responsible-play guide once a quarter
What to read next
The routes that pair well with this one are the bonus-code note, the responsible-play guide and the safety explainer. The reading-room reader who has read all four has read the full referral spine.
A final note from the desk
The reading-room desk publishes this referral-code note as part of the editorial bulletin on the room's pages. The desk reads the referral-code notes quarterly and notes any changes at the foot of this note. The reader who has revisited this note has read the most useful version of it.
The reader who has read the bonus-code note has read the most useful companion to the referral-code note. A referral-code reader who has not read the bonus-code note has read the lesser companion.
What the desk reads when it revisits this note
When the desk revisits this note on the quarterly review cycle, the desk reads the page against the source and against the reader's likely intent. The reading-room note is that the page is more useful when it has been read at least once by the reader before the revision; the reader who has read a page once has read the most useful baseline. The reader who revisits a page after a quarter has read the most useful updated version.
The desk's read is that the quarterly review also creates a small archive of dated revisions. The reader who has revisited a page after several quarters has read the most useful arc of the page. The desk publishes a dated note at the foot of every page when a revision has changed the content. The reader who has read the editorial standards page has read the most useful description of how the desk handles revisions.
The desk reads every page against the same three criteria. First, accuracy against the source. Second, plain-language writing without jargon. Third, adult-reader framing, no promotional language. A page that meets all three criteria on the quarterly review has read the most useful test. A page that fails one of the three has read the most useful reason for a revision.
What the desk does not revise
- The desk does not revise the URL of a page once it has been published
- The desk does not revise the publication date of a page without noting the revision
- The desk does not revise the editorial voice of a page without noting the revision
- The desk does not revise the page structure without noting the revision
The reading-room reader who has read this list has read the most useful description of what the desk does not revise.
How the desk handles reader feedback
The desk reads every message sent to the contact page. The desk replies within a week to messages that include a name, a return address and a clear subject. The desk publishes a dated correction note at the foot of a page when a verified error has been reported. The desk's read is that a feedback message with a dated source is more useful than a feedback message without one; the reader who has included the source has read the most useful feedback format.
The desk also reads the messages for patterns. A pattern the desk has noticed in reader feedback is the request for more practical examples; the desk responds by adding more examples in the next quarterly review. The reading-room reader who has written a feedback message with a specific example has read the most useful contribution to the next quarterly review.
Three kinds of useful feedback
- A correction with a dated source
- A practical example that illustrates the page's content
- A suggestion that links the page to a related page in the room
The reading-room reader who has included one of these three has read the most useful feedback format.
What the reader should expect on the next quarterly review
The reader should expect a small update to the page's content. The desk publishes a dated note at the foot of the page when the update has changed the content. The reader who has revisited the page after the quarterly review has read the most useful updated version. The reader who has read the editorial standards page has read the most useful description of how the desk handles updates.
The desk's read is that the quarterly review is also a useful opportunity for the reader to revisit related pages. The reader who has revisited the related pages has read the most useful full route. The reader who has read all three related pages has read the most useful reading-room spine for this route.
What to read next
The routes that pair well with this one are the bonus code note, the responsible play note and the safety note. The reading-room reader who has read all four has read the full refer a friend spine.