Privacy
Privacy, in plain English.
Alpha Medic is published by Code 3 Tek, LLC, an Arizona limited liability company. This policy covers both this website and the Alpha Medic mobile app. It says what we collect, what leaves your phone, who receives it, and how long anyone keeps it.
The short version
- Almost everything you do in the app stays on your phone. Your region, certification records, quiz progress, incident log, hospital favorites and door codes are never uploaded to us or to anyone else.
- The app has no user accounts. We cannot identify you, and we do not try to.
- No ads, no analytics, no tracking, on the site or in the app. We do not sell or share your information, and nothing goes to data brokers or ad networks.
- Your location never leaves your device, even though the app asks for the permission.
- Four things you deliberately send out: asking the AI a question, describing a scenario, dictating by voice, and photographing a continuing-education certificate. Each is explained below.
- We store two small things on our own servers: an email address, only if you type one in yourself, and any quiz question you flag as wrong, with no identity attached.
1. This website
One thing: your email address, and only if you type it into the early-access form yourself. There are no ad trackers, no analytics cookies, and no third-party data brokers on this site.
We store it securely and use it to tell you about Alpha Medic availability and major updates. We never sell it, rent it, or share it with anyone outside CODE3TEK. We don't spam - expect a small number of emails that actually matter.
To have it removed, email us from the address you signed up with and say "remove me." It'll be deleted from the list. Done.
2. In the app: what never leaves your device
Most of Alpha Medic works entirely offline. The following is stored in the app's private storage on your phone. There is no network path that sends any of it anywhere:
- Your selected region, certification scope, and exam target
- Quiz progress, scores, and session history (NREMT Prep)
- Continuing-education and certification records, expiry dates, and any photos you attach to them
- Incident log entries and exposure records
- Hospital favorites, phone-number overrides, contact edits, and door codes
- Learning Lab and Rhythm Lab progress
- Cached protocol content and downloaded regional protocol PDFs
Location. Alpha Medic requests location permission and uses it in one place: sorting a list of hospitals, which ships inside the app, by distance from you. That calculation happens entirely on your phone. Your location is never attached to any request that leaves the device, and we never receive it.
3. In the app: what does leave your device
There are six paths out. Five happen only when you choose to use the feature. One is automatic.
3.1 Voice recordings (Scenario AI)
When: you tap the microphone in Scenario AI and speak.
What is sent: the audio recording, and nothing else. No name, no identifier, no location, no region.
Who receives it: Groq, Inc., which converts speech to text using the Whisper model.
How long it is kept: not at all. Zero Data Retention is enabled on our Groq account, so the recording is processed and discarded, and Groq's usual short-term operational logs are suppressed as well.
Is it used to train AI models: no.
Please do not speak patient-identifying information into the app. Alpha Medic is a training and reference tool. When you practice off a real call, leave out names, dates of birth, addresses, and anything else that could identify a patient. The app cannot detect or remove such details, and Code 3 Tek is not a HIPAA covered entity or business associate.
3.2 Certification and CE photos
When: you photograph a CE certificate or certification card and ask the app to read it.
What is sent: the image, plus a label saying which kind of document it is.
Who receives it: Anthropic, PBC, which reads the text out of the image.
How long it is kept: up to 30 days on Anthropic's systems, then deleted automatically.
Is it used to train AI models: no.
These images normally contain your full legal name, and often your license or registry number. That is genuinely identifying information about you, and we treat it that way. The text that comes back is only used to pre-fill a review screen. Nothing is saved to your records until you confirm it, and the record it creates stays on your phone.
3.3 Questions you ask Alpha Medic AI
When: you ask the in-app AI a question about a protocol.
What is sent: your question exactly as you typed it, plus the context the answer needs: your region code, the name of the source protocol document, page references, the region's drug list, and protocol entries. Reference images are never sent, only their titles and page numbers.
Who receives it: Anthropic, PBC.
How long it is kept: up to 30 days, then deleted. Not used for training.
Whatever you type is sent as written, so please don't include patient details or personal information you don't want transmitted.
3.4 Scenario descriptions
When: Scenario AI matches a patient presentation to the right protocol.
What is sent: the scenario text, either what you typed or the transcript of what you dictated.
Who receives it: Anthropic, PBC.
How long it is kept: up to 30 days, then deleted. Not used for training.
3.5 Crash reports
When: automatically, if the app crashes or hits an error. Release versions of the app only.
What is sent: a technical stack trace, the name of the screen you were on, and a trail of which screens and network addresses were involved.
Who receives it: Functional Software, Inc. (Sentry).
What is deliberately excluded, by design and enforced in our code:
- No identity. No user identifier is attached, and any identity field is stripped before the report is sent.
- Nothing you typed, dictated, or photographed. Request contents are removed, and all internal application log messages are dropped wholesale before transmission, so no text from anywhere in the app can reach a crash report.
- No performance or behavior tracing.
The result is a diagnostic report about the software, not about you.
3.6 Flagging a quiz question
When: you tap Flag on a quiz or Rapid Fire question to tell us it looks wrong.
What is sent: which question it was, the version of the question bank, whether you use iPhone or Android, the time, and the note you typed, if any (up to 500 characters). No name, email, user identifier, device identifier, or location.
Who receives it: us. It is stored in our database, hosted by Supabase, and read only by our team to correct the question.
How long it is kept: while we review and correct the question, or until you ask us to delete it.
Please keep notes about the question itself, and leave out patient details and anything personal.
4. What we store on our own servers
An email address, if you give us one. That is the early-access address from this website, or, in the app, the address you enter if your region is not yet supported and you ask to be notified. With the in-app one we also store the region code you asked about and where in the app you asked from.
We keep it until we contact you or until you ask us to remove it, whichever comes first. Ask us to delete it at any time and we will.
Question flags, if you flag a quiz question (section 3.6). They carry no identity.
Emails you send us. A few links in the app, such as "Protocols need updating? Let us know", open a message in your own email app. If you send it, it reaches our mailbox like any other email, and we keep it as ordinary correspondence.
Everything else is passthrough. The services that carry your question, scenario, voice recording or certificate photo to the AI providers do not write anything to a database and do not store files. They receive the request, forward it, return the answer, and discard it.
Protocol content updates are one-directional: the app downloads protocol data from us. It never uploads your data to us.
5. Companies that process data on our behalf
| Company | What it receives | Kept | Trains on it |
|---|---|---|---|
| Anthropic, PBC United States | CE photos, AI questions, scenario text | Up to 30 days | No |
| Groq, Inc. United States | Voice recordings | Not retained | No |
| Supabase, Inc. | Waiting-list email addresses and question flags, and it runs our passthrough services | Until deleted | No |
| Hostinger | Hosts this website and the early-access signup list | Until deleted | No |
| Functional Software, Inc. Sentry | Crash diagnostics only, with no identity | Per their retention schedule | No |
These providers are located in the United States, so information sent to them is processed there.
One honest caveat: our AI providers may retain a request longer than stated above in narrow cases, where the law requires it or where their automated abuse-detection systems flag a request for review. These are standard terms and we would rather state them than pretend they don't exist.
6. Permissions the app asks for, and why
| Permission | What it is used for |
|---|---|
| Location while using the app | Sorting the built-in hospital list by distance. Calculated on your device, never transmitted. |
| Camera | Photographing CE certificates and certification cards. |
| Photo library | Attaching existing photos of certificates and cards. |
| Microphone | Dictating a patient presentation into Scenario AI. |
| Storage and downloads | Saving and caching your region's protocol PDF for offline use. |
| Network state | Checking whether you are online before attempting a download. |
You can refuse or revoke any of these in your device settings. The features that depend on them stop working. The rest of the app does not.
7. What we do not do
- We do not sell your personal information, and we do not share it for cross-context behavioral advertising.
- We do not use advertising networks or advertising identifiers.
- We do not use analytics or attribution SDKs.
- We do not track you across other apps or websites.
- We do not build a profile of you, and the app does not have the account system that would be needed to.
- We do not access your contacts, your health records, your financial information, or your browsing history.
8. Your choices and your rights
Deleting what is on your phone. Because your records live on your device, uninstalling Alpha Medic removes them. Please note that this is permanent. There is no cloud backup of your certification records or incident log, and we cannot restore them, because we never had them. The app does not currently offer an in-app "erase everything" button. Uninstalling is the way.
Deleting your email address. Email us and we will remove it. We do not require you to prove an account, because there is no account.
Access, correction, and deletion generally. Depending on where you live, including California, other U.S. states with comprehensive privacy laws, and the United Kingdom and European Economic Area, you may have the right to request access to your personal information, ask us to correct or delete it, and object to certain processing. Contact us and we will honor those requests. We will not treat you differently for exercising them.
In practice this is a short conversation: the only personal information we hold is an email address, if you gave us one. Step-by-step instructions for every kind of deletion are on Delete your data.
9. Security
Information sent between the app and our services, and onward to the providers listed above, travels over encrypted connections (TLS). So does this website.
Data stored on your phone lives in the app's private storage area, protected by your device's own operating-system protections: your passcode, biometric lock, and device encryption. Please use a screen lock. Certification records and incident log entries are meaningful information about you, and the strongest protection on them is the one your phone already provides.
No system is perfectly secure, and we will not claim otherwise.
10. Children
Alpha Medic is built for working EMS professionals and EMS students. It is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has provided us information, contact us and we will delete it.
11. Changes to this policy
If we change what the site or the app does with information, we will update this policy and change the "Last updated" date at the top. Material changes, for example adding user accounts or purchases, will be described here plainly rather than folded in silently.
12. Contact us
Questions about this policy, or a request about your information:
For anything that isn't about privacy, ask a human: Info@Code3Tek.com.