Public and private data
Official-source records and public analysis are separated from private organisation profiles, decisions, controls, evidence and comments.
Security and trust
How Edict IQ protects source-backed work
Public source intelligence stays separate from private organisation work. Access, provenance and automated outputs are presented as reviewable product controls, not as blanket assurance claims.
Access model
Workspace routes use authenticated sessions, server-side authorisation and role-aware product states. Public pages do not expose customer workspace records.
Encryption
Public web traffic is served over HTTPS. Contractual claims about private-data encryption, key handling and retention require current infrastructure evidence.
Source provenance
Material public claims are designed to point back to official source identity, citation status, publication date and review state where the public read model exposes them.
Automated analysis
Automated processing may structure facts, interpretations and proposed actions, but it is not presented as legal authority, professional judgement or a final compliance decision.
Responsible disclosure
Security reports should use the security contact category. Do not include secrets, credentials or sensitive customer data in public forms.
Connected AI and MCP data boundary
When a customer connects an AI client through OAuth or a tenant-bound MCP credential, Edict IQ sends only the product data required by the selected tools and permissions. The machine surface does not expose APS configuration, acquisition URLs, crawler or fallback logic, provider prompts, model routing, raw organisation context, internal user identifiers or bulk corpus access. Workspace data requires an explicit workspace-bound permission.
Claims not made here
Edict IQ does not claim ISO, SOC, penetration-test completion, uptime SLA, legal certification or unrestricted global hosting coverage on this page.