Evidence-governed workflow intelligence

Privacy Policy

DIO Workflows is designed around evidence, bounded authority and inspectable state. This policy explains how personal information may be handled across our public website, communications and authorised platform integrations.

Effective date: 9 August 2026

1. Who this policy covers

This Privacy Policy applies to DIO Workflows and public-facing workflow services operated under the DIO product family, including HOMS, Evidex, Sophia and VAMP, as well as DIO communication, intake and marketing-measurement surfaces where this policy is referenced.

For privacy enquiries, contact dio_workflows@outlook.com.

2. Information we may receive

Depending on how you interact with DIO, we may receive information such as:

  • your name, email address, organisation and other contact information you choose to provide;
  • the professional problem, request or workflow information you submit;
  • conversation and support information when you contact DIO through authorised channels;
  • campaign, referral or attribution identifiers used to understand how a person reached a DIO service;
  • order, payment-status and fulfilment references required to operate a requested service, without exposing unnecessary payment credentials;
  • documents or evidence you intentionally provide through an approved secure intake channel; and
  • technical, security and audit information reasonably required to operate, protect and troubleshoot the service.
The public DIO Workflows website currently instructs users not to place files or sensitive evidence in its simple public intake form. Higher-sensitivity material should only be supplied through an explicitly approved intake route.

3. How we use information

We may use information to:

  • respond to enquiries and requested communications;
  • create, route and operate requested HOMS, Evidex, Sophia, VAMP or related workflows;
  • prepare work for human review and preserve the authority of the relevant professional or customer;
  • verify customer or order relationships before disclosing restricted status information;
  • maintain security, evidence lineage, operational logs and auditability;
  • measure the effectiveness of campaigns and public channels without treating unverified attribution signals as commercial truth;
  • improve workflow reliability and product performance; and
  • meet applicable legal, regulatory, accounting or security obligations.

4. Human authority and automated processing

DIO may use software and AI-assisted systems to classify, structure, translate, format, summarise or prepare workflow material. DIO is designed so that consequential professional approval, release or authority remains bounded by explicit policy and, where required, human review. Automated systems should not silently acquire authority merely because they can produce an output.

5. Platform and service providers

To operate requested services, DIO may use third-party infrastructure, communication, payment, hosting, analytics or platform providers. These may include services used for email, cloud hosting, payment processing, social-media or advertising APIs, voice services and authorised business communications.

Information is shared with such providers only where reasonably necessary for the relevant function or integration and subject to the provider's own terms and privacy practices. DIO does not sell personal information to advertisers.

6. Social and advertising platform integrations

Where DIO is authorised to connect to platforms such as LinkedIn, Meta, TikTok or other marketing services, the integration may receive permitted account, campaign or performance information for reporting, attribution and Market Command analysis. Access is limited to the permissions granted to the DIO integration and the relevant platform account.

DIO's current operating doctrine separates observation from authority. Read access, reporting access or professional-identity verification does not by itself grant DIO permission to spend advertising funds, publish content, contact people, or make unrelated account changes.

7. Payments and commerce

Payments may be handled by external payment providers. DIO may retain transaction references, order identifiers and verified payment state needed to reconcile and fulfil a transaction. Full payment-card credentials should remain with the authorised payment provider and are not required by the public DIO intake form.

8. Data retention

We aim to retain personal information only for as long as reasonably necessary for the purpose for which it was collected, to maintain legitimate business and evidentiary records, to resolve disputes, or to meet applicable legal and security obligations. Retention may vary according to the type of workflow and information involved.

9. Security

DIO is designed to use bounded permissions, explicit identity binding, signed or traceable events where appropriate, and separation between public-facing and privileged operator surfaces. No system can guarantee absolute security, but we aim to apply reasonable technical and organisational safeguards appropriate to the information being processed.

10. Children and educational workflows

Some DIO products support education professionals. The public DIO Workflows site is not intended as an unrestricted collection service for children's personal information. Educational material involving learners should be handled through an authorised educator, institution or appropriately governed workflow and should minimise personal information wherever possible.

11. International processing

Some service providers may process information in countries other than your own. Where cross-border processing occurs, DIO aims to use it only where reasonably necessary for the relevant service and to handle personal information consistently with applicable data-protection obligations.

12. Your choices and privacy requests

You may contact us to ask about personal information associated with you, request correction or deletion where appropriate, withdraw a consent you previously provided, or raise a privacy concern. Some information may need to be retained where required for security, legal, accounting or legitimate evidentiary purposes.

Send privacy requests to dio_workflows@outlook.com with enough information for us to identify and respond to the request safely.

13. Changes to this policy

We may update this policy as DIO's public services, integrations or legal obligations change. The effective date above will be updated when material revisions are published.

14. Current public-site boundary

The DIO Workflows GitHub Pages site is currently a public informational and intake surface. Decorative event-console values are expressly presented as simulations rather than live customer telemetry. As additional production integrations are enabled, this policy should be reviewed against the actual deployed data flows.