WISERREVIEW — Enterprise Security & Compliance Pack

1. Executive Summary

Security at a Glance

Infrastructure Provider Certifications

Compliance Roadmap

Security Governance

Security responsibilities are embedded into engineering roles at WiserReview, not siloed into a separate department. The Security Officer owns the overall security program, with direct accountability across a small team structure that enables fast decision-making.

2. Platform Architecture

System Architecture

Complete view of the WiserReview platform showing all services across four security zones: the Edge Zone (Cloudflare), the Application Zone (Azure App Services), the Data Zone (MongoDB Atlas, Redis, Azure Service Bus), and External Services (AWS SES, Chargebee, Sentry). All external traffic is filtered through Cloudflare before reaching Azure-hosted application services.

Data Ingestion & Review Display

Reviews, orders, and product data enter WiserReview through four distinct ingestion paths: e-commerce platform webhooks, manual CSV imports, the review submission form, and platform API syncs. Every path is authenticated and encrypted.

Multi-Tenant Data Isolation

Every request carries a JWT token with a unique workspace identifier. All database queries, cache keys, and API responses are scoped to that workspace. No merchant can access another merchant's data.

Widget Delivery & Storefront Safety

The WiserReview widget loads asynchronously from the CDN, executes after the merchant's page has rendered, and never sends the merchant site's cookies or credentials to WiserReview servers. Zero impact on storefront performance and security.

Auto-Scaling & High Availability

Every layer of the platform scales independently. During traffic spikes the system automatically provisions additional capacity without manual intervention. Merchant storefronts are never affected by WiserReview scaling events.

3. Infrastructure Security

Core Services

Network Security

Rate Limiting

Encryption in Transit

Encryption at Rest

CI/CD Pipeline Security

Monitoring & Observability

Availability & Disaster Recovery

4. Data Privacy & Protection

Data from End Consumers (Reviewers)

Data from Merchants

Data We Do NOT Collect

Data Lifecycle

GDPR Alignment

WiserReview acts as Data Processor on behalf of merchants (Controllers). The formal agreement governing this relationship is our Data Processing Agreement (DPA).

Data Subject Rights

Automated Data Deletion

WiserReview implements automated data deletion events through platform integrations. For example, Shopify's mandatory GDPR webhooks (CUSTOMERS_DATA_REQUEST, CUSTOMERS_REDACT, SHOP_REDACT) are fully supported for automated compliance.

Data Retention & Deletion

Breach Notification

In the event of a confirmed personal data breach, affected merchants will be notified within 72 hours of discovery, in compliance with GDPR Article 33. A root cause analysis will be conducted and remediation steps implemented. The relevant supervisory authority will be notified where required.

CCPA (California Residents)

WiserReview does not sell personal information. California residents may exercise their Right to Know, Right to Delete, and Right to Non-Discrimination by contacting [email protected]. We will respond within 45 days.

5. Compliance & Certifications

Current Compliance Status

SOC 2 Trust Service Criteria: Control Mapping

We don't hold a SOC 2 Type II report yet. The table below maps our existing controls to the Security Common Criteria:

ISO 27001 Annex A: Control Mapping

How our practices map to ISO 27001 Annex A:

6. Access Control

Merchant Workspace Roles

Each merchant workspace supports three roles. Role assignments are stored in the user's JWT token context and enforced server-side on every API request. Authorization is independently enforced in the backend regardless of UI state.

Authentication Mechanisms

• JWT Token Authentication: Signed with a server-side secret; required on every API request; tokens carry user identity and workspace context
• OAuth 2.0: Authorization code flow for all platform integrations; least-privilege scopes; HMAC validation on incoming webhooks
• bcrypt Password Hashing: One-way hashing; passwords never stored in plaintext or any reversible format
• Cloudflare Turnstile CAPTCHA: Protects registration and public forms from bot abuse and credential stuffing

Production Access Controls

• No SSH access to containers: Azure App Services is a managed platform with no direct SSH access to production containers
• No direct production database access for developers: MongoDB Atlas access restricted to Engineering Lead and Security Officer only
• Deployments via CI/CD only: All production changes go through GitHub Actions: no manual file uploads or hotfixes applied directly
• MongoDB Atlas IP whitelisting: Database clusters accept connections only from authorized Azure App Service IP ranges
• GitHub encrypted secrets vault: All production credentials stored as encrypted secrets, injected at runtime only

7. Incident Response

Response Process Overview

Incident Classification

Communication Plan

• Confirmed personal data breach: affected merchants notified within 72 hours of discovery (GDPR Article 33)
• Extended P1 service outage: customer notification within 4 hours if outage persists beyond 1 hour
• Relevant supervisory authority notified where required by GDPR or applicable law
• Post-incident review conducted within 5 business days for all P1/P2 incidents

8. Backup & Disaster Recovery

Recovery Objectives

Backup Strategy

• MongoDB Atlas: Continuous automated backups with point-in-time recovery. Replica sets (minimum 3-node) with automatic failover and zero data loss
• File Storage (Azure Blob / AWS S3): Server-side AES-256 encryption at rest. AWS S3 provides 99.999999999% (11 nines) durability
• Azure Service Bus: Dead-letter queue preserves all unprocessable messages; automatic retry with configurable intervals
• Application Layer: Docker images stored in Azure Container Registry with version history. Prior deployments redeployable at any time

Disaster Recovery Scenarios

9. Sub-Processors

The following third-party sub-processors are engaged in the processing of personal data on behalf of WiserReview:

10. DPA Summary

WiserReview offers a GDPR Article 28 compliant Data Processing Agreement. Below is a summary of the processing details and security measures outlined in the DPA.

Processing Details

Technical & Organisational Security Measures

The full Data Processing Agreement is available at /dpa and can be countersigned upon request.

11. Privacy Policy Summary

Data Collected

WiserReview collects two categories of personal data: consumer data (submitted with reviews or received from e-commerce platform order data) and merchant data (provided during registration and platform integration). The detailed breakdown is covered in Section 4 above.

Data Retention

GDPR Rights

• Right to Access: merchants can export all data; consumers can request via merchant or directly
• Right to Rectification: review content editable by merchant or upon consumer request
• Right to Deletion: individual reviews deletable; full account deletion removes all data
• Right to Data Portability: CSV export from dashboard
• Right to Object: email unsubscribe available at any time

The full Privacy Policy is available at /privacypolicy.

12. Change Management

CI/CD Pipeline

All production deployments go through the GitHub Actions CI/CD pipeline. No changes are applied to production servers directly. The pipeline includes: code push, Docker multi-stage build, push to Azure Container Registry, staging verification, and production promotion. All credentials are stored in GitHub's encrypted secrets vault and never appear in source code or build logs.

Environment Separation

Rollback Procedures

13. Contact & Next Steps

Full Documentation