Workspace isolation
Every operator has their own workspace. Properties, bookings, tenants, evidence and credentials never cross a workspace boundary, and access is enforced in the database, not only in the interface.
Security
Security by design, described honestly.
StayMesh handles booking evidence, tenant details and financial obligations. These are the design principles we build against today. We do not hold security certifications yet, and we do not display badges we have not earned.
Role-based permissions
Owner, administrator, operator and viewer roles decide who can read, change and approve. Sensitive actions are restricted to the roles that should carry them.
Human approval
Actions that affect money, contracts, access or a tenant's standing require a person to approve them before anything is applied.
Evidence provenance
Original channel and e-mail evidence is stored immutably. Later corrections are recorded as new entries and never overwrite what arrived.
Protected credentials
Channel and mailbox credentials are encrypted, held server side and never returned to the browser. Mailbox access is read only and limited to a single chosen label.
Data minimization
We store the operational facts needed to run the work, not entire mailboxes. Raw message bodies and personal identifiers stay behind the server boundary.
Controlled agent permissions
Agents observe and prepare by default. Any automatic action requires an explicit workspace policy with defined limits, and can be switched off.
Audit history
Applied changes are recorded with the previous values, the new values, the source, the person and the time, in a history that cannot be edited afterwards.
StayMesh does not currently claim any certification, regulatory approval or formal security standard. If that changes, this page will say so with the date and the scope.
Questions from a security review?
We answer security questionnaires directly and we will tell you plainly when something is not built yet.