Privacy Policy & Data Handling
Last updated: November 2026 • Hyperacusis Treatments (.org)
We take patient privacy seriously. Submitting a case report is always voluntary, you can publish anonymously without creating an account, and any private contact email you choose to share is never displayed publicly.
1. What Information We Collect
Hyperacusis Treatments (hyperacusistreatments.org) is a community-maintained registry of patient-reported outcomes for loudness hyperacusis and pain hyperacusis (noxacusis). We separate publicly published clinical notes from strictly private metadata:
- Public Case Report Data (voluntary): your chosen public handle (or 'Anonymous'), hyperacusis subtype, approximate onset, suspected cause, baseline symptom severity, treatment details (medication dosage/duration or procedure details), outcome category, narrative results, side effects, co-factors, and community source.
- Strictly Private Metadata (optional, editors only): if you choose to provide a private email address (to receive publication notices or verify future updates/removal requests) or an internal username while publishing as Anonymous, those fields are stored in an access-restricted private table (report_private_meta) and are never displayed, exported publicly, or searchable on the website.
- Existing Community Reports: historical case reports compiled from public discussions on Reddit, Discord, and community forums are maintained for educational reference and can be updated, anonymized, or removed by their author at any time.
2. Legal Basis & Sensitive Health Data
Because case reports describe health symptoms and treatments, they constitute special-category health data (e.g., under Article 9 of the EU GDPR). We only process and publish direct submissions based on your explicit, voluntary consent given before submitting the form.
Please do not include personally identifiable information (such as your full legal name, phone number, home address, medical record numbers, or identifying details of third parties) inside public narrative fields.
3. Editorial Review & Automated AI Pre-Screening
Every patient submission (new report, update, or privacy request) enters a private moderation queue and is reviewed by authorized community editors before publication.
To assist editors with spam detection, duplicate checking, outcome consistency, and clean formatting, the clinical text of your submission may be pre-screened automatically by an AI provider (Google Gemini and/or DeepSeek). Your private email address and internal anonymous username are never sent to AI providers and are never posted to editor notification channels.
4. Third-Party Infrastructure & Sub-Processors
We do not sell, rent, or monetize any user data. To operate the site securely, we rely on the following infrastructure providers strictly as needed:
- Vercel: web application hosting and server-side API execution.
- Supabase (PostgreSQL): cloud database with Row Level Security (RLS) separating public reports from editor-only private metadata and moderation tables.
- Resend: transactional email delivery for optional email confirmation links, 6-digit author verification codes (OTP), and publication confirmations.
- Google Gemini / DeepSeek: behind-the-scenes editorial QA on non-private report text only.
- Discord: private staff webhook alerts notifying editors when a new submission arrives (excludes private email and internal identity).
- Cloudflare Turnstile (when enabled): privacy-preserving anti-bot verification on public submission forms.
5. Data Retention & Security
Published case reports remain in the registry to help other patients and researchers unless you request anonymization or permanent removal. One-time verification tokens expire automatically (15 minutes for 6-digit update codes; 72 hours for email confirmation links) and are stored only as cryptographic SHA-256 hashes.
Access to private metadata and pending submissions is restricted via PostgreSQL Row Level Security and server-side authentication exclusively to authorized members of the editor pool.
6. Your Rights (Access, Update, Anonymization & Deletion)
You retain full control over your contribution. At any time, you may withdraw consent or request access, correction, anonymization (keeping de-identified clinical data under 'Anonymous'), or permanent deletion of your case report and private email:
- Self-service updates: use the Update Existing Case tab on /submit.
- Self-service anonymization or removal: use the Anonymize / Remove tab on /submit.
- Direct contact: email info@hyperacusistreatments.org with the treatment name and case number or handle.
7. Cookies & Local Storage
This site does not use advertising cookies, cross-site tracking pixels, or behavioral analytics profiling. We use only strictly necessary technical storage: browser localStorage for your light/dark theme preference and essential session cookies exclusively for authenticated community editors signing into /editor.
8. Data Use & Licensing
The compiled registry structure, normalized classifications, charts, and aggregated statistics published on hyperacusistreatments.org are made available free of charge for non-commercial educational, informational, and academic or clinical research reference, provided clear attribution is given to Hyperacusis Treatments (hyperacusistreatments.org).
- Attribution & non-commercial reuse: when citing aggregated outcomes, charts, or summaries in educational resources, community discussions, or research, please credit hyperacusistreatments.org and link to the relevant treatment or analytics page. Commercial resale, paywalled redistribution, or marketing use of the registry is not permitted without prior written permission.
- Contributor rights & revocability: individual case reports come from voluntary direct submissions or historical community discussions (e.g., Reddit and Discord). Original authors retain control over their personal accounts and may request anonymization or permanent removal at any time (Section 6); accordingly, this dataset is not released under an irrevocable open-data license.
- No re-identification or clinical reliance: anyone referencing this dataset must not attempt to re-identify anonymous or pseudonymous patients and must preserve the context that these are self-selected anecdotal reports rather than controlled clinical trials.
Privacy Inquiries: For any question about how your data is handled, or to exercise your rights regarding an entry in this registry, contact the project team at info@hyperacusistreatments.org or submit a request directly via the self-service privacy form.