Privacy Policy

Last updated: November 4, 2026 (app version 1.4.33)

This Privacy Policy describes how SPEAR ("SPEAR", "we", "the app") collects, uses, and protects information, including information accessed through Google APIs.

Account & Application Data

SPEAR accounts are managed via Firebase Authentication. We store your email address, display name, phone number (optional), profile picture (optional), unit/platoon assignment, and role. Records you enter into SPEAR (personnel records, weapon/equipment serial numbers, weapon cards) are stored in your unit's own Firebase project and, if configured, in your unit's own Google Drive/Sheets/Docs.

In-App Messaging

SPEAR's in-app messages (including messages you send to the app owner through the owner mailbox) are stored in your unit's Firebase project and are visible only to the sender and recipient, or to the unit/platoon channel they were posted to. Messages to the owner are addressed to a generic "owner" mailbox, so the owner's personal email address is never shown to other users.

When you use the "Message the owner" feature, the message you write (and any attachment you choose to add) is saved as a message in the owner's account in Firestore, our cloud database. It is readable only by you and by the app owner's account, and it is used only to read and answer your message.

Camera & Photo Library

SPEAR accesses your device's camera or photo library only when you choose to attach a photo (for example a profile picture, a chat attachment, or an account background image). It never accesses them in the background. The photo you pick is uploaded to your unit's Firebase Storage only for that purpose, and nothing is read from your camera or library otherwise.

Smartwatch (Wear OS and Apple Watch) Companion

The optional SPEAR watch apps (Wear OS and Apple Watch) are display-only companions to the phone app. The phone app sends your paired watch a small roster/status snapshot over the local Bluetooth/wearable link only. That snapshot is a small summary — total headcount, number of deadlined personnel, and per-group counts only. No names, DoD ID numbers, blood types, serial numbers or other personal records are sent to the watch. The summary is held in the phone app's memory and sent directly to your paired watch over the Bluetooth/Wi-Fi link provided by Google Wear OS or Apple WatchConnectivity; it is not written to the watch's storage, and it is cleared when you sign out. No data is sent to any SPEAR server by the watch app.

Google User Data

If you use SPEAR's "Automatic Setup with Google" feature, you sign in with Google and SPEAR requests these permissions:

Permissions you grant to the scripts themselves. The three scripts run in your Google account, not on SPEAR's servers, and you authorize each one separately on Google's own Apps Script authorization screen. Google offers Apps Script no folder-restricted Drive permission, so each script asks to use Google Drive, Sheets, and/or Docs, and Google words the Drive permission broadly ("see, edit, create and delete all of your Google Drive files"). The scripts are written to work only with the Drive folder you chose, the subfolders and files they create inside it, and their own script file (which they move into that folder). They touch the top level of your My Drive only to take a newly created file out of it, or if no folder has been chosen. They contain no code that searches or lists your Drive outside that folder. The full source code of each script is shown in SPEAR's Deploy Guide so you can read exactly what it does, and you can revoke a script's access at any time.

Google API Services User Data Policy

SPEAR's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

Data Retention & Deletion

You may revoke SPEAR's access to your Google account at any time via your Google Account permissions page. Revoking access does not delete any Google Apps Script projects, Sheets, or Docs already created in your Drive — those remain under your own Google account and are managed by you like any other file you own.

Contact

Questions about this policy can be sent to the developer contact listed on our Google Cloud OAuth consent screen.