Nerzo security isn’t a feature. It’s foundational.
Enterprise-grade cloud infrastructure with encrypted communication, isolated production environments, and continuous monitoring. Access is controlled, logged, and restricted by operational necessity.
Secure authentication flows including Apple Sign In, Google Sign In, and encrypted credential handling. Permissions are role-based and account-scoped. Internal access is restricted and audited.
All data is encrypted in transit and logically isolated at the database level. Row-level security ensures users access only their own workspace data. Private business information is never sold or monetised.
AI features operate within controlled request environments and isolated sessions. Outputs are assistive and require review before implementation. Generated content does not constitute legal, financial, or professional advice.
Payments are processed through Stripe using encrypted, PCI-compliant systems. Full card details are never stored. Subscription management and renewals are handled securely through the billing provider.
If you discover a vulnerability, suspicious activity, or security concern, please report it immediately. We investigate all legitimate reports.
Responsible disclosure is encouraged. Do not attempt to exploit or publicly disclose vulnerabilities.
Personal data is processed securely and only for the purpose of delivering the service. Data is never sold or monetised.
You retain ownership of your data and may request export or deletion at any time.
Designed in alignment with recognised security and data protection practices.
Infrastructure Architecture
The platform runs on secure, enterprise-grade cloud infrastructure designed for reliability and resilience.
Infrastructure access is restricted to authorised operational personnel only. Every access event is logged and traceable.
Backups are performed routinely and recovery procedures are documented and tested.
This architecture ensures continuity, integrity, and controlled system evolution.
Authentication & Access Control
Authentication uses secure third-party providers including Apple and Google where selected.
Credential handling is encrypted and never exposed to client-side storage beyond session requirements.
Access permissions are:
• Role-based
• Account-scoped
• Enforced at database level
• Auditable
Internal system access is limited by operational role and logged for accountability.
Session management prevents cross-workspace access and ensures data boundaries are maintained.
Data Protection Model
All data is encrypted in transit using modern TLS protocols.
At the database level, row-level security policies enforce strict workspace isolation.
Users can only access records associated with their authenticated account.
Key principles:
Data integrity and separation are fundamental design decisions, not optional layers.
Controlled AI Execution
AI requests operate within defined system constraints.
Inputs are processed within isolated sessions tied to authenticated users.
No persistent memory is shared across accounts.
Outputs are generated as assistive content only and must be reviewed before implementation.
The system does not provide legal, financial, or professional advice.
Users retain full responsibility for decisions made using generated insights.
AI execution is rate-limited, monitored, and logged to prevent misuse.
Payments & Financial Handling
All payment processing is handled through Stripe.
Billing logic is handled server-side to prevent tampering or client-side manipulation.
Subscription limits, usage checks, and entitlement gating are enforced before execution of premium features.