Protocol Guide

Privacy Policy

Last updated: May 27, 2026 · Operator: TheFireDev LLC.

1. Introduction

Protocol Guide, operated by TheFireDev LLC (“Company,” “we,” “our,” or “us”), explains how we collect, use, disclose, and safeguard information when you use our mobile application and related services (the “Service”).

This policy applies to individual EMS professionals and personnel using the Service through enterprise or agency subscriptions.

2. Information we collect

Account: name, email, auth credentials (hash or OAuth tokens), agency affiliation if provided, optional professional role.

Usage: search queries, protocol views, feature use, session paths, device type/OS/app version, IP for security and abuse prevention.

Device: identifiers for analytics/security, push tokens with permission, crash/performance data.

Payments: processed by Stripe. We do not store card numbers. We retain Stripe customer ID, subscription status, billing history, and invoices as required by law.

Voice: if you use voice input, foreground microphone audio may be uploaded for transcription; transcribed text is treated as a search query.

3. How we use information

4. Sharing

We do not sell personal information. We may share with service providers (Stripe, Supabase, Railway, Sentry, AI providers) as needed to run the Service; when required by law; to protect rights and safety; or in a merger/acquisition. Agency admins may see aggregated usage for enterprise seats—not individual search content.

5. AI / LLM usage

Search may use AI (including Anthropic Claude and Google Gemini embeddings). We send search text and relevant protocol context for a response—not your name, email, credentials, or payment data. If you connect Protocol Guide to ChatGPT or Claude, that platform sends your tool query to Protocol Guide and receives protocol excerpts, source citations, and the reference-only disclaimer. Connected searches use the same account access and daily usage limit as the web and iOS apps. Do not enter patient-identifiable information. AI output is reference only; always follow local protocols and medical direction.

6. Security & retention

We use TLS in transit, encryption at rest, row-level security, access controls, and incident procedures. No system is perfectly secure. Retain account and billing records as needed for the Service and law; delete account via Profile → Account → Delete Account, or email support.

7. Your choices & contact

Access, correction, and deletion requests: support@protocol-guide.com

Also see Support, Terms, and Clinical Disclaimer.