Giving a stranger your gate code
How access windows work, what screenshot blocking really does, and the honest limits of both.
The Xoot team
Start with the status
A gate code is sensitive information. The useful question is who can see it, for how long, and how access can be withdrawn. A reassuring badge is not enough.
Xoot's access-window mechanism is deployed and encrypted but has not yet been proven by a code stored and read back through the app. The interactive Trust illustration explains the intended behaviour; it is not a live customer booking.
One assigned visit, for a limited window
The design releases details to the assigned Xooter 45 minutes before the visit and locks them again when it completes. The intended retention period is seven days after the visit, followed by deletion rather than indefinite archiving.
That design needs an end-to-end check before it can be relied on as a proven live workflow. Read the current status beside the mechanism, rather than assuming this article announces its activation.
What screenshots can and cannot do
Android can prevent capture of the protected screen. On iOS the control detects capture rather than preventing it. The app is designed to blank the screen when backgrounded.
No software can stop a second phone photographing a screen. Capture controls are one layer; they cannot undo information someone has already seen.
Withdrawing access and limiting exposure
The revoke control is designed to take effect at the next read, including mid-visit. Withdrawing access does not cancel the visit or add a charge. It cannot erase a code from a person's memory.
Avoid sending access codes in ordinary messages. Use the protected flow only once its current status and your actual booking support it. If a code may already be exposed, withdrawing access alone does not change the physical gate code; arrange a change through the person responsible for the property.
Quick answers
Does screenshot blocking prevent every copy of my code?
No. iOS supports detection rather than prevention, and a second device can photograph any screen. Timed access and withdrawal reduce exposure but are not absolute guarantees.
Is the website access-window demo operating on a real booking?
No. It is labelled as an illustration with sample codes. The mechanism's published status still requires an end-to-end stored-code and readback check.
Ready for Xoot?
Choose your service, review the details and continue through the booking flow.