Trust & safety

Security & responsible disclosure

How we protect ClinicNearMe and your information, and how security researchers can report a vulnerability safely.

Effective and last updated

How we protect the service

  • Encryption in transit

    Every page is served over HTTPS with HSTS; mail between servers uses TLS with MTA-STS.

  • Account protection

    Passwords are stored as one-way hashes. Two-step verification is required for staff and available for clinic accounts.

  • Secure by default

    Content Security Policy, request-forgery protection, rate limits and role-based permissions on every clinic account.

  • Minimal data

    We do not ask for medical records, we do not store card numbers, and personal data is deleted on a fixed schedule.

Responsible disclosure policy

If you believe you have found a security vulnerability in ClinicNearMe, please tell us. We will work with you to understand and fix it.

How to report

  • Email security@clinicnearme.net with a description, the affected URL or component, steps to reproduce and the impact you observed.
  • We acknowledge reports within 3 business days, keep you informed and tell you when the issue is fixed.
  • Our machine-readable contact file is at /.well-known/security.txt.

In scope

clinicnearme.net and its subdomains, the clinic dashboard and our public API.

Out of scope

  • Denial-of-service or load testing, spam, social engineering or physical attacks.
  • Reports from automated scanners without a demonstrated impact, missing best-practice headers without a working exploit, and self-XSS.
  • Third-party services we use (report those to the vendor) and clinic websites linked from listings.

Rules

  • Do not access, change or delete data that is not yours; use test accounts and stop as soon as you confirm an issue.
  • Do not disrupt the service or degrade it for others.
  • Give us reasonable time to fix the issue before any public disclosure.

Safe harbor

If you act in good faith and follow this policy, we will not pursue legal action against you for your research, and we will consider your activity authorized. We do not currently run a paid bug bounty, but we are glad to credit researchers who want recognition.

Incidents

If a security incident affects your personal information, we will notify you and the authorities as the law requires.

0 clinics selected Compare