A plain guide to Ruby registration: eligibility, the form itself, and the parts worth getting right the first time.
Age is the first thing any licensed operator checks, and in Canada there is no single number to check against. The law says 18 or 19 depending on the province or territory, a provincial matter rather than a federal one. This review site is written for readers 19+, which is the stricter of the two thresholds and therefore safe everywhere in Canada. The operator sets its own eligibility rules on top of the law, and those are worth reading on its own site before you start.
The split across Canada looks like this:
| 19 and over | Ontario, British Columbia and most other provinces |
| 18 and over | Alberta, Manitoba and Quebec |
The long version: 19 in Ontario, British Columbia and most provinces, and 18 in Alberta, Manitoba and Quebec. It is your address that decides, though nothing stops an operator applying one higher limit across the board.
The sequence is consistent across this industry, whatever the form looks like:
That is the pattern, not a walkthrough of Ruby's own form — we have not registered there ourselves.
Expect the form to want these:
The date of birth carries the weight here: it is the field the age rule is applied to. Entering details that are not yours creates a problem later rather than now, because the name on the account has to match the name on whatever payment method you use.
Nothing has to be scanned or photographed to open an account in the ordinary case. Those checks belong to a later stage and are normally triggered by a withdrawal rather than by signing up. What that means practically: registering costs you nothing and commits you to nothing. The detail of what Ruby asks for and when is covered on our withdrawals page.
The empty account is worth having on its own — the real terms, the real lobby and the real payment options are all visible before a deposit. Worth doing straight away: put limits in place before there is anything to lose (responsible gaming), and look at what the welcome offer asks for in return — the bonus page has the terms.
What looks like an intrusive form is mostly a regulatory requirement to identify account holders. What they may do with it beyond that — marketing especially — is set out in the privacy policy and in those consent boxes, which are worth reading separately from the terms.
The registration form works in a phone browser the same way it works on a laptop — nothing needs to be installed to open an account. Autofill is the one thing worth watching: it is good at addresses and bad at dates of birth, and a wrong date here reads as an age problem. Our app page covers mobile play itself.
This is not a throwaway password: the account it guards will eventually hold funds and personal data. One password, used nowhere else, does more than any special character requirement. Anything about signing in later, including recovery, is on the login page.
Opening another account when one exists is usually caught and usually ends badly for the bonus. We cannot give a universal answer: this varies by operator, and Ruby's own terms are the place it is written down. A forgotten password is not a reason to register again; the login page covers getting back in.
If a self-exclusion is in place, registering elsewhere undoes the only thing it was meant to do. Schemes differ in reach: some cover a single operator, others a whole regulated market, and coverage is not something we can confirm for any specific brand. The tools and the support services are covered on our responsible gaming page.
The honest boundary: we have not opened an account at Ruby, so its exact form, its own stated minimum age and its processing times are not claims we make. The legal ages are Canada's, the 19+ line is ours, and the rest is standard industry practice rather than brand-specific fact.
Because that is how eligibility is verified: the date is checked against the legal age in your province.
Set deposit limits before the balance exists rather than after, and read the actual terms of any offer before accepting it.
Practice varies. Shared addresses and devices are sometimes treated as connected accounts, so the operator's terms are the place to check.
It is generally optional and decided at the first deposit. The bonus page sets out what accepting it requires.
No. Registration happens in a browser; anything about apps is covered on our app page.
The form checks the date immediately. Proof of it, if asked for at all, normally arrives at the verification stage rather than now.
Eligibility and terms change — the operator's own page is the current version.
Visit Site