Contact and support information
Contact and support messages are used to discuss workflows and resolve website issues. Include business contact details and a non-sensitive description of the request. Keep production documents and customer records in their approved systems.
Do not include credentials, financial account numbers, employee records, or regulated personal data in an inquiry. Keep the submission reference for follow-up so related messages can be connected without resending sensitive information.
Map a workload by data category
| Category | Design question |
|---|---|
| Source documents | Which pages or fields are needed, and which may leave the source environment? |
| Business context | Which supplier, order, receipt, or catalog records can be retrieved? |
| Credentials | Which component holds them, and which operations can they authorize? |
| Model inputs and outputs | Which provider receives which content, under which terms? |
| Evidence and logs | Which references are necessary without duplicating sensitive source content? |
| Support material | How can a problem be investigated using minimized or redacted examples? |
A fallback is also a data-flow decision
A model fallback can change the organization or region processing a request. Routing requirements must identify permitted data destinations before cost or quality preferences. A stronger model is useful only when it fits the same processing restrictions.
Distinguish transient processing, retained inputs, output storage, provider logging, and training permissions. Record the applicable provider terms and retention requirements for each processing path, including fallback routes.
Resolve retention and deletion together
Source files, operational records, idempotency references, and evidence receipts serve different purposes. Define their retention separately and explain how deletion affects reconciliation, investigation, and historical proof.
Confirm hosting and processing locations, subprocessors, access controls, retention periods, deletion behavior, backup treatment, and contractual responsibilities before submitting business workloads. Assign an owner for policy changes and their effect on existing records.
Missing a detail or found a problem?
Send a documentation question →