1. Scope and responsible party
This policy applies to the public DIO Workflows website, DIO-powered product pages, controlled pilots, public intake flows, and supported integrations with services such as Microsoft, Google, Meta, LinkedIn and TikTok where those integrations are enabled.
For privacy questions or requests, contact dio_workflows@outlook.com.
2. Information we may collect
- Contact and organisation information: your name, email address, organisation and information you choose to include in an enquiry or service request.
- Work materials: documents, prompts, evidence, briefs, correspondence or other material you submit for a DIO workflow.
- Account and integration data: platform account identifiers, permissions, authorisation metadata and access tokens where you deliberately connect a supported third-party service.
- Commercial data: order references, payment status, transaction identifiers and related records when a paid service is used. Card or banking credentials are ordinarily handled by the relevant payment provider rather than stored by the public DIO website.
- Technical and security data: timestamps, request metadata, event receipts, error records, security logs and other operational information needed to protect, diagnose and audit the service.
- Outcome and feedback data: customer replies, acceptance states and bounded campaign or service outcomes where these are part of an authorised DIO workflow.
3. Why we process information
We process personal information only for specific, relevant purposes, including to respond to enquiries, provide requested services, authenticate integrations, prepare customer deliverables, preserve evidence and audit trails, prevent abuse, secure the system, reconcile authorised transactions, comply with legal obligations and improve DIO through governed feedback processes.
Where consent is required, we seek it before the relevant processing. Where processing is necessary to respond to your request, perform an agreed service, protect legitimate security interests or comply with law, we process only the information reasonably necessary for that purpose.
4. Google and YouTube API data
When you explicitly authorise the DIO Workflows Google/YouTube integration, DIO may access Google/YouTube data only for the media workflow you authorised. The current integration may access the connected YouTube channel identity and metadata, upload user-authorised videos and related thumbnails, captions or metadata, verify channel and video state, and read channel/video statistics and YouTube Analytics for reporting and verification.
The current OAuth workflow requests permissions for YouTube uploads, YouTube operations needed by the authorised media workflow, read-only YouTube channel/video access and read-only YouTube Analytics. DIO does not use those permissions to build unrelated advertising profiles or to sell Google user data.
Where a refresh token is required for continued authorised access, it is stored in a private operator-controlled configuration or secret store and exchanged for short-lived access tokens when needed. Tokens are not intentionally published in the public website or repository. Access is limited to the authorised integration and may be revoked by the user through their Google Account permissions.
Google user data is shared only with Google/YouTube APIs and infrastructure providers necessary to perform the authorised workflow, or where disclosure is required by law. DIO does not sell Google user data. DIO Workflows' use and transfer of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements.
If you revoke the Google connection, DIO stops using that authorisation for future Google API access. You may also request deletion of stored integration data or credentials as described in the Data Deletion Instructions. Minimal security, transaction or evidence records may be retained where reasonably necessary and lawful, but unnecessary Google user content and credentials are not retained merely because the integration once existed.
5. Automated and AI-assisted processing
DIO uses automated and AI-assisted components to classify requests, structure material, prepare drafts, bind evidence, produce controlled outputs and perform quality checks. DIO is designed so that consequential professional, legal, academic, employment, financial, publication and external-release authority remains with the authorised human or organisation responsible for that decision.
We do not present an automated draft as a human decision merely because the system produced it.
6. Third-party services and processors
DIO may rely on service providers for hosting, infrastructure, email, authentication, platform integrations, payments and other bounded functions. Depending on the workflow, these may include GitHub, Cloudflare, Microsoft, Google, Meta, LinkedIn, TikTok and payment providers selected for a transaction.
When you connect or use a third-party platform, that platform also processes information under its own privacy terms. DIO does not control the independent processing performed by those third parties.
7. Sharing and sale of personal information
We do not sell personal information. We disclose information only where needed to provide an authorised service, operate a connected platform integration, process a transaction, protect the service, comply with law, or where you direct or consent to the disclosure.
8. International processing
Some infrastructure and platform providers may process or store information outside South Africa. Where cross-border processing occurs, we take reasonable steps to use providers and safeguards appropriate to the information and the applicable legal requirements.
9. Retention
We retain personal information only for as long as reasonably necessary for the purpose for which it was collected, including service delivery, security, evidentiary integrity, dispute handling, accounting and lawful record-keeping. Where an auditable receipt must be retained, we may preserve a minimal record or cryptographic reference while deleting unnecessary personal content where lawful and technically feasible.
10. Security
DIO uses technical and organisational controls intended to reduce unauthorised access, alteration, disclosure or loss. These include bounded permissions, event logging, separation of authority, credential controls and controlled release paths. No internet service can guarantee absolute security.
11. Cookies, analytics and advertising technology
The public DIO website does not intentionally require non-essential advertising cookies simply to view its public pages. If analytics, conversion measurement, social-platform pixels or similar technologies are introduced, DIO will update the relevant notice and consent controls where required.
Third-party platforms you visit or authenticate with may set their own cookies under their policies.
12. Children and special personal information
The public DIO website and developer integrations are intended for adults and organisations. Do not submit children's information, special personal information or highly sensitive records unless a specific governed workflow expressly permits that material and you have lawful authority to provide it.
13. Your privacy rights
Subject to applicable law, you may ask us to confirm whether we hold personal information about you, request access or correction, object to certain processing, request deletion or restriction where appropriate, withdraw consent where processing depends on consent, or ask questions about how your information is used.
Send requests to dio_workflows@outlook.com. We may need to verify your identity before acting on a request.
South African data subjects may also raise concerns with the Information Regulator (South Africa).
14. Platform disconnection and deletion
If you disconnect a DIO integration, we stop using that authorisation for future platform access. You may also request deletion of personal information associated with the integration. See the DIO Data Deletion Instructions for the request process.
15. Changes to this policy
We may update this policy as DIO products, integrations or legal requirements change. The effective date at the top of this page identifies the current published version. Material changes will be reflected on this public page.