Data in scope
List the asset records, work orders, user details, attachments, and integrations the proposed workspace will handle.
Which data is required, and who can view or change it?
Loading PredictAint...
Security requirements vary by organization and deployment. Before sharing operational data, confirm the controls, hosting, and contractual terms for the specific PredictAint workspace you are evaluating.
Request written answers for your proposed configuration and keep them with your vendor review and pilot agreement.
List the asset records, work orders, user details, attachments, and integrations the proposed workspace will handle.
Which data is required, and who can view or change it?
Confirm the hosting provider, storage region, data flows, and any location requirements that apply to your organization.
Where is data stored and processed, including backups?
Review user roles, authentication options, administrator access, and how access changes when people leave a team.
Which access controls are included in the proposed plan?
Ask for written details about encryption, backups, retention periods, incident handling, and deletion procedures.
Which controls are in place, and what evidence is available?
If your evaluation includes the AI assistant or an integration, confirm which information is processed, which service providers are involved, what is retained, and what review controls are available. Validate the exact workflow with representative, non-sensitive data before a production rollout.
Bring your hosting, access, data handling, and integration questions to a product walkthrough before deciding whether a pilot fits your requirements.