Privacy
Secrient is an early-stage beta service for sensitive client work. This page explains what we collect today and why.
Last updated April 21, 2026
Secrient is built for sensitive client work, so we try to collect only what is needed to operate, secure, support, and improve the service.
During the private beta, we keep the product surface and data collection intentionally narrow. If a workflow does not need a piece of information, we should not ask for it.
When you request beta access, we collect the information shown in the form: name, work email, company, role, team size, industry, type of sensitive work, and a short description of the problem you are trying to solve.
We use this information to review fit for the beta, prioritize onboarding, contact you about Secrient, and understand which sensitive client workflows need careful product design.
Like most web services, Secrient and its infrastructure providers may process limited operational data such as request times, IP address, browser or device information, error details, and security events.
We use this data to run the site, diagnose issues, prevent abuse, secure the service, and understand whether core flows are working. We do not describe this as zero logging or zero metadata.
Secrient uses infrastructure and service providers to host the site, process beta requests, store signup records, secure the service, and operate related systems.
These providers may process data on Secrient's behalf under their own security and operational controls. We avoid sharing more information with providers than is reasonably needed for the service.
Secrient does not sell personal data. We also do not use beta signup details to build advertising profiles.
If that position changes, this page should change first and beta participants should receive clear notice where appropriate.
You can ask us to delete or correct beta request information by contacting privacy@secrient.com.
We may need to keep limited records where required for security, legal, abuse-prevention, or operational reasons.
| Data | What it includes | Retention approach |
|---|---|---|
| Beta signup information | Name, work email, company, role, team size, industry, sensitive work type, problem description, record ID, and submission time. | Retained only as long as needed to review beta fit, manage onboarding, understand early product needs, and keep basic operating records. |
| Contact and support messages | Email address, message content, and any details you choose to include when contacting Secrient. | Retained as long as needed to respond, maintain context for the conversation, and keep practical records of privacy, security, or beta-related requests. |
| Limited operational and security data | Request times, IP address, browser or device information, error details, security events, and similar service metadata where applicable. | Retained as needed to run the site, diagnose issues, prevent abuse, investigate security events, and support provider or infrastructure requirements. |