Security
Minimal access. Clear boundaries.
CatalogTrail is designed to read supported Item Library and location data without gaining permission to edit your Square catalog.
Read-only Square permissions
The production integration requests Items read and Merchant profile read. The latter lets CatalogTrail display recognizable location names. It does not request item-write, payment, customer, banking, payroll, or order permissions.
Token protection
Square OAuth tokens are encrypted with AES-256-GCM before database storage. Encryption keys are kept separately in the deployment secret store, with authenticated context preventing ciphertext from being moved between connections.
Tenant isolation
Every product query is scoped to an authenticated organization and workspace. Provider webhooks are signature-verified before processing and handled idempotently.
Data minimization
CatalogTrail stores supported catalog projections and before-and-after records. It does not ingest payments, customers, card data, payroll, or stock counts. Raw provider webhook payloads are scheduled for removal after 30 days.
Responsible disclosure
Report a suspected security issue privately to security@catalogtrail.com. Do not include live credentials or sensitive merchant data in the first message.