Patrol Forge Privacy Policy

Patrol Forge Privacy Policy Version: 2026-08-03 Last Updated: August 3, 2026 1. Introduction Patrol Forge respects the privacy of companies, administrators, supervisors, dispatchers, officers, employees, contractors, clients, residents, property representatives, tow vendors, support users, permit holders, website visitors, and other authorized users who access or use the Patrol Forge website, web application, Windows desktop application, mobile applications, portals, APIs, app download pages, and related services. This Privacy Policy explains how Patrol Forge collects, uses, stores, protects, discloses, and manages information when users access or use Patrol Forge. Patrol Forge is designed for security operations, patrol management, CAD and dispatch coordination, GPS-enabled officer accountability, reporting, scheduling, time clock, client visibility, parking enforcement, parking permits, parking violation notices, towing workflows, payments, collections, support access, onboarding meetings, vehicle checkout, license and certification tracking, and related business operations. If you use Patrol Forge through your employer, security company, client organization, property manager, HOA, apartment community, association, or another company account, your use may also be governed by that organization's employment policies, client agreements, resident policies, post orders, parking rules, operating procedures, community governing documents, and legal obligations. 2. Important Notice About Company-Controlled Accounts Patrol Forge is primarily a business-to-business software platform. Many users access Patrol Forge through an account created, managed, or controlled by a company, employer, security provider, contractor, client, property manager, association, or organization. If your account is provided by a company, that company may control information associated with your use of Patrol Forge, including your user account, role, rank, assigned properties, assigned shifts, patrol activity, GPS activity while logged in and using the app, CAD status activity, reports, photos, documents, time and attendance records, parking enforcement records, parking permit records, approval history, client-visible records, and audit log activity. Patrol Forge provides the software platform. The company using Patrol Forge is responsible for deciding how the platform is used within its organization, including how employees, contractors, clients, residents, permit holders, and other affected individuals are notified about monitoring, GPS tracking, report requirements, parking enforcement, violation notice processing, towing, payments, collections, disciplinary procedures, and client or property rules. 3. Definitions "Patrol Forge," "we," "our," or "us" means the Patrol Forge software platform, website, web application, Windows desktop application, mobile applications, portals, APIs, and related services. "Platform" means the Patrol Forge website, web application, desktop application, mobile application, software tools, databases, dashboards, portals, APIs, and related services. "User" means any person who accesses or uses Patrol Forge, including company owners, administrators, supervisors, dispatchers, officers, employees, contractors, clients, property managers, residents, permit holders, tow vendors, support users, and authorized representatives. "Company" means a security company, employer, contractor, property management company, HOA, apartment community, association, organization, or business that creates or manages an account through Patrol Forge. "GPS Data" means location information collected through GPS, device location services, IP address, or similar technology while an authorized user is logged in and actively using Patrol Forge or performing a function that requires location verification. "Operational Data" means information submitted, generated, received, or stored in Patrol Forge, including patrol logs, CAD events, dispatch calls, emergency alerts, incident reports, daily activity reports, time records, vehicle checkout records, license and certification records, parking enforcement records, parking permits, violation notices, tow cases, photos, attachments, payments, collections, and audit logs. 4. Scope of This Privacy Policy This Privacy Policy applies to information collected through the Patrol Forge website, web application, Windows desktop application, mobile applications, company admin panels, platform admin panels, officer dashboards, supervisor dashboards, dispatcher tools, PatrolForge CAD, client portals, tow vendor portals, patrol tracking, GPS tracking, checkpoint scanning, NFC and QR features, incident reporting, daily activity reporting, scheduling, time clock, vehicle logs, vehicle checkout, equipment tracking, training records, license and certification uploads, expiration alerts, parking enforcement, registered vehicle management, parking permits, QR permit verification, warnings, parking violation notices, tow review, violation notice payments, disputes, collection notices, collection reporting, agency placement, agency reconciliation, collection packet exports, support tickets, support access codes, onboarding meetings, app download pages, email communications, platform security, and audit logs. This Privacy Policy does not apply to third-party websites, services, or applications that Patrol Forge does not control. Third-party services, including payment processors, mapping providers, email providers, SMS providers, hosting providers, app store providers, and operating system providers, may have their own privacy policies and terms. 5. Information We Collect Patrol Forge may collect several categories of information depending on how the platform is used, what features are enabled, what permissions are granted, what device is used, and what information is entered by companies, administrators, supervisors, dispatchers, officers, clients, residents, tow vendors, permit holders, or other users. Account information may include full name, email address, phone number, username, password credentials, company name, assigned company account, user role, rank, permission level, account status, profile settings, login credentials, security settings, two-factor authentication settings, password reset activity, account creation date, account update history, device identifiers, legal acceptance status, and legal acceptance history. Company information may include company legal name, trade name or DBA, company address, phone number, email address, website, administrators, subscription plan, plan limits, billing status, add-ons, beta plan settings, custom plan terms, plan-specific terms, internal ranks, chain of command structure, permission settings, company policies, report fields, branding information, logo uploads, support access settings, onboarding availability, app download configuration, and client access settings. Client and property information may include client name, client business name, contact information, property name, property address, site contact information, post location, post orders, assigned patrol zones, checkpoint locations, QR code or NFC checkpoint details, site instructions, access notes, service expectations, parking rules, parking locations, authorized vehicles, parking permit locations, resident or unit records when entered by a company, client visibility settings, property health records, issue trends, and approved client reports. Officer and employee information may include name, email address, phone number, employee ID, rank, assigned supervisor, assigned properties, assigned shifts, assigned posts, patrol routes, certifications, training records, license type, license number, license issue date, license expiration date, uploaded license images or documents, equipment assignments, vehicle assignments, availability, time records, attendance records, call-off records, submitted reports, GPS activity while logged in and using the app, uploaded photos or documents, supervisor comments, approval history, parking enforcement actions, CAD status history, emergency alert activity, and audit log history. Security and audit information may include login date and time, logout date and time, failed login attempts, IP address, device information, browser type, operating system, desktop app version, mobile app version, app status check information, session information, password reset activity, two-factor authentication activity, support access code generation and use, role changes, permission changes, report edits, report approvals, report rejections, client visibility changes, deleted or archived records, administrative actions, API requests, route requests, security headers, rate-limit events, and system security events. 6. Patrol, GPS, Checkpoint, Desktop App, and Mobile App Information Patrol activity may include patrol start time, patrol end time, assigned property, assigned officer, patrol route, checkpoint scans, QR code scans, NFC scans if supported, missed checkpoints, completed checkpoints, patrol notes, GPS location attached to patrol events, photos uploaded during patrols, exceptions, supervisor review status, and client visibility status. GPS-related information may include latitude, longitude, accuracy radius, timestamp, officer, patrol identifier, property identifier, checkpoint identifier, route information, speed when available, heading when available, device-generated metadata, location source, IP address, and distance from relevant property or checkpoint. Patrol Forge may collect GPS location information when location services are enabled on the user's device and the user is logged into Patrol Forge, actively using the website, Windows desktop application, Android application, iOS application, or mobile-ready API workflows, starting or completing patrol activity, scanning checkpoints, creating reports, submitting daily activity, reporting maintenance issues, completing inspections, uploading supported photos, responding to dispatch, using CAD status functions, triggering emergency or safety features, verifying parking permits, completing vehicle checkout, or performing another function requiring location verification. Depending on operating system, device, browser, and enabled features, Patrol Forge applications may request access to location services, camera, photo library, file storage, notifications, internet connectivity, NFC reader functionality, QR scanning, device identifiers, and device status information. These permissions are requested to provide platform functionality, security, officer safety, evidence capture, checkpoint scanning, field documentation, app updates, and communication. The Windows desktop application may be used on laptops, desktops, dispatch workstations, supervisor computers, or command center devices. The desktop application may display Patrol Forge through a secure embedded browser or application shell and may communicate with Patrol Forge servers to authenticate users, load authorized pages, check desktop app version status, enforce minimum supported versions, provide download or update links, validate approved Patrol Forge origins, and support desktop-specific security controls. Desktop application information may include desktop app version, operating system information, device name or device identifier when configured, user agent, IP address, session information, route or status check requests, error status, update status, and authentication/session cookies required to keep users signed in. The desktop application does not give Patrol Forge unlimited access to a user's computer. Patrol Forge collects only information reasonably needed to provide the desktop app, authenticate access, protect the platform, support updates, troubleshoot issues, and enforce company permissions. NFC and QR information may include checkpoint identifiers, tag or code identifiers, permit verification identifiers, scan timestamps, scan results, user performing the scan, device information, GPS location associated with the scan, and related patrol, property, parking location, route, post, or permit records. If an authorized NFC writer feature is used, Patrol Forge may write checkpoint or routing data to an NFC tag as directed by an authorized user. GPS information is not collected for advertising purposes. GPS visibility is controlled by role-based permissions and may be visible to company owners, administrators, authorized supervisors, dispatch personnel, authorized managers, authorized client portal users when included in approved reports, and Patrol Forge system administrators only when necessary for support, security, troubleshooting, or legal compliance. 7. CAD, Dispatch, Officer Safety, and Communications Patrol Forge CAD and dispatch features may collect call intake records, call type, priority, call location, caller or requester information when entered, assigned officer or unit, unit status, status timestamps, enroute status, on-scene status, clearing status, custom status history, notes, attachments, incident links, officer messages, dispatcher messages, assignment history, response history, report-needed status, and audit details. Officer safety features may collect emergency alert activity, panic or emergency button events, welfare check requests, readiness check responses, current or last known GPS location, status update history, response acknowledgments, supervisor actions, and related timestamps. These features are intended for safety, accountability, dispatch coordination, and operational review. Messaging and support communications may include message content, sender and recipient, timestamps, attachments, support tickets, ticket replies, department routing, internal support notes, customer-provided screenshots or files, support access code information, quote request messages, onboarding meeting information, and email delivery history. 8. Reports, Photos, Documents, Licenses, and Uploaded Files Report information may include incident reports, daily activity reports, patrol reports, maintenance reports, post check reports, vehicle logs, vehicle checkout inspections, supervisor notes, corrective comments, client-facing reports, internal-only reports, photos, videos if enabled, documents, signatures, witness information, involved persons, event descriptions, dates, times, locations, custom report fields, report print history, and approval history. Uploaded content may include incident photographs, patrol photographs, parking enforcement photographs, violation notice evidence, vehicle photographs, vehicle damage evidence, permit or decal images, resident or vehicle documents when entered by a company, maintenance photographs, site documentation, license or certification images, authorized identification documents, PDFs, forms, supporting evidence, tow case files, dispute evidence, collection packet documents, and other company-approved files. License and certification records may include certification type, license type, license number, issuing authority when entered, issue date, expiration date, renewal information, uploaded license photos or documents, training records, company review status, alert status, and email notification history. Uploaded files may contain metadata including upload date, upload time, file type, file size, GPS location if enabled by the device, user who uploaded the file, device metadata, and associated report, violation notice, tow case, vehicle, permit, license, certification, property, or company record. Companies are responsible for ensuring uploaded files comply with applicable laws and company policies. Companies are responsible for training users on what information should and should not be entered into reports or uploaded into Patrol Forge. Users should avoid entering unnecessary sensitive personal information unless it is required for legitimate security, safety, legal, employment, parking enforcement, collections, licensing, training, or operational purposes. 9. Parking Enforcement, Registered Vehicles, Permits, Violation Notices, Towing, and Collections When parking enforcement features are enabled, Patrol Forge may collect and store parking-related information entered by companies, officers, clients, property managers, residents, permit holders, tow vendors, or authorized users. Registered vehicle information may include resident or owner name, unit number, property, client, contact information, license plate number, state, VIN where entered, vehicle make, model, color, year, body style, category, permit number, decal number, registration status, expiration dates, authorization notes, documents, photos, vehicle history events, and related client or property records. Parking permit information may include permit number, QR verification token, permit status, issue date, expiration date, property, parking location, client, resident or unit information when entered, license plate, vehicle information, permit holder information, printed permit details, verification scan history, revocation status, deletion status, and audit history. Parking enforcement information may include warnings, parking violation notices, tow review actions, violation type, parking rule, notice number, action number, fine or administrative fee amount, due date, issued date and time, issuing officer, property, location description, GPS location, vehicle snapshot, registration snapshot, violation snapshot, prior warning counts, prior notice counts, repeat count history, officer notes, client-visible notes, internal notes, photos, evidence, review status, HOA or client review status, delivery status, PDF notice files, audit trail, timeline events, and client visibility settings. Violation notice payment information may include notice amount, balance due, amount paid, payment status, payment date, receipt information, transaction identifiers, processor response data, refund status, waiver status, waiver reason, payment confirmation status, and limited payment processor details. Patrol Forge does not store complete card numbers, CVV/CVC security codes, or banking credentials. Dispute information may include dispute status, dispute reason, resident or submitter information when entered, dispute notes, evidence files, review decision, reviewer, decision notes, timestamps, and communications related to the dispute. Tow case information may include tow case number, property, vehicle, violation notice or tow review reference, tow company, vendor portal status, tow status, timestamps, files, photos, vendor notifications, vendor responses, status updates, and related audit history. Collection information may include notice aging, reminder notices, collection notices, collection status, promise-to-pay information, hold status, HOA escalation status, external collection status, closeout status, recovery notes, follow-up dates, collection activity logs, collection staff records, exceptions, calendars, status aging, escalations, agency placement records, agency packet exports, agency reconciliation records, remittances, fees, statements, performance data, variance or reconciliation review details, and related reporting exports. Companies are responsible for ensuring parking enforcement, towing, violation notice payments, disputes, collections, agency placement, and resident communications are performed in compliance with applicable law, contracts, property rules, HOA rules, lease requirements, consumer protection laws, debt collection laws, and company policies. 10. Vehicle Checkout, Fleet, and Equipment Information Vehicle and fleet information may include vehicle records, assigned users, checkout and check-in times, mileage, fuel level, dents or damage reports, tire condition, headlight status, taillight status, blinker status, inspection results, good or needs work status, maintenance notes, custom checklist responses, officer comments, supervisor review, photos, documents, service records, and audit history. Equipment information may include equipment inventory, serial numbers, assigned users, checkout status, return status, damage notes, photos, documents, overdue status, and related audit history. Companies are responsible for ensuring vehicle, fleet, and equipment information is accurate and for deciding how inspection results, maintenance needs, and damage records are reviewed or acted upon. 11. Billing and Payment Information Patrol Forge offers subscription-based services and may support violation-notice-related payments. Payments may be processed through third-party payment processors such as Stripe, Authorize.Net, or other configured payment providers. Patrol Forge does not collect or store complete credit card numbers, debit card numbers, CVV/CVC security codes, or banking credentials. Payment processors may collect name, billing address, billing email, payment method, payment card information, transaction information, tax information, fraud prevention information, and payment authorization details. Patrol Forge may receive limited payment information including customer name, billing email, billing address, invoice number, subscription status, payment status, renewal date, refund status, transaction ID, authorization code, card brand, last four digits, payment method type, and processor response messages. Payment processors independently process payment information under their own privacy policies and terms. Users should review the privacy policies of applicable payment processors. 12. App Downloads, Updates, and Version Checks Patrol Forge may provide download links for Windows, Android, and Apple applications. App download pages may display available app links, version numbers, availability status, and release notes or descriptions. The Windows desktop application and related status endpoints may check whether an app version is current, supported, blocked, or requires an update. Version checks may include the app version, IP address, user agent, operating system, request headers, status result, and update/download URL returned by Patrol Forge. Mobile apps, app stores, operating systems, and third-party distribution tools may collect their own download, installation, crash, diagnostic, device, or usage information under their own privacy policies. 13. How We Use Information Patrol Forge uses collected information only for legitimate business purposes necessary to operate, improve, secure, and provide the platform. Information may be used to create user accounts, authenticate users, verify identity, assign permissions, manage chain of command, configure settings, create patrol assignments, verify patrol completion, record checkpoint activity, manage CAD and dispatch, support officer safety, generate reports, manage maintenance records, manage vehicle and equipment records, track officer activity while using Patrol Forge, provide client portal access, process approvals, generate audit logs, detect fraud, monitor performance, diagnose issues, respond to support requests, communicate service updates, process subscription payments, process authorized violation notice payments, support parking enforcement workflows, support parking permit workflows, support disputes, support towing workflows, support collection workflows, support license and certification alerts, support onboarding meetings, enforce terms, comply with law, and protect Patrol Forge, customers, users, clients, residents, property, and the public. Patrol Forge does not sell users' personal information to advertisers or data brokers. Patrol Forge does not use GPS location information for advertising or behavioral marketing. 14. How We Share Information Patrol Forge is a multi-tenant Software-as-a-Service platform that allows companies to manage their own personnel, clients, properties, reports, patrols, parking records, and operational data. Patrol Forge does not sell personal information, GPS information, employee information, customer information, resident information, parking information, or report data to advertisers, data brokers, or marketing companies. When you use Patrol Forge through a company account, information may be accessible to authorized users within your organization based on assigned permissions. Companies are responsible for configuring user permissions and determining which users may access company information. Companies may choose to grant clients access through the Client Portal. Clients may only view information the company has authorized for client visibility, such as approved patrol reports, approved incident reports, daily activity reports, maintenance requests, property activity, patrol completion, officer arrival times, report photographs, attachments, GPS locations associated with approved reports, service history, property notes, parking enforcement records, permit information, violation notice status, dispute status, payment status, and registered vehicle information when authorized. Companies may choose to grant tow vendors access through a tow vendor portal or notify tow vendors through Patrol Forge. Tow vendors may receive tow case details, vehicle information, property information, photos, files, status updates, and related information reasonably necessary to perform tow-related services. Companies may choose to send accounts or violation notice records to outside collection agencies or export collection packets. Collection agencies or authorized recipients may receive information included in agency placement records, collection packets, violation notice records, payment records, resident or vehicle records, notices, supporting evidence, and reconciliation records as directed by the company. Patrol Forge may work with trusted service providers for hosting, data storage, payment processing, email delivery, SMS messaging, push notifications, mapping, geocoding, analytics, support, security monitoring, backups, software updates, error monitoring, and infrastructure management. Service providers receive only information reasonably necessary to perform contracted services. Patrol Forge may disclose information when reasonably necessary to comply with law, respond to lawful orders, subpoenas, warrants, or law enforcement investigations, protect life or safety, investigate fraud or misuse, protect legal rights, protect customers, protect client property, or prevent illegal activity. 15. Company Responsibility for Submitted Information Companies and authorized users are responsible for the information they enter into Patrol Forge. This includes report content, parking enforcement content, permit information, vehicle information, resident or unit information, license and certification records, uploaded files, client visibility choices, payment records, towing records, and collection records. Companies are responsible for entering only true, accurate, authorized, and lawful information into Patrol Forge. Companies are responsible for having appropriate authority from property owners, associations, clients, employers, residents, permit holders, or other applicable parties before entering, using, sharing, enforcing, or collecting on records in the platform. Patrol Forge does not independently verify every report, parking notice, permit, vehicle record, collection record, license record, or uploaded file submitted by companies or users. 16. Data Retention Patrol Forge retains information only as long as reasonably necessary to provide services, comply with legal obligations, resolve disputes, enforce agreements, maintain security, and support legitimate business operations. Retention periods may vary based on company settings, subscription plan, applicable law, regulatory requirements, litigation holds, contractual obligations, collection activity, payment records, and customer requests. Companies generally control retention of incident reports, patrol reports, daily activity reports, vehicle inspections, maintenance reports, post checks, parking enforcement records, parking permit records, registered vehicle records, tow cases, uploaded photographs, attachments, client-visible records, and exports. GPS records may be retained to verify patrols, document service delivery, investigate incidents, support emergency response review, resolve disputes, support internal investigations, support parking enforcement, and comply with legal obligations. Certain records may be retained longer where reasonably necessary for audit trails, payment records, tax records, legal compliance, safety incidents, litigation holds, collections, agency reconciliation, chargebacks, fraud prevention, account security, or enforcement of agreements. When a company account is deleted or scheduled for deletion, Patrol Forge may support retention options such as deletion immediately, deletion after one month, deletion after six months, or deletion after one year. Some information may remain in backups, logs, audit trails, payment processor records, security records, or legal archives for a limited period where necessary for security, legal compliance, fraud prevention, dispute resolution, backup integrity, or enforcement of agreements. 17. Data Security Patrol Forge implements reasonable administrative, technical, and physical safeguards designed to protect information against unauthorized access, alteration, disclosure, or destruction. Security measures may include HTTPS encryption, TLS communications, password hashing, multi-factor authentication, role-based permissions, rank-based permissions, support access codes, session expiration, secure authentication, access logging, audit trails, database security, signed private file URLs, private file storage, file upload validation, CSRF protection, rate limiting, server hardening, firewall protection, intrusion monitoring, malware protection, software updates, encrypted backups where supported, and least-privilege administrative access. No method of electronic storage or transmission is completely secure, so Patrol Forge cannot guarantee absolute security. Users are responsible for protecting passwords, devices, account credentials, support access codes, app sessions, authentication codes, and any exported files. 18. Cookies and Similar Technologies Patrol Forge uses cookies and similar technologies to improve security, functionality, and user experience. Cookies may authenticate users, maintain login sessions, remember preferences, store security tokens, prevent fraudulent activity, improve performance, analyze application usage, load user settings, support accessibility features, support desktop app sessions, and remember device identifiers used for legal acceptance history. 19. Third-Party Services Patrol Forge may integrate with trusted third-party services including payment processors, email providers, cloud hosting providers, SMS providers, push notification providers, mapping providers, geocoding providers, authentication providers, backup providers, app stores, mobile operating system services, desktop runtime providers, error monitoring tools, and customer support platforms. Each third-party service operates under its own privacy policy. 20. Legal Acceptance, Acknowledgments, and Plan-Specific Terms Patrol Forge may require users to accept legal documents, including the Privacy Policy, Terms of Service, Acceptable Use Policy, GPS Acknowledgment, company acknowledgments, and plan-specific terms. Acceptance records may include document title, document version, document body hash, user name, email, role, company, acceptance date and time, IP address, user agent, device identifier, device name, device fingerprint, and acceptance source. Some companies may use beta plans, custom plans, or plan-specific terms. When plan-specific terms are required, Patrol Forge may collect and store acceptance history for those terms. 21. Your Privacy Rights Depending on where you reside, you may have certain legal rights regarding your personal information. Because Patrol Forge is primarily a business-to-business platform, some requests regarding employee, officer, client, resident, permit, parking, or operational data may need to be directed to the company that controls the account rather than Patrol Forge directly. Where applicable, you may have the right to know what personal information is collected, access personal information, correct inaccurate information, request deletion subject to legal and contractual obligations, obtain a portable copy of certain information, restrict or object to certain processing, withdraw consent where processing is based on consent, appeal certain privacy decisions, and file a complaint with an appropriate regulatory authority. 22. California Privacy Rights If you are a California resident, you may have rights under the California Consumer Privacy Act as amended by the California Privacy Rights Act. Subject to applicable law, California residents may have rights to know categories, sources, purposes, third-party sharing, request deletion, request correction, request access, limit certain sensitive personal information where applicable, and receive equal service regardless of exercising privacy rights. Patrol Forge does not sell personal information and does not share personal information for cross-context behavioral advertising. Sensitive information is collected only when reasonably necessary to provide requested services or where entered by customers using the platform. 23. Other State Privacy Laws Residents of certain U.S. states may have additional privacy rights. Where required by applicable law, Patrol Forge will honor valid requests relating to access, correction, deletion, data portability, opt-out rights where applicable, and appeals of denied privacy requests within required timeframes. 24. GDPR and UK GDPR Where GDPR or UK GDPR applies, Patrol Forge processes personal information only when a lawful basis exists, including performance of a contract, compliance with legal obligations, legitimate business interests, protection of vital interests, or user consent where required. Users subject to GDPR may have the right to access personal data, correct inaccurate data, request erasure, restrict processing, object to certain processing, request data portability, withdraw consent where applicable, and lodge a complaint with an appropriate supervisory authority. 25. International Data Transfers Patrol Forge primarily operates within the United States. If information is transferred internationally, Patrol Forge will take reasonable measures designed to protect personal information in accordance with applicable law. 26. Children's Privacy Patrol Forge is intended for business, government, property management, HOA, association, and professional use. Patrol Forge is not directed toward children under the age of 13 and does not knowingly collect personal information from children under 13. Companies should not use Patrol Forge to collect information from children except where legally permitted and necessary for legitimate safety, security, property, legal, or operational purposes. 27. Law Enforcement and Government Requests Patrol Forge may receive requests from law enforcement agencies, regulatory authorities, courts, or other governmental entities. Patrol Forge reviews requests before disclosing information and will disclose information only when required by applicable law, court order, subpoena, warrant, life or safety concerns, criminal activity investigation, legal rights protection, or other authorization by applicable law. 28. Data Breach Notification Patrol Forge maintains incident response procedures designed to identify, investigate, contain, and remediate security incidents. If Patrol Forge determines that a security incident involving personal information requires notification under applicable law, affected customers will be notified within the timeframe required by applicable law. 29. Changes to This Privacy Policy Patrol Forge may update this Privacy Policy from time to time to reflect changes in applicable law, platform functionality, desktop or mobile applications, security practices, business operations, third-party services, or customer feedback. When material changes are made, Patrol Forge will update the version and Last Updated date. Users may be required to accept the updated policy before continuing to use the platform. 30. Contact Information Questions regarding this Privacy Policy or privacy practices may be directed to Patrol Forge at privacy@patrolforge.com or 505-219-1987. For payment-related questions, users may also review the privacy policy of the applicable payment processor. 31. Governing Law This Privacy Policy shall be governed by and interpreted in accordance with the laws of the State of New Mexico, without regard to conflict of law principles, except where applicable federal or international law requires otherwise. 32. Severability If any provision of this Privacy Policy is determined to be unlawful, invalid, or unenforceable, the remaining provisions shall remain in full force and effect. 33. Entire Agreement This Privacy Policy, together with the Patrol Forge Terms of Service, Acceptable Use Policy, GPS Acknowledgment, company acknowledgments, plan-specific terms, and any other policies or agreements expressly incorporated by reference, constitutes the entire agreement regarding the collection, use, disclosure, and protection of information through Patrol Forge. 34. Contact for Privacy Requests Individuals wishing to exercise privacy rights or submit privacy-related questions may contact Patrol Forge using the contact information listed above. Privacy requests should include sufficient information to verify identity and allow Patrol Forge or the applicable company administrator to process the request. 35. Acknowledgment By accessing or using Patrol Forge, you acknowledge that you have read, understood, and agree to this Privacy Policy. If you do not agree with this Privacy Policy, you should discontinue use of Patrol Forge and notify your company administrator if your access is provided through an employer, property, client, or organization. Mailing address: Patrol Forge LLC P.O. Box 20431 Albuquerque, NM 87154