Eligibility
Read the eligibility clause. The clause names who can claim; the desk treats the eligibility clause as the rule.
Home · Bonus code
Promo categoryA bonus code is a category on a rummy operator's account screen, not a published numeric coupon. This page describes what the operator publishes about its bonus category, what the desk cannot publish about a live code, and where to verify a code on the operator's own page.

The desk does not paste a specific jackpotnow bonus code in any visible copy. The desk's editorial position is that the live code is the operator's own publication on the wallet or promotion tab; pasting it on a third-party site creates a category misuse, not a service to the reader.
Read the eligibility clause. The clause names who can claim; the desk treats the eligibility clause as the rule.
Read the time window. The window is the operator's contract with the reader; the desk recommends a screenshot of the window on the date of the read.
Where a wagering requirement applies, the requirement is named in the terms. Treat the requirement as the rule; do not paste a numeric multiple here.
The summary of the three clauses is the audit trail. The desk recommends the reader keep the screenshot, the summary, and the operator's URL in the same folder.
Where a family member is reading this page rather than the reader, the practical next step is identical to /responsible-play/'s family-side framing: ask the reader to open the wallet or promotion tab and read the eligibility, the time window and the wagering requirement together. The offer terms are the rule; the family-side habit is to keep them readable on the reader's own device.
The desk does not list a generic "use this code" recommendation. A generic code is the marketing pattern the family-side read is meant to displace; the family-side habit is the same: keep the audit trail on the operator's own page, not on the desk's.
The wallet or promotion tab is the operator's own publication. The desk recommends the reader open the tab and read the eligibility, the time window and the wagering requirement together.
Read the terms pageOn the wallet or promotion tab. The panel is the offer's headline.
A screenshot of the terms on the date of the read. The screenshot is the audit trail.
A multiplier named in the offer's terms. Treat the requirement as the rule; do not paste a numeric multiple on this page.
On the wallet or promotion tab. The tab is the operator's own publication.
An offer panel, the offer's headline, and the offer's terms. The terms are the rule.
A specific jackpotnow bonus code, a specific bonus value, or a "free money" framing.
Read the eligibility clause. The clause names who can claim; the deck treats the eligibility clause as the rule.
Read the time window. The window is the operator's contract with the reader.
Where a wagering requirement applies, the requirement is named in the terms. Treat the requirement as the rule.
This page is the contextual read; the operator's own help-centre article is the rule. The contextual read and the rule are aligned when the operator publishes the rule on the help centre. The contextual read and the rule are unaligned when the operator does not publish a rule on the help centre; the desk treats the unaligned case as the audit trail.
The contextual read sits between the reader's own jurisdiction and the operator's own publication. The reader's jurisdiction is the rule the reader is actually making the decision on; the operator's own publication is the rule the reader is binding to. The two are aligned when the reader's jurisdiction is one of the published rules; the two are unaligned when the reader's jurisdiction is not. The desk's habit is to assume the reader's jurisdiction is one of the published rules; the reader's audit trail is the operator's help-centre article number on the date of the read.
The contextual read and the regulator's publication interact in the rule shape: the regulator's publication is the central framing the desk aligns with; the contextual read is the desk's reading of the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the regulator's publication is unchanged; the two are unaligned when either side rotates.
The audit trail is the operator's help-centre article on the date of the read. The reader's screenshot is the audit trail; the operator's reply on the /customer-care/ ticket is the rule. The two are aligned when the screenshot matches the reply; the two are unaligned when the screenshot shows a different rule. The desk's habit is to assume the screenshot is the audit trail and the operator's reply is the rule; the reader's audit trail is the screenshot and the reply together.
The audit trail and the central framing interact in the rule shape: the central framing is the Promotion and Regulation of Online Gaming Act 2025; the audit trail is the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the central framing is unchanged; the two are unaligned when either side rotates.
The audit trail and the per-state rule interact in the rule shape: the per-state rule is the regulator's own publication; the audit trail is the operator's help-centre article. The two are aligned when the regulator's publication is unchanged and the operator publishes the rule on the help centre; the two are unaligned when either side rotates. The desk's habit is to assume the per-state rule is the regulator's own publication; the reader's audit trail is the per-state rule itself.
The desk does not paste a numeric withdrawal window. The operator does not publish one; the desk does not invent one. The reader's audit trail is the operator's help-centre article; the regulator's publication is the audit trail for any per-state eligibility.
The desk does not paste a per-operator licence. The regulator's own publication is the audit trail. The desk does not paste a per-state eligibility list; the reader's jurisdiction is the audit trail. The desk does not paste a "guaranteed" claim; the central framing is the audit trail.
The contextual read is the same across operators; the operator's publication differs. The contextual read sits between the reader's own jurisdiction and the operator's own publication. The desk's habit is to assume the contextual read is the contextual read; the reader's audit trail is the operator's help-centre article number on the date of the read.
The contextual read and the operator's publication interact with the central framing: the central framing is the Promotion and Regulation of Online Gaming Act 2025; the contextual read is the desk's reading of the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the central framing is unchanged; the two are unaligned when either side rotates.