Keep control of your business data.
Understand the questions to resolve before connecting company data, starting a pilot, or planning production.
Ask the practical questions.
Start with a description of your data and requirements. You do not need to upload a sensitive dataset to discuss whether the workflow fits.
Controls and contractual terms need to be confirmed for the proposed setup.
Define the data boundary.
Document what the dataset contains and whether it includes sensitive or regulated information. Agree on which data can be shared, who can review it, and what environment the project requires before an evaluation begins.
- Data categories and sensitivity.
- Required hosting region and environment.
- Permitted uses of the dataset and derived outputs.
Agree on access and retention.
Access, storage, and deletion expectations should be part of the project discussion. Ask for the relevant technical and contractual details so your own security team can assess whether the proposed setup meets its requirements.
- People and systems that require access.
- Retention and deletion requirements.
- Logging, review, and incident contacts.
Verify before connecting.
Make security review part of the evaluation. Request documentation for the controls your organization requires, confirm the proposed hosting arrangement, and resolve contractual requirements before transferring production data.
- Request applicable security documentation.
- Review the proposed contractual terms.
- Confirm responsibilities before starting a pilot.
Can I test the product examples with sensitive data?
The examples on this website use illustrative data and do not accept dataset uploads or run live inference. Discuss data handling, access, and retention requirements before sharing a production dataset for an evaluation.