What limited profile visibility means.

With limited visibility enabled, the ordinary agency interface generally displays a name while withholding email address and telephone information. Without it, authorized personnel with access to the relevant interaction may be able to see those contact details.

The actual interface and disclosures presented when you use a feature matter.

A tip can identify its author through its words, attachments, location, or other context. The setting does not stop Detailr and its providers from processing information to operate the service, and does not retract details already disclosed.

The policies describe preservation and disclosure when directed by the user, required or permitted by law, or necessary in specified serious emergency circumstances. Where legally permitted, disclosure may occur without notice.

Before sending information, review the recipient, the content, any attached location, and your settings. If you need an anonymous channel, use a service expressly described as anonymous for that specific purpose and understand its stated limits.

A person can be identified in more than one way. A profile name is one route; a face, a recognizable building, a phone number visible in an image or a precise account of a private event may be another. Changing routine visibility for email or telephone details does not remove those clues from the substance of a tip.

Before submitting, look at the account details and the contribution together. Ask what you intend the recipient to learn, what is unnecessary and whether an attachment includes someone else’s private information. Use the specific policy description rather than assuming that a privacy toggle means the same thing across different services.

Imagine a resident who limits routine agency visibility of an email address and telephone number, then submits a photograph containing a vehicle registration document. The setting and the photograph do different things. The account fields may be limited while the attachment still contains identifying material. This example illustrates a distinction; it is not an actual submission or a product screenshot.

The published policy also describes legal and safety circumstances affecting disclosure. Review those clauses, along with the receiving agency’s role, before relying on a preference for a sensitive situation. Contact the team if the available interface or policy leaves a material question unanswered.

Consider a fictional tip about an item outside a building. Even if some account fields have limited routine visibility, the photo might include a house number and the written account might identify the contributor as the only person present at a particular time.

That is why the content deserves its own review. Ask what someone could learn from the image, the place, the time and the account together. A profile preference does not automatically remove details from those materials.

The setting can still be worth understanding. The important point is to rely on the specific protection described in the policy, rather than treating a narrower interface choice as a guarantee about every way a person could be identified.

Source: Lucas Privacy Policy, effective September 14, 2026

Which account fields are affected in ordinary agency access? Who receives the tip’s text and attachments? What exceptions can apply for law, safety or service operation? Can the receiving agency keep the delivered account after a user changes a setting?

Those questions distinguish routine visibility from confidentiality, anonymity and retention. A service using one of those words should explain its scope. If an answer is important to whether you send information, resolve it through the policy or the provider before submission.

The separate guide on anonymous and confidential tips explores the terminology across reporting services. It does not turn Lucas into an anonymous reporting channel, and it does not promise how another service will handle a particular report.

A helpful support question names the decision: “I want to understand which account fields the selected agency can routinely see when I send a tip.” That is more precise than asking whether the whole app is private. You can seek that explanation without attaching the sensitive material you are considering sharing.

Source: Lucas Privacy Policy, effective September 14, 2026

A harmless-looking attachment can become identifying when it is combined with a detailed account. A later submission can reveal information that was absent from the first. Review the current contents each time rather than relying on a setting chosen months earlier.

If you want to change your account or ask about deletion, use the published support and privacy contact. A change to the service account and a request concerning an agency-held record may follow different processes. Explain which information and which organization your question concerns.

This page is a plain-language explanation of selected points. The complete Privacy Policy and Terms of Service remain the controlling consumer documents. Read them before relying on a brief description of a setting.

Source: Lucas Privacy Policy, effective September 14, 2026 · Lucas Terms of Service, effective September 14, 2026