Europe Quizly Privacy Policy — Development Prompt

Copy the complete prompt below for the page build.
Create one complete, publication-ready Privacy Policy page for Europe Quizly (https://europequizly.com/) using HTML5, CSS3, Bootstrap-compatible markup, and vanilla JavaScript for WordPress + Divi + WP Coder.

Return one self-contained HTML, CSS, and JavaScript snippet only when coding is requested. Do not include a site header, footer, global navigation, PHP, templates, external frameworks, placeholder content, fake claims, or developer notes.

Brand requirements:
- Brand: Europe Quizly
- Privacy Policy URL: https://europequizly.com/privacy
- Contact email: support@europequizly.com
- Contact page: /contact
- Last updated: November 9, 2026
- Font: Inter
- Icons: Boxicons only
- Colors: orange #FF9E20, teal #215E61, charcoal #1D2128, light grey #F4F2F2, white #FFFFFF
- Maximum inner content width: 1350px
- Root wrapper: #eqz-privacy-page
- Prefix all page classes with eqz-privacy-

Use exactly one H1: “Privacy Policy”. Create a clean, editorial legal-document layout with light-grey introductory background, teal “LEGAL INFORMATION” eyebrow, subtle orange accent, visible last-updated date, spacious typography, white content surfaces, and restrained decoration.

Include all policy sections in this order:
1. Privacy Policy Introduction
2. Privacy at a Glance
3. Information We May Collect
4. How Information May Be Collected
5. How Information May Be Used
6. Cookies and Similar Technologies
7. Website Analytics and Third-Party Services
8. Contact Forms and Communications
9. Quiz Activity and Website Interaction
10. Data Sharing and Disclosure
11. Data Storage and Retention
12. Data Security
13. International Data Processing
14. Children’s Privacy
15. Your Privacy Rights and Choices
16. External Websites and Links
17. Changes to This Privacy Policy
18. Contact Europe Quizly About Privacy
19. Final Navigation CTA

Write complete, original, clear privacy-policy copy. Explain that exact data handling depends on website configuration where implementation facts are unknown. Do not claim that Europe Quizly collects no data, never uses cookies, never stores IP addresses, never shares data, uses named analytics or advertising services, maintains accounts, stores quiz progress, profiles users, uses specific security systems, or deletes data after a fixed period.

Include the specified policy content:
- Explain that contact messages may include name, email, subject, message, and voluntarily supplied information.
- Explain that ordinary web access may involve IP address, browser, device, operating system, requested pages, timestamps, referrer, and technical error information depending on hosting and technical configuration.
- Explain quiz interactions only as processing needed to present questions and handle responses; do not assert persistent answer, score, or progress storage.
- Explain direct collection through contact forms, email, feedback, and technical issue reports; web requests and hosting; and relevant services involved in website operations.
- Limit stated uses to website operation, responding to inquiries, troubleshooting, security, and legal obligations.
- Define cookies and explain they may support functionality, sessions, security, preferences, and integrated services. State that browser settings can manage cookies and restricting them can affect functionality. Do not invent cookie names, periods, or a preference centre.
- Describe potential third-party service categories such as hosting, security, email delivery, maintenance, and analytics only if implemented. Do not name Google Analytics, Meta, Cloudflare, Google Ads, or other unverified services.
- State that the contact form is available through the existing Contact Page and link “Contact Europe Quizly” to /contact. Do not recreate a Contact Form 7 form.
- Explain potential service-provider handling and lawful disclosure without claiming commercial sales or advertising sharing.
- Explain flexible retention based on purpose, systems, legal requirements, and operational needs, without fixed retention promises.
- Use balanced security wording and state that no internet transmission or service can guarantee absolute security. Ask visitors not to submit passwords, financial details, or unnecessary sensitive information in general messages.
- Explain that processing may involve different jurisdictions depending on services used, without inventing hosting locations or transfer mechanisms.
- Explain children’s privacy in an educational context, encourage parental supervision, and direct concerns to support@europequizly.com without inventing age gates or consent systems.
- Explain privacy rights may vary by jurisdiction and may include access, correction, deletion, objection, restriction, consent withdrawal, and portability, subject to legal conditions. Use a functional mailto:support@europequizly.com link.
- Explain external sites have their own content and privacy practices.
- Explain that updates may be published on this page with an updated date; display “Last Updated: November 9, 2026”.
- Include a white contact panel with website link, email link, contact-page link, subtle teal accents, Boxicons, and no phone number or address.
- End with a restrained charcoal section: eyebrow “CONTINUE EXPLORING”, heading “Explore More of Europe Quizly”, supporting text, a teal “Explore Europe Quizly” link to /, and “Contact Us” link to /contact.

Create “Privacy at a Glance” with four concise icon blocks:
- bx-globe: website technical information may be involved in web access.
- bx-envelope: contact messages may be used to understand and respond.
- bx-cookie: cookies and similar technologies may be involved depending on configuration.
- bx-shield-quarter: privacy questions can be sent to support@europequizly.com.
Use four columns on desktop, two on tablet, and one on mobile.

Create an accessible table of contents:
- Desktop: two columns, 25% sticky sidebar and 75% content. Heading: “On This Page”.
- Include links to all main policy sections.
- Mobile: compact collapsible table of contents near the top, keyboard operable, with correct aria-expanded and aria-controls states; close it after navigation.
- Use smooth scrolling, appropriate sticky-header offsets, visible focus states, and IntersectionObserver for active-link tracking.
- Do not use global scroll listeners.

CSS requirements:
- Scope every selector under #eqz-privacy-page.
- Do not target body, html, generic elements globally, .container, .row, .card, .btn, or .et_pb_*.
- Use CSS Grid/Flexbox, responsive layouts, readable 15–17px body copy, 44–58px desktop H1, 25–34px H2, 19–22px H3, and paragraph line-height around 1.7–1.85.
- Ensure no horizontal overflow and test layouts at 320px, 375px, 414px, 768px, 1024px, 1280px, and 1440px+.
- Include reduced-motion support and accessible color contrast.

JavaScript requirements:
- Use a vanilla JavaScript IIFE only.
- Query only inside #eqz-privacy-page.
- No globals, jQuery, frameworks, or dependencies.
- Initialize safely whether loaded before or after DOMContentLoaded.
- Prevent duplicate initialization and event listeners.
- Safely handle missing optional elements.
- Do not interfere with Divi, WordPress, or plugins.