Security overview
Steadwell holds the details of people’s homes: addresses, floorplans, the codes on the gate. This page is a plain summary of how that data is protected, written so you can answer a question about it without asking us first.
Where Steadwell runs
Section titled “Where Steadwell runs”Steadwell runs on Amazon Web Services (AWS) in the United States. Backups and media are replicated across regions for redundency.
Data protection
Section titled “Data protection”Data at rest
Section titled “Data at rest”All datastores with customer data, in addition to S3 buckets, are encrypted at rest. Additionally, sensitive data is protected with field-level encryption.
This means the data is encrypted even before it hits the database so that neither physical access, nor logical access to the database, is enough to read the most sensitive information.
Data in transit
Section titled “Data in transit”Steadwell uses TLS 1.2 or higher everywhere data is transmitted over potentially insecure networks. We also use features such as HSTS (HTTP Strict Transport Security) to maximize the security of our data in transit. Server TLS keys and certificates are managed by AWS and deployed via Application Load Balancers.
Secret management
Section titled “Secret management”Encryption keys are managed via AWS Key Management System (KMS). KMS stores key material in Hardware Security Modules (HSMs), which prevents direct access by any individuals, including employees of Amazon and Vanta. The keys stored in HSMs are used for encryption and decryption via Amazon’s KMS APIs.
Application secrets are encrypted and stored securely via AWS Secrets Manager and Parameter Store, and access to these values is strictly limited.
How people sign in
Section titled “How people sign in”- Google sign-in and passkeys are the recommended paths. Neither involves a password Steadwell has to store; both are described below.
- Email and password, as a fallback. A password is 12 to 128 characters and may use any characters, including spaces; there is no required mix of character types, because length matters more than symbols. Steadwell refuses passwords found in known data breaches and passwords that contain your email address, your name or “steadwell”, and a strength meter helps you choose a good one. You are never asked to change your password on a schedule - only if we suspect it has been exposed. Passwords are stored hashed, never in a readable form.
- Google, where the operator turns it on. Signing in with Google hands Steadwell only a verified email address and name; Steadwell never sees a Google password. A Google account connects only to the Steadwell account with the same address, and never creates one.
- No self-service sign-up. An account exists only because an administrator in an organization invited it. There is no public registration page.
- Passkeys - Face ID, a fingerprint, a device PIN - to sign in and to confirm your identity before sensitive actions. A passkey sign-in is accepted only when your device has unlocked the passkey. See Set up and use passkeys.
- Rate limiting on sign-in, password reset and verification, so guessing is slow. Repeated sign-in attempts are slowed both per account and per network address.
- Step-up verification before an estate’s secured values are revealed or changed, valid for ten minutes on one device only.
Inside the product, every piece of data belongs to one organization and is reachable only by members of it, further narrowed by the member’s role and, for staff, by which estates they are assigned.
Reporting a security issue
Section titled “Reporting a security issue”If you believe you have found a vulnerability in Steadwell, email security@steadwell.estate with enough detail to reproduce it. Please do not test against another customer’s data or run anything that could degrade the service for other people.
Report a security issue has the full detail, including what to expect after you send it.

