Security
Your clients’ information, kept to your account.
How Gable protects your data
Encrypted in transit and at rest
Every connection to Gable is HTTPS, and browsers are told never to use anything else. The database is encrypted at rest. Access tokens for connected calendars and social accounts are encrypted again by Gable before they are stored, with a key kept outside the database, and API keys are stored only as a one-way hash.
Each agent sees only their own deals
Access is enforced inside the database with row-level security, so a session can read only its own deals and its team’s. A seller or buyer sees only their own deal’s page, and the tasks and notes an agent keeps private never reach it.
Assistants and keys are scoped and revocable
An assistant such as Claude connects through Sign in with Gable, and your own tools through an API key. Either one acts as you, on your deals only, is limited in how often it can call, and can be revoked in Settings at any time. Nothing is changed without your confirmation in Ask Gable.
Connections ask for as little as they can
Google Calendar access is limited to the calendar Gable creates for itself. It cannot read the rest of your calendar. Gable posts to Facebook or Instagram only a post you have approved.
Client pages stay private
A client’s page is shown only to that client and their own agent. Client pages are kept out of search engines: they carry a noindex tag and header, and are excluded in robots.txt.
Privacy law
Gable handles personal information in line with PIPEDA, Canada’s federal private sector privacy law. Client email carries the sender’s mailing address and a way to stop it, as Canada’s anti-spam law requires. The privacy policy sets out what is collected and why.
Report a security issue
Email hello@getgable.ca with Security in the subject. A person reads it, and we will reply to tell you what we found.
Try it with your own listing.
Launching soon.