Lost-and-found returns and guest data exposure research visual

Lost and Found

Published

Lost-and-found returns and guest data exposure

A measurement protocol for lost-item returns that counts delivery success and the personal data retained at each step of the return.

A return is complete when the item reaches the guest and the personal data collected to send it has been removed from the active record.

Methodology

  1. The unit of analysis is one lost item attached to one stay and one property. An item enters the population when a staff member logs it during or after a turnover. Items found before a guest arrives and never claimed are excluded from the return stream and counted as unclaimed. Each case carries the property, the find date, the item class, the guest contact channel, and the return method.
  2. Item class is recorded as personal effect, document, medication, electronics, child item, or other. The class matters because a passport or a medication needs a different handling path from a charger. The reviewer records the class before contacting the guest. A case that changes class after inspection is recorded under the corrected class with a note.
  3. The first contact time is the moment the property messages the guest about the item, and the response time is the guest’s first reply. The reviewer records both because a return can stall on either side. A guest who never replies is not a failed return; it is an unclaimed item after the policy window. The report separates no response from a declined return.
  4. The personal fields collected are listed for each case: name, address, phone number, email, identification, and any photo of the item. The reviewer marks each field as necessary, optional, or unnecessary for the chosen return method. An unnecessary field is one that was not needed to deliver the item or meet a carrier requirement. The list is reviewed without retaining the values in the study file.
  5. Delivery is scored as confirmed, in transit, failed, or not attempted. Confirmed means the carrier record or the guest confirms receipt. In transit means the item left the property but delivery is not yet confirmed. Failed means the carrier returned or lost the item. Not attempted covers a guest who declined or never responded within the window.
  6. Retention is checked thirty days after delivery or disposal. The reviewer records whether the address, phone number, and item photo are still present in the active record. A field that remains because the property has no deletion step is marked as retained by default. The report does not treat a locked folder as deletion unless the record is actually removed.
  7. Sampling uses every logged item in the window when fewer than forty cases exist. Above that volume, the frame uses a fixed interval across properties and item classes, stratified by whether the guest responded. The frame is frozen before the first message is read. An item is replaced only when the log is missing, and the replacement is recorded with the reason.
  8. Two reviewers code the first fifteen cases independently and compare the item class, the fields collected, the delivery state, and the retention state. Disagreements are resolved by the operations lead, who records the rule that settles the case. Reliability is reported as the share of matching fields. Guest identities are replaced with study identifiers before coding.
  9. The guest’s consent to the return is recorded before any address is collected. Consent includes the chosen method, the carrier, and the expected timing. A guest who asks the property to hold the item for a local pickup has not consented to a shipment. The reviewer marks a case as over-collected when an address was taken before the guest agreed to the delivery, even if the guest later accepted it.
  10. The item’s storage location and access are checked at the close because an unclaimed item can remain in a closet long after the case is marked complete. The reviewer records the shelf or safe, the person who holds access, and the disposal date. An item with no storage record is treated as lost within the property. The protocol counts storage as part of the return record rather than an informal habit.
  11. A return that is handed to a third party, such as a cleaner or a local cohost, is recorded with the person who takes custody and the time of the handoff. The reviewer notes whether the guest was told about the third party and whether the item was tracked after the handoff. An untracked handoff is marked as an open custody gap. The protocol treats custody as part of delivery, not as an internal detail.
  12. The report states the number of items, properties, returns, and unresolved cases in the window. It also states the share of cases with a confirmed delivery and the share of records that still held personal data after thirty days. Those conditions limit how far the result travels, and the note says so before offering a recommendation. No local rate is presented as a standard for the wider market.

Findings

  • Most returns are completed within a week when the guest responds on the first contact. The delay comes from a missing reply, not from the carrier. The reviewed cases show that a second contact through the booking channel improves the response rate. The protocol reports the contact channel so the team can see which one works.
  • Coordinators often collect a full address before the guest has agreed to the return. The address then sits in the inbox even when the guest declines or the item is never sent. The reviewer marks the field as unnecessary when it was collected before consent. A short consent question before the address would remove the most common retention risk.
  • Medication and documents are handled more carefully than chargers and clothing, but the difference is mostly informal. The reviewed cases show a safer handoff when a manager reviews the item, not when the class is simply labeled sensitive. The protocol recommends a manager check for the sensitive classes. A label without a review step does not change the handling.
  • Carrier tracking is the strongest predictor of a confirmed delivery. Cases with a tracking number are confirmed more often than cases sent through an untracked method. The association may also reflect the value of the item, because valuable items are more likely to be shipped with tracking. The report still recommends one tracked method for every return.
  • Addresses remain in the active record after delivery in most of the reviewed cases. The team does not have a deletion step, so the field stays until someone cleans the inbox. The reviewer marks the field as retained by default rather than as a deliberate decision. A deletion reminder at the close step would remove the data without extra work.
  • Guests rarely object to providing an address when the message explains why it is needed and how long it will be kept. The reviewed cases with a clear explanation produced fewer follow-up questions. The protocol records the explanation as part of the contact quality. A short privacy note is more useful than a long policy link.
  • The clearest operational repair is a single item log with a close state. Properties that used the log returned more items and retained less data than properties that tracked returns in chat threads. The local sample cannot establish causation, so the result is a hypothesis for the next cycle. A second window after the next busy season is required before the rule is treated as settled.
  • Unclaimed items are a hidden cost. The reviewed properties kept items in closets for months because no one owned the disposal decision. The reviewer records the age of unclaimed items at the end of the window. A written holding period and a disposal owner would free the space and reduce the data risk.
  • Lost items are more common in units with a high turnover of short stays, especially when the checkout message does not include a reminder. The pattern is not proof that the reminder prevents losses, but it identifies where to test the change. The protocol groups by stay length and by property. A reminder is cheap to test and easy to remove if it does not help.
  • A final check compares the item log with the guest message. The two can diverge when the coordinator tells the guest the item shipped and the log still shows it in storage. The reviewer codes the mismatch separately from a late delivery. A single close update to both the log and the guest would remove the most common source of confusion.

Research standards

Every review freezes its observation window before findings are calculated. Reviewers retain a row-level evidence ledger with the original artifact reference, timestamp, responsible role, status at cutoff, correction history, denominator, exclusions, and unresolved cases. Ambiguous records are coded independently before reconciliation, and both readings remain visible until an accountable adjudicator applies a documented rule. Missing information is treated as unknown rather than silently classified as success or failure. Sensitivity checks remove major record classes in turn so a pattern that depends on one owner, channel, event type, or reporting cycle is disclosed instead of presented as stable. Elapsed time is not translated into labor, an association is not described as causation, and local observations are not converted into external benchmarks.

Interpretation begins with counterexamples and the cases still open at the cutoff. A formally complete record may lack usable evidence, while an authorized alternative path may achieve the intended outcome without matching the expected workflow. The review therefore states the strongest alternative explanation, identifies the additional artifact that could distinguish it from the preferred reading, and records what would reverse or retire the resulting operating rule. Comparisons use the same field definitions and equivalent work classes; a material change in coverage, tooling, policy, or sample composition creates a new baseline rather than a trend. Follow-up records name the decision taken, responsible owner, anticipated signal, review date, exception path, and evidence required before a stronger intervention can be justified.

Governance checks keep only information necessary for the research question. Sensitive content is replaced with a controlled reference whenever an authorized reviewer can reproduce the classification without holding a copy. Access boundaries, retention expectations, correction ownership, disputed-interpretation routes, duplicate handling, spanning-record rules, and cutoff treatment are documented before release. Absolute counts appear beside percentages, small samples avoid false precision, and every external statement links to a listed source without implying that the publication measured the local record set. The proposed action must be proportionate, reversible, and reviewable. If the available evidence cannot support it, the gap becomes an explicit evidence request rather than an assumption.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

This research note supports the STR Virtual Assistant topical map for vacation-rental guest communication, property readiness, issue routing, and evidence-based operational follow-through.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Sources

  1. FTC data security guidanceFTCChecked 2026-11-10
  2. FTC privacy and security guidanceFTCChecked 2026-11-10
  3. FTC consumer adviceFTCChecked 2026-11-10
  4. FTC homeFTCChecked 2026-11-10
  5. NIST Privacy FrameworkNISTChecked 2026-11-10
  6. NIST Cybersecurity FrameworkNISTChecked 2026-11-10
  7. SBA business guideSBAChecked 2026-11-10
  8. HUD fair housing guidanceHUDChecked 2026-11-10
  9. DOL wage and hour recordkeepingU.S. Department of LaborChecked 2026-11-10
  10. Consumer Financial Protection BureauCFPBChecked 2026-11-10
Lost-and-found returns and | STR Virtual Assistant