AMMERZE

Legal

Security

Last updated: 10 November 2026

Your data security is fundamental to Ammerze. This page describes our security architecture and how to report a vulnerability.

1. Data Encryption

  • Credentials at rest: All third-party channel credentials (Amazon SP-API keys, Shopify tokens, Zoho OAuth tokens, Shiprocket passwords, WooCommerce keys) are encrypted with AES-256-GCM before storage. The encryption key is derived from a dedicated ENCRYPTION_SECRET environment variable — never from JWT signing secrets.
  • Passwords: User passwords are bcrypt-hashed and are never stored or logged in plaintext.
  • Data in transit: All traffic between your browser and Ammerze is encrypted over TLS/HTTPS.

2. Authentication Security

  • HTTP-only cookies: Access tokens (7-day) and refresh tokens (30-day) are set as HTTP-only, Secure, SameSite=Strict cookies — they are never accessible to JavaScript.
  • Token rotation: Refresh tokens are single-use and rotated on every use. A stolen token can be invalidated by logging in again.
  • OTP verification: Account creation and password reset require a 6-digit OTP sent to your registered email. OTPs expire in 15 minutes and are deleted immediately after use. Failed OTP attempts are rate-limited per IP and per account.
  • OAuth CSRF protection: Shopify and Zoho OAuth flows use signed state parameters to prevent forged callback attacks.

3. Infrastructure Security

  • CORS allowlist: Only authorised frontend origins can make API requests — no wildcard CORS.
  • Environment secrets: The server refuses to start if JWT_ACCESS_SECRET, JWT_REFRESH_SECRET, or ENCRYPTION_SECRET are unset — there are no hardcoded fallback secrets.
  • Logging: Credential fields (API keys, passwords, tokens, OTPs) are redacted from all application logs.

4. Responsible Disclosure

If you discover a security vulnerability in Ammerze, please report it responsibly:

Emailinfo@ammerze.com with subject "Security Vulnerability Report"
IncludeDescription of the vulnerability, steps to reproduce, potential impact, your contact details
We willAcknowledge your report within 48 hours, provide a status update within 7 days, and credit you (if desired) when the fix is released
Please do notPublicly disclose the vulnerability before we have had a reasonable opportunity to fix it (minimum 90 days)
Scopeammerze.com and *.ammerze.com. Third-party platforms connected via Ammerze (Amazon, Shopify, etc.) are out of scope.

5. Incident Response

In the event of a security incident affecting your data:

  • You will be notified within 72 hours of a confirmed breach.
  • We will provide details of what was affected and what actions we have taken.
  • We will cooperate fully with any investigation required by the Data Protection Board of India.

6. Known Limitations (Transparency)

We believe in transparency. The following known gaps are on our security roadmap:

  • The standalone Shiprocket module (/api/channels/shiprocket/*) is not currently protected by authentication middleware — this is a known gap being addressed.
  • Google and GitHub OAuth login buttons are visible in the UI but not yet implemented.

7. Questions

Contact info@ammerze.com for general security questions.