About the academy

Open learning.
Clear boundaries.

Public lessons, fictional examples, and a practical approach to keeping people in control.

Public by design

FusionWork Academy is public, with no login, no analytics, advertising or tracking scripts, no cookies. The site uses no external fonts or third-party scripts. All learning pages can be read without creating an account. The hosting provider, Cloudflare, may collect standard operational logs and browser network-error reports.

Fictional examples

All companies and people in the teaching examples, including Lane & Hoy and its team, are fictional. The public lab repository will use fictional data only, with no real customer data or secrets. Fictional email addresses in the supplied material are omitted from the public pages.

Learning scope

The academy teaches practical workflow design: outcome, steps in existing tools, approval gates and an action log. The samples are teaching models, not claims about a verified product release. Local mock exercises establish foundations; supervised work and explicit senior sign-off are required before an FDE leads an engagement.

Regional privacy and governance briefing

Citations are being verified against official texts; editions, dates and section references remain pending verification. Official starting points: Singapore Personal Data Protection Act 2012, Thailand PDPA — Ministry of Digital Economy and Society legislation index, and IMDA — Model AI Governance Framework for Agentic AI. These links do not mean citation verification is complete.

This is practitioner briefing, not legal advice. References: Singapore, Personal Data Protection Act 2012; Thailand, Personal Data Protection Act B.E. 2562; Singapore Infocomm Media Development Authority (IMDA), Model AI Governance Framework for Agentic AI. Citation review date: 16 November 2026, Asia/Singapore. For each reference, the official consolidated text/edition, publication or update date, URL and relevant section numbers are pending verification: citations are being verified against official texts; see the official source links in this briefing. Do not infer certification, statutory compliance or exact framework recommendations from this reference list.

Start with Singapore PDPA questions for the fictional Singapore company. Flag Thailand PDPA assessment whenever people in Thailand are involved; location alone does not settle applicability or the lawful processing/transfer route. Customer counsel and the customer's privacy lead decide those questions; FusionWork's own questions go to its DPO. A person approving an agent action is authorising that particular execution. It is not privacy consent from the people whose data appears in it. A connector permission grant is also not privacy consent.

Draw the data flow before access: source mailbox or file → local extraction → restricted evidence store → draft/approval view → destination connector → event record, snapshots, traces and backups. Mark the people, purpose, fields, readers, processing locations, remote access and service providers at every step. A Singapore mailbox viewed by a Bangkok operator, or Thai staff data processed in Singapore or another hosting region, raises transfer questions even when no attachment is emailed. Have the customer confirm the appropriate arrangements before using real data; no invented section number or generic consent checkbox resolves this.

Minimise records and set purpose-based retention, review dates, authorised access/correction/deletion procedures, and a backup-expiry schedule. Append-only logs and immutable source versions mean that ordinary agents cannot silently rewrite history; they do not mean keep personal data forever. Store minimal event metadata separately from restricted, expiring payloads. Controlled retention/correction can purge or redact source versions, snapshots, index entries, wiki pages, caches and backups, leaving only a minimal lawful audit marker. Hashes and tokenised identifiers may remain personal data if linkable. Holds need an authorised reason, owner, expiry/review date and restricted access; they are not permission to keep everything.

If something goes wrong, stop the affected workflow, restrict further exposure, preserve only appropriate evidence, and escalate to the customer's incident lead and privacy lead/counsel. Those roles decide containment, notifications and legal deadlines. The FDE does not independently notify people or authorities based on this briefing. The academy's rule that send, pay and delete always need separate named-person approval is academy policy, not a claimed statutory rule or a claimed IMDA prescription.

Access and privacy preflight

Before A1, B1, C1 or D1 invites action, record: authorised data and purpose; the smallest mailbox/folder/field/time access; a named owner and backup; where data flows and when it expires; the stop switch and person to escalate to; and the exact approval route. Start on fictional or explicitly authorised material. No live outbound action is allowed outside the stated approval process. If authority, translation, evidence or destination is uncertain, hold and ask the owner. A missing preflight means a paper exercise only.

Reuse and licensing

Academy content is licensed under Creative Commons Attribution 4.0 International. Website code is licensed under the MIT License, reproduced below. Attribute content to FusionWork Academy and indicate any changes. Do not imply endorsement.

Trademark rights in the FusionWork name and logo are not granted by this content license.

MIT License

Copyright (c) 2026 FusionWork

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.