Color Match Pro Published by Frozen Gator
Privacy Terms Security

Frozen Gator

Security and Data Processing

Effective and last updated August 6, 2026

Color Match Pro is designed as a multi-tenant print-production service. Its security controls protect merchant configuration, customer chart information, historical production specifications, generated files, and connector credentials without making one store's information available to another.

Security is a release gate. A public deployment must pass application readiness, migration, private-storage, queue, mail, privacy-recovery, and production-renderer validation before it is admitted for merchant use.

Tenant and identity protection

  • Authorized staff sessions and signed connector requests are verified server-side.
  • Every merchant-owned record and file is resolved through the authenticated tenant.
  • New stores are admitted only after a valid, authorized platform connection.
  • Suspended stores are not automatically reactivated by an ordinary request.
  • Staff preferences and audit actors use tenant-specific one-way identifiers where raw identity is unnecessary.

Secrets, sessions, and browser protection

  • Application and provider credentials remain server-side and are never shipped in storefront JavaScript.
  • Sensitive stored values use application encryption; production sessions use encrypted, secure, HttpOnly, host-only cookies.
  • Exact trusted-host enforcement, HTTPS, HSTS, restrictive framing, MIME protection, referrer limits, and browser permission limits are applied in production.
  • Expensive generation, support, and write operations are tenant- and actor-scoped and rate limited.

Production files and storage

  • Generated files are stored privately without public directory access.
  • Downloads require current authorization or a narrow signed token and are recorded.
  • A failed generation cannot replace a previously valid immutable file.
  • Production binaries normally expire after seven days; incomplete staging artifacts are removed.
  • Historical production specifications remain versioned so authorized regeneration does not depend on current defaults.

Privacy operations

  • Platform privacy notices and requests from authorized native privacy tools are verified before processing.
  • Customer and company names are encrypted at rest. Tenant-specific keyed search terms support authorized lookup without storing plaintext indexes.
  • Personal-data access evidence records the tenant, purpose, route class, and pseudonymous actor without copying chart content or raw customer identity.
  • Backup recovery is reconciled against verified erasure evidence so deleted store data is not silently restored.

Reliability and recovery

  • Managed session and workload controls preserve tenant boundaries as the service scales.
  • Background commerce work and production generation are isolated and monitored.
  • Generation retries are bounded. Terminal failures preserve the saved specification and expose controlled regeneration.
  • Backup recovery, scheduled-work checks, and private-file validation are part of deployment qualification.

Responsible reporting

Please report a suspected vulnerability or unauthorized disclosure privately to support@frozengator.com. Include enough information to reproduce the issue, but do not access another merchant's information, disrupt service, or include live customer data that is not necessary for the report.

Questions can be sent to support@frozengator.com.