Legal
Confidentiality
What to send us, what not to send us, and how we handle it.
Version 1.0 · 21 August 2026 · Draft, not yet reviewed by counsel. This page will be replaced with a reviewed version before Agynx accepts customers under it.
Draft of 21 August 2026, pending legal review. This document has not yet been reviewed by counsel and should not be relied upon as final. It will be replaced before Agynx accepts customers under it.
Before an agreement is in place
Early conversations happen before any confidentiality agreement exists. Please treat them accordingly, and tell us about your workflow in terms that do not require you to expose anything sensitive.
Please do not send
- Customer or patient records of any kind
- Medical, financial or otherwise regulated data
- Credentials, API keys, or access to any system
- Real documents containing personal information
- Anything you are contractually obliged to protect
A description of the workflow is enough for a first conversation. If we need to see a real example, we will put an agreement in place and arrange a secure way to send it.
Describing a workflow safely
You can tell us what kind of document arrives, how many, what your team does with it, which systems are involved and what goes wrong, without sending a single real record. That is normally enough for us to know whether there is something worth building.
How we handle what you do send
Form submissions are processed on hardware we operate, are reviewed by a person, and are used to prepare for a conversation with you. Access is limited to the people who need it. If you tell us you sent something you should not have, we will delete it and confirm that we have.
Sample data during a pilot
Where a pilot requires real data, it is covered by a written agreement that sets out what may be sent, who may see it, where it is stored, how long it is kept, and how it is destroyed. That agreement is signed before anything is transferred.