Last written 26 July 2026 · PT

1. Who this page is about

PT publishes this website and supplies the engines described on it. Where this page says we, us or our, it means PT.

This page has two halves. The first half covers visitors to this website. The second half covers the engines we supply to a customer, where the customer decides what happens to the information and we act on their instructions.

The product name and the company details on this page stand as placeholders until launch. A named legal entity, a registered address and a supervisory authority reference will replace them before this site goes live.

2. Visitors to this website

2.1 What we collect when you browse

Reading this site requires no account and no form. Our host records the ordinary technical details every web server records, so pages can be served and the service can be kept healthy and safe.

The address of the page you asked for.
The date and time of the request.
Your browser type and version.
Your network address, held for a short period for security reasons.

The site loads no third party analytics, no advertising pixels and no social widgets. Every asset a page needs comes from the same place the page comes from.

2.2 What we collect when you write to us

The contact form asks for your name, your work email address, your company, what you run, the engine you are most interested in, and your message. A hidden field sits on the form to catch automated submissions, and a value in that field causes the submission to stop.

We use what you send for a single purpose. Replying to you and arranging a demonstration.

2.3 How long we keep it

Server records of page requests: up to ninety days.
Messages sent through the contact form: up to twenty four months from your last contact.
Anything that becomes part of a signed agreement: as long as the agreement and the law require.

2.4 Our legal grounds

We rely on our legitimate interest in running a business website, answering the people who write to us, and keeping the service secure. Where you begin a commercial conversation with us, we also rely on the steps taken ahead of a contract.

3. Cookies and local storage

This site keeps one small item in your browser, and it exists to remember that you have seen the cookie note. It carries the value seen and nothing else. Clearing your browser storage removes it, and the note appears again on your next visit.

The cookie page describes this in full.

4. The engines

4.1 The roles

A customer who licenses an engine decides which information enters it and what happens to it. In data protection language that customer is the controller, and we act as the processor on their documented instructions.

A player who wants to understand how their information is handled should ask the casino brand they play with. That brand holds the relationship and the answers.

4.2 What the engines process

The set is agreed with each customer before the connection is built. It commonly covers:

An identifier that lets a record be matched with the customer platform.
Activity events such as registrations, deposits, sessions and bets.
The values an engine needs to reach its money decisions.
The decisions themselves, and the record of how each one was reached.
For the affiliate engine, the referral codes and the partner records attached to them.

Player balances stay on the customer platform. The engines hold the rules, the counting and the record, then signal the customer platform at the moment of a money decision.

4.3 Sub processors

We use a small number of suppliers for hosting and platform operations. A current list goes to every customer, and a customer receives notice ahead of a change so they can raise an objection.

4.4 Security measures

Access follows the role a person holds and the brands that role covers.
Each brand keeps its own settings, its own switches and its own records.
Calls out to a customer platform carry a signature the receiver checks.
Money decisions are written down and stay readable afterwards.
An engine stays switched off until somebody at the customer switches it on.

4.5 A personal data breach

A breach affecting a customer gets reported to that customer without undue delay, together with what we know, what we are doing, and what we suggest they do.

5. Sharing

We sell personal information to nobody, and we share it with nobody for advertising. Sharing happens in three cases only: a supplier acting for us under contract, a customer receiving information that belongs to them, and a lawful request we are obliged to answer.

6. Transfers

Where information travels outside the region it was collected in, we put an approved transfer mechanism in place first, and we describe the arrangement to any customer who asks.

7. Your rights

Under the law that applies to you, you may hold rights to:

Ask what personal information we hold about you, and receive a copy.
Have something corrected when it is wrong.
Ask for erasure where the grounds for holding it have ended.
Ask us to restrict what we do with it.
Object to processing that rests on a legitimate interest.
Receive what you gave us in a portable form.
Complain to your supervisory authority.

Write to hello@pt.example and we will answer inside one month. A request about a record held for a casino brand goes faster if you send it to that brand, because the brand decides the outcome.

8. Children

This website is aimed at businesses and their staff. We collect nothing knowingly from anyone under the age of eighteen through this site.

9. Changes to this page

When this page changes, the date at the top changes with it. A change that materially affects a customer arrives by direct notice as well.

10. Reaching us

Email hello@pt.example for anything on this page. A named contact for data protection, and a postal address, will sit here before launch.

11. Review status

This page is written to be read and understood, and it awaits review by a qualified adviser in each market where the engines are sold. Treat it as a working draft until that review lands.