Privacy Policy Publication Status
- Effective date
- This policy is not yet in effect.
- Last updated
- A publication date cannot be stated until the deployment audit is complete.
- Publication status
- Blocked pending verification of the responsible party, contact channel, service providers, technical configuration, safeguards, and retention schedule.
Dice Rules & Odds is planned as an informational, operator-free reference about dice-game rules and probability. Its privacy policy will apply to this website and to contact or correction workflows operated on its behalf. It will not govern independently operated regulator, support, museum, standards, or educational websites reached through external links.
Review privacy choices and requests or read the privacy contact status.
Who is responsible and what this policy covers
- Website
- Dice Rules & Odds
- Responsible party
- No verified legal name or responsible-party details were supplied.
- Privacy contact
- No monitored privacy contact method was supplied.
The responsible party’s verified name, applicable identifying details, and monitored contact method must be added before publication. General information about the project belongs on About Dice Rules & Odds.
The completed policy must cover:
- requests for pages and other website files;
- hosting, logging, security, and performance systems;
- analytics, cookies, consent records, and browser storage actually used;
- editorial messages, correction reports, and source submissions;
- privacy questions and applicable privacy requests; and
- service providers processing information on the site’s behalf.
Data practices at a glance
A static website can process technical information through its hosting and network infrastructure. The absence of PHP does not establish that no visitor information is processed.
| Data or interaction | Source | Purpose | Recipient | Retention | Status |
|---|---|---|---|---|---|
| Page-request technical data | A visitor’s browser and network | Transmit and deliver a requested resource | Deployment infrastructure that has not been identified | Cannot be stated without provider and configuration records | Network transmission is necessary; logging practices remain unknown |
| Contact or correction submissions | Information deliberately supplied by a visitor | Respond to a message or evaluate an editorial report | No deployed workflow or processor was identified | No approved retention schedule was supplied | Must not be presented as available until implemented and disclosed |
The available evidence supports only the limited conclusions above. It does not establish whether technical requests are logged or whether analytics, cookies, forms, email tools, anti-spam services, consent systems, or embeds are deployed.
Terms used on this page
- IP address
- A network address used to route a request between a device and an online service. It may be treated as personal information in some circumstances.
- Cookie
- A value a website or service asks a browser to store and return with later requests.
- Local storage
- Information stored in a browser for a website without using a traditional cookie.
- Analytics
- Technology used to measure matters such as visits, navigation, performance, or feature use.
- Service provider
- An outside organization that handles information to provide hosting, security, email, forms, analytics, or another service.
- Retention
- The period information is kept or the concrete criteria used to decide when it is deleted or de-identified.
Technical data and server logs
When a browser requests a page, a network address and the requested resource pass through the systems delivering that page. A host or security service may also record the request time, requested URL, response status, browser user agent, or referring page. The supplied materials do not establish which fields, if any, are retained for this deployment.
The deployment audit must identify the hosting, content-delivery, and security providers and confirm:
- which fields are retained rather than merely transmitted;
- the operational purpose for each retained field;
- who can access the records;
- storage and processing locations where relevant;
- the retention period or concrete deletion criterion;
- backup treatment; and
- whether logs are linked to messages or other records.
No claim is made that IP addresses or other identifiers are anonymous. Masking, truncation, aggregation, and de-identification must be confirmed against the deployed configuration before being described.
Analytics, cookies, and browser storage
No deployed analytics provider, cookie inventory, browser-storage item, consent system, or handling of browser preference signals was identified in the supplied materials. That absence of documentation is not evidence that these technologies are absent.
| Technology | Required verification |
|---|---|
| Analytics | Provider, collected fields, purpose, configuration, retention, sharing settings, and applicable choice or consent |
| Cookies | Name or category, provider, purpose, duration, and whether each item is essential or optional |
| Local or session storage | Stored value, purpose, duration, access, and effect of disabling it |
| Consent records | Provider, recorded preferences, retention period, and method for changing a choice |
| Preference signals | Technical handling and applicable legal obligations, including Global Privacy Control where relevant |
If optional technologies are introduced, they must not load before any required choice is obtained. Optional choices must not be preselected, and accept and reject actions must be presented without manipulative design.
Information you choose to submit
No verified contact, correction, source-submission, or privacy-request workflow was supplied. Before one is launched, its disclosure must identify every field collected, whether the field is required or optional, its purpose, its destination, each processor involved, anti-spam behavior, and the applicable retention period.
A public correction record may describe an error and the resulting editorial change. A submitter’s identity or contact details should not be published merely because that person reported an error.
For the editorial correction process, see Editorial Standards and Calculation Methodology.
How information is used
Each collected category must be connected to a documented purpose. A completed policy may describe purposes such as delivering requested pages, protecting the website, diagnosing faults, measuring performance, responding to messages, reviewing corrections, or maintaining consent records only when the corresponding technology and data category have been verified.
The site is planned as an educational reference without operator referrals, bonuses, paid rankings, or gambling-promotion modules. The supplied materials do not establish whether visitor information is used for advertising, profiling, personalization, targeted advertising, cross-context behavioral advertising, or automated decision-making. A documented technical and legal review is required before publishing either a positive or negative statement about those practices.
A materially new purpose requires an updated disclosure and any applicable visitor choice before information is used for that purpose.
Service providers and other disclosures
The operative policy must name or clearly categorize every provider actually used for:
- hosting and content delivery;
- security and abuse prevention;
- analytics and performance monitoring;
- consent and preference management;
- forms, email, and ticket management;
- anti-spam or bot detection;
- backups and storage; and
- embedded content.
For each provider, the final disclosure must explain its limited function, the information it receives, relevant processing locations where verified, and provide a descriptive link to its privacy information.
Information may be disclosed when required by applicable law or when reasonably necessary to investigate a security incident, protect the website, or prevent abuse. This does not mean such disclosures routinely occur.
No verified determination was supplied about sale, sharing for cross-context behavioral advertising, or targeted advertising. Advertising, affiliate, or promotional technology must not be deployed until the policy and any required consent or opt-out controls have been updated.
How long information is retained
No category-specific retention schedule was supplied. The policy cannot use a general “as long as necessary” statement in place of verified periods or concrete criteria.
| Record category | Required decision |
|---|---|
| Server, network, and security logs | Provider setting, site setting, backup treatment, access period, and deletion schedule |
| Analytics records | Provider and property-level retention settings if analytics are deployed |
| Consent records | Period needed to retain and demonstrate a visitor’s current choice |
| Contact correspondence | Period based on resolving the message and a documented follow-up need |
| Correction reports and source submissions | Separate the editorial record from unnecessary submitter contact details |
| Privacy requests | Period based on the applicable request process, verification needs, and recordkeeping obligations |
| Backups | Backup frequency, access restrictions, restoration process, and expiration schedule |
Deletion, anonymization, and de-identification practices must be described only when they are technically implemented and verified. Provider-side retention must also be included where applicable.
Your privacy choices and requests
Available controls must match the deployed technology. No cookie-settings control, analytics opt-out, privacy-request form, or monitored privacy address was supplied.
Depending on a visitor’s jurisdiction and the site’s legal obligations, a person may be able to request access to, correction of, or deletion of certain information, or another action provided by applicable law. Not every right applies in every location, and verified legal, security, recordkeeping, or identity-related exceptions may apply.
A request process should collect only:
- the requested action;
- enough information to locate the relevant interaction or record;
- a practical way to provide a response; and
- jurisdiction information reasonably needed to assess applicable rights.
Response timing, authorized-agent procedures, and any appeal process must not be promised until their legal applicability and implementation have been reviewed.
How information is protected
Static delivery does not eliminate hosting, logging, email, form, backup, or vendor security considerations. No verified inventory of administrative, technical, or organizational safeguards was supplied.
The completed policy may describe access controls, encrypted transmission, software updates, backups, monitoring, incident response, and vendor management only when those measures are implemented and verified. It must not reveal configuration details that could weaken security.
Reasonable safeguards can reduce risk, but no website, network transmission, or storage system can be guaranteed to be completely secure.
External links and embedded services
Dice Rules & Odds links readers to independently operated regulators, gambling-support organizations, standards bodies, museums, and educational resources. When a visitor follows an external link, the destination organization receives the request and applies its own privacy practices.
An embedded service is different from an ordinary link because it may receive technical information when the page loads or when a visitor interacts with it. No implemented embedded service was identified in the supplied materials.
Before an embed is introduced, the site should consider an ordinary privacy-preserving link or a click-to-load treatment. Any nonessential embed must be included in the provider and storage inventory and placed behind applicable consent controls.
Children’s privacy
Dice Rules & Odds is intended as an educational reference for U.S. adults. That audience statement does not by itself determine whether children’s privacy requirements apply.
Children’s privacy obligations can depend on whether an online service is directed to children under 13 or whether its operator has actual knowledge that it collects personal information from a child. The site’s content, audience, design, collection practices, and actual use must be assessed together.
The project should avoid child-directed presentation and unnecessary collection of personal information. Before publication, the responsible party must establish a monitored process for a parent or guardian to report information submitted by a child and for the site to take any required action.
Changes to this Privacy Policy
When an operative policy is published, its effective and last-updated dates must be shown at the top of the page. The last-updated date should change for substantive revisions, not typographical or visual edits.
The privacy policy and supporting inventory must be reviewed before introducing or replacing any hosting, security, analytics, advertising, form, email, anti-spam, consent, storage, or embedded-content integration.
Material changes should be communicated using a method that has actually been implemented. Additional notice or consent should be provided when appropriate. The responsible party should maintain an internal change record and summarize material public-facing changes on this page when useful.
Contact us about privacy
This page cannot serve as an operative policy until it provides a monitored channel for policy questions, applicable privacy requests, suspected privacy or security issues, and parent or guardian reports. The final disclosure must also identify any email, form, anti-spam, or ticketing provider involved and the retention period for correspondence.
Do not send private or sensitive information through an unrelated or unverified channel.
- For general information about the project, visit About Dice Rules & Odds.
- For factual, mathematical, historical, legal, accessibility, or sourcing corrections, review Editorial Standards.
- For gambling-related help, visit Responsible Gambling Help and Support Resources rather than using a privacy channel.
Related policy
Review the Terms of Use for the separate conditions governing use of this website.