Access with purpose
Role-based permissions and mutual consent limit access to hiring information.
Security at sii{me}
Trust starts with protection.
Safeguards around your account, your information, and every private introduction.
Explore the detailsSensitive data stays limited
Persona handles identity media. Stripe handles payment credentials.
A direct reporting path
Report a concern to Rhett so it can be investigated and addressed.
Access and isolation
Authenticated roles, server-owned transitions, row-level database policies, least-privilege service credentials, protected admin actions, private-by-default identity, and mutual-consent gates limit who can see or change hiring information.
Provider boundaries
Persona handles government-ID and live-selfie media. Stripe handles bank and card credentials. sii{me} retains provider references, verification or payment status, signed agreement receipts, and the minimum operational data needed to run the service.
Application controls
Signed webhooks, idempotency records, input validation, rate limits, immutable attribution snapshots, structured audit events, protected approval links, and server-side authorization guard high-impact actions.
Operational readiness
Our operational requirements include configuration checks, backup and restoration validation, dependency review, incident response ownership, error monitoring, availability checks, and checks after releases. Report security concerns to rhett@siime.ai.
A real person. A direct line.
Your questions deserve an answer.
Privacy request, security concern, or accessibility barrier? We’re here to help.