How the desk handles personal data
Reading the pages of Velqorixs leaves very little with the desk. This notice covers the few things that can reach it: a message sent through the form, the record of your cookie choice, the traffic that passes through the servers, and Google measurement if it is ever switched on and you agree to it.
The controller, and where to write about your data
Personal data collected through Velqorixs at velqorixs.uk has one controller: [COMPANY — to be confirmed], company number [No.], registered in [England and Wales], with its registered office at [Registered office — to be confirmed]. That company publishes the site and decides what is collected and for what purpose.
Questions about personal data, and any request under the rights listed further down, go to notices@velqorixs.uk. Other messages for the desk go to desk@velqorixs.uk or through the form on the contact page. This notice is written under the UK GDPR and the Data Protection Act 2018.
A message sent through the contact form
The form asks for the details below. The field names are the ones your browser sends with the message; two of them are never typed by a person and exist only to keep automated spam out.
| What you fill in | Name of the field | Needed to send? |
|---|---|---|
| Your name | who_writes | No |
| E-mail address for the reply | reply_to | Yes |
| What the message is about | regarding | Yes |
| The casino concerned | casino_in_question | No |
| Address of the page concerned | from_page | No |
| Your message | note | Yes |
| Box confirming you have read this notice | consent_ok | Yes |
| Hidden field, left empty by people | site_url | — |
| Moment the form was opened, set by the browser | started_at | — |
The website does not store what you send. The server turns the message into an e-mail to desk@velqorixs.uk and forgets it; if sending fails, nothing you typed is kept and the page shows an address to write to instead. To stop one connection flooding the inbox, the server keeps your IP address only in scrambled (hashed) form, together with the times of messages sent from it in the last hour; that record holds no name and no message.
The desk uses the message only to read it and answer it. The lawful basis is the publisher’s legitimate interest in replying to people who write; for a request about your own data, it is the legal duty to answer such requests. Leave card numbers and passwords out of the message, and do not attach copies of identity documents: the desk has no use for them.
Visits, server records and the Google tags
Two kinds of data pass the site without the desk asking for them: what a server sees on any visit, and what Google would see if you allowed it.
What every visit passes through
To deliver a page, the hosting server and Cloudflare, which sits in front of it, handle your IP address, the page asked for, the time, and what your browser says about itself. These records serve delivery, fault-finding and protection against attacks, under the publisher’s legitimate interest in a working, safe site. The desk does not use them to work out who a reader is.
Google Analytics, Google Ads and Consent Mode
The site is built to use two Google services: Google Analytics 4, which adds up how often each page is read, and Google Ads, which tells the publisher whether its adverts bring readers. Both run via the Google tag (or via Google Tag Manager, if that is chosen instead). Neither is connected today. They will be loaded only if you agree and only once the tags are switched on.
Before you answer the cookie box, each page sets Google Consent Mode v2 to “denied” for analytics storage, advert storage, advert user data and advert personalisation. The Google tag itself is not fetched until you allow at least one of the two kinds of measurement. If you allow visit counting and refuse advert measurement, the tag is told to hold back advertising identifiers.
With your consent, Google Analytics would receive the pages viewed, the type of device and browser, an approximate location worked out from your IP address, and a random identifier kept in a cookie; Google Ads would receive the fact that a visit came from one of the site’s adverts, and Google may use that for adverts elsewhere. The lawful basis is your consent, which you can withdraw at any time through “Change cookie choice” in the footer. The cookies themselves are listed on the cookies page.
Who else handles the data
No personal data is sold or handed to the casinos on the site. A “Visit site” link carries a code that tells the casino the visit came from Velqorixs; it carries nothing you typed here. Once you are on the casino’s site, its own privacy notice applies. How those links pay for the site is set out under funding.
- The hosting provider runs the server that stores and delivers the pages and processes the contact form.
- Cloudflare carries traffic to the site, filters attacks and may route mail sent to the site’s addresses on to the mailbox where it is read.
- The mail service that delivers form messages, and the mailbox provider where the desk’s inbox sits, together with any support contractor the publisher engages to answer it under a written contract.
- Google, for Google Analytics and Google Ads, only once the tags are switched on and only after your consent.
- Courts, the police or a regulator, where the law requires the publisher to disclose data.
Data that leaves the United Kingdom
Cloudflare, Google and some mail services process data outside the UK, in the United States and elsewhere. Where they do, the transfer rests on UK adequacy regulations for that country (for the United States, the UK Extension to the Data Privacy Framework, for companies certified under it) or on the International Data Transfer Agreement or Addendum issued under UK law. You can ask notices@velqorixs.uk which safeguard covers a given recipient.
How long each item is kept
- Messages and replies: for as long as the exchange needs, then deleted no later than 12 months after the last reply, unless a legal claim or a request about your data requires them for longer.
- The anti-spam record: times older than one hour are disregarded, and the small file is removed when the server clears its temporary files; the record never holds a name or a message.
- Your cookie choice: 365 days in your own browser, after which the box asks again.
- Server and Cloudflare records: removed by automatic rotation; the desk keeps no copies of its own.
- Google data: nothing exists while the tags are off. The retention period chosen for Google Analytics will be stated here before the tag is switched on.
Your rights under the UK GDPR
You may ask for a copy of the personal data the publisher holds about you, have it corrected, have it deleted, restrict how it is used, object to its use, and receive data you supplied in a form a computer can read. Where processing rests on consent, you may withdraw consent at any time; for the Google tags, “Change cookie choice” in the footer does it in one step.
Write to notices@velqorixs.uk. A request costs nothing and is answered within one month; a complex one can take up to two months more, and you will be told if it does. The desk may ask for enough detail to be sure the data is yours. No decision about you is made by automated means alone.
If you are unhappy with the answer
A complaint may also go to the UK regulator for data protection, the Information Commissioner’s Office (ICO), whatever the desk has answered. Writing to notices@velqorixs.uk first often settles the matter faster, and the ICO may ask whether you have done so.
Readers under 18, and changes to this notice
The site is meant for adults (why 18+), and the desk does not knowingly collect data about anyone younger. If a person under 18 has written through the form, a note to notices@velqorixs.uk is enough to have the message deleted.
This notice was last updated on 14 November 2026. When it changes, the new date appears here, and a change to what is collected is described in the notice itself. The rules for using the site are on the conditions of use.
Page revised