Security & privacy
A resident list holds names and home addresses, and a check-in log shows when a family was at the pool. Here is how Pool Check-in™ keeps that inside the community it belongs to.
How your records are protected
Each community sees only its own records
Every request is checked on the server against the signed-in person's community or organization. A manager can't open another community's residents, check-ins or reports.
The database is closed to the public
Row-level security is on for every table, and no public key can read or write them. Only the application server holds the key that can, and it never reaches a browser.
Gate devices are registered
Checking people in takes a username, a password and a device registered with your community's PIN. Revoking a device cancels its registration. To keep it out for good, change the PIN as well.
Passwords are never stored
Only a one-way hash of each password is kept. New accounts start with a temporary password that must be changed at first sign-in.
Guessing gets locked out
After repeated failed sign-ins for an account or from a network, sign-in pauses for 15 minutes. Every attempt, successful or not, is recorded with its time and device.
Resetting a password ends old sessions
When a password is reset or an account is switched off, anyone still signed in on that account is signed out at their next click.
Partner access is read-only and logged
If your organization connects another system, it gets a read-only token for the communities you choose. Every request it makes is recorded.
Hosted in the United States
The application runs on Vercel and the database on Supabase, both in the US East region.
Read VendoRFP’s Privacy Policy and Terms of Service.
Questions from your board?
We’ll answer them on a call, in as much detail as they want.