Patrol Forge Law Enforcement / Government Request Policy

Patrol Forge Law Enforcement / Government Request Policy Version: 2026-08-18 Last Updated: August 18, 2026 1. Purpose of This Policy This Law Enforcement / Government Request Policy explains how Patrol Forge LLC ("Patrol Forge," "we," "us," or "our") receives, reviews, responds to, and documents requests for information from law enforcement agencies, government agencies, courts, regulators, administrative agencies, public authorities, and similar government bodies. This policy is intended to protect customer data, user privacy, company-controlled operational records, and the integrity of the Patrol Forge platform while allowing Patrol Forge to comply with valid legal obligations. This policy does not create a private right of action, does not waive any rights, objections, privileges, immunities, or defenses available to Patrol Forge or its customers, and does not limit Patrol Forge's ability to respond as required or permitted by applicable law. 2. Scope This policy applies to requests seeking access to, preservation of, disclosure of, or restriction on data associated with Patrol Forge, including: - Account registration information. - Company account information. - User profile and login information. - Security and audit logs. - Device, session, browser, desktop app, mobile app, IP address, and access records. - Patrol, dispatch, CAD, GPS, time clock, reporting, citation, parking enforcement, permit, vehicle, client, property, equipment, support, billing, and operational records. - Uploaded files, images, documents, licenses, certifications, vehicle checkout files, incident report attachments, permit materials, citation or parking notice materials, and related metadata. - Communications sent through Patrol Forge, including support requests, dispatch messages, report text, client portal communications, onboarding requests, and notification records. - Data deletion, privacy, legal acceptance, and agreement acceptance records. 3. Customer-Controlled Records Patrol Forge is a software platform used by customer companies to manage their own operations. Many records stored in Patrol Forge are created, uploaded, controlled, configured, or maintained by customer companies, their employees, officers, administrators, clients, or authorized users. When a request seeks customer-controlled records, Patrol Forge may require the requesting agency to direct the request to the customer company, property owner, association, employer, contracting agency, or other record owner when appropriate. Patrol Forge may also notify the affected customer company unless prohibited by law, court order, or other valid legal restriction. Patrol Forge does not independently verify the truth, completeness, or legal sufficiency of every customer-created operational record. Customers are responsible for ensuring that the data they enter into Patrol Forge is accurate, lawful, authorized, and appropriate for their use of the platform. 4. Required Legal Process Patrol Forge generally requires valid and properly served legal process before disclosing non-public information. Depending on the type of information requested and applicable law, this may include: - A subpoena. - A court order. - A search warrant. - A preservation request. - A regulatory demand. - A civil investigative demand. - A national security request or other request authorized by law. - A written emergency disclosure request where applicable law permits emergency disclosure. Patrol Forge may reject, challenge, narrow, or request clarification for requests that are informal, overbroad, vague, legally insufficient, improperly served, directed to the wrong entity, missing required identifying information, seeking data outside Patrol Forge's possession or control, or inconsistent with applicable law. 5. Required Request Information To help Patrol Forge identify and evaluate a request, agencies should include as much of the following as possible: - The requesting agency's name. - The officer, agent, investigator, or official's name, title, badge number or employee number if applicable, phone number, and official email address. - The legal authority supporting the request. - A copy of the subpoena, warrant, court order, preservation letter, emergency request, or other legal process. - The case number, court name, docket number, or investigation reference. - The specific account, company, user, email address, phone number, incident number, citation or notice number, permit number, vehicle plate, property, client, date range, or other identifier connected to the request. - The specific categories of data requested. - The time period covered by the request. - Any nondisclosure, sealing, delayed notice, gag, or confidentiality order. - The deadline for response. - Whether the request involves an emergency involving danger of death or serious physical injury. Patrol Forge may be unable to locate responsive information if the request does not provide enough detail. 6. Where to Send Requests Government and law enforcement requests should be sent to Patrol Forge through the official contact methods listed on Patrol Forge's website, through any dedicated legal request channel Patrol Forge publishes, or by service on Patrol Forge's registered agent. Patrol Forge's registered agent information is: Registered Agents Inc. 1209 Mountain Road Pl NE STE R Albuquerque, NM 87110 Requests sent to the registered agent should clearly identify Patrol Forge LLC, include the requesting agency's contact information, include a copy of the legal process or request, and include enough information for Patrol Forge to identify the account, company, user, record, date range, or data category involved. Requests should not be sent to unrelated support, sales, employee, or customer company contacts unless Patrol Forge has expressly designated that contact for legal requests. Sending a request to the wrong contact may delay review. Publication of registered agent information does not waive any objection, defense, privilege, requirement for valid legal process, requirement for proper service, customer notice right, jurisdictional objection, or other right available to Patrol Forge, its customers, or its users. 7. Preservation Requests Patrol Forge may preserve identified records when it receives a valid preservation request from law enforcement or another authorized government body. A preservation request does not by itself authorize disclosure of preserved content or records. Disclosure generally requires valid legal process or another lawful basis. Patrol Forge may preserve only records that can be reasonably identified from the information provided. Preservation is subject to technical limits, account state, retention settings, backup practices, system architecture, deletion workflows, and applicable law. 8. Emergency Requests Patrol Forge may voluntarily disclose limited information when we have a good-faith belief that an emergency involving danger of death or serious physical injury requires disclosure without delay and applicable law permits the disclosure. Emergency requests should clearly state: - The nature of the emergency. - The person or persons believed to be at risk. - The specific danger of death or serious physical injury. - The information requested. - Why the requested information is necessary to address the emergency. - Why ordinary legal process cannot be obtained in time. - The requesting official's identity and contact information. Patrol Forge may limit emergency disclosures to the information we believe is necessary to address the emergency. Patrol Forge may later require formal legal process for additional records. 9. Notice to Customers or Users Patrol Forge may notify affected customer companies, account owners, users, or other parties about a government request unless prohibited by law, court order, nondisclosure order, delayed notice order, emergency circumstances, risk of harm, or other valid restriction. If a request includes a nondisclosure or delayed notice order, Patrol Forge may comply with that restriction for the period required by law. Patrol Forge may seek clarification or challenge a nondisclosure restriction when appropriate. 10. Narrowing Requests Patrol Forge reviews requests to determine whether they are specific, legally valid, and appropriately limited. Patrol Forge may seek to narrow a request when it appears to seek more information than necessary or when the request covers unrelated companies, users, dates, features, or records. Examples of narrowing may include limiting a request by: - Company. - User. - Property. - Client. - Incident number. - CAD call number. - Parking notice or permit number. - Vehicle plate or VIN. - Date range. - Data category. - Specific uploaded file or record type. 11. Content and Non-Content Information Different laws and legal standards may apply to different categories of data. Account information, logs, metadata, subscriber records, non-content records, communications content, uploaded files, photos, GPS records, operational notes, reports, and attachments may require different types of legal process. Patrol Forge will evaluate the requested data category and the provided legal process before disclosure. Patrol Forge may require higher legal process for sensitive or content-related records where required or appropriate. 12. Data Minimization Patrol Forge aims to disclose only the information reasonably required by a valid request. When possible, Patrol Forge may redact, withhold, limit, or segregate information that is not responsive, belongs to an unrelated company or user, is outside the date range, or is otherwise protected. 13. Authentication of Requesting Officials Patrol Forge may take steps to verify the identity and authority of a requesting official before preserving or disclosing information. This may include contacting the agency through official contact information, requesting a government email address, verifying a court filing, confirming a badge or employee number, or requiring additional documentation. 14. Requests From Non-U.S. Authorities Patrol Forge is based in the United States. Requests from authorities outside the United States may need to proceed through appropriate legal channels, such as mutual legal assistance procedures, letters rogatory, treaties, court orders, or other lawful mechanisms. Patrol Forge may decline or require additional process for non-U.S. requests when the request conflicts with U.S. law, customer rights, privacy obligations, contractual commitments, or platform security. 15. Civil and Private Party Requests This policy is focused on law enforcement and government requests. Civil subpoenas, private party subpoenas, discovery requests, insurance requests, attorney requests, private investigator requests, and similar non-government requests may be handled under separate procedures. Patrol Forge may require notice to affected customers or users, valid service, a court order, customer authorization, or other appropriate process before responding to civil or private party requests. 16. Customer Authorization and Consent Patrol Forge may disclose information when an authorized customer, account administrator, user, or data subject gives valid written consent and Patrol Forge is able to verify that consent. Patrol Forge may still refuse or narrow a request if disclosure would violate law, another person's rights, confidentiality obligations, platform security, or customer-controlled data restrictions. 17. Child Safety, Threats, Fraud, Abuse, and Platform Security Patrol Forge may preserve, investigate, report, or disclose information when required or permitted by law to protect the platform, prevent fraud or abuse, respond to security incidents, protect rights or property, report child exploitation, prevent imminent harm, or comply with applicable reporting obligations. 18. Cost Reimbursement Patrol Forge may seek reimbursement for costs associated with responding to legal process where permitted by law. This may include costs related to search, retrieval, review, export, redaction, certification, storage, or delivery of records. 19. Internal Logging and Audit Records Patrol Forge may keep internal records of government requests and our responses, including request dates, requesting agency information, legal process type, affected accounts, data categories, review notes, response dates, disclosures made, objections raised, and personnel involved. These internal records help Patrol Forge maintain accountability, security, compliance, and auditability. 20. Transparency Patrol Forge may publish or internally maintain summary information about government requests, unless prohibited by law or operational security needs. Any public transparency reporting may be aggregated and may omit details that identify customers, users, investigations, or sensitive operational matters. 21. No Backdoor Access Patrol Forge does not provide government agencies with self-service backdoor access to customer accounts, user accounts, databases, source systems, administrative panels, or production infrastructure. Requests are reviewed and processed through controlled procedures. 22. Security of Production Systems Patrol Forge will not install monitoring tools, change code, weaken security controls, bypass authentication, disclose credentials, disable audit logging, or otherwise compromise the security of the Patrol Forge platform unless legally compelled and reviewed under appropriate procedures. 23. Conflicts With Customer Contracts or Privacy Rights If a request conflicts with customer agreements, privacy obligations, confidentiality duties, data processing commitments, or legal rights, Patrol Forge may notify the requesting agency, seek clarification, notify the customer when allowed, object to the request, or require additional legal process. 24. Changes to This Policy Patrol Forge may update this policy from time to time. The version and last updated date shown above identify the current policy. Material changes may be reflected in the Patrol Forge Legal Center or Super Admin legal policy editor. 25. Contact Questions about this policy or government requests may be directed to Patrol Forge through the contact methods listed on the Patrol Forge website. For emergencies involving danger of death or serious physical injury, agencies should clearly mark the request as an emergency and provide direct return contact information for the responsible official.