Security Brief

Security is built into how Buyer Engine is deployed and managed. We minimize data exposure, separate financial control, and operate with explicit platform governance.Data Security
✔ No data export: leads are never downloaded, stored, or resold by Third Palm Labs; capture and storage remain solely in the client’s CRM.
✔Least‐necessary access: any CRM/IDX credentials you provide are used only for setup; clients secure the environment post‐launch by updating all credentials.Access and Account Controls
✔ You own your Google billing; we connect via Google’s Manager Account (MCC).
✔ Integrity controls: revoking MCC access while running Buyer Engine or cloning structure is a license breach; use beyond term without renewal is prohibited.
✔Change management: clients should not alter campaign structure, budgets, or conversion settings without written approval to avoid performance degradation and support forfeiture.Infrastructure & Tracking
✔ Tagging & attribution implemented on client’s site, permissioned install & CRM handoff.
✔Proprietary tracking is embedded to detect unauthorized replication & protect IP.Compliance & Ethical Use
✔Licensed professionals only; the system is operated under the client’s name, brokerage, and license in the target market. Required disclosures should be displayed on landing pages.
✔ Market integrity: one license per ZIP; exclusivity prevents internal competition.Insurance & Assurance
✔ Third Palm Labs maintains Errors & Omissions and Cyber Liability coverage; Certificates of Insurance are available upon request.
✔ Every engagement is governed by a formal SOW and master terms; support is included for 12 months from activation.Client Responsibilities (Summary)
✔ Maintain accounts in good standing; retain sole control of payment methods.
✔ Post‐onboarding, change all CRM/IDX/site passwords to secure your environment.
✔Avoid unauthorized structural changes or plugin conflicts; request changes through support.