Enterprise Privacy & Data Handling Policy
NEXUS AI SYSTEMS INC. ("NEXUS", "we", "our") is committed to uncompromising privacy and proprietary data protection for all B2B enterprise partners.
1. Non-Training Guarantee on AI Foundation Models
We maintain direct enterprise API agreements with foundational model providers (including OpenAI, Anthropic, and Microsoft Azure). Under no circumstances will any client customer records, proprietary CRM databases, meeting transcripts, or strategic documents be used to train, fine-tune, or reinforce public commercial AI models.
Strict Zero Data Retention (ZDR) flags are enforced at the HTTP gateway layer for every API payload.
2. Information We Ingest During Automation
To construct deterministic autonomous workflows, we may process information ingested via authorized webhooks and API tokens, including:
- CRM contact records, company firmographics, and deal pipeline status.
- Customer service tickets and inbound communication channels (Zendesk, Intercom, Slack, Email).
- Operational logs and execution timestamps generated across n8n, Zapier, and custom serverless functions.
- Authorized account credentials and OAuth tokens stored in hardware-encrypted keystores.
3. Data Encryption & Storage Protocols
All data in transit is encrypted using TLS 1.3 with forward secrecy. All vector embeddings, synthetic datasets, and cached metadata stored at rest are encrypted with AES-256 standards. RAG vector databases are provisioned inside private virtual clouds (VPCs) with strict IP allowlisting.
4. Global Regulatory Compliance (GDPR, CCPA & HIPAA)
Our automation architectures comply with the EU General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA). For healthcare and fintech partners, we sign Business Associate Agreements (BAAs) and configure HIPAA-eligible isolated clusters.
5. Data Ownership & Right to Deletion
You maintain 100% full legal ownership of your data at all times. Upon contract termination or formal request via security@nexus-ai.agency, all client-specific vector stores, temporary queues, and cached telemetry are securely purged using cryptographic erasure within 7 business days.