Draft policy: replace bracketed placeholders and complete the publication checklist before relying on this document.
Jam / JamStudio Cookie Guidance and Notice
Effective date: [DATE]
Cookie settings: [SETTINGS URL]
This is both a user-facing notice and an implementation checklist. Keep only rows that are true in production; create a live cookie table from your consent-management platform and vendor scan.
User-facing cookie notice
Jam uses cookies and similar technologies to make the Service work, keep accounts secure, remember settings, measure use and—only where you agree—provide optional analytics or marketing.
Strictly necessary technologies are used to provide a service you request, such as authentication, load balancing, fraud prevention, consent-preference storage and security. They do not require consent where local law permits that exemption.
Analytics, personalisation and marketing technologies are optional. We will not set/read them until you choose “Accept” or make a granular selection. You can refuse them just as easily as you accept them, and can change or withdraw consent at any time in [SETTINGS URL]. Refusal does not prevent use of the core Service.
| Category | Purpose | Legal basis | Retention | Providers / cookie names |
|---|---|---|---|---|
| Strictly necessary | sign-in, security, load balancing, consent choice | legitimate interest / service necessity | [X] | [LIST] |
| Preference | language, UI settings | consent [OR EXEMPTION IF APPLICABLE] | [X] | [LIST] |
| Analytics | understand performance and usage | consent, unless the precise local exemption conditions are met | [X] | [LIST] |
| Marketing | measure campaigns / personalised advertising | consent | [X] | [LIST] |
See the Privacy Policy for broader personal-data information and contact [PRIVACY EMAIL] with questions.
Banner copy (recommended)
Title: Your privacy choices
Text: We use essential technologies to run and secure Jam. With your permission, we also use optional analytics to understand and improve the Service. You can accept, refuse, or choose by purpose. Your choice can be changed anytime.
Buttons shown at equal prominence: Accept optional cookies · Reject optional cookies · Manage choices
The initial layer must not treat scrolling, continued browsing, or closing the banner as consent. Do not pre-tick optional categories. Do not make “Reject” less visible, harder, or slower than “Accept”.
Engineering checklist
- Run a pre-production scan in authenticated and logged-out states, including embedded players, support widgets, payment screens and CDN scripts.
- Block non-essential tags before consent—not merely after page load. Test network traffic and local/session storage, pixels, SDKs and fingerprinting-like identifiers.
- Record consent version, timestamp, purposes and evidence; make it easy to change/withdraw.
- Separate essential service telemetry from product analytics. Only claim a consent exemption after privacy/legal review of the exact configuration.
- Review vendor contracts, data locations and any use of cookies by third-party embeds. Update the table whenever vendors or purposes change.
- Re-ask for consent only when necessary under applicable local rules or after a meaningful change; do not repeatedly prompt users who refused.
