What this notice covers
betnowin.com's privacy notice applies to betnowin.com and to any subdomain We operates. It does not apply to the betnow platform on its own domain, to any third-party service betnowin.com links to, or to any platform or service We do not operate. A reader who navigates from betnowin.com to a third-party site should read that site's privacy notice before providing any personal data.
We collect a small amount of data needed to operate betnowin.com. We do not collect data We do not need. We do not sell, rent or trade reader data with third parties. We do not use reader data for advertising, profiling or any commercial purpose beyond betnow's editorial work.
What We collect
We collect three kinds of data: technical data needed to serve betnowin.com (request logs, error logs, browser type and version), aggregated analytics data that We use to understand which pages are read and which pages are not, and any data a reader chooses to send to betnowin.com through a contact form or an email. We do not collect any data beyond these three categories.
The technical data is retained for 30 days and then deleted. The aggregated analytics data is retained indefinitely in aggregated form (page counts, referrer counts) but is not retained in a form that identifies a specific reader. Any data a reader sends to betnowin.com through a contact form is retained for the time needed to respond and then deleted, unless the reader asks for the data to be retained for a longer period.
What We do not collect
We do not collect names, email addresses, phone numbers, addresses, payment information, government-issued ID numbers, biometric data, location data beyond what the browser sends in a request, or any data that identifies a specific reader beyond the technical data described above. We do not use cookies for tracking, advertising or profiling. We do not use third-party analytics that track readers across sites.
We do not collect data from readers who do not contact betnowin.com. A reader who visits betnowin.com without contacting betnowin.com sends only the technical data the browser sends in any HTTP request, and the technical data is retained for 30 days and then deleted.
Cookies
We use a minimal set of cookies needed to operate betnowin.com. The cookies include a session cookie that lasts for the duration of the visit and a preferences cookie that lasts for 30 days. We do not use third-party cookies, advertising cookies or tracking cookies. We do not use cookies to identify a specific reader across visits.
A reader who prefers not to accept cookies can configure the browser to block cookies. Blocking the session cookie may affect betnowin.com's behaviour, the mobile menu, the sticky CTA and the in-page anchors may not work correctly. We do not promise a usable experience with cookies disabled.
Third-party services
We use a small number of third-party services to operate betnowin.com: a content delivery network (CDN) to serve betnowin.com's static assets, a font service to serve betnowin.com's typography, and an analytics service to understand which pages are read. We do not use third-party advertising networks, third-party tracking services or third-party data brokers.
The CDN and the font service receive the browser's IP address and the request URL as part of normal HTTP traffic. The analytics service receives the request URL and the referrer URL as part of normal HTTP traffic. None of the three services receive personal data from betnowin.com, because We do not send personal data to the three services.
Data retention
betnowin.com retains technical data for 30 days, aggregated analytics data indefinitely in aggregated form, and any data a reader sends to betnowin.com for the time needed to respond. We do not retain data beyond the time needed for the purpose it was collected. We do not retain data for legal hold, backup or any other secondary purpose.
A reader who asks betnowin.com to delete any data the reader has sent retains the right to do so. betnowin.com deletes the data within 30 days of the request and confirms the deletion in writing.
Reader rights
A reader has the right to ask what data betnowin.com holds about the reader, to ask betnowin.com to correct the data, to ask betnowin.com to delete the data, and to ask betnowin.com to confirm the deletion. We respond to reader requests within 30 days. We do not charge for responding to a reader request.
A reader who makes a request should use the contact path described below. We may need to verify the reader's identity before acting on a request, to prevent betnowin.com from acting on a request from someone pretending to be the reader.
Children
We do not collect data from children. Betnowin.com is intended for adult readers who are 18 or older. A reader who is under 18 should not provide any data to betnowin.com and should not use the contact form. betnowin.com deletes any data received from a reader who is under 18 as soon as betnowin.com becomes aware of the reader's age.
International transfers
betnowin.com's hosting and CDN services may store or process data outside the reader's jurisdiction. We rely on the standard contractual clauses published by the European Commission and on the published data-processing terms of betnowin.com's service providers. We do not transfer data to a country that lacks adequate data-protection law without a contractual safeguard.
Changes to this notice
We may update this privacy notice from time to time. betnowin.com posts the updated notice on this walkthrough with a date stamp at the top of the walkthrough. We do not retroactively change the notice to apply to data collected before the update. A reader who disagrees with an update can stop using betnowin.com and ask betnowin.com to delete any data the reader has sent.
How to contact betnowin.com
A reader who has a question about this privacy notice or a request about the reader's data should use the contact form on the customer-care page. We respond to privacy requests within 30 days. We do not charge for responding to a privacy request.
Where to go next
For the four trust gates, account, payment, table integrity, dispute, the safety desk is the place to start. For the controls the platform exposes, the responsible-play desk covers deposit caps, session limits and self-exclusion. For the editorial standards We follow, the about page is the place to start.
Six questions readers ask about privacy
Each answer names what the desk collects, what it does not, and the verification step the reader can run.
1. Does the desk set advertising cookies on this domain?
No. The desk uses a minimal set of cookies: a session cookie that lasts for the duration of the visit and a preferences cookie that lasts for 30 days. The desk does not use third-party cookies, advertising cookies or tracking cookies on this domain.
2. What does the desk do with request logs?
The desk retains technical request logs (request URL, browser type, response code) for 30 days and then deletes them. The desk uses the logs to diagnose errors and to understand which pages are read. The logs are not retained for advertising, profiling or commercial reuse.
3. Does the desk sell or trade reader data?
No. The desk does not sell, rent or trade reader data with third parties. The desk does not use reader data for advertising, profiling or any commercial purpose beyond the desk's editorial work on this domain.
4. How long does the desk keep aggregated analytics?
The desk retains aggregated analytics indefinitely in aggregated form (page counts, referrer counts). The aggregated form does not identify a specific reader. The desk does not retain analytics in a form that ties a visit to a specific browser, IP address or account.
5. Can a reader ask the desk to delete data the reader sent?
Yes. A reader can use the customer-care page to request deletion. The desk deletes the data within 30 days of the request and confirms the deletion in writing. The desk may need to verify the reader's identity before acting on a request, to prevent the desk from acting on a request from someone pretending to be the reader.
6. Where is the desk's data stored?
The desk's hosting and CDN services may store or process data outside the reader's jurisdiction. The desk relies on the standard contractual clauses published by the European Commission and on the published data-processing terms of the desk's service providers. The desk does not transfer data to a country that lacks adequate data-protection law without a contractual safeguard.
How a reader can limit what We collect
We collect a small amount of data; a reader can limit what We collect by configuring the browser, by not contacting betnowin.com, and by asking betnowin.com to delete any data the reader has sent.
Browser controls
The browser controls what cookies are accepted and what HTTP headers are sent. A reader who blocks all cookies will disable the session cookie and the preferences cookie, which may affect betnowin.com's behaviour. A reader who blocks third-party cookies will disable betnowin.com's third-party cookies (We do not use any, so the change has no effect on betnowin.com's data collection).
Not contacting betnowin.com
A reader who does not contact betnowin.com sends only the technical data the browser sends in any HTTP request. The technical data is retained for 30 days and then deleted. A reader who prefers not to send any data should configure the browser to block requests to this domain; We do not promise a usable experience with requests blocked.
Asking betnowin.com to delete data
A reader can ask betnowin.com to delete any data the reader has sent. betnowin.com deletes the data within 30 days of the request and confirms the deletion in writing. We may need to verify the reader's identity before acting on a request, to prevent betnowin.com from acting on a request from someone pretending to be the reader.
Asking betnowin.com to confirm the deletion
betnowin.com confirms the deletion in writing after the data has been deleted. The confirmation is sent to the contact channel the reader used to make the request. A reader who does not receive a confirmation within 30 days should follow up with betnowin.com through the same channel.