Who holds the data
STAyTUTE is deployed for your community, and the database is yours — not a shared tenant alongside other governments. Export runs from your own system, so a records request, an audit, or a change of vendor does not depend on an extract you cannot verify. Category vendors typically host your data in their multi-tenant cloud; ask any of them where the database lives and who can export it.
Everyday controls
- Encrypted browser sessions (HTTPS)
- Staff roles and permissions
- Strong passwords, lockout, optional passkeys
- Form protection and a staff action history
- People and cases linked by unique party IDs, not email
Subprocessors
When enabled for a deployment, these vendors may receive data needed to run the Services:
- Postmark — email delivery (recipient, subject, message body)
- OpenStreetMap Nominatim / tile servers — geocoding and map images (address query or IP)
- Telnyx — SMS when that channel is on (phone number and message)
- Amazon S3 — file storage when uploads are configured for object storage
- OpenAI-compatible API — staff draft and FAQ harvest when AI is enabled (redacted thread text)
AI and Telnyx default off. We do not load advertising or analytics scripts today.
SOC 2 path
Type I is an independent look at whether controls are designed the way we describe, at a point in time. Type II watches the same criteria over several months — the report communities often ask for. We will not put a SOC 2 badge on this site until the report exists.
Public pages
The public directory shows licensed stays. A resident can file a problem with a photo and location on that property. Redaction on public records follows the rules you set. Auth and support tickets on your deployment are noindexed.