Security
Sensra handles client intake submissions, project documents, and workspace data on behalf of service businesses. Here is how we approach security across the platform.
Authentication
Sign-in and account management are handled by Clerk, an industry-standard authentication provider. Sensra never stores raw passwords. Multi-factor authentication is available on all accounts.
Data in transit
All communication between your browser and Sensra's servers uses TLS. Data in transit is encrypted end-to-end.
Data at rest
Your project data, client intake submissions, proposals, scopes, and files are stored encrypted at rest in our cloud infrastructure.
Workspace isolation
Each workspace is a hard boundary. Members can only access data belonging to their own workspace. There is no shared data pool across accounts.
Access controls
Workspace roles (Owner, Admin, Member) restrict which actions each user can take. Admins manage members and workspace settings. Owners control billing and deletion.
Client-facing links
Public share links (intake forms, delivery views, client input requests) use token-based access with no login required. Tokens are hashed server-side — the raw token is only visible once.
AI and your data
Content you create in Sensra is not used to train AI models. AI-generated drafts are produced on your request and are stored only within your workspace.
Subprocessors
We use a small number of trusted infrastructure providers for hosting, authentication, payments, and email delivery. We do not sell data to third parties.
Report a security issue
If you discover a security vulnerability in Sensra, please contact us directly at security@sensra.io. Please do not disclose security issues publicly until we have had a chance to address them.
Please do not disclose security issues publicly until we have had a chance to address them.
Questions? Contact us or read our Privacy Policy.