Security
Last updated October 26, 2026
Gapfill is built to hold as little as possible and to protect what it holds.
What we hold
Record ids and appointment times, never clients' names, phone numbers, emails, appointment titles or notes. Names are read from the CRM only to show them on screen.
How it's protected
- All traffic uses HTTPS. The CRM's access keys are encrypted at rest (AES-256-GCM) and never sent to a browser.
- We check the CRM's signature on every webhook it sends us. Each one is handled once, even if it arrives twice. Workflow calls must carry our own secret key and name the account that installed us.
- The page inside your CRM signs people in only with the CRM's encrypted user details, which our server checks. Owners, managers and staff see and change only what their role allows, and only in their own business account.
- Booking links are random, signed and expire; we store only a fingerprint of each. Pages for a business's clients show only the business name, the time and a button.
- Every public page and workflow endpoint is rate-limited, so links can't be guessed and runaway workflows can't flood the app.
- Our logs and error reports leave out access keys, links, names and email addresses.
- One part of the code is allowed to book on a calendar. It re-checks the calendar right before booking, books once per offer, reads the booking back, and never cancels anything to fix a conflict; it tells you instead.
- 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.