Security & Incident Response Policy

AdMantle is committed to protecting the data of every merchant who uses our platform. This document describes our security practices, infrastructure safeguards, and the process we follow when responding to security incidents.

Data Encryption

• All data in transit is encrypted via TLS 1.2 or higher
• Data at rest is encrypted via AES-256 (database provider-managed encryption)
• Sensitive credentials (Shopify access tokens, Meta tokens) are encrypted at rest using AES-256-GCM with a dedicated encryption key

Application Security

• Authentication via industry-standard identity providers with JWT verification
• Role-based access control (Owner, Admin, Member) enforced at the API layer
• Organization-scoped data isolation: merchants can only access their own data
• Input validation at all system boundaries
• Structured logging with correlation IDs for auditability
• Error monitoring via Sentry for real-time anomaly detection

Infrastructure

• Application hosted on managed cloud platforms with automatic patching
• Database hosted on Neon (PostgreSQL) with automated backups and point-in-time recovery
• Redis used for transient caching and job queues only (no persistent sensitive data)
• Secrets managed via environment-level injection (Doppler), never stored in source code

• Production database access restricted to application service accounts only
• No direct production database access by team members during normal operations
• Authentication enforced via identity provider with strong password policies and optional MFA
• API endpoints protected by JWT verification with issuer, audience, and algorithm validation
• Third-party platform tokens (Shopify, Meta) stored encrypted and scoped to the minimum required permissions

In the event of a suspected security incident, AdMantle follows a structured response process:

Step 1: Detection & Triage

• Incidents detected via application monitoring (Sentry), log analysis, customer reports, or third-party notifications
• Initial triage within 4 hours of detection to classify severity (Critical, High, Medium, Low)
• Critical incidents (data breach, unauthorized access) trigger immediate response

Step 2: Containment

• Isolate affected systems to prevent further exposure
• Revoke compromised credentials or tokens immediately
• Disable affected integrations if necessary
• Preserve evidence and logs for investigation

Step 3: Investigation

• Determine root cause, scope, and impact of the incident
• Identify affected merchants and data
• Review access logs and correlation traces
• Document timeline and findings

Step 4: Notification

• Affected merchants notified within 72 hours of confirmed data breach
• Notification includes: what happened, what data was affected, what we are doing about it, and recommended actions
• Regulatory authorities notified as required by applicable law (GDPR, CCPA)
• Shopify and Meta notified if their platform data was involved

Step 5: Recovery & Remediation

• Deploy fixes to address the root cause
• Rotate affected credentials and encryption keys
• Restore systems from clean backups if necessary
• Verify fix effectiveness before returning to normal operations

Step 6: Post-Incident Review

• Conduct post-mortem within 7 days of incident resolution
• Document lessons learned and preventive measures
• Update security controls and monitoring to prevent recurrence

If you discover a security vulnerability in AdMantle, please report it responsibly by emailing hello@admantle.com.

We ask that you:

• Do not publicly disclose the vulnerability before we have addressed it
• Provide sufficient detail for us to reproduce and fix the issue
• Allow reasonable time for remediation before disclosure

We are committed to investigating and responding to all legitimate security reports promptly.

• Merchants can disconnect integrations at any time, which stops data collection immediately
• Full data deletion can be requested by emailing hello@admantle.com
• Data deletion requests are processed within 30 days
• Backup retention follows cloud provider schedules (typically 7-30 days) after deletion

For security concerns, incident reports, or privacy questions, contact us at hello@admantle.com.