Cloud Data Storage and Segregation

IPERA’s platform is designed as a secure, enterprise-grade multi-tenant SaaS architecture, ensuring that each customer’s data, users, and configurations are logically isolated and protected from access by other tenants, including IPERA’s internal users.

1. Logical Data Segregation (Tenant Isolation)

All customer data is logically segregated using a unique Tenant ID (tenantID) at the application and database layers. Every data object (e.g., user data, analytics records, reports, configurations) is strictly bound to a tenantID. Cross-tenant access is technically prevented by enforced tenant scoping in: Application logic Database queries API request validation The platform does not support shared data tables without tenant scoping, eliminating the risk of accidental data exposure.

2. Role-Based Access Control (RBAC)

Access to tenant data is governed by fine-grained Role-Based Access Control (RBAC). Users are created only within a specific tenant and cannot view or access data outside that tenant. Supported roles include (configurable per tenant): System Administrator – Full tenant-level configuration and user management Marketing / Business Users – Access to analytics and insights only Read-Only Users – View-only access with no modification rights Permissions are enforced server-side and cannot be bypassed via the UI or APIs.

It is also possible to allow some dashboard users managing multi-tenants for holdings that have multiple brands

3. Authentication & Authorization Controls

Secure authentication mechanisms are enforced for all dashboard and API access. Authorization checks validate both user role and tenant context for every request. Session tokens and API credentials are tenant-scoped and cannot be reused across tenants.

4. Administrative & Internal Access Controls

IPERA internal staff do not have default access to customer data. Any exceptional access (e.g., for support purposes) is: Role-restricted Time-bound Logged and auditable Production access is limited to authorized personnel only, following the principle of least privilege.

5. Data Encryption & Infrastructure Isolation

Customer data is encrypted: In transit using TLS 1.2+ At rest using industry-standard encryption mechanisms The platform runs in a hardened cloud environment with: Network segmentation Secure VPC/VNet isolation Restricted management interfaces 

6. Monitoring, Logging & Auditability

Access to tenant data is continuously monitored. Security events, authentication attempts, and administrative actions are logged and retained for audit purposes. Alerts are generated for anomalous or unauthorized access attempts.

7. Secure Development & Change Controls

All changes to tenant access logic, roles, or data models follow: Secure development lifecycle (SDLC) Peer review and testing Controlled deployment processes Regular internal security reviews are conducted to ensure tenant isolation remains effective.