Privacy Notice
This notice describes how personal data is handled on this public site today. It reflects how the site works now, rather than possible future features.
What data we handle
Optional contact details in feedback/disputes: when you submit feedback or dispute an update, you may optionally provide your name and email. The submission content and any quoted text/evidence you include are also stored.
Operational request data: like most websites, hosting and security infrastructure may process technical request data (for example IP address and user-agent) for service delivery, security, abuse prevention, and service reliability.
First-party interaction analytics: we collect limited, first-party interaction events to understand which chapters, citations, searches, and feedback flows are actually used. This is used for aggregate reporting and product improvement.
What we do not currently offer on this public site: no public paid subscription or checkout flow, and no user-account registration. If that changes, this notice will be updated before launch.
Why we use this data
- • To receive and review correction requests and evidence submissions.
- • To follow up with you only if follow-up is needed and you provided contact details.
- • To operate, secure, and maintain the website and editorial workflow.
- • To understand aggregate usage patterns such as chapter readership, citation engagement, and search success.
Feedback/dispute retention (current process)
- • Optional name/email are kept only as long as needed for follow-up.
- • For resolved submissions older than 12 months, optional contact fields may be anonymized.
- • Older resolved submissions may be deleted after 24 months when no operational/legal need remains.
This is currently handled through an operational review process (not an automated user-facing retention tool).
Cookies and tracking
The public site does not currently use third-party analytics or marketing trackers, and it does not use browser cookies for public product analytics.
- • Public page responses currently return no
Set-Cookieheaders from the application for analytics purposes. - • No Google Analytics, Tag Manager, Plausible, PostHog, Mixpanel, Hotjar, Clarity, Segment, or similar client tracker is currently loaded on the public site.
- • We do record limited first-party interaction events, such as page views, chapter opens, citation clicks, search success, and feedback submits, using our own Cloudflare-hosted infrastructure.
- • These analytics are used in aggregate reporting and do not rely on cookie-based user profiles.
- • Cloudflare may still process technical request metadata and emit operational response headers such as
NEL/Report-Tofor network and security operations.
For that reason, the public site does not currently use a cookie banner. If we later add features that require more tracking, analytics, or user data, this notice will be updated as part of that rollout.
Responsible editorial party and contact
Editorial responsibility for this edition rests with Tal M. Hörer MD, PhD and David T. McGreevy MD, PhD.
- Tal M. Hörer MD, PhD
- David T. McGreevy MD, PhD
Editorial base: Örebro University Hospital (USÖ), Sweden.
Privacy and editorial contact: tal.horer@regionorebrolan.se. At present, this site does not name a separate publisher or company behind the publication. For this edition, the editors listed above are the named responsible contacts.