Lost and Found Descriptions That Protect Private Details

The AZET team represents AZET, the operator of azet.io. This illustrative guide is for reference and creative exploration, not a demonstrated AZET feature; every object, notice, and claimant scenario below is hypothetical.

As of 2026-10-12

A notice says, “Found: green umbrella with a wooden handle.” Its private note says, “Small stitched patch inside the canopy.” Publishing both sentences makes the umbrella easier to recognize, but also tells every reader the detail you intended to ask about later.

We would draft the public notice and the private comparison note separately. The goal is a useful description with a deliberate information boundary. This article offers writing guidance, without claiming to track objects, establish legal ownership, or make a claim decision for the person holding an item.

Start with what each audience needs

A passerby needs enough information to decide whether the notice might concern their object. The person handling a claim needs a few details that were not handed to every reader.

For the hypothetical umbrella, public details can include its broad color, object type, a general finding area, and a route to contact the desk holding it. Private details can include a distinctive repair and a feature of the handle.

Keep the real comparison note outside an AI drafting prompt. You can use placeholders such as “[withheld identifying detail]” when asking for wording. Once you include a detail in drafting material, you need to inspect every returned version for accidental disclosure.

A hypothetical two-part artifact

The following fictional material demonstrates the boundary. Its identifiers are invented for this example and should not be reused as real verification questions.

Public notice draft:

Found: a green umbrella near the reading room entrance on Monday afternoon. It is being held at the community desk. If you think it is yours, contact the desk privately and describe its handle and any distinctive marks. Reference: umbrella notice A.

Private comparison note:

Hypothetical item record: umbrella notice A
Broad public description: green umbrella, reading room entrance.
Withheld comparison detail: stitched patch inside the canopy.
Additional observation: a small notch near the handle's end.
Claim status: no claim assessed.
Publication check: do not expose the patch or notch in an image.

This is an example of separation, not a script for deciding ownership. Someone may remember the object differently, overlook a mark, or know details because they saw it before. A matching answer alone is not conclusive.

Write the missing-object version differently

If you lost the umbrella, the notice has a different job: helping a finder connect the object with your request. A hypothetical draft could read: “Missing: a green umbrella, last remembered near the reading room entrance on Monday afternoon. Please contact the community desk if one has been handed in.”

“Last remembered” preserves uncertainty about the location. Do not convert it into “lost at” merely because that sounds more decisive. Keep uncertain times broad too.

Retain your distinctive details privately so you can describe them if a possible match appears. There is usually no writing benefit in adding a home address, a daily travel pattern, or unrelated information about the person who lost the object.

Use a prompt with a narrow input set

For the hypothetical found-object notice, try:

Draft a short public notice using only these approved details: green umbrella; near reading room entrance; Monday afternoon; contact community desk privately; reference umbrella notice A. Ask possible owners to describe distinctive details in their own words. Do not invent identifying marks, contact details, an exact time, or a collection arrangement. Keep any missing contact route as a placeholder for human review.

The important step happens before the prompt: selecting the approved details. A request to “protect privacy” cannot replace that editorial choice.

For a real notice, supply an appropriate contact route before publication. A polished draft with an unresolved placeholder is still a draft.

Check the photo as carefully as the words

The common failure is a restrained caption attached to an overly revealing image. A photo may show the very patch reserved for private comparison. It may also expose a name tag, an address, a key, or another person's belongings in the background.

Review the exact final image and caption together. Remove or cover unnecessary details before sharing. If the object is already recognizable from the words, consider whether the image adds enough to justify using it.

A second failure is feeding back the expected answer. In the hypothetical claim exchange, “Does yours have a stitched patch inside?” gives the claimant a simple yes. “Describe any marks you remember” leaves room for their own account.

Leave a clear status after the exchange

Keep a small private status note: awaiting description, possible match, needs further comparison, or handed over. Record only the information needed to handle the item. Avoid retaining a long personal conversation as the object record.

If a handover happens, update the public notice to say the item is no longer available for claims. Do not publish the recipient's name or their private description to demonstrate that the notice worked.

FAQ

How specific should a public location be?

Use enough detail for recognition without exposing someone's routine or private address. A shared reception area may be sufficient; the appropriate level depends on the actual setting.

Should the private note contain photographs?

Only if they are useful for comparing the object and can remain appropriately restricted. A text note may be enough. Check who can access whatever record you choose.

What if two people provide plausible descriptions?

Keep the status unresolved while a person reviews the competing information. This writing method does not establish ownership, and a confident generated answer does not settle the question.

Our October 3 introduction described an email waitlist for the AI assistant. Visit azet.io for the waitlist and current notices about that project. We have not established October 12 availability through this guide.