Legal
This Privacy Policy describes how QuietLeverage LLC, doing business as PatrolDocs ("PatrolDocs," "we," "us"), handles data in connection with the PatrolDocs platform.
It addresses both agencies and officers who use PatrolDocs to manage and deliver documents and members of the public who receive a document or resource through PatrolDocs.
This Privacy Policy describes how QuietLeverage LLC, doing business as PatrolDocs ("PatrolDocs," "we," "us"), a Nevada limited liability company located at 2746 Gordon Avenue, Minden, NV 89423, handles data in connection with the PatrolDocs platform.
This policy addresses both, since the data footprint and controls are different for each.
By design, not policy alone, PatrolDocs has no database field for victim or witness names, incident narratives or case notes, defendant names, or evidence of any kind. If you're evaluating this policy against a records-management or CJIS standard, start here: PatrolDocs is not that kind of system and does not hold that kind of content.
Separately, an Agency may choose to attach a short case or kit reference number to a delivery. That is an optional identifier the Agency configures. PatrolDocs does not store the underlying report, narrative, evidence, or investigative record associated with that identifier — see Section 4 for what it is and isn't.
From Officers/Agency personnel: name, badge number, rank, and agency-issued contact information, used to operate their account. This is standard account/roster information, comparable to what any business software holding named user accounts collects — not case or investigative data.
From Recipients, at the moment of delivery:
PATROLj***@example.com). The full address is also necessarily processed by our email delivery vendor, Resend, to transmit the message.Engagement data: if a Recipient opens a delivered link or interacts with a resource, we log that event. This event is tied to the specific delivery it belongs to, not to a stored name, phone number, or email. We describe this as pseudonymous and scoped to the delivery — it is not anonymous in the strict sense, because the event can still be traced back to the delivery it belongs to. Engagement events are retained on the same schedule as the delivery record they belong to and are deleted when that record is purged, not retained separately or indefinitely.
Delivery and engagement records let an Agency track the status of a legally-required notice through the delivery process, and let PatrolDocs operate and support the Service. We do not sell data, and we do not use Recipient contact information for any purpose other than completing the delivery it was collected for.
What a delivery record can and can't tell you. A delivery record reflects a series of system-level events: the document was selected and a delivery was created, a message transmission was initiated to the recipient's phone/email or a QR code was generated, the delivery provider (Twilio or Resend) accepted the message for transmission, and — if the recipient later opens the link — that the recipient's page was accessed and which resources on it were viewed. Each of these is a distinct, separately-timestamped event, and the system does not claim more than what it actually observed at each stage.
In particular, a successful message transmission confirms the message reached the recipient's phone/email provider; it does not, by itself, confirm a person read, understood, or acted on it. Whether the recipient's page was later accessed is tracked separately and is the closest available signal that a human interacted with the delivery.
These vendors process data only as necessary to provide their specific function (message delivery, hosting, rate limiting) and do not have independent access to use PatrolDocs data for their own purposes. Once a message is handed to Twilio or Resend for delivery, that vendor's own processing and retention of the message content and recipient contact information is governed by that vendor's own privacy policy and data processing terms, not by PatrolDocs directly.
Access controls (row-level, per-Agency and per-role), audit logging for administrative mutations such as document changes, account changes, Agency lifecycle actions, and permission changes, encrypted data in transit, and security headers are in place. Simply viewing a record without changing it does not currently generate a separate log entry. Multi-factor authentication is required for Agency Admin and Records Supervisor accounts — roles with agency-wide visibility — and for PatrolDocs' own Platform Administrator account, used to operate the Service across agencies, under this same standard. Verified sessions expire after 16 hours and require re-verification. Full detail is available in our Security documentation for Agency procurement contacts on request.
Officers may request deletion of their own account information at any time through the app; this scrubs personal identifying fields from their account while preserving Agency delivery records, which belong to the Agency, not the individual Officer. Recipients who wish to inquire about a delivery record involving them should contact the Agency that made the delivery, since PatrolDocs acts as the Agency's processor for this data, not as an independent controller of it.
PatrolDocs is not directed at children and is not knowingly used to collect information from children. Given that Recipients may occasionally be minors, for example in some victim-notice contexts, we apply the same data-minimization approach described in this policy.
We may update this Privacy Policy from time to time. Material changes will be communicated to the Agency's designated administrative contact.
QuietLeverage LLC d/b/a PatrolDocs
2746 Gordon Avenue, Minden, NV 89423
legal@patroldocs.com
775-600-0453