How your residents’ bookings and details are kept safe
These protections live in the database itself, so they hold even if a screen or a server ever gets something wrong.
- No double bookings, everThe database refuses a booking that overlaps another one for the same space, cleaning time included. A request waiting for approval holds its time too.
- Residents see their ownA resident reads only their own bookings and their own entry on the list. When they look for a free time, they see which times are taken, never by whom.
- Signed agreements can’t be rewrittenWhat a resident agreed to is stored with a fingerprint of the exact rule text. Nobody can edit or delete it afterwards, including our own servers.
- Bookings can’t be moved quietlyOnce made, a booking’s resident, space and time are fixed. To change them, it is cancelled and booked again, so the record shows what happened.
- Only what booking needsWe keep a resident’s name, email, address, whether they own or rent, and their standing. We store no full IP address, only its first part.
- No passwordsResidents and board members sign in with a one-time link sent to their email.
- Permission checked on every requestEach change made in the console is checked against your community’s roster before anything is read or written. A board seat runs reservations only if it has been given that permission.
- Nothing for anyone signed outWithout signing in, none of your community’s booking data can be read at all.
- Card details never touch our serversCard payments are handled by Stripe. Amenity Reserve never sees or stores a card number.
- One place for your community’s dataEach community’s spaces, residents and bookings are kept apart from every other community’s, by the same database rules.
Questions from your board?
We’ll walk your board or manager through how access and records work.