Features · Blacklist & security
Guest blacklist and security screening
Every arriving guest's ID is checked against your property's blacklist automatically, during online check-in — before a door code is ever issued. An exact document match blocks check-in; a similar name only flags the booking for a human to review.
What is a guest blacklist for a hostel?
A guest blacklist is a list of individuals a property, or a group of properties, chooses not to accommodate — checked automatically against arriving guests instead of relying on staff memory. In EZ2Stay, screening runs during the ID-verification step of online check-in: an exact match on the document number blocks check-in and alerts the owner immediately, while a similar-name match only flags the booking for manual review. Entries can stay private to one property or be shared across the platform. Screening is treated as a legitimate-interest security measure, not something requiring guest consent, and every match — plus any staff override — is written to the audit trail. Entries hold identifying details only, never biometric data such as a selfie.
| Capability | Limit | Status |
|---|---|---|
| Automatic screening during the ID-verification step | runs the moment ID data is captured, not before the check-in link is opened | Live |
| Exact ID-number match blocks check-in and alerts the owner | the guest sees a generic message, never the blacklist reason itself | Live |
| Similar-name match flags the booking for manual review | a name match alone never blocks automatically — a person decides | Live |
| Entries private to one property, or shared across the platform | shared entries are visible to other organizations on EZ2Stay; private ones are not | Live |
| Staff override with a documented reason | every override is written to the audit trail, never applied silently | Live |
| Entry record: name, ID type/number (masked), reason, severity, added by | no biometric data — selfies are never stored in a blacklist entry | Live |
How it works
- An entry is added. An owner (or another org, if shared) adds a name, ID type/number, reason and severity — no selfie or biometric data involved.
- A guest reaches the ID step. During online check-in, the guest's document is captured and OCR extracts their identifying data automatically.
- Screening runs instantly. An exact ID-number match blocks check-in and alerts on-duty staff immediately; a similar name alone only flags the booking.
- Staff review the flag. They confirm the block or override it with a documented reason — either decision is logged, not applied silently.
- The match is audit-logged. Date, reason, who acted and the outcome are recorded, whether the guest was blocked, overridden or cleared.
What the owner configures
| Setting | Default | Who can change it |
|---|---|---|
| Entry visibility | private to the creating property | Owner — can mark an entry Shared across the platform |
| Match sensitivity for names | high-similarity fuzzy match only | Not configurable — by design, to limit false positives |
| What happens on an exact ID match | block check-in + alert on-duty staff | Not configurable — by design |
| Staff override | requires a documented reason | Owner and staff with access — always logged |
| Entry fields collected | name, ID type/number, reason, severity | Owner — photo and notes are optional |
This screening runs in production at Popcorn Hostel, Bucharest — 49 beds, 63 smart locks — checking every arriving guest's ID against the property's blacklist before a door code is ever issued.
Not a fit if
- You want a criminal-background-check service — EZ2Stay only screens against entries your property, or the platform, has explicitly added.
- You need it to stop a guest before the check-in link is even sent — screening runs at the ID step, not before.
- You want automatic blocking on a name match alone — EZ2Stay only auto-blocks on an exact ID-number match; a name match always goes to a person to review.
Frequently asked questions about EZ2Stay for hostels
When does blacklist screening happen?
Automatically during the ID-verification step of online check-in, the moment the guest's document data is captured.
What triggers an automatic block?
Only an exact match on the ID document number. A similar name alone flags the booking for staff to review — it never blocks by itself.
Can staff override a block?
Yes, with a documented reason. Every override is recorded in the audit trail, including who acted and when.
Are blacklist entries shared between properties?
Only if the creating organization marks an entry 'Shared'. Private entries stay visible only to the property that added them.
Does the blacklist store biometric data?
No. Entries hold name, ID type/number (masked in the UI), reason, severity and optional notes — never a selfie or biometric record.
Is this a criminal background-check service?
No. It only screens against entries your property or the platform has explicitly added, on a legitimate-interest basis — it prevents a flagged guest from completing check-in, nothing more.