Privacy Policy — Fireline Forms
This Privacy Policy explains how Anchor Point Apps, LLC ("we," "us," or "our"), an Arizona limited liability company based in Phoenix, Arizona, handles information in connection with the Fireline Forms mobile app for iOS and Android and the Fireline Forms web app at firelineforms.app (also available at app.anchorpointapps.com) (together, the "App"), and our website at anchorpointapps.com (the "Site"). Section 14 covers the Site.
The short version: Fireline Forms is built to work offline, and your forms stay on your device. You do not need an account: accounts are optional, and we do not store your forms on our servers. We do not sell your information. We do not currently use third-party analytics or advertising SDKs. A few features do connect to the internet, and this policy explains each one:
- Agency access (only if you use it). If you work for a listed agency and ask for free agency access, the App sends your work email address to our verification service so it can email you a code (section 3).
- Optional account (only if you sign in). You can sign in with an emailed code, Sign in with Apple, or Sign in with Google so a subscription bought in the phone app also works in the web app. We then keep your account email, a random account ID, and sign-in records on our servers. You can delete your account in the App at any time (section 4).
- Document timestamps (when active in your version of the App). The App can send a one-way fingerprint of each PDF it makes to our timestamp service, which records it permanently on a public blockchain. The fingerprint is a short code, not the document, and it cannot be turned back into your form. Once recorded, it cannot be deleted (section 5).
- Subscriptions. Paid plans are sold by Apple and Google and managed for us by RevenueCat, which never receives your forms (section 7).
1. Information stored on your device (not collected by us)
The App lets you create and store information only on your own device. This includes:
- Incident forms and records. Examples: ICS 213 general messages and resource requests, ICS 214 activity logs, OF-288 and OF-297 shift tickets, SF-261 Crew Time Reports, Personnel Time Reports, crew swap and extension requests, IQCS/IQS experience records, mileage and per diem logs, demob packets, and paycheck estimates.
- My profile (optional). If you choose to fill it in: your name, home unit, agency type, phone number, usual positions, red card details (including a photo of your red card, if you add one), and pay rate. It is used only to fill in your forms and estimates.
- Signatures and contacts. A saved signature, if you choose to save one, and contacts in your folders (names, roles, phone numbers, and email addresses that you type in or that the App reads from a resource order). Email addresses you enter in the App are used only to fill in forms and to open your own email app when you tap them. The one exception is the agency work email described in section 3.
- Files, photos, and locations you add. Examples: resource order PDFs you pick for the resource order reader, documents you convert or fill in, photos of paper forms, photos or files you attach to a form, and a location you add with "Use my location."
- App records. A random install ID that the App creates the first time you open it (it is not your name, email, phone number, or an advertising ID), a count of PDFs made this month (for the Free plan limit), and, if you use them, your agency access pass (section 3), your sign-in session and account details (section 4), and document timestamp records (section 5).
We do not have access to this information. It is stored locally by the App on your device (or, in the web app, in your browser's local storage). It is not sent to us or to any server we operate, except for the limited items described in sections 3, 4, 5, and 7.
2. Features that move data — and who controls it
- Resource order reader and Convert documents. When you pick a resource order or another PDF, the App reads it on your device to pull out details. The file is not uploaded to us.
- Crew QR sync. You can share selected records with a crewmate by showing a QR code that their device scans. The transfer is directly phone-to-phone and does not pass through our servers. You decide what to share and who scans it. Once shared, the data is on the other person's device, and they control it.
- Encrypted backup files (.ffbackup). You can export a backup file that is encrypted with AES-256 using a password you choose. You choose where to save or send it (for example iCloud Drive, Google Drive, the Files app, or email). That service's privacy policy applies to the file while it is stored there. We never receive your backup password, and we cannot recover a lost password or decrypt your backup.
- Exporting and sharing PDFs. When you export a form (for example a demob packet PDF) and share, email, or print it through your phone's own share options (such as email, messaging, another app, or a printer), that transfer is controlled by you and by the app or service you choose. The App does not send your forms or requests to any dispatch system itself.
- Maps, calls, and email links. If you tap an address or a map link, the App opens Apple Maps or Google Maps, and that service receives the address or coordinates. If you tap a phone number or email address, the App opens your phone or email app. These happen only when you tap, and those companies' privacy policies apply.
- NFES catalog. The NFES catalog in the App is built in and updated only through App updates. It is not downloaded from our servers or any other server.
3. Agency access (only if you use it)
We offer free access to Fireline Forms for staff of listed agencies who verify a work email address. Today the list includes the Arizona Department of Forestry and Fire Management (DFFM) and email addresses ending in @dffm.az.gov. Agency access is offered by Anchor Point Apps, LLC. Fireline Forms is not affiliated with or endorsed by the Arizona Department of Forestry and Fire Management or any government agency.
How it works. Agency access starts only when you enter your work email and tap "Email me a code." By doing that, you ask us to process your email address as described here. Then:
- The App sends your work email address and the App's install ID to our verification service, which runs on Cloudflare Workers. If the email's domain is on the list, the service emails you a 6-digit code that expires in 10 minutes.
- You enter the code. The App sends your email address, the code, and the install ID to the service again.
- If the code is right, the service sends back a signed access pass. The pass is good for one year and works only with this install of the App. It contains the install ID, the agency's name, the plan it unlocks, the dates it was issued and expires, and a short one-way code made from your email address (not the address itself).
- The App checks the pass on your device, so it keeps working offline. The App does not contact our service again to keep using it. Starting 30 days before the pass expires, the App asks you (at most once a week) to verify your work email again, using the same steps.
What our service keeps. We do not keep a list of the people who verify, and the service does not store your email address. It stores the code only as a one-way scrambled value (combined with your email, the install ID, and a secret key) and deletes it once it is used, after 5 wrong tries, or when it expires 10 minutes later. To prevent abuse, the service keeps short-lived counters tied to your IP address, the install ID, and a one-way scrambled form of your email address. Each counter deletes itself at the end of its time limit: one hour, or one day for the daily email limit. Cloudflare keeps request logs for this service, which can include your IP address and basic request details, for up to 7 days. While the service is in test mode, the code is written to that log instead of being emailed, with your address partly hidden (for example, j***@dffm.az.gov), and the App says "Test mode."
Who else is involved. Cloudflare hosts the service. To deliver the code, we use an email delivery provider (Cloudflare's email service or Resend), which receives your email address and the code message only to deliver it, under its own privacy policy. If subscriptions are managed through RevenueCat (section 7), the service may also tell RevenueCat to give this install's ID the plan that agency access unlocks until the pass expires. In that case RevenueCat receives only the install ID, the plan name, and the end date, never your email address. We do not send your information to your agency.
On your device. The access pass and your work email address (so the App can fill it in when you verify again) are saved on your device. Deleting the App removes them.
We use this information only to check that your email is on the agency list, send your code, unlock your plan, and prevent abuse. We do not use it for marketing.
4. Optional accounts (only if you sign in)
You can use Fireline Forms without an account. An account is optional. Its purpose is to link a subscription bought in the phone app to you, so that the web app can unlock it too. Everything else works the same without one.
How you sign in. In My profile > Account (or Sign in in the web app), you can choose:
- Email code. The App sends your email address and the App's install ID to our account service, which runs on Cloudflare Workers. The service emails you a 6-digit code that expires in 10 minutes. Codes are handled the same way as in section 3: stored only in scrambled form, deleted once used or expired, with short-lived abuse-prevention counters.
- Sign in with Apple or Sign in with Google. Apple or Google confirms who you are and gives the App a signed token, which our service checks with Apple or Google. From it we receive only your email address and a stable user ID that Apple or Google assigns to you for our App. If you choose Apple's "Hide My Email," the email is an Apple relay address. We do not receive your Apple or Google password, and we do not ask for your name, contacts, or other profile information.
What we keep (Cloudflare D1). Our account service stores your account in a Cloudflare D1 database: a random account ID (for example "ffa_…"), your account email, which sign-in methods you have used (email, Apple, Google), and the date the account was created. It also keeps sign-in records that link your email and your Apple or Google user ID to the account, stored only as one-way scrambled values, and your sessions.
Session tokens. When you sign in, the service gives the App a random session token, which the App saves on your device (or in your browser). Our service stores only a one-way scrambled form of it. A session ends when you sign out, when you delete your account, or after 365 days.
Linking purchases (RevenueCat). When you are signed in, the phone App uses your account ID as its app user ID with RevenueCat (section 7), so your subscription records are linked to your account ID. In the web app, our service asks RevenueCat whether your account ID has an active subscription, so the web app can unlock it. RevenueCat receives the account ID, never your email address. Signing out returns the App to an ID that is not linked to your account.
On your device. The session token, your account ID and email, and the last subscription status our service reported are saved on your device (or in your browser) so the App works offline. Signing out or deleting your account removes them from that device.
Deleting your account. You can delete your account at any time:
- In the App: My profile > Account > Delete account. Your account is deleted from our servers right away.
- By email: email [email protected] from your account's email address with the subject "Delete my account."
Deleting your account removes your account email, your sign-in records (Apple and Google user IDs), your sessions, and the account record in our database, which also removes the link between you and your subscription status. Deleting your account does not cancel a subscription; cancel it in your Apple or Google account settings. Apple, Google, and RevenueCat keep their own purchase records under their own policies. Your forms are never on our servers, so they stay on your device. More details: anchorpointapps.com/delete-account.
We use account information only to sign you in, keep your sessions, link your subscription, and prevent abuse. We do not use it for marketing.
5. Document timestamps (when active in your version of the App)
Some versions of the App include a document timestamp feature. It creates a public, permanent record that a specific PDF existed at a specific time, without revealing what the PDF says.
- What happens. When the feature is active, each time the App makes a PDF (for example a form, a re-signed or approved form, your own document, a combined PDF, or a demob packet), the App calculates a SHA-256 fingerprint of that PDF on your device. It sends the fingerprint to our timestamp service, which runs on Cloudflare Workers. The service writes the fingerprint, with a short label for our record format, into a transaction on the public Kaspa blockchain.
- What is sent. The fingerprint, the App's install ID (used to limit abuse and control costs), and a key that identifies the App. Like any internet request, our service also sees your IP address. The PDF itself and the contents of your forms are never sent. Your name, location, and other form details are not sent.
- When. It runs in the background, with no extra step on screen. If you are offline, the fingerprint waits on your device and is sent the next time you have a connection while the App is open.
- What a fingerprint can and cannot reveal. A fingerprint is a one-way code. It cannot be turned back into the document, and it does not reveal the contents of your form. But anyone who already has an exact copy of the same PDF can calculate its fingerprint and check it against the public record to see that the PDF existed when it was recorded.
- It is permanent. Anyone can read the Kaspa blockchain, and records written to it cannot be changed or deleted, by us or by anyone else. Deleting a form, deleting the App, or asking us to delete your information does not remove a fingerprint that has already been recorded.
- What our service keeps. It keeps the fingerprint and its transaction ID, so the same PDF is not recorded twice. It uses the install ID and IP address only to limit abuse and control costs, not to identify you. Cloudflare keeps request logs for Workers for up to 7 days.
- On your device. The fingerprint and transaction details are saved with your records, so they are included in your backup files.
- Is it active? Some builds include this feature. When it is included, it is on by default, and you can turn it off (or back on) in My profile > Forms under PDF fingerprint record. Turning it off stops new fingerprints from being sent and drops any that are still waiting on your device; fingerprints already recorded on the blockchain stay there permanently. The Privacy section of the App's About screen says whether fingerprints are being sent.
6. Device permissions
The App may ask for permission to use:
- Camera — to photograph paper forms so you can fill them in, and to scan crew QR codes.
- Photos / media library — only when you choose a picture of a paper form or a photo to attach.
- Files / documents — to open resource order PDFs and other documents you pick, to import backups, and to save exports.
- Location (while using the App) — only when you tap "Use my location" to add a drop-off point. The App reads your position once and puts it in the form on your device. It is not sent to us.
- Notifications — only if you turn on red card reminders. Reminders are scheduled on your device. The App does not use push notifications and sends nothing to us for them.
These permissions are used only for the features you trigger. The App does not use them to collect data for us. You can turn permissions off at any time in your device settings, though some features may stop working.
7. Information we do receive
- When you contact us. If you email us for support or to join a beta, we receive your email address and anything you include in your message. We use it only to reply, provide support, or run the beta, and we keep it only as long as we need it for those purposes.
- Send feedback. If you use Send feedback in the App, the App sends what you type, a screenshot only if you choose to attach one, a reply-to email address only if you enter one, the App's install ID, and basic app and device details (App version, platform, operating system version, device model, and the screen you were on) to our service on Cloudflare Workers, which emails it to us. We use it only to improve the App and to reply.
- Agency access, accounts, and document timestamps. See sections 3, 4, and 5.
- In-app purchases. Paid plans (such as Fireline Forms Basic) are bought through the Apple App Store or Google Play. Apple or Google processes your payment. We never receive your credit card or full payment details. The App checks whether your subscription is active through RevenueCat (see the next item). Apple and Google may give us limited, generally aggregated sales and reporting information (for example the number of purchases by country), as required to run a store listing. Apple's and Google's privacy policies apply to your purchase.
- Subscriptions (RevenueCat). We use RevenueCat, Inc. to manage subscriptions and to check which plan you have. RevenueCat is a service provider that does this on our behalf. We use it only for purchases and subscriptions, not for advertising and not to track how you use the App. When the App checks your plan, or when you buy or restore a subscription, RevenueCat receives:
- an app user ID. If you are not signed in, it is a random ID created in the App (it may be the same install ID described in section 1) that is not linked to your name, email address, or Apple or Google account. If you are signed in, it is your account ID (section 4), which our account service links to your account email. RevenueCat itself does not receive your email address;
- your purchase and subscription records from Apple or Google, such as the product, price, purchase and renewal dates, whether the subscription is set to renew or has been canceled, and the store's transaction IDs; and
- basic device and app information, such as your platform (iOS or Android), operating system version, App version, and country or region.
- Web app. The web app at firelineforms.app (also app.anchorpointapps.com) is hosted on Cloudflare Pages. Your forms stay in your browser's local storage and are not sent to us. Like any website, Cloudflare may automatically log standard technical information, such as your IP address and browser type, to deliver and secure the site. We do not use it to identify you. Nothing is sold in the web app; if you sign in, it checks your subscription as described in section 4.
- App store information. Apple and Google may provide us with anonymized crash reports or usage statistics if you have agreed to share them with developers in your device settings. You control this in your device settings.
Service providers. The companies that handle information for us are: Cloudflare (hosts our verification, account, feedback, and timestamp services, the account database (D1), the web app, and this website, and may deliver code and feedback emails), Resend (may deliver code emails), RevenueCat (subscriptions), and Apple and Google (app stores, payments, and Sign in with Apple / Google). The Kaspa blockchain is a public network, not a service provider. Anyone can read it.
8. What we do NOT do
- We do not require an account. Signing in is optional, and you can delete your account at any time.
- We do not store your forms or their contents on our servers.
- We do not sell or "share" your personal information, as those terms are defined under the California Consumer Privacy Act (CCPA/CPRA).
- We do not use your information for targeted advertising.
- We do not currently use third-party analytics or advertising SDKs.
- We do not track you across other companies' apps or websites.
- We do not send your information to your agency or employer.
9. Keeping your information safe
Because your data stays on your device, its security depends mostly on your device. Use a device passcode, keep your operating system updated, and use a strong password for backup files. Backup files are encrypted with AES-256. The App connects to our verification and timestamp services over encrypted connections (HTTPS), and verification codes, sign-in records, and session tokens are stored only in scrambled form. No method of storage or transfer is 100% secure.
10. Keeping and deleting your information
On your device, you control your data. You can delete it at any time:
- Forms, drafts, and folders: swipe left on an item or long-press it and choose Delete, or use Select in a folder to delete several at once. Deleting a folder deletes what is in it.
- My profile and signature: clear any fields you no longer want, and use Clear to delete a saved signature.
- Clear my entries: in a form's ⋯ menu, this clears what you typed on that form.
- Everything: deleting the App from your device removes all of its locally stored data, including your forms, profile, install ID, agency access pass and work email, your sign-in session, and any fingerprints still waiting to be sent. Deleting the App does not delete your account on our servers; see section 4 to delete it.
Backup files you have saved elsewhere (for example in iCloud Drive, Google Drive, or email) are not deleted by these steps. Delete them directly from wherever you saved them. Records you shared with crewmates by QR are stored on their devices, and only they can delete them. Because we do not hold your forms, we cannot restore them for you.
What we or our providers keep, and for how long:
- Agency verification: codes up to 10 minutes; abuse-prevention counters up to one day; Cloudflare request logs up to 7 days. We keep no list of who verified. The email delivery provider keeps delivery records under its own policy.
- Document timestamps: fingerprints recorded on the Kaspa blockchain are permanent and cannot be deleted by anyone. A fingerprint does not reveal the contents of your form, but it cannot be removed. Our service keeps the fingerprint and transaction ID, and Cloudflare request logs are kept up to 7 days.
- Accounts (if you sign in): your account record and sign-in records until you delete your account; each session until you sign out or for up to 365 days; Cloudflare request logs up to 7 days.
- Subscriptions: RevenueCat keeps subscription records for us until you ask us to delete them. Apple and Google keep their own purchase records. Deleting the App does not delete these records.
- Emails you send us: only as long as we need them to help you.
To ask us to delete information, email us at the address in section 16. To delete your account, use My profile > Account > Delete account, or email us from your account's email with the subject "Delete my account" (section 4). We will delete your account and the support emails and subscription records we hold for you, and we will explain anything we cannot delete, such as fingerprints already recorded on the public blockchain.
11. Your privacy rights
Depending on where you live (including California and other U.S. states with privacy laws), you may have the right to know what personal information we hold about you, to ask for a copy, to correct it, to delete it, and to opt out of its sale or sharing. In most cases we hold little or no personal information about you. The exceptions are support or beta emails you send us; if you create an account, your account record (section 4); if you subscribe or the App checks your plan, the subscription records RevenueCat keeps for us under your install ID or, if you are signed in, your account ID (section 7); if you use agency access, the short-lived verification records described in section 3; and, when document timestamps are active, the fingerprints and install ID described in section 5. You can ask us to delete information at any time (see section 10). We will not discriminate against you for using your privacy rights. To make a request, email us at the address below. We may need to confirm that the request comes from you.
12. Children's privacy
The App is designed for wildland fire personnel and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has sent us personal information, contact us and we will delete it.
13. Do Not Track and Global Privacy Control
We do not track users across sites or apps, so there is nothing to opt out of. We honor Global Privacy Control signals to the extent they apply.
14. This website
Our website, anchorpointapps.com, does not use cookies, analytics, tracking, or ads, and it has no forms that collect information. Like any web host, our host (Cloudflare) may process standard technical data, such as IP addresses, in server logs to deliver and secure the site. If you email us from the website, see "When you contact us" in section 7.
15. Changes to this policy
We may update this Privacy Policy as the App changes. For example, we will update this policy before adding any feature that sends data off your device. The "Effective" date at the top shows when it was last updated. If we make a significant change, we will tell you in the App or on our website before the change takes effect.
16. Contact us
Anchor Point Apps, LLC
Based in Phoenix, Arizona
Email: [email protected]