Privacy Policy
Accounted For (the person running a team can rename the app header on their phone).
Effective November 12, 2026.
The short version
Your roster stays on your phone. The app's server is a Supabase database; anything the app sends there (Feed posts, messages, page posts and photos, backups) is encrypted or scrambled on your phone first, so neither we nor Supabase can read it. We don't use analytics, ads or trackers.
What the app stores
Only what you type in or load from your own files: names, ranks or job titles, sections or teams, status and duty status, dates, locations or notes you add, phone numbers for a recall or call tree, equipment or asset assignments, incident (6W/IR) drafts, event attendance and app settings.
When you load a file, the app keeps only the columns it needs. ID numbers (EDIPI, Social Security), sex, emergency contact and next-of-kin columns are skipped and never stored. The one exception is what you type yourself into a person's record in Add people: an optional role, email, emergency contact (name, relationship, phone) and note. That stays on your phone like the rest of your roster.
Where it's stored
In your phone's local app storage for this app only. It is not uploaded anywhere. If you turn on PIN lock (DATA → Security), the stored data is encrypted on your phone with AES-256 using a key made from your PIN. There is no PIN recovery, so we can't unlock it either.
When data leaves your phone
Only when you choose to send it: tapping Text it, Share, Copy, Call, or exporting a backup file. That data then goes through the app you pick (Messages, Signal, email and so on) under that app's privacy terms. Exported backup files are not encrypted, so handle them like any personnel document.
Reports can carry a short code line so a higher-level leader's app can add up the numbers (Rollup). That line holds counts only, no names. A recall check-in link holds your unit name, the recall time and, if you enter it, your cell number so replies come to you. Those details sit after the # in the link, which browsers never send to the website host. The person tapping the link chooses whether to send their reply.
Live check-in (optional, on by default; turn off in DATA). During a recall, check-ins pass through a Supabase database (the app's server, called the relay below). It never receives names or phone numbers: the app scrambles each word a person types (one-way hash, unique to that recall) and sends only those codes, Good/Delayed/Need help, and an optional note of up to 60 characters. Only the leader's phone holds the key to read a recall. Each recall and its check-ins are deleted when the leader closes it out, or automatically after 72 hours.
QR check-in at formation. Works the same way: the scan sends scrambled name codes and a short-lived code to the relay, and the leader's phone matches them. It is deleted when the muster is closed out, or after 72 hours.
Live section updates (optional, off until you turn it on). Section leaders' phones send their section's statuses to the leader's board through the same relay. Only one-way scrambled codes of each person's name, a status code (for example Leave or TAD), the section's headcount and the time are sent; names are matched back on the leader's phone. Only the leader's phone can read them. The relay keeps the last few updates per section, and boards unused for 45 days are deleted. Turning live updates off deletes the board.
Section rosters for section leaders (part of live section updates). So section leaders don't have to load anything, the leader's phone shares each section's roster (rank, name, section, status, duty status, dates, location, detail and phone number) with that section's leader. It is encrypted on the leader's phone with AES-256 using a separate key for each section that rides only in that section leader's link, so the relay stores text it cannot read, and a section leader can open only their own section. The unit Feed keys travel inside the same encrypted copy, and inside each member's private My page, so people land in the unit Feed without a second link. Turning off live updates deletes the shared copies.
Ask (optional AI feature, off until you turn it on; Pro). When you tap Ask, the question you typed (and your last two questions and answers, for follow-ups) is sent through your unit's server to Anthropic's Claude API to write an answer, and the AI may search public official websites. The app blocks questions that contain Social Security or ID numbers, phone numbers, email addresses or names from your roster. Questions are not stored on the server; only a daily count is kept to cap costs. Your past questions stay on your phone. Anthropic handles API data under its own commercial terms and privacy policy (anthropic.com/legal). Don't enter anything personal, sensitive or classified. Answers can be wrong and are not official guidance.
Requests (optional). A request (for example leave dates and a short reason) is encrypted on the member's phone with the feed key before it reaches the relay; only the leader's phone can fetch it. Requests older than 120 days are deleted.
My page (optional). When a leader turns on My page for someone, the leader's phone encrypts that person's own status, duty, due-outs and calendar with a key that exists only in the private link sent to them. The relay stores one unreadable copy per person and deletes pages not updated in 120 days. Leader notes are never included.
Section calendars. When a section leader adds appointments for their people, the list is encrypted on their phone with a key that is only in the board link, then shared with the leader's board through the relay. The relay stores one unreadable copy per section. My log entries stay on the phone that wrote them (and in that person's encrypted backup, if turned on).
Send (messages with read receipts). The message text travels only in your text message and in the part of the link after the #, which browsers never send to the website host; it is never stored on the relay. When someone taps Got it, only scrambled codes of the name they type, Got it or Problem, and an optional short note go to the relay. Each message is deleted from the relay when you close it out, or after 72 hours.
Messages (optional). Private messages between a leader and one person, including photos, are encrypted on the sender's phone (AES-256) with a key that only those two phones have (it travels inside that person's private My page). Supabase stores text it cannot read. Each conversation keeps its last 300 messages.
Pages (optional). Personal and group pages, their posts, photos, comments and likes are encrypted on the poster's phone with the page key, which is only in the invite link. Only people the owner invites can read a page. The owner can remove any post or delete the page; you can delete your own posts, comments and likes. Photos are shrunk on your phone before they're sent.
Feed (optional). Feed posts are encrypted on the leader's phone (AES-256) before they reach the relay. The key is only in the join link the leader sends, so the relay stores text it cannot read. When someone taps Got it or Problem, only scrambled codes of the name they entered, the choice and an optional short note are sent. The relay keeps the latest 200 posts per feed; a deleted feed removes all its posts and confirmations, and feeds unused for 90 days are deleted. Anyone holding the join link can read the feed, so leaders should send it only to their people.
Backup and sync (optional, off until you turn it on). The app encrypts all of its data on your phone (AES-256) with a key made from a 24-character recovery code, then uploads the encrypted copy. The server stores only that unreadable copy, a version number and the time. Without the code, no one, including us, can read or restore it, and there is no reset if the code is lost. Phones that share the code stay in sync. You can delete the cloud copy at any time in DATA.
Server hub (optional, Pro, off until you turn it on). This is the one feature where the server can read your data. So the server can do the leader's phone's job while that phone is off, turning it on stores your backup's recovery code on the server, encrypted with a key only the server's hub program has. Every minute the hub opens your backup, applies section leaders' updates and calendar changes, sends each section leader their roster and saves the backup again. Turning the server hub off deletes the stored code; the server can't open your backup after that. If you don't want any server able to read your roster, leave it off.
Missed check-in alerts (optional). If you set a deadline on a live recall, the server keeps the deadline and how many people should check in, and sends one alert with the count when it passes. It never has names. Deleted with the recall.
Rally point (optional). The rally point's position rides in the check-in link after the #, never on the server. When someone taps "I'm at the rally point", their phone compares its location to it and only adds "AT RP" or a distance to their check-in note. Their location is not sent anywhere.
Slack, Teams and Discord (optional). If you save a webhook link and post the numbers, the report text goes through the app's server to that chat service and isn't kept. It includes names only if you turned on names in the report. That service's privacy terms then apply.
Texting from the server (optional, Pro). If you tap "Text the check-in link to everyone", the phone numbers and the link go through the app's server to Twilio, which delivers the texts. The server doesn't keep the numbers; Twilio keeps delivery records under its own privacy policy. A daily count is kept to cap costs.
Replying by text and family "safe" texts (optional, Pro). So people can check in by replying 1, 2 or 3, the server keeps, for that check-in only, a one-way key made from each texted number with a server secret (it can't be turned back into the number) and the same scrambled name codes the check-in link uses. When a reply arrives from Twilio, the server makes the key again from the sender's number, records a normal check-in, and doesn't keep the reply's number. The keys are deleted when the check-in is closed, or after 72 hours. Family "safe" texts send each family's number, the child's first name and last initial, the time and the pickup place you typed through the server to Twilio for delivery; none of it is kept on the server.
Calendar export and PDF report. Both are made on your phone and only leave it if you share or import them.
What we collect
Very little. Signing in to an account is optional, and the app has no analytics, advertising or tracking, and doesn't sell or share data. The only things the server can read are the items below, plus your roster if you turn on the Server hub (above).
Optional account. If you choose to sign in (email code, text code, or Sign in with Apple on the web), we keep your email address or phone number and a saved list of your teams, including each team's recovery code, so your teams follow you to another phone and leaders can send you a team. This list is stored so the server can read it. If you never sign in, none of this exists. Delete it any time: Tools → Data and settings → Security → Delete my account.
Crash reports. If the app hits a script error, it sends the error message, where in the code it happened, the app version, the kind of device (iPhone, Android or web) and a random ID for the phone (so one broken phone doesn't look like a hundred). Text inside quotes is removed on the phone, and the server removes anything that looks like a phone number or email. Never sent: roster, names, messages or anything you typed. Kept 30 days. Turn off in Tools → Data and settings → Crash reports.
The web version is hosted on GitHub Pages. Like any website host, GitHub may log technical information such as IP addresses when the app's files are downloaded; see GitHub's privacy statement. Those files contain no roster data. Fonts and file readers are served from the same site, not from third parties.
Accounted For Pro. Pro is an optional subscription. On iPhone, Apple sells it through the App Store; on the web, Stripe does. Apple or Stripe handles the payment; we never see your card. So Pro features that run on the server (Ask, the Server hub, texting from the server) know your team has Pro, the app sends Apple's signed receipt to the server, which checks Apple's signature and keeps the subscription's ID number, product, end date and a scrambled copy of your team's Pro code. On the web, Stripe also tells the server the subscription's customer ID (so you can manage it) and its end date. No name or email is stored. The Pro code also lets members of your Feeds use Ask; anyone holding it gets your team's Pro, so keep it private. Manage or cancel: on iPhone in Settings → your name → Subscriptions; on the web with Manage subscription in the app.
Add-ons (optional). Text credits, Event Pass, Compliance pack, template kits, branding and site licenses are one-time purchases or codes. They are tied to a random key stored on your phone, not to your name or email; the server keeps only a scrambled copy of that key with what the key has (for example a credit balance and an end date). Payment is handled by Stripe (on the web and Android), which tells the server that a purchase was paid; we never see your card. Add-ons are not sold on iPhone yet; a code works everywhere. Your drill log, signatures, team name and logo stay on your phone and are not uploaded. If you copy your key to another phone, that phone gets the same add-ons.
Verified leader (optional, free). A leader can confirm their email or phone with a sign-in code and send an organization name, website and role for review. We keep a partly hidden copy of the contact (for example "l***@example.com" or the last three digits), the organization details, and the review result, tied to a scrambled copy of the team's key, so we can show people a badge. Members see the badge (and the organization name once approved) on the check-in page before they check in. No ID is collected or kept.
Video clips in posts. A leader can attach one short video to a Feed post. It is encrypted on the leader's phone with the feed key before upload, the same way photos are, and expires with the post.
Deleting your account and data
In the app: Tools → Data and settings → Security → Delete my account. It deletes your sign-in (if you were given one), every feed, login, live section link, My page and server backup you created, your feed memberships and alert subscriptions, and then erases everything on the phone. It can't be undone.
To only clear the phone, use Security → Erase all app data on this phone, or delete the app. Anything still on the relay expires on its own (see the time limits above). Need help? Email administration@accountedforteam.com and we'll delete what we can find within 30 days.
Deleting your account doesn't cancel a subscription. Cancel on iPhone in Settings → your name → Subscriptions, or on the web with Manage subscription.
Reports and blocking
When someone reports a Feed post, the report (reason, optional note, the reporter's name as they entered it and a short quote of the post) is encrypted on their phone and sent only to the person running that team. Blocking and hiding happen only on your phone. See the Terms of Use.
Children
The app is meant for adults managing teams. It isn't directed to children under 13. Schools, clubs and youth programs use it through their adult staff: children don't create accounts, and what is kept about them is only what staff enter on their own phones (such as a roster).
Not a government system
Accounted For is an independent app. It is not an official system of, and is not endorsed by, the Department of Defense, the U.S. Marine Corps, any military service, police agency or government. Follow your organization's rules on what personal information may be kept on personal devices.
Changes and contact
If this policy changes, the new version will be posted here with a new effective date.
Questions: administration@accountedforteam.com · Support · Open the app