Business separation
Core records carry the business they belong to, and every read is checked against the signed-in business. One pet care company cannot read another company’s clients, pets, bookings, sitters or messages.
Sitterly holds access instructions, contact details, pet medical context, team identities, messages, location data and payment records. Security is part of how we run the product every day, not a badge on a website.
Ask a security questionWe describe each control specifically, so you can judge it for yourself rather than take a badge on trust.
Core records carry the business they belong to, and every read is checked against the signed-in business. One pet care company cannot read another company’s clients, pets, bookings, sitters or messages.
Owners, office staff, sitters, clients and platform administrators have different responsibilities. Sensitive actions are checked against the person’s role and their relationship to the record.
Entry instructions and codes are shown to a sitter only for a client the owner has confirmed. A booking sent through the public form with a client’s phone number never releases that client’s codes on its own.
Sessions are checked on the server and stop working when a person’s access is removed. A second sign-in step is available for protected accounts.
Selected sensitive actions emit audit events. The engineering workflow includes dependency checks, secret scanning, protected build gates, and authorization and tenant-boundary tests on every change.
We would rather tell you where the program stands than describe it in words we cannot back.
Each pet care business remains responsible for its own staff, devices, permissions and handling of client information.
Send security questions or suspected vulnerabilities to support@sitterlysoftware.com. Please leave client secrets, passwords, full payment data and other personal details out of that first message. We will ask for what we need.