Security
Last updated November 16, 2026
Counterline is built to hold as little as possible and to protect what it holds.
What we hold
Record ids, dates, money amounts, catalog item names and one-way fingerprints for matching. Never customers' names, emails, phone numbers, addresses, birthdays, notes or card details: those pass through memory on their way from the point of sale to the CRM.
How it's protected
- All traffic uses HTTPS. The CRM's access keys and the point of sale's access keys are encrypted at rest (AES-256-GCM) and never sent to a browser.
- Every webhook is checked for its sender's signature before anything is stored, and handled once even if it arrives twice. Workflow calls must carry our own secret key.
- The in-CRM page signs people in only with the CRM's encrypted user details, checked on our server; owners, managers and staff see and change only what their role allows, and only in their own business account.
- Connecting a point of sale uses a signed, short-lived link tied to the business account and the person who started it.
- Public pages, sign-in links, connect pages and webhooks are rate-limited, so links can't be guessed and a flood can't take the app down.
- One part of the code writes to the CRM and one part per point of sale writes there. Each refuses writes on paused, read-only or sample accounts, and none of them deletes anything.
- Consent only gets stricter: the app can turn email Do Not Disturb on, never off.
- Our logs and error reports leave out access keys, links, names, emails, phones, addresses and card details.
- When a business uninstalls, its access keys are deleted right away, and all its data 30 days later.
Reporting a problem
Email hello@goldstandardweb.com with "Security" in the subject. We reply within 24 hours and fix confirmed issues promptly. Please don't access other businesses' data or disrupt the service while testing.