Privacy & Terms

How the workflow assessment handles data.

Use this page to understand what the XIANNOVATIONS workflow assessment is for, what XIANNOVATIONS tracks by default, how OpenAI fits into processing, and what you should avoid submitting.

Important

This page explains the current product behavior and terms of use. It is not legal advice and it does not replace your own vendor, privacy, security, or compliance review.

Assessment scope

What the assessment is designed to handle

The assessment is meant for workflow descriptions such as approval chains, intake routing, reporting bottlenecks, service handoffs, or other repeated operating problems. It is meant to analyze process structure, not sensitive records.

  • 01Use it to describe a workflow, a repeated task, or an operating bottleneck.
  • 02Do not use it to submit customer lists, credentials, contracts, or regulated records.
  • 03Treat the output as an initial diagnostic, not a final implementation plan.

XIANNOVATIONS handling

What XIANNOVATIONS tracks by default

The current implementation is intentionally conservative. By default, analytics capture usage metadata instead of the full assessment text.

  • 01Analytics focus on metadata such as character count, prompt usage, page path, and timing.
  • 02Raw assessment text is not tracked in analytics by default.
  • 03If this behavior changes later, the product behavior and this page should be updated together.

OpenAI processing

How OpenAI fits into the workflow

If the assessment uses OpenAI's API or business services, submitted workflow descriptions are processed by OpenAI as the underlying AI provider. OpenAI states that API and business data are not used to train models by default unless a customer explicitly opts in.

  • 01OpenAI documents that API and business data are not used for training by default.
  • 02OpenAI also documents that some API data may be retained for abuse monitoring or application state depending on endpoint and account configuration.
  • 03OpenAI's consumer privacy policy is separate from API and business customer handling.

Data hygiene

What you should not submit

You will get a better result and reduce unnecessary risk if you describe the structure of the workflow rather than the sensitive payload inside it.

  • 01Do not paste passwords, API keys, or internal secrets.
  • 02Do not paste health data, financial account data, government identifiers, or protected personal records.
  • 03Do not paste confidential customer material when a generalized workflow description will do the job.

Terms of use

What the assessment is and is not

The assessment is an informational workflow review and prioritization tool. It does not replace legal, compliance, security, or other professional advice.

  • 01Treat output as directional workflow guidance, not a guaranteed implementation outcome.
  • 02Recommendations may change as the live product and workflow details become clearer.
  • 03If you need contractual privacy, retention, or deployment guarantees, those should be handled in a direct engagement.

Source basis

Official OpenAI documentation used for this disclosure

This page is grounded in OpenAI's published business-data and API-data documentation. If those policies change, this disclosure should be updated.

If you need a direct privacy conversation before using the assessment, email alex@xiannovations.ca and describe the workflow at a high level without confidential payload data.