Security
Your team's memory is sensitive. Here is how std::nous is built to protect it.
Access follows your permissions
- Connectors request read-only access.
- Every answer is built only from sources the asking member can already open.
- Private channels and restricted documents stay restricted.
Your data stays yours
- Workspace content is never used to train models, ours or any provider's.
- Disconnect a source and its index is deleted.
- Each workspace is kept separate from every other workspace.
Encrypted in transit
- All traffic between you, us, and our providers is encrypted with TLS.
- Integration credentials are never shown in the interface.
Answers you can audit
- Every answer shows which sources it used.
- When the sources don't cover a question, std::nous says so instead of guessing.
Providers
Hosting runs on Vercel. Answers are generated with Claude by Anthropic under commercial terms that do not allow training on our customers' data. DNS and email go through Cloudflare. The full list is in our Privacy policy.
Responsible disclosure
If you believe you've found a security issue in std::nous or stdnous47.cloud, email support@stdnous47.cloud with the subject "Security report". Include steps to reproduce and any proof of concept.
- We acknowledge reports within 3 business days.
- Please give us reasonable time to fix the issue before disclosing it publicly.
- Don't access or modify other users' data, and don't run tests that degrade the service.
- We won't pursue legal action for good-faith research that follows these guidelines.