Security
Trust needs boundaries.
Our published security practices and responsibilities for using Intellectz products.
Updated 16 October 2026. These practices describe the shared Intellectz workspace and the boundaries customers should understand.
Identity and permissions
The shared workspace uses verified-email accounts and authenticated sessions. Company membership, product roles and invitations determine which records and actions are available. Studio invitations and other restricted products retain their access scope. Product recovery codes are not a substitute for general account access.
Separate records, connected access
Products use different storage systems, including Cloudflare databases and object storage and retained product databases. Server-side access checks protect tenant and product boundaries. We do not claim that every product uses the same database or security mechanism.
Secrets and payments
Service credentials belong on the backend. Payment status is checked by the backend before granting paid access; a checkout return page alone is not proof of payment. Payment-provider account controls remain separate from the Intellectz login.
AI and consequential work
Review extracted specifications, assumptions, quantities and outputs before production or a commercial commitment. AI interpretation can be incorrect. Product-specific checks, human approvals and deterministic calculations have different responsibilities; a successful model response is not a guarantee of manufacturing suitability.
Your responsibilities
Use a unique password, invite only authorised people and protect exported files and recovery codes. Review company and product permissions when team members change. Browser-local drafts depend on the device and its storage.
Report a concern
Email hello@intellectz.ai with the affected product and a description. Do not send passwords, payment details or sensitive production files in the initial report. We will arrange an appropriate way to investigate.