The selected agency is a recipient
A submitted tip may contain its text, attachments, time, location, account information, and other metadata the feature permits. The department selected for the submission receives the relevant information.
The agency handles its copy independently
An agency may keep information, assess it with other records, and lawfully share it with other agencies or officials. It may become an investigative, evidentiary, administrative, or public record.
The relevant laws and agency procedures can affect access, retention, disclosure, and responses to requests.
Account deletion does not recall delivery
Deleting a Lucas account does not retrieve or erase information already delivered to an agency. Detailr may also retain information where a legal or safety basis applies, as described in the published policies.
Direct a request to the right organization
The privacy policy explains requests to Detailr. Questions about an agency-held copy may need to be directed to that agency through its own records or privacy process.
Delivery changes the information relationship
Before a submission, the resident is choosing what to provide. After a receiving agency has a copy, that organization has its own responsibilities for handling it. The product’s account controls and the agency’s recordkeeping process are related systems, not a single undo button.
This matters when deciding what to send. A contribution should be relevant, factual and limited to the information appropriate for the request. A later correction can help clarify an account, but it should not be assumed to erase the original or every copy already made. Refer to the published policies for the precise service terms.
Questions worth asking before an evaluation
A department can make the relationship easier to understand by deciding how it will explain records to residents. Who receives questions about a delivered tip? How should a correction be identified? What existing agency process applies to disclosure or retention questions? Which product support issues belong with Detailr Corp instead?
These are operating questions to settle alongside the technical workflow. They help keep public-facing explanations aligned with actual responsibilities. This page does not prescribe a records schedule or interpret the law for a particular agency; those decisions need the agency’s authorized review and applicable requirements.
Two copies can mean two responsibilities
A user account belongs to the consumer-service relationship with Detailr. A submitted tip can also become a record held by the receiving agency. Those copies may have different purposes, access arrangements and retention obligations.
That distinction explains why an account-deletion request cannot be treated as a recall. The agency may already have used or retained its delivered copy. Ask the organization holding the relevant information about its process rather than assuming one action changes every copy everywhere.
The consumer Privacy Policy explains the service’s handling and the agency-recipient distinction. It does not establish the retention period, public-records treatment or disclosure rules of every agency that might participate.
Prepare a precise records question
Identify the submission or approximate date, the recipient and the kind of request you are making. A question about an app account is different from a request to correct information in an agency-held record. Keep sensitive details out of an initial general inquiry when they are not needed.
The receiving agency can direct you to its current records contact and procedures. Applicable rights, exemptions and duties depend on the organization and circumstances. This website cannot decide whether a particular record must be released, deleted or withheld.
If your question concerns Detailr’s service account or consumer policy, use the published privacy contact. If it concerns what an agency did with a delivered tip, begin with that agency’s official process. The two questions can exist at the same time.
For departments assessing the workflow
Review how records move from the product into your agency’s operating process. Ask what staff can access, how a submission is associated with a case and what happens during a permitted handoff. Inspect the current implementation and document any uncertainty.
Discuss who owns decisions about retention, sharing, access requests and evidence handling. General governance guidance can help frame those questions, but it does not prove that the product implements a particular control or meets a certification.
Before residents are invited to use a new channel, align the public explanation with the agency’s actual practices. A clear recipient and a realistic account of record handling are part of an understandable reporting experience.
Source: NIJ-sponsored technology adoption and implementation guide
Sources and further reading
- Lucas Privacy Policy — effective September 14, 2026
- Lucas Terms of Service — effective September 14, 2026
- NIJ-sponsored technology adoption and implementation guide
- Lucas Privacy Policy, effective September 14, 2026
Page reviewed October 27, 2026. External guidance explains the stated topic; it does not establish a product outcome or endorsement.

