Bumpass Volunteer Fire Department
Privacy Policy
Effective November 18, 2026
The Bumpass Volunteer Fire Department (“BVFD,” “we,” “us,” or “our”) is a registered 501(c)(3) nonprofit organization serving northeastern Louisa County, Virginia, and the Lake Anna area. This Privacy Policy explains what information we collect through bumpassfire.org (the “Site”), how we use it, and the choices you have. By using the Site, you agree to the practices described here.
Information We Collect
- Information you give us. When you use our contact form, membership/volunteer application, event registration, or donation forms, we may collect your name, email address, phone number, mailing address, and any additional details you choose to provide in your message or application.
- Applicants under 18.A volunteer application from someone under 18 needs the approval of a parent or legal guardian. We ask for the parent or guardian’s name, relationship to the applicant, email address and phone number, and email them a link to approve or decline. We keep a record of their decision: the name they typed, the date and time, and the IP address it was made from. The parent or guardian sees only the applicant’s name and the agreement, none of the applicant’s answers. If the parent or guardian declines, the application is closed and its Social Security number is deleted at once. If they never respond, the application is deleted, with its Social Security number, 30 days after the link expires (links expire after 14 days).
- Membership & portal information. If you are a BVFD member with a portal account, we collect the information needed to administer membership, training, scheduling, and department operations.
- Donations.Online donations are processed by PayPal. Payment card and bank details are entered on PayPal’s secure platform — BVFD does not collect or store your card or bank account numbers.
- Information collected automatically. Like most websites, we automatically receive standard server log data (such as IP address, browser type, and pages visited) and may use cookies or similar technologies for site functionality, security, and to understand how the Site is used.
How We Use Your Information
- Respond to your inquiries and requests.
- Process and follow up on membership/volunteer applications and event registrations.
- Administer donations and send acknowledgments or receipts.
- Operate, maintain, secure, and improve the Site and our services.
- Send department communications you have requested or that relate to your involvement with BVFD.
- Comply with legal obligations.
How We Share Information
We do not sell your personal information. We share information only as needed to operate the Site and our organization:
- Service providers.We use trusted third parties to run the Site — for example, website and database hosting, email delivery, and payment processing (PayPal). These providers may process your information solely to provide services to us.
- Volunteer onboarding. As part of the volunteer application and background process, relevant application information may be shared with Louisa County or other authorities where required for membership eligibility.
- Legal requirements. We may disclose information if required by law, subpoena, or to protect the rights, safety, or property of BVFD, our members, or the public.
Artificial Intelligence Service Providers
Some features use artificial intelligence (AI) services run by outside companies. Only the content described below is sent, and only when you use the feature.
- Anthropic (maker of Claude). Anthropic, PBC provides the AI model behind these features:
- Ember Guide.Questions you type to Ember on this website, in the member portal or in the member app, and the earlier messages of the same conversation, are sent to Anthropic to produce an answer. In the member portal and the app, Ember’s instructions also include the names and roles of department officers.
- Certificate scan.When a member uses the scan to fill in a certification, the certificate image or PDF is sent to Anthropic to read the certificate’s name and dates.
- Receipt scan. When an officer scans a receipt for a county expense report, the receipt image is sent to Anthropic to read the vendor, date and line items.
- Meeting minutes. The transcript of the monthly business meeting is sent to Anthropic to draft the minutes, which officers then review. The names of current members (so names are spelled correctly) and the attendance recorded at the kiosk for that meeting are sent with it.
- Groq.The audio recording of the monthly business meeting is sent to Groq to turn speech into a transcript. Zero data retention is turned on for the department’s Groq account.
- Modal.Speaker recognition runs on Modal, a cloud computing service. The meeting’s audio recording is sent to Modal, which works out where each voice speaks and returns a voice signature for each speaker; the audio is held only in a temporary working folder for that job. Matching those signatures to members’ stored voiceprints happens in the member portal, and voiceprints are kept there, not on Modal. The bot that records the meeting’s Google Meet call also runs on Modal; it sends the recording, the names shown in the call and the call’s captions to the portal. The portal deletes the audio after 60 days. Voice recognition is on for every member by default; a member who has been given the switch can turn it off on their profile (others can ask the IT Administrator), which deletes their voiceprint at once. A voiceprint is also deleted when the member leaves, or after three years without a confirmed match.
The current version of the member app asks for your permission before Ember or the certificate scan sends anything to Anthropic.
The department uses Anthropic’s commercial API service. Under Anthropic’s commercial terms, Anthropic does not use this data to train its models. Anthropic deletes these inputs and outputs from its own systems within 30 days, unless it must keep them longer to enforce its Usage Policy (up to 2 years for content its safety systems flag). Anthropic and Groq are third parties with their own privacy policies.
Data Security
We use reasonable administrative, technical, and physical safeguards to protect your information, including encryption of data in transit over HTTPS. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Data Retention
We keep personal information only as long as necessary for the purposes described in this policy, to administer membership and department records, and to meet legal or reporting obligations, after which it is deleted or anonymized.
Children’s Privacy
The Site is intended for a general audience 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 provided us information, please contact us and we will delete it.
Your Choices
You may request access to, correction of, or deletion of the personal information you have provided to us by contacting us using the details below. You can also opt out of non-essential communications at any time. Most browsers let you refuse or delete cookies through their settings.
Third-Party Links
The Site may link to third-party websites (such as PayPal or Facebook). We are not responsible for the privacy practices of those sites; please review their policies separately.
Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with a revised effective date.
BVFD Member App (Android and iPhone)
The BVFD Member App, for Android (package org.bumpassfire.bvfd) and for iPhone (bundle ID org.bumpassfire.bvfd), is for current members of the department only. It lets a member sign in with their department Google account and use the member portal on their phone. This section describes what the app does with information. The website sections above still apply to everything else. The Android and iPhone apps work the same way: they use the same BVFD server under the same rules, and everything in this section applies to both unless it says otherwise.
- Sign-in. You sign in with your bumpassfire.org Google account. The app receives a sign-in token from Google and sends it to BVFD; the server verifies that token with Google and confirms you are a current member. Shared department mailboxes and former members cannot sign in. We do not receive or store your Google password.
- Your sign-in session.The server keeps a record of each app sign-in session: which member it is for, the address signed in with, the phone’s maker and device model (for example “Google Pixel 8”, so you and IT can tell your phones apart), and when it was created, last used and ended. The token that keeps you signed in is stored on the server only in scrambled (hashed) form, and a session lasts at most 30 days before you sign in again.
- Information the app shows and stores.Your name, department email address, phone number and home address (your own), your birthday (month and day only; the department does not hold your birth year), your role, and your certifications, hours, releases and gear. The app also handles what you enter or upload: expenses with their receipts, certificate and ID photo uploads, chat messages, duty shift claims and wellness check-in responses. All of it is kept on BVFD’s portal, the same records the website uses.
- What the app stores on your phone.The sign-in session token, kept in the phone’s secure storage (the Android Keystore on Android, the iOS Keychain on iPhone), and your alert sound choices. Documents and photos you open, and files you prepare to upload, are kept in the app’s private cache, which other apps cannot read, until you sign out or clear the app’s storage. Signing out removes them.
- Member portal content. The app shows the same member information the portal shows you, based on your role and permissions.
- Files you upload.Certificates you submit for your training record, expense receipts, and an ID photo for your Digital ID are sent to BVFD’s portal and stored there with the same protections as files uploaded on the website. Officers who review them can see them.
- Chat.Messages you send in group, officers-only or direct chat are stored on BVFD’s portal so members can read them. Chat messages are visible to the people allowed to see that conversation. If a member reports a message, including a direct message, that message is shown to the department’s IT administrators and the Secretary so they can review it. The portal also stores the members you block, the reports you make, and your acceptance of the chat rules.
- Ember Guide.Questions you ask the Ember Guide are sent to Anthropic to produce an answer (see Artificial Intelligence Service Providers above). Your name, role and account are not sent with your question. BVFD does not store your questions or Ember’s answers; it keeps only usage counters that limit how many questions can be asked. The conversation stays in the app until you leave it.
- Push notifications.Only if you turn alerts on, your phone gives the app a push notification token from Google’s Firebase Cloud Messaging (on iPhone, Firebase Cloud Messaging delivers through Apple Push Notification service), and the app sends it to BVFD so the department can send you alerts (urgent department alerts such as an apparatus or hydrant taken out of service, officer alerts, chat and direct messages, announcements). BVFD stores the token hashed and encrypted, never in readable form, with your phone’s alert channel choices, and deletes it when you turn alerts off, sign out, or request account deletion. Google (Firebase) delivers the notifications, so alert text passes through Google to reach your phone, and on iPhone also through Apple.
- No advertising or tracking. The app contains no advertising, no analytics and no crash-reporting software, and does no tracking across other apps or websites. BVFD does not sell information.
- Sharing. Information is shared only with BVFD officers who need it for department business, and with the service providers the portal already uses, listed in the sections above, plus Anthropic (Ember Guide and the certificate scan) and Google Firebase Cloud Messaging, with Apple Push Notification service on iPhone (alerts), as described here.
- Deleting your account. In the app, on Android or iPhone, open More, choose Request account deletion, and send the request, or follow the steps on our account deletion page. As soon as you send the request from the app, you are signed out of the app on every phone, every app sign-in session is ended, and the tokens that let the department send alerts to your phones are deleted. The department’s IT administrator reviews every request and completes it within 30 days, and you receive an email when it is done. Some records must be kept by law or department policy. The account deletion page lists what is deleted and what is kept by law or department policy: your membership record, meeting minutes and attendance records, training and certification records, LOSAP and hours records, financial records of expenses you submitted, and records of equipment and gear issued to you.
Questions about the app and your information: admin@bumpassfire.org.
Contact Us
If you have questions about this Privacy Policy or your information, please contact us:
Bumpass Volunteer Fire DepartmentPO Box 158, Bumpass, VA 23024
96 Fredericks Hall Road, Bumpass, VA 23024
Phone: 540-872-2400
Email: admin@bumpassfire.org
Or use our contact form.