Cookie Policy

This Cookie Policy explains the limited browser-side storage and cookie-like behaviour associated with CDL Drill & Review. The site is built as a lightweight study product. Storage exists because a practice flow that spans session, result, review, and progress pages needs continuity. It does not exist to mimic the full tracking posture of a large commercial platform.

1. Functional continuity

Browser-side storage may preserve recent study state so that later pages can interpret the same practice round or the same developing weakness pattern. This is a functional requirement of the product loop. Without it, review and progress surfaces would lose their practical value.

2. Technical and infrastructure cookies

Hosting, CDN, or security layers may also use technical cookies or challenge systems to deliver the site, maintain caching, and reduce abusive traffic. Those controls are part of normal site operation and should not be confused with a broad cross-site advertising system.

3. User choice

Users can usually clear cookies or browser storage through standard browser settings. Clearing that data may reset study continuity and remove local progress traces. On shared devices, this is also the practical way to avoid leaving behind session state for the next user of the same browser profile.

4. Why the policy is specific

The policy is specific because a small study tool should describe its storage reality directly. Trust improves when a lightweight product explains a lightweight storage model honestly.

5. Storage limits and expectations

The site does not promise permanent cross-device history, deep behavioural analytics, or a rich member account built on cookies. Users should expect a narrower, browser-first continuity model. That is a design choice, not an omission by accident.

6. Review-readiness and trust

For a small static study product, a clear cookie page is part of trust. It tells a reviewer that the site understands the difference between functional continuity, infrastructure protection, and invasive tracking.

5. Storage limits and expectations

Users should not expect CDL Drill & Review to create a rich, permanent, cross-device training account through cookies or browser storage. The storage model is intentionally narrower. It exists to keep the study loop functional inside the current browser context, not to accumulate an expansive hidden history.

6. Infrastructure versus product tracking

This distinction matters: technical cookie or challenge behaviour may come from infrastructure required to deliver and protect the site, while the study product itself remains relatively light. A clear cookie policy should help a reviewer understand that difference instead of blurring everything into one vague sentence about “tracking.”

7. Why this page matters for a study product

On a small site, a credible cookie page signals that the operator understands the difference between legitimate continuity, ordinary hosting protection, and invasive behavioural collection. That clarity is part of trust, not a legal decoration.