Privacy
Privacy and Data Handling Framework
This page explains what information @I Design may process, why it is processed, how access is controlled, and how data rights requests are handled across product and engagement workflows.
The operating model is built for security-sensitive engineering programs and follows a minimal-data, purpose-bound approach rather than broad collection by default.
- Data minimization by default.
- Purpose limitation and controlled access.
- Security controls aligned with deployment mode.
Collection Scope
What We May Collect
Only data required to provide service operations, support, and governance controls is collected.
This may include contact details, business identifiers, account metadata, support communications, and engineering artifacts submitted through approved channels.
- Contact and account information.
- Project-level technical inputs you provide.
- Operational telemetry for reliability and security.
Use and Legal Basis
How Information Is Used
Information is processed to deliver requested services, maintain platform integrity, and meet legal obligations.
- Contractual service delivery.
- Legitimate interests in security and reliability.
- Regulatory and legal compliance requirements.
Security Model
Security and Access Controls
Data access is restricted by role, purpose, and environment boundaries.
- Role-bound authorization controls.
- Environment-specific isolation pathways.
- Documented incident response process.
Retention and Rights
Retention, Deletion, and Your Rights
Data retention is time-bounded and purpose-driven, and lawful access, correction, deletion, portability, or objection requests are handled through verified channels.