# Doctorsa security contact and vulnerability disclosure policy # https://www.doctorsa.com/.well-known/security.txt # RFC 9116 — https://securitytxt.org/ Contact: mailto:security@doctorsa.com Contact: mailto:help@doctorsa.com Contact: tel:+39-06-679-0695 Contact: https://www.doctorsa.com/contact/ Expires: 2027-06-24T23:59:59.000Z Preferred-Languages: en, it Canonical: https://www.doctorsa.com/.well-known/security.txt Policy: https://www.doctorsa.com/privacy-policy/ Policy: https://www.doctorsa.com/terms-and-conditions/ Policy: https://www.doctorsa.com/.well-known/agent.json Acknowledgments: https://www.doctorsa.com/contact/ # ----------------------------------------------------------------------------- # Organization # ----------------------------------------------------------------------------- # Legal name: Doctorsa S.r.l. # VAT / reg. no: IT14465600964 # Address: Via Privata del Gonfalone, 3, 20123 Milan, Italy # Website: https://www.doctorsa.com/ # API host: https://findapi.doctorsa.com/ (LLM booking agent / MCP) # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Scope — IN SCOPE for responsible disclosure # ----------------------------------------------------------------------------- # - https://www.doctorsa.com/ and subpaths (marketing site, intake forms) # - https://doctorsa.com/ (apex; same content as www) # - https://findapi.doctorsa.com/ (LLM booking REST API, MCP, payment redirects) # - Public mobile app backends explicitly linked from doctorsa.com # - Authentication, authorization, and session handling on the above # - Injection, XSS, CSRF, SSRF, IDOR, and business-logic flaws in booking flows # - Information disclosure of patient or session data beyond intended access # - Rate limiting, OTP abuse, and verification bypass in the booking API # - Misconfiguration of TLS, cookies, CORS, or security headers # - Stripe Checkout integration issues that expose payment or PII incorrectly # # Machine-readable agent surfaces (report defects affecting agent discovery # only if they enable misuse of patient data or booking APIs): # /.well-known/agent.json # /.well-known/mcp.json # /llms.txt # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Scope — OUT OF SCOPE # ----------------------------------------------------------------------------- # - Third-party services (Stripe, Twilio, Cloudflare, WordPress plugins, etc.) # Report those to the respective vendor unless our integration clearly # amplifies impact on Doctorsa patient data. # - Social engineering, phishing, or physical attacks against staff/patients. # - Denial-of-service or load tests without prior written approval. # - Automated scanning that degrades production availability for travelers # seeking urgent care. # - Issues in doctor-facing console / internal admin tools unless reachable # from the public internet without authentication. # - Missing security headers or best-practice hardening with no demonstrable # exploit (e.g. clickjacking on static marketing pages alone). # - Reports based solely on unauthenticated access to intentionally public # metadata (agent.json, mcp.json, llms.txt, OpenAPI LLM docs). # - Medical malpractice, clinical judgment, or quality-of-care complaints # (route to help@doctorsa.com / patient support). # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Protected health & personal data (GDPR / special-category data) # ----------------------------------------------------------------------------- # Doctorsa processes health-related and personal data. Researchers MUST NOT: # - Access, exfiltrate, or retain real patient records, OTPs, or session IDs # belonging to other users. # - Use production booking flows with another person's phone or email. # - Publish screenshots or logs containing PHI/PII. # Use only your own test accounts and data. If you accidentally access # another user's data, stop immediately, delete local copies, and report # via security@doctorsa.com within 24 hours. # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Responsible disclosure guidelines # ----------------------------------------------------------------------------- # 1. Email security@doctorsa.com with a clear description, impact, steps to # reproduce, and affected URLs (include User-Agent / X-LLM-Agent only if # relevant to API bugs — never include live patient OTPs). # 2. Allow up to 90 calendar days for remediation before public disclosure. # We may request extension for complex issues; we will respond in good faith. # 3. Do not exploit beyond what is needed to demonstrate impact. # 4. Do not modify, delete, or corrupt user data. # 5. We do not currently operate a paid bug bounty program. Acknowledgment # in our security page may be offered at our discretion for valid reports. # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Safe harbor (good-faith research) # ----------------------------------------------------------------------------- # Doctorsa will not pursue legal action against researchers who: # - Comply with this policy and applicable law; # - Avoid privacy violations and service disruption as described above; # - Report findings promptly and allow reasonable time to fix. # This safe harbor does not apply if you violate law or access data beyond # what is necessary to demonstrate the vulnerability. # ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # Emergency / active exploitation # ----------------------------------------------------------------------------- # If you believe patient data is actively being exploited in the wild, # mark the subject line [URGENT] and include a phone number. For life- # threatening medical emergencies, patients must call local emergency services # (e.g. 112 in most of Europe) — Doctorsa is not an emergency service. # ----------------------------------------------------------------------------- # Encryption: (optional — add OpenPGP key fingerprint and URL when available) # Encryption: https://www.doctorsa.com/.well-known/pgp-key.txt Hiring: https://www.doctorsa.com/contact/