Do not include PHI
No subject names, identifiers, source excerpts, medical history, visit data, safety cases, or document content.
Contact
Talk to CliniStack.
Use this page for product questions, commercial conversations, partnerships, security or privacy routing, and general contact. Public channels must not include PHI, subject identifiers, credentials, source documents, or regulated trial records.
Contact routes
Product, security, privacy, support.Contact routes
Send the question to the right public channel.
Role-based public addresses keep routing clear while the product is in early public-market contact mode.
Product and commercial
For product fit, buying committee questions, partnerships, and demo requests.
Security reports
For vulnerability disclosure and security reporting, email security@clinistack.dev without PHI, regulated records, credentials, or secrets.
Privacy questions
For public-site privacy questions and public-contact data handling.
Public channel boundaries
Do not send regulated trial content through public email.
Public email is for routing, early product discussions, and non-sensitive diligence questions. Customer application data and regulated trial records belong in approved product or diligence channels.
Do not include credentials
Never send passwords, API keys, tokens, secrets, or screenshots containing sensitive access details.
Use approved channels later
When diligence needs sensitive materials, we will route the work through an approved channel with the right controls.
Contact
Send the question without regulated data.
Tell us who you are, what you are trying to solve, and the safest way to route the conversation.