This Policy explains how the operator of williamdatahub.com (trading as William Data Insights / WDI) processes personal data for the public site, accounts, and prepaid research access. Using the service means you have read this Policy together with the Disclaimer and Terms.
1. Operator
Controller: the operator of William Data Insights. Privacy and legal notices should use the contact method in the Terms. Those channels are for privacy and legal requests only — not for model support or disputes about picks.
We may appoint or change infrastructure and payment vendors. Where law requires a processor list, we will provide a current summary on a verified request. This Policy does not publish feed maps, hosting topology, or vendor contracts.
2. Data we process
Site and security
- Technical logs needed to deliver, cache, and protect the site (for example IP address, user agent, requested paths, timestamps, and host-derived network metadata).
- Essential session storage on your device so a signed-in plan can be recognised.
Accounts and access
- Email and authentication credentials (stored in hashed or equivalent protected form).
- Plan type, prepaid period, and payment/order references required to grant or revoke access.
- Invite / Partner codes, and whether a paid order was referred, when the Partner program is enabled (not betting history).
- Operational messages (verification, expiry, security).
What we do not treat as betting data
We do not ask for bookmaker logins, wagering bank cards, or your betting history. Research views you open are used to run the product and prevent abuse — not to place or underwrite a wager on your behalf.
3. Purposes and legal bases
- Contract / requested access: create an account, complete prepaid crypto or card checkout you start, show the research tier you bought, and (when the Partner program is enabled) attribute a referred paid order and settle Partner commission.
- Legitimate interests: security, fraud and scrape prevention, reliability, Partner abuse controls, and basic audience measurement if we enable it.
- Legal obligation: tax, accounting, and lawful requests.
- Consent: only if we later add non-essential cookies; this Policy will be updated first.
Model scores and fixture research are not automated decisions that produce legal effects about you. They describe matches, not your credit, employment, or a licence.
4. Cookies and similar technology
We use what is required to keep you signed in and to secure the site. When the Partner program is enabled we may store an essential invite code on your device so a shared invite link can be applied at register or sign-in. That storage is not an advertising pixel; it does not record commission by itself. Commission is recorded only after a confirmed payment. You may block non-essential storage in your browser; the public Hub may still load, but an invite code may need to be typed again.
We do not run advertising pixels today.
5. Processors and transfers
Personal data may be handled by hosting, CDN, security, email, cryptocurrency payment, and (for card/PayPal) hosted-checkout vendors we appoint. The checkout invoice identifies the processor for that payment. Vendors may process data outside your country under their terms. We do not sell personal data.
Fixture, odds, and league-identity inputs used to build research pages are supplier materials, not a file of your personal data. Supplier identities and contracts are not disclosed in this Policy.
6. Retention
Security logs: short operational windows set by us or the host. Account, payment, and Partner commission records: for the life of the account and thereafter as needed for disputes, accounting, and law, then deletion or irreversible aggregation.
7. Your choices
Depending on applicable law you may request access, correction, deletion, or export of personal data we hold, or object to certain processing. We may refuse requests that are unfounded, excessive, or that would compromise security, other users, or our research product. Privacy requests do not entitle you to model weights, unpublished slates, or vendor credentials.
8. Children
The service is not directed at anyone under 18. If we learn a minor created an account, we will close it and delete associated personal data we no longer need.
9. Changes
Material changes will be posted with a new Last updated date. Continued use after that date is acceptance, except where a stricter local rule requires another mechanism. Related: Disclaimer · Terms of Service.