Privacy Policy
Effective September 16, 2026
What BuildSignal collects
We collect account identity provided by Google, company profile and lead preferences, product activity, CRM notes and follow-ups, billing status supplied by Stripe, and support or feedback you submit. We also process public permit, inspection, contractor-license, and first-party contractor contact information.
How information is used
We use information to authenticate users, personalize and rank project leads, provide contractor and CRM tools, operate subscriptions, prevent abuse, improve the product, and respond to support requests. We do not sell personal information.
Google user data
Google sign-in is used only to identify your account. BuildSignal requests basic profile information such as your Google account identifier, name, email, and profile image. Gmail access is not requested as part of sign-in. If a future mailbox connection is offered, it will use a separate consent screen, the narrowest available scope, and a separate activation step. BuildSignal’s use of Google data will comply with the Google API Services User Data Policy, including Limited Use requirements.
Service providers
We use hosting and database infrastructure to run the service, Google for optional identity, and Stripe for checkout, subscription management, and payment processing. Stripe receives payment information directly; BuildSignal does not store full card numbers.
Retention and control
We retain account and CRM information while your account is active and as reasonably required for billing, fraud prevention, legal obligations, and backups. You may request access, correction, export, or deletion. Disconnecting a future Google integration will revoke access and remove stored tokens, subject to limited security and legal retention.
Security and contact
We use access controls, encrypted transport, restricted secrets, and audit records appropriate to the service. No system is completely secure. For privacy questions or requests, contact sam@samryan.work.