Grounded AI
Responses use approved sources, defined guardrails and confidence-based escalation.
Trust centre
Safe by design. Honest about the boundaries.
Owlcumen combines preventative controls, human approvals and auditable actions. This page describes the product standard; the legal agreements govern the service.
Human authority
Sensitive actions and corrections can require review before they affect customers.
Scoped access
Workspaces, roles and integrations follow least-privilege access principles.
Secure transport
HTTPS, HSTS and secure provider connections protect data in transit.
Auditability
Material actions, approvals and security events produce an auditable record.
Quarantined uploads
Files are validated, isolated and scanned before approved processing.
Web application controls
Protection is implemented—not disclaimed.
The production release checklist treats XSS, malicious uploads, credential leakage and unbounded consumption as engineering risks.
| Risk | Owlcumen baseline | Operational evidence |
|---|---|---|
| Cross-site scripting (XSS) | Framework escaping; no unsafe HTML; strict CSP; output encoding; dependency review. | Header scan and security test before release. |
| Cross-site request forgery | SameSite cookies, state/nonce checks, origin validation and scoped tokens. | Auth and billing integration tests. |
| Malicious uploads | Size, count, extension, MIME and magic-byte checks; random names; private quarantine; malware scanning. | Blocked-file tests and quarantine audit events. |
| Abuse and cost exposure | Rate limits, prepaid usage wallet, alerts, hard caps and per-workspace attribution. | Usage ledger and automated stop thresholds. |
| Tenant data leakage | Workspace-scoped access, private object keys and least-privilege service accounts. | Authorisation tests and access logs. |
Upload policy
Assume every file is hostile.
Browser checks improve usability. Server checks make the decision.
10 MB default file limit and bounded files per request
Allowlist for PDF, PNG, JPEG and plain text where needed
Explicit denial of PHP, JSP/JSPX, ASP/ASPX, PHTML, PHAR, CGI, scripts, binaries, archives and active SVG
MIME plus magic-byte validation; extension alone is never trusted
Randomised private object key, quarantine state and no executable serving
Malware/content-disarm provider adapter before release to processing
Shared responsibility
Clear ownership.
Owlcumen is responsible for
- Platform security controls
- Tenant isolation and access logic
- Provider secret handling
- Product audit events
- Incident response process
Customers are responsible for
- Lawful data and outreach
- User and administrator access
- Knowledge accuracy and approvals
- Endpoint/device security
- Using connected services within their terms
Security statements describe intended production controls and do not replace a customer’s own risk assessment. Provider-specific residency, retention and certification claims must be confirmed against the final contracted infrastructure before sale.