CodeScribe EMS

Privacy Policy

Effective November 6, 2026. Replaces the policy of October 7, 2026.

CodeScribe EMS is an app for iPhone, iPad and Android phones for documenting cardiac arrest resuscitations. This policy says what the app stores, where it goes, who can see it, and how to get rid of it. It is written to be read, not skimmed, because the people who use this app are responsible for patient records and deserve a straight answer.

Who publishes each app

In this policy, "CodeScribe EMS" means the app on whichever store you got it from. Contact details for both are in section 8.

There are two ways to use CodeScribe EMS, and they are covered separately below.

1. The app on its own

What the app stores on your device

Every code record you create: the start time, each logged intervention and its time, the patient category (adult or pediatric), the outcome, and the optional fields you choose to fill in (age range, estimated downtime, incident or run number, notes). Your button layout, timers and settings. All of it is stored on the device in Apple's standard on-device storage and protected by the device passcode. The app does not use iCloud for records, so records do not sync between devices and are not stored in iCloud except as part of your normal device backup, which you control.

On Android, the same records are kept in the app's private storage on the phone, protected by the device lock. The Google Play version has no network access at all: it does not have Android's internet permission, so it cannot send anything anywhere. Android's cloud backup and device-to-device transfer are turned off for the app, so records are not copied to Google Drive or to a new phone; if you change phones, export the records you need first.

What leaves your device

Nothing, unless you send it. Copying a narrative, sharing a PDF, or sending a record file to your department all start with you tapping Share, and the file goes only where you send it through Apple's share sheet or Android's (AirDrop, email, your ePCR, and so on). Once it is there, it is governed by that system's rules, not this policy.

Analytics and tracking

None. The app has no analytics, no advertising, no crash reporting service and no tracking of any kind. We do not know how many people use it, what they tap, or how long a code lasts, unless you tell us.

Shared button setups

A department can share its button layout as a file, or by a code that the app looks up in Apple's iCloud public database. A shared layout contains configuration only: button names, timers, option lists and the department's name. It contains no records and no personal information. Looking up a code sends that code to Apple's servers and nothing else. The Android app has no network access, so it does not look up codes.

App Store and Google Play purchase

On iPhone and iPad, buying the app or the export unlock is handled entirely by Apple. We receive no name, address or payment information from Apple, only anonymous sales totals. On Android, buying the app is handled entirely by Google Play. We receive no name, address or payment information from Google, only anonymous sales totals.

2. Department and training-program accounts

This section applies only if you sign in and join a department. Until you do, section 1 is the whole story. Department accounts are not yet available in the Android app; this section applies to the iPhone and iPad app.

Signing in

You sign in with an email address (we send a one-time code) or with Sign in with Apple. We store the email address you sign in with, or the relay address Apple gives us if you choose to hide yours. Sign-in emails are sent through Resend, an email delivery service, which sees your address and the email content for as long as it takes to deliver. We use the address for signing in and, for officers, for messages about the department's account. We do not send marketing email to members.

What your department receives about you

When you join, your department's officers see: the name you entered on the roster, when you joined, which protocol revision your phone has, your app version, and the date of your last check-in (the day, not the time). They do not see your email address unless you are the officer who set the department up.

What your department receives about each code

After a code ends, the app prepares a summary and sends it the next time the app opens with a signal, after a random wait of 12 to 72 hours. The wait exists so that the time the summary arrives cannot be used to work out when the arrest happened. A summary contains exactly these things and nothing else:

A summary never contains the date or clock time of the code, the incident or run number, the notes field, age, weight, any free text, or anything that identifies a patient. The app's own code decides what can be sent, and the server independently refuses anything outside this list, so a future version of the app cannot quietly send more. You can see every field the app would send under Settings, Department account, What your department sees, before you join.

In a training program (an EMT or paramedic course), where every code is a practice scenario with no patient, two things differ: the summary goes up at your next check-in instead of after the wait, and it may carry the scenario name you typed. The server refuses a scenario name from any department that is not a training program.

Taking a summary back

If you delete a code from your phone, or mark it as training, the app withdraws that summary from your department at its next check-in. Officers keep the summaries of codes you have not withdrawn, including after you leave, because they are the department's quality records; they stay linked to your roster name until you delete your account, after which they are unlinked from any name.

Officers and the dashboard

Officers sign in to a web dashboard at app.codescribeems.org and see their department's roster, protocol and summaries. The dashboard also stores: the department's protocol (buttons, timers and option lists) and each revision's publisher and date; which summaries an officer has marked as reviewed and by whom; and a log of department activity (members joining, being approved or removed, protocol revisions) kept as references to roster entries rather than names. Officers can download their department's summaries as a spreadsheet. There is no log yet of who viewed or downloaded what. The dashboard keeps one sign-in token in your browser and nothing else, and it has no analytics; it stays signed in on that browser until you sign out, so sign out on a shared computer. Removing an officer from the roster, or making them a member, ends their dashboard access at once.

Officers who were on a call can often tell which summary is which from its length and timings, even without a date. Treat the dashboard like any other QA record, and use it to improve care rather than to single anyone out.

Paying for a department

Department licenses are sold through Stripe. Card details are entered on Stripe's page and never reach us; we receive the buyer's email address, the department name and Stripe's customer and subscription identifiers so we can renew or end the license. Stripe's handling of your payment is covered by Stripe's privacy policy.

Where account data is kept and who can reach it

Account data is stored with Supabase in a database in the eastern United States. Access is enforced in the database itself: a member can read their own department's protocol and roster and write only their own summaries; an officer can read their department's summaries; nobody can read another department's data; the app and dashboard have no access path that bypasses these rules. The website and dashboard are served through Cloudflare, which sees the usual web request information (your IP address and the pages requested) to deliver them. Lawrence International LLC, as the operator, can see account data for support and billing and does not look at summaries except to help an officer who asks.

How long it is kept

Roster entries and summaries are kept while the department's account exists. If you leave a department, your roster entry is removed; your sent summaries stay with the department but are unlinked from your name once you delete your account. When a department's pilot or license ends without being renewed, its data is kept for twelve months so it can pick up where it left off, then deleted. A department can ask to be deleted at any time, which deletes everything about it, and we confirm the deletion in writing. Sign-in emails held by Resend and payment records held by Stripe follow those companies' own retention rules.

Deleting your account

Settings, Department account, Delete account. This deletes your sign-in, removes you from your department's roster, and unlinks your summaries from any name, immediately. Your records on the phone are not touched; delete those in the app if you want them gone too. You can also email us to delete the account for you.

3. Patient information and HIPAA

CodeScribe EMS is designed to be used without patient names, dates of birth, medical record numbers or other identifiers, and has no fields meant to hold them. Your records on the phone are yours and your service's; treat them as you would any PCR draft, and do not put patient identifiers in the notes field.

The summaries a department receives are designed to contain no protected health information: no identifiers, no dates, no times, no free text. On that basis we do not act as a business associate, and departments have not needed a business associate agreement to use the dashboard. This is our design and our understanding, not legal advice; if your department's counsel wants to review the exact field list, we will send it, and if they conclude an agreement is needed we will discuss one. We will not change what a summary contains without updating this policy first.

4. Your rights

You can see everything the app holds about you on your phone, in the app. For account data, email us and we will send you a copy, correct it, or delete it. If you are in the European Economic Area, the United Kingdom, Canada or another place with a data protection law, the same applies: the lawful basis for processing account data is the agreement you make with us when you join a department, your data is processed in the United States, and you can complain to your local data protection authority if we do not resolve something. We respond within 30 days.

5. Security

Records on the phone are protected by your device passcode and Apple's file protection. They are included in your phone's normal iCloud or computer backup like any app's data; if your department doesn't allow that on personal phones, turn off iCloud Backup or exclude the app. On Android, the app is excluded from backup and device transfer. Account traffic uses TLS. Membership is proved with a signed token that cannot be forged or altered. Sign-in tokens live in the device keychain. Database access rules are tested on every change. If we ever learn of a breach affecting account data, we will tell affected officers within 72 hours of confirming it.

For your IT department

Account data is stored in a Supabase-managed PostgreSQL database in AWS us-east-1, encrypted at rest by the provider and in transit with TLS 1.2 or newer; backups are encrypted the same way. Sign-in is by one-time email code or Sign in with Apple; there is no password to store, and no single sign-on (SAML or Active Directory) yet. Access rules are enforced inside the database (row-level security) and tested on every change. No third party has audited us yet; we are a small company and will say so. We will complete your vendor security questionnaire or a short data-handling agreement on request, and we will send the exact list of fields a summary contains. Email support@codescribeems.org. To report a security problem, email the same address with "Security" in the subject; we reply within two business days.

Outside services we use

ServiceWhat forWhat it handlesWhere
Supabase (on Amazon Web Services)The database, sign-in and server functionsAll account data: emails, rosters, protocols, summariesEastern United States (AWS us-east-1)
ResendSending sign-in codes and license emailsEmail addresses and the email contentUnited States
StripeCard payments for department licensesThe buyer's email, card and billing detailsUnited States
CloudflareServing the website and dashboard, and our email routingIP addresses and the pages requested; mail sent to our addressesGlobal network
AppleSign in with Apple, App Store sales, shared button layouts (iCloud public database)The Apple sign-in relay address; button layouts with no personal dataApple's servers

Each handles data under its own published data processing terms. We will update this list before adding a service that handles department data.

6. Children

CodeScribe EMS is a professional tool for trained emergency responders and students in accredited EMS programs. It is not directed at children, and we do not knowingly collect information from anyone under 16.

7. Changes

When this policy changes, the new version is posted here with a new effective date, and officers of active departments are told by email before the change takes effect if it affects what a department receives.

What changed on October 7, 2026: this version adds section 2 for department and training-program accounts, which did not exist before, and the list of outside services. Nothing about the standalone app (section 1) changed.

Also changed since the October 7, 2026 policy: the policy now covers the Android app as well as iPhone and iPad (section 1, the purchase paragraph, and the backup sentence in section 5). Nothing about what the iPhone app does changed.

What changed on November 6, 2026: the policy now says who publishes each app. The Android app on Google Play is published by Lawrence International LLC; the iPhone and iPad app on the App Store is currently published by Sasha Lawrence as an individual developer, and this page will say so if that changes. The contact details now name Lawrence International LLC, which also operates the department accounts. Nothing about what either app does, or about what data is collected, changed.

8. Contact

Lawrence International LLC, a Virginia limited liability company, 507 16th St NW, Charlottesville, VA 22903, United States. support@codescribeems.org. Please do not include patient information in any email.