Cookie Policy

DriversEdPro, owned and operated by Corebytes LLC

This Cookie Policy explains how DriversEdPro ("we," "our," or "us"), operated by Corebytes LLC in the United States, uses cookies and similar technologies when you visit or use our websites and web applications. It should be read together with our Privacy Policy, which describes personal information more broadly, including location features that rely on browser APIs rather than cookies, and our Terms of Service, which describe payment disputes, chargebacks, and the non-refundable DriversEdPro enrollment fee.

1. What cookies and similar technologies are

Cookies are small text files stored on your device when you visit a site. Similar technologies include local storage, session storage, and pixels used for security or measurement. These technologies help the Service remember who you are after you sign in, protect accounts, and understand whether pages load correctly.

1.1 U.S. legal context (informational)

Cookie and online tracking practices in the United States are subject to the Federal Trade Commission Act, 15 U.S.C. § 45(a) (prohibiting unfair or deceptive practices), the Children's Online Privacy Protection Act, 15 U.S.C. §§ 6501–6506 and 16 C.F.R. Part 312 (where applicable to services directed to children), the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510–2522 and 2701–2712 (in criminal and certain access contexts), state consumer protection laws, and—for California residents—the California Consumer Privacy Act and California Privacy Rights Act, California Civil Code §§ 1798.100 et seq., including rules on "sale" and "sharing" of personal information and opt-out signals. We do not use cookies to "sell" or "share" personal information for cross-context behavioral advertising as defined in the CPRA.

2. Why we use cookies

2.1 Security and authentication

• Maintain signed-in sessions and reduce session hijacking risk
• Apply fraud protections and rate limits tied to browser signals
• Route traffic safely across application tiers

2.2 Product functionality

• Remember preferences you select inside the product
• Keep course progress and form drafts where those features are enabled
• Support downloads and document viewers that rely on short-lived tokens

2.3 Reliability and improvement

• Measure errors and latency so we can improve stability
• Understand which features are used in aggregate so we can invest engineering time responsibly

3. Location, maps, and cookies

Some product experiences involve maps or optional device location. Map tiles or geocoding requests may send limited technical data to mapping or search providers under their policies. When you approve browser geolocation, that location is handled by the browser and our application code as described in the Privacy Policy, not as a traditional first-party cookie. You can revoke location permission in your device or browser settings at any time.

4. Payments with Intuit QuickBooks

When your school collects tuition or fees through Intuit QuickBooks Payments, Intuit may set or read cookies and similar identifiers on Intuit-controlled pages or domains to complete authentication, reduce fraud, and meet card network rules (including rules promulgated under the Truth in Lending Act, 15 U.S.C. § 1601 et seq., and Regulation Z, 12 C.F.R. Part 1026, for credit products where applicable). DriversEdPro does notstore full payment card numbers on our own servers. For details on how Intuit processes data, review Intuit's privacy and cookie disclosures when you are redirected into their checkout experience.

Fraudulent checkout activity, false payment disputes, and abusive chargebacks harm schools and processors. Our Terms of Servicedescribe administrative charges (up to U.S. $150.00 per wrongful dispute, plus processor pass-through costs), immediate termination of a school's license in serious cases, and civil remedies that may apply under U.S. fraud and computer-abuse statutes.

5. Third-party services

We rely on a small number of service providers who may use their own cookies or storage when their content loads:

• Cloud hosting and database vendors that power the Platform
• Email delivery providers for transactional messages
• Analytics or observability vendors configured to minimize personal data where feasible
• Mapping or geocoding providers when you use address lookup features

We do not allow third-party advertising networks to drop marketing cookies on DriversEdPro for retargeting across unrelated sites.

6. What we do not do with cookies

7. Managing cookies and storage

Most browsers let you refuse or delete cookies. If you block strictly necessary cookies, parts of the Service may not work, including sign-in. You can also clear storage for our origin from your browser settings if you share a device and want a clean session.

Some preferences inside DriversEdPro are mirrored into cookies or local storage so the interface stays consistent between visits. If you clear storage, those preferences may reset.

8. Security practices related to cookies

• We prefer secure, HTTP-only, and SameSite protections on authentication cookies where supported by the architecture.
• We use encrypted transport (HTTPS) for web traffic.
• We limit employee access to production diagnostics and review access periodically.

9. Retention

Session cookies typically expire when you close your browser. Authentication cookies may persist until you sign out or until they expire based on our security configuration. Functional storage may persist longer so preferences survive updates. Analytics cookies, if present, use vendor-specific lifetimes that we configure to reasonable defaults.

10. Children and schools

Where students are minors, schools and parents remain responsible for supervising device use and permissions. Cookies that are strictly necessary for delivering assigned coursework may still be required even when optional analytics are limited.

11. Updates to this Cookie Policy

We may update this Cookie Policy when we change providers, add product capabilities, or when law requires clearer disclosures. We will revise the effective date and, when changes are material, provide additional notice such as an email to administrators or a banner inside the application.

Document version 1.2. Last updated April 17, 2026.