Workspace data is scoped to the organisation. Sensitive governance APIs enforce server-side role checks rather than relying on hidden buttons.
TRUST · GOVERNANCE · SECURITY
Protected by design. Governed with human accountability.
Oprun is being designed as a multi-tenant business operating system with role-based access, privacy controls, complaint escalation, human oversight of consequential AI actions, append-only governance evidence and clear customer/staff rights pathways.
This overview describes our security and governance approach. It is not a certification, legal opinion or guarantee of compliance.
Critical governance events are written to an append-only ledger with linked hashes so later alteration can be detected. Personal content is not placed on a public blockchain.
AI or automated triage can route, draft and summarise. Legal, employment, privacy, safety, complaint outcomes and other consequential decisions require human review.
HELP & COMPLAINTS
One protected route for customers, workers and the public
Every user can open the Help & Complaint Desk. The system creates a reference and private case access key, applies automated risk triage and routes the case to support, a complaints officer, manager or owner. Protected/anonymous intake is available; confidential cases can bypass conflicted roles.
High-risk escalationSecurity, privacy, fraud/scam, safety, legal correspondence and serious staff-conduct matters can generate immediate in-app alerts and configured email/SMS escalation to an authorised senior person.
Conflict-aware accessA complaint involving a manager is hidden from manager-role case administration; a complaint involving the owner is routed to an authorised complaint officer/external escalation channel rather than the owner. Confidential routing is enforced server-side.
Permanent case historyCase creation, status changes and escalation events are stored as append-only case events with linked cryptographic hashes.
PRIVACY & DATA
Privacy lifecycle, not just a privacy page
- Role and business-need access restrictions.
- Data minimisation and retention/de-identification planning.
- Access, correction, export and deletion workflows to be finalised for production.
- Incident and Notifiable Data Breach assessment workflow where Australian NDB obligations apply.
- Cross-border provider and subprocessor review before enabling production integrations.
For Australian APP entities, OAIC guidance emphasises transparent privacy management, complaint handling, and reasonable technical and organisational steps to protect personal information.
AI GOVERNANCE
Approval boundaries for consequential actions
AI is designed to assist with drafting, classification, recommendations, search, content preparation and operational summaries. It should not silently make final employment, legal, financial, safety, privacy, complaint, disciplinary or other materially consequential decisions.
Australian privacy transparency requirements for certain significant automated decisions commence on 10 December 2026. The governance layer therefore records AI-assisted workflows and keeps human escalation paths visible.
SECURITY ARCHITECTURE
Layered controls rather than a public blockchain
IdentityVerified account creation, strong passwords, HTTP-only sessions, rate limiting, temporary login lockout and optional MFA.
AccessRole-based permissions, senior-only governance logs, least privilege and confidential complaint routing.
EvidenceHash-chained audit events plus an append-only governance ledger. The ledger stores evidence hashes and metadata rather than public personal data.
Production storageUse a real encrypted database for structured records, encrypted object storage for calls/media/files, a managed key/secrets service, monitored backups and point-in-time recovery. Google Drive/OneDrive can be optional document integrations, not the core database.
AWS readinessThe production architecture can use AWS S3-compatible object storage, KMS-managed encryption keys and protected backups when configured by the platform operator. Oprun does not claim AWS certification or display certification badges; any such status must be verified for the deployed environment and organisation before it is shown.
SecretsProvider application keys stay server-side. Customers should connect accounts through approved OAuth/provider authorisation rather than entering developer secrets.
COMMUNICATION GOVERNANCE
Consent-aware messaging
Marketing automation should distinguish promotional messages from operational/service communications, retain consent evidence, identify the sender and maintain suppression/unsubscribe controls. Provider connection does not itself authorise marketing.
PROTECTED DISCLOSURES
Do not label every complaint a statutory whistleblower report
The platform can provide a confidential protected-disclosure pathway, but legal whistleblower protections depend on eligibility, subject matter, recipient and circumstances. Australian corporate whistleblower rules protect specified eligible whistleblowers and restrict disclosure of identity; only some entities are required to maintain a formal whistleblower policy.
AUSTRALIAN READINESS SOURCES
Official guidance used for the control model
Need help or want to raise a concern?
Use the Help & Complaint Desk on this page. Serious cases can be escalated to authorised senior users through configured notification channels.