Effective Date: March 1, 2026
Last updated: March 1, 2026
Privacy Policy
1. Information We Collect
We collect business user information (name, company, email, phone, billing data),
consumer lead information (name, phone, email, insurance interest data), and technical data
(IP address, browser type, usage analytics, cookies).
2. How We Use Information
We use data to provide CRM services, manage leads, improve AI models,
process payments, provide support, comply with legal obligations, and prevent fraud.
3. Sharing of Information
We may share information with service providers, payment processors,
messaging providers, telecom providers, legal authorities if required, and business successors.
We do not sell personal data in the traditional sense.
4. AI & Automated Processing
RevBind uses AI systems to prioritize leads, automate messaging,
analyze engagement, and generate insights. Users remain responsible for compliance.
5. Data Retention
We retain information while your account is active and as required
for legal, compliance, and dispute resolution purposes.
6. Security Measures
We implement SSL encryption, access controls, monitoring, and secure hosting.
7. Your Privacy Rights
Depending on jurisdiction, you may request access, deletion, or correction
of your data by contacting info@revbind.com.
8. CCPA Disclosure
California residents may request disclosure or deletion of collected data.
We do not knowingly sell personal information of minors under 16.
9. Cookies
We use cookies for analytics, functionality, and performance optimization.
10. Children’s Privacy
Our Services are not directed to individuals under 18.
11. International Users
If accessing outside the U.S., you consent to data transfer to the United States.
12. Updates to This Policy
13. Google User Data
RevBind integrates with Google to let sales agents manage their prospect communication and scheduling from inside our app. This section describes how we access, use, store, and share data from your Google Account.
Google services we integrate with
Google Calendar — to create, update, cancel, and check availability for appointments with your prospects. Gmail — to read, send, and organize email correspondence with your prospects from a unified inbox inside RevBind.
Scopes we request and why
We request the minimum scopes necessary to deliver the above features. You will be asked to grant each of the following during connection: https://www.googleapis.com/auth/calendar.events — Create, read, update, and delete events on your calendar. When the RevBind AI assistant books, reschedules, or cancels an appointment, we write the event directly to your Google Calendar. https://www.googleapis.com/auth/calendar.freebusy — Read your free/busy blocks (no event content). Used to check your real availability before proposing times to a prospect, so we never double-book. https://www.googleapis.com/auth/gmail.modify — Read, send, and label email in your Gmail account. Used to let you reply to prospects from your own Gmail address inside RevBind, display inbound replies, and apply Gmail labels that reflect RevBind pipeline state. We do not request or use any Google scope beyond the three listed above.
How we use your Google data
Calendar event data is used only to display, create, update, and delete appointments scheduled through RevBind. We do not read, copy, or analyze the content of events you created outside of RevBind. Calendar free/busy data is used only at the moment you propose a meeting, to hide time slots that conflict with your existing calendar. Gmail message data is used only to display your Gmail inbox inside RevBind, to send email on your behalf, and to apply labels you select. Messages are fetched on demand; we do not bulk-download or index your mailbox. Attachments are cached in encrypted S3 storage (AWS) to render inline previews and deleted when your account is deleted. We do not use Google user data to train AI models, serve advertisements, or for any purpose other than providing the features described above.
Who we share Google data with
We do not sell, rent, or share Google user data with third parties. Google user data is processed only by Amazon Web Services (AWS), which hosts our application infrastructure, and Google APIs, the source of the data itself. All transfers use encrypted connections (TLS 1.2+). We do not transfer Google user data to marketing platforms, data brokers, or any other third party.
How we store and protect Google data
All data is transferred over TLS 1.2 or higher. Data is stored on AWS infrastructure with AES-256 encryption. OAuth tokens are stored in AWS Secrets Manager, encrypted with AWS KMS, and used only to make API calls on your behalf. Access to production data is restricted to authorized RevBind engineers under least-privilege roles and logged for audit.
Retention and deletion
Cached Gmail data is retained only while your RevBind account is active. When you disconnect Google (Settings → Integrations → Disconnect), we revoke your OAuth token and delete all cached Google data within 30 days. When you delete your account, all Google user data is permanently deleted within 30 days. You can also revoke access at any time at https://myaccount.google.com/permissions.
Limited Use disclosure
RevBind's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google data contact
Questions about how RevBind handles Google user data can be directed to privacy@revbind.com.
We may revise this Privacy Policy periodically.