Agent Onboarding Privacy & Data Assurance Policy
At REbbit, your privacy and data security is not just a feature — it's a foundational promise.
Here's exactly how we protect your data, leads, and activity on our platform.
1. Introduction
Rebbit.AI Private Limited (“Rebbit AI,” “we,” “our,” or “us”) operates an AI-powered real estate assistant platform available at https://rebbit.ai and through associated mobile applications (collectively, the “Platform”). This Privacy Policy describes how we collect, use, disclose, retain, and protect information in connection with the Platform and our services.
This Privacy Policy applies to all users of the Platform, including Agent Users and End Recipients, as defined below. By accessing or using the Platform, you acknowledge that you have read and understood this Privacy Policy.
Registered Entity Information
Indian Entity: Rebbit.AI Private Limited (Registration No. 29AAPCR2150N1ZS)
USA Entity: REBBITAI LLC
India Office: 53/B, Ward Number 57, 1st Main Road, JP Nagar Phase 3, Sarakki Industrial Layout, Bengaluru, Bengaluru Urban, Karnataka 560078, India
U.S. Office: 135, 505 E Huntland Drive, 1st Floor, Austin, Texas 78752, United States
Contact Email: hileads@rebbit.ai
2. Definitions and User Categories
2.1 Agent Users
“Agent Users” are licensed U.S. real estate professionals who subscribe to and use the Rebbit AI Platform to manage their real estate business communications, leads, appointments, and client interactions. Agent Users are data controllers with respect to the personal data of their clients and contacts that they input into or process through the Platform.
2.2 End Recipients
“End Recipients” are home buyers, home sellers, or other individuals who communicate with Agent Users via SMS text messages, voice calls, or email facilitated through the Rebbit AI Platform. End Recipients may interact with the Platform without creating an account or subscribing to the service.
2.3 Rebbit AI as Service Provider / Data Processor
With respect to personal data of End Recipients and client data processed on behalf of Agent Users, Rebbit AI acts as a service provider and data processor. Agent Users are the data controllers who determine the purposes and means of processing End Recipient data through the Platform. Rebbit AI processes such data solely on behalf of Agent Users and in accordance with their instructions, subject to applicable law.
With respect to Agent Users’ own account data and subscription information, Rebbit AI acts as the data controller.
3. Information We Collect
3.1 Information Collected from Agent Users
3.1.1 Account Registration and Identity Data
When an Agent User creates an account, we collect: full name; email address; phone number; real estate license number and state of licensure; brokerage name and affiliation; billing and payment information (processed through third-party payment processors); and login credentials. When an Agent User authenticates using Google or Microsoft single sign-on, we additionally collect basic profile information provided through identity scopes (see Sections 3.1.3 and 3.1.5), including the user’s name, email address, and profile identifier, solely for the purpose of authenticating the user and provisioning their Platform account.
3.1.2 Platform Usage Data
We collect data generated through use of the Platform, including: CRM entries, lead records, contact information entered by the Agent User; appointment and scheduling data; communication logs (SMS, voice call metadata, and email metadata); AI assistant configuration preferences; and analytics related to Platform feature usage.
3.1.3 Google API Data — Scopes and Purpose
When an Agent User connects their Google account, Rebbit AI requests access to the following Google API scopes. Each scope, its purpose, and the data it provides are described below:
What We Access: This scope grants read-only access to the Agent User’s Gmail inbox. However, Rebbit AI does not scan or process all emails in the inbox. During onboarding, the Agent User configures an “Allowed Sender List” — a specific set of email addresses (for example, lead@rebbit.ai or notifications@zillow.com) from which the Platform is authorized to process incoming messages. The Platform only reads and processes inbound emails that originate from email addresses on this Agent User-defined Allowed Sender List. All other emails in the inbox are ignored and are not accessed, read, or processed.
Why We Access It: Email data from allowed senders is accessed solely to detect inbound real estate inquiries (such as new lead notifications, property inquiry alerts, and showing requests) and to trigger the Platform’s automated workflow: notifying the Agent User of the new lead, initiating an AI-assisted outbound call to the prospect using the agent’s dedicated AI phone number, and scheduling an appointment on the agent’s calendar when confirmed.
How It Is Processed: Incoming emails from allowed senders are scanned programmatically using automated filters. Matched inquiries are parsed to extract relevant lead information (such as the prospect’s name, phone number, email address, property of interest, and inquiry details). This extracted lead data is stored in the Agent User’s CRM within the Platform. Raw email content is processed transiently and is not permanently stored on Rebbit AI servers (see Section 11.3 for retention details).
Email Data Is NOT Sold. We do not sell, rent, lease, or trade any email data obtained via the Gmail API to any third party for any purpose whatsoever.
Email Data Is NOT Used to Train AI Models. We do not use email data obtained via the Gmail API to train, improve, or develop generalized or non-personalized artificial intelligence or machine learning models. Email data is used exclusively to provide and improve the user-facing features of the Platform as described in this Privacy Policy.
3.1.4 How the Platform Uses Google Data — End-to-End Workflow
During onboarding, the Agent User connects their Google account and configures an Allowed Sender List specifying the email addresses from which the Platform should process incoming messages (e.g., lead@rebbit.ai, alerts@realtor.com).
When a new email arrives in the Agent User’s Gmail inbox from an address on the Allowed Sender List, the Platform detects and reads the email using the gmail.readonly scope.
The Platform parses the email to extract lead information, including the prospect’s name, phone number, email address, and property interest details. This information is stored in the Agent User’s CRM.
The Platform’s AI voice assistant initiates an outbound call to the prospect using the dedicated AI phone number assigned to the Agent User. The call includes required TCPA disclosures (see Section 8).
If the prospect confirms interest and agrees to schedule an appointment, the AI assistant checks the Agent User’s Google Calendar for availability using the calendar.readonly scope.
The AI assistant creates a new calendar event on the Agent User’s Google Calendar using the calendar (read/write) scope, including appointment details such as date, time, location, and prospect contact information.
The Agent User is notified of the new lead and the scheduled appointment through the Platform dashboard and via their preferred notification method.
3.1.5 Microsoft Graph API Data — Scopes and Purpose
When an Agent User connects their Microsoft account, Rebbit AI requests access to the following Microsoft Graph API scopes:
User.Read: This scope allows the Platform to read the signed-in Agent User’s basic profile information, including display name, email address, and user identifier. This data is used solely for authentication, account provisioning, and linking the Microsoft account to the Agent User’s Rebbit AI account.
openid, profile, and email: These are standard OpenID Connect identity scopes. The openid scope enables authentication using the Microsoft identity platform. The profile scope provides access to the user’s basic profile information (name, preferred username). The email scope provides the user’s email address. These scopes are used exclusively for authenticating the Agent User, provisioning their Platform account, and displaying their identity within the Platform interface. No email content, calendar data, or other mailbox data is accessed through these scopes.
Mail.Read: This scope grants read-only access to the Agent User’s Microsoft Outlook mailbox. The Platform’s use of this scope mirrors the Gmail integration described in Section 3.1.3(b): the Platform processes only inbound emails that originate from email addresses on the Agent User’s configured Allowed Sender List. All other emails are ignored. Email data from allowed senders is processed to detect real estate inquiries and extract lead information for the automated workflow described in Section 3.1.4. The same protections apply: Outlook email data is not sold, not used for advertising, and not used to train generalized AI or ML models.
Calendars.ReadWrite: This scope grants read and write access to the Agent User’s Microsoft Outlook Calendar. It serves the same purpose as the Google Calendar scopes described in Sections 3.1.3(c) and 3.1.3(d): the Platform reads existing calendar events to check availability and detect scheduling conflicts, and writes new calendar events when the AI assistant schedules appointments on behalf of the Agent User.
offline_access: This scope allows the Platform to maintain access to previously authorized Microsoft data without requiring the Agent User to re-authenticate for each session. This ensures continuous service delivery, including uninterrupted monitoring of the Allowed Sender List and timely lead detection. The Agent User may revoke this access at any time.
3.1.6 Calendar Data
When an Agent User connects Google Calendar or Microsoft Outlook Calendar, we access calendar event data to provide scheduling, appointment management, availability checking, and conflict-detection features. Calendar data is used solely for Platform functionality and is not shared with unauthorized third parties.
3.2 Information Collected from End Recipients
We may collect the following information about End Recipients through their interactions with Agent Users via the Platform: name and contact information (phone number, email address) as provided by Agent Users or as extracted from inbound lead emails from the Agent User’s Allowed Sender List; SMS message content sent to and received from Agent Users via the Platform; voice call metadata (call duration, timestamps, phone numbers) and, where applicable, call recordings or AI-generated transcripts from calls placed by the Agent User’s dedicated AI phone number; email message content and metadata where the End Recipient communicates with an Agent User through a connected email integration; and property interest information and other real estate-related details shared during communications.
Rebbit AI collects and processes End Recipient data on behalf of and at the direction of Agent Users. End Recipients with questions about how their data is handled should contact the Agent User with whom they are communicating.
3.3 Automatically Collected Information
We automatically collect: IP address and approximate geolocation; device type, operating system, and browser type; pages visited and features used within the Platform; cookies and similar tracking technologies (see Section 10); and crash reports and diagnostic data.
4. Google API Services User Data Policy Compliance
4.1 Limited Use Disclosure
In accordance with the Google API Services User Data Policy and the Limited Use requirements, Rebbit AI:
Limits its use of data obtained through Google APIs to providing or improving user-facing features that are prominent in the Platform’s user interface. All other uses of such data are prohibited.
Does not transfer data obtained through Google APIs to third parties unless: (i) it is necessary to provide or improve user-facing features that are prominent in the Platform’s user interface; (ii) it is necessary to comply with applicable laws or regulations; (iii) it is necessary for security purposes, such as investigating abuse; or (iv) the data (including derivations) is aggregated and anonymized and used for internal operations in accordance with applicable privacy and legal requirements.
Does not use data obtained through Google APIs for serving advertisements, including retargeting, personalized advertising, or interest-based advertising.
Does not use data obtained through Google APIs to determine creditworthiness or for lending purposes.
Does not allow humans to read user data obtained through Google APIs unless: (i) the user has provided affirmative consent to view specific data; (ii) it is necessary for security purposes (such as investigating a bug or abuse); (iii) it is necessary to comply with applicable law; or (iv) the data (including derivations) is aggregated and anonymized and used for internal operations.
Does not use data obtained through Google APIs to train, improve, or develop generalized or non-personalized artificial intelligence or machine learning models.
4.2 Scope of Google API Data Usage
Data obtained through the Gmail API (gmail.readonly scope) is used exclusively to: detect inbound real estate inquiries from the Agent User’s configured Allowed Sender List; extract lead information (prospect name, contact details, property interest) from those emails; trigger the Platform’s automated lead response workflow, including AI-assisted outbound calls and appointment scheduling; and notify the Agent User of new leads within the Platform dashboard.
Data obtained through the Google Calendar API (calendar and calendar.readonly scopes) is used exclusively to: read existing calendar events to check agent availability and detect scheduling conflicts; create new calendar events when appointments are confirmed through the AI assistant; update or cancel calendar events when appointments are rescheduled or canceled; and send appointment reminders and confirmations.
Data obtained through identity scopes (openid, userinfo.email) is used exclusively to: authenticate the Agent User; provision and link the Agent User’s Rebbit AI account; and display the Agent User’s identity within the Platform.
5. Microsoft Graph API Data Protection
When Agent Users connect their Microsoft accounts, Rebbit AI accesses data through Microsoft Graph API using delegated permissions authorized by the Agent User. The following protections apply:
Data accessed through Microsoft Graph API is used solely to provide the Platform’s core features as described in this Privacy Policy.
Identity data (User.Read, openid, profile, email) is used exclusively for authentication and account provisioning. No mailbox or calendar data is accessed through these scopes.
Mail data (Mail.Read) is accessed in read-only mode and is processed only for inbound emails from the Agent User’s configured Allowed Sender List, for the purpose of detecting real estate inquiries and extracting lead information.
Calendar data (Calendars.ReadWrite) is used exclusively for availability checking, scheduling conflict detection, and creating, updating, or canceling appointment events on behalf of the Agent User.
Refresh token access (offline_access) is used solely to maintain continuous service delivery without requiring repeated re-authentication, and may be revoked by the Agent User at any time.
Data accessed through Microsoft Graph API is not sold, not used for advertising, and not used to train generalized AI/ML models.
Rebbit AI complies with the Microsoft APIs Terms of Use and maintains proper retention and deletion policies for data accessed through Microsoft Graph API.
Agent Users may revoke Microsoft Graph API access at any time through their Platform account settings or through their Microsoft account security settings at https://account.live.com/consent/Manage.
6. How We Use Information
We use information collected through the Platform for the following purposes:
Service Delivery: To provide, operate, maintain, and improve the Platform and its features, including AI voice assistant, SMS messaging, email integration, calendar integration, CRM, lead management, and appointment scheduling.
Lead Detection and Response: To monitor inbound emails from addresses on the Agent User’s configured Allowed Sender List, detect real estate inquiries, extract lead information, and initiate the automated response workflow (including AI-assisted outbound calls to prospects and appointment scheduling).
AI-Assisted Outbound Calling: To place outbound calls to prospects using the dedicated AI phone number assigned to each Agent User, for the purpose of following up on detected real estate inquiries, qualifying leads, and scheduling appointments on the agent’s behalf.
Appointment Scheduling and Calendar Management: To check the Agent User’s calendar availability, create appointment events on the Agent User’s connected Google Calendar or Microsoft Outlook Calendar, and manage scheduling changes.
Communication Facilitation: To facilitate communications between Agent Users and End Recipients via SMS, voice calls, and email, including AI-assisted communications initiated by Agent Users.
Account Administration: To authenticate Agent Users, manage accounts, process subscription payments, and provide customer support.
Platform Improvement: To analyze usage patterns and improve Platform features, functionality, and user experience, using only aggregated and anonymized data where applicable.
Security and Compliance: To detect, prevent, and address fraud, security incidents, and technical issues, and to comply with applicable laws, regulations, and legal processes.
Legal Obligations: To comply with applicable federal, state, and local laws, including the Telephone Consumer Protection Act (TCPA), CAN-SPAM Act, and applicable state privacy laws.
Zero AI Training on User Data: We do not use Agent User or End Recipient data (including email content, call transcripts, or SMS messages) to train, improve, or develop generalized or non-personalized AI/ML models. Our AI assistant is configured to use data solely for the benefit of the specific Agent User to whom the data belongs.
7. SMS Messaging Disclosures (A2P 10DLC Compliance)
7.1 SMS Messaging Program Description
Rebbit AI facilitates Application-to-Person (A2P) SMS text messaging on behalf of Agent Users to End Recipients for the following purposes: real estate inquiry responses; property information and updates; appointment confirmations, reminders, and scheduling communications; lead follow-up communications; and other real estate transaction-related messages initiated by Agent Users.
7.2 Consent and Opt-In
End Recipients receive SMS messages from Agent Users via the Rebbit AI Platform only when:
the End Recipient has provided prior express consent to receive SMS text messages from the Agent User, such as by submitting a web form, texting a keyword, or otherwise affirmatively opting in to receive messages;
the End Recipient has initiated a communication with the Agent User (for example, by submitting an online lead inquiry form that includes a phone number); or
the Agent User has an established business relationship with the End Recipient and has informed the End Recipient that they may receive SMS communications regarding their real estate interests.
7.3 Message Frequency and Rates
Message frequency may vary depending on the nature and context of the real estate transaction and the Agent User’s communication practices. Message and data rates may apply. Please contact your wireless carrier for details about your messaging plan and any applicable charges.
7.4 Opt-Out Instructions
End Recipients may opt out of receiving SMS messages at any time by replying STOP to any message received through the Platform. Upon receipt of a STOP request, the End Recipient will receive a single confirmation message and no further SMS messages will be sent from that Agent User via the Platform unless the End Recipient re-opts in.
7.5 Help and Support
End Recipients may reply HELP to any message received through the Platform to receive information about the SMS messaging program, including the Agent User’s identity, opt-out instructions, and a support contact method. End Recipients may also contact Rebbit AI support at hileads@rebbit.ai.
7.6 SMS Data Sharing
We do not sell, share, or disclose SMS opt-in data, phone numbers, or SMS message content to third parties for marketing or advertising purposes. SMS data is shared only with the Agent User on whose behalf the message was sent and with telecommunications carriers and messaging infrastructure providers as necessary to deliver the messages.
7.7 Carrier Compliance
Rebbit AI registers all SMS messaging campaigns through The Campaign Registry (TCR) in compliance with A2P 10DLC requirements. All messaging is conducted through registered 10-digit long code numbers with appropriate brand and campaign registration as required by U.S. mobile carriers.
8. AI Voice Call Disclosures
8.1 AI Voice Assistant Description
The Rebbit AI Platform provides an AI-powered voice assistant that handles inbound and outbound telephone calls on behalf of Agent Users. Each Agent User is assigned a dedicated AI phone number. When the Platform detects a new real estate lead (through the email integration or manual entry), the AI voice assistant places an outbound call to the prospect from the Agent User’s dedicated AI phone number to follow up on the inquiry, qualify the lead, and schedule an appointment.
8.2 AI Voice Disclosure
All outbound calls placed by the AI voice assistant will clearly disclose at the beginning of the call that the call is being made using AI-generated voice technology. The disclosure will identify the Agent User on whose behalf the call is being made and that the call is facilitated by Rebbit AI.
All outbound calls using the AI voice assistant require prior express consent from the End Recipient, or prior express written consent where the call constitutes telemarketing, in accordance with TCPA requirements.
The AI voice assistant will provide an automated opt-out mechanism allowing call recipients to request placement on a do-not-call list.
All AI voice calls will comply with calling hour restrictions, limiting calls to between 8:00 a.m. and 9:00 p.m. in the called party’s local time zone.
Agent Users are responsible for ensuring that appropriate consent exists from End Recipients before the Platform initiates outbound AI voice calls. When a lead is detected from the Agent User’s Allowed Sender List (for example, a lead submission through a third-party platform), the consent obtained at the point of the End Recipient’s original inquiry submission is relied upon by the Agent User.
8.3 Call Recording and Transcription
Where permitted by applicable law and with appropriate notice and consent, calls facilitated through the Platform may be recorded and/or transcribed using AI technology. Call recordings and transcripts are stored securely and are accessible only to the Agent User on whose behalf the call was placed. Rebbit AI does not use call recordings or transcripts to train generalized AI or ML models.
9. How We Share Information
Rebbit AI does not sell personal information. We share information only in the following limited circumstances:
With Agent Users: End Recipient data, lead information extracted from Allowed Sender List emails, and communication records are shared with the Agent User on whose behalf the communication was facilitated.
Service Providers: We share information with third-party service providers who assist in operating the Platform, including: cloud hosting and infrastructure providers; telecommunications carriers and messaging infrastructure providers (for SMS and voice calls); payment processors; email delivery services; and analytics providers (using only aggregated, de-identified data). All service providers are contractually obligated to use personal data only for the purpose of providing services to Rebbit AI and in accordance with this Privacy Policy.
Legal Compliance: We may disclose information if required to do so by law, regulation, legal process, or governmental request, including in response to lawful requests by public authorities for national security or law enforcement purposes.
Business Transfers: In the event of a merger, acquisition, reorganization, bankruptcy, or sale of all or a portion of our assets, personal data may be transferred as part of such transaction. We will notify affected users of any change in ownership or control of their personal data.
With User Consent: We may share information for any other purpose disclosed to you at the time of collection or with your consent.
10. Cookies and Tracking Technologies
We use cookies and similar tracking technologies to operate and improve the Platform. These include: essential cookies necessary for Platform functionality and authentication; performance cookies to analyze usage patterns and improve service; and preference cookies to remember user settings and preferences.
We do not use tracking technologies for cross-site advertising or retargeting purposes. Users may manage cookie preferences through their browser settings.
11. User Rights and Controls
11.1 Disconnecting Gmail or Outlook
Agent Users may disconnect their Gmail or Microsoft Outlook integration at any time by navigating to the Platform’s account settings and selecting the option to disconnect the applicable email or calendar integration. Upon disconnection:
- The Platform will immediately cease accessing the Agent User’s email and/or calendar data;
- The Allowed Sender List configuration will be deactivated;
- No further inbound emails will be processed;
- Previously extracted lead information stored in the CRM will be retained unless the Agent User requests its deletion;
- Any cached email data will be purged within 72 hours.
Agent Users may also revoke access through their Google Account security settings (https://myaccount.google.com/permissions) or their Microsoft Account security settings (https://account.live.com/consent/Manage).
11.2 Account Deletion
Agent Users may delete their accounts by: (a) using the account deletion feature in the Platform’s account settings; or (b) submitting a written request to hileads@rebbit.ai. Upon account deletion, we will:
- Deactivate the account and cease all data processing within 24 hours;
- Permanently delete all personal data associated with the account within 30 days, subject to legal retention requirements;
- Disconnect all Google and Microsoft integrations and revoke all API tokens;
- Deactivate the Agent User’s dedicated AI phone number;
- Provide confirmation of deletion upon request.
11.3 Data Deletion Requests
Both Agent Users and End Recipients may request deletion of their personal data by contacting us at hileads@rebbit.ai. We will verify the identity of the requestor and process the request within thirty (30) days, or such shorter period as required by applicable law. Where Rebbit AI processes data on behalf of an Agent User, deletion requests from End Recipients may be directed to the applicable Agent User.
11.4 Additional Rights
Depending on your jurisdiction, you may have additional rights, including: the right to access your personal data; the right to correct inaccurate personal data; the right to restrict processing of your personal data; the right to data portability; the right to object to processing; and the right not to be subject to automated decision-making. To exercise any of these rights, contact us at hileads@rebbit.ai.
12. Security Measures
Rebbit AI implements and maintains commercially reasonable administrative, technical, and physical security measures designed to protect personal data from unauthorized access, disclosure, alteration, and destruction. These measures include:
(a) Access controls including role-based access control (RBAC), multi-factor authentication for administrative access, and principle of least privilege for all system access.
(b) Regular security assessments, vulnerability scanning, and penetration testing.
(c) Secure software development lifecycle practices, including code review and security testing.
(d) Employee training on data protection and security best practices.
(e) Incident response procedures for timely detection, investigation, and notification of security breaches.
(f) Logging and monitoring of access to personal data and system resources.
(g) OAuth tokens and API credentials are stored encrypted and are never exposed to unauthorized personnel.
No method of transmission over the Internet or method of electronic storage is completely secure. While we strive to protect your personal data, we cannot guarantee its absolute security.
13. Children’s Privacy
The Rebbit AI Platform is designed for use by licensed real estate professionals and is not directed at individuals under the age of eighteen (18). We do not knowingly collect personal information from children under the age of eighteen (18). If we become aware that we have inadvertently collected personal information from a child under the age of eighteen (18), we will take reasonable steps to delete such information promptly.
If you are a parent or guardian and believe that your child has provided personal information to Rebbit AI, please contact us at hileads@rebbit.ai so that we may take appropriate action.
For purposes of compliance with the Children’s Online Privacy Protection Act (COPPA), we do not knowingly collect personal information from children under the age of thirteen (13). The Platform is not intended for use by any person under the age of eighteen (18).
14. State-Specific Privacy Rights
14.1 California Residents (CCPA/CPRA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA), including: the right to know what personal information is collected, used, disclosed, and sold; the right to delete personal information; the right to opt out of the sale or sharing of personal information (Rebbit AI does not sell personal information); the right to correct inaccurate personal information; the right to limit use of sensitive personal information; and the right to non-discrimination for exercising your privacy rights. To exercise these rights, contact us at hileads@rebbit.ai or write to: Rebbit.AI Private Limited, 135, 505 E Huntland Drive, 1st Floor, Austin, Texas 78752.
14.2 Virginia Residents (VCDPA)
If you are a Virginia resident, the Virginia Consumer Data Protection Act (VCDPA) provides you with the right to: access your personal data; correct inaccuracies; delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai. If we decline your request, you may appeal by emailing hileads@rebbit.ai with the subject line “VCDPA Appeal.”
14.3 Colorado Residents (CPA)
If you are a Colorado resident, the Colorado Privacy Act (CPA) provides you with the right to: access, correct, and delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai.
14.4 Connecticut Residents (CTDPA)
If you are a Connecticut resident, the Connecticut Data Privacy Act (CTDPA) provides you with the right to: access, correct, and delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai.
14.5 Utah Residents (UCPA)
If you are a Utah resident, the Utah Consumer Privacy Act (UCPA) provides you with the right to: access and delete your personal data; obtain a portable copy; and opt out of targeted advertising and sale of personal data. To exercise these rights, contact us at hileads@rebbit.ai.
14.6 Texas Residents (TDPSA)
If you are a Texas resident, the Texas Data Privacy and Security Act (TDPSA) provides you with the right to: access, correct, and delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai.
14.7 Oregon Residents (OCPA)
If you are an Oregon resident, the Oregon Consumer Privacy Act (OCPA) provides you with the right to: access, correct, and delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai.
14.8 Montana Residents (MCDPA)
If you are a Montana resident, the Montana Consumer Data Privacy Act (MCDPA) provides you with the right to: access, correct, and delete your personal data; obtain a portable copy; and opt out of targeted advertising, sale of personal data, and profiling. To exercise these rights, contact us at hileads@rebbit.ai.
14.9 Other States
Residents of other states with comprehensive privacy laws enacted after the date of this Privacy Policy may have similar rights. Please contact us at hileads@rebbit.ai to exercise any applicable rights. We will evaluate your request in accordance with the laws of your state of residence.
15. Do Not Track Signals
The Platform does not currently respond to “Do Not Track” (DNT) browser signals, as there is no consistent industry standard for handling DNT requests. If a standard is adopted in the future, we will update this Privacy Policy accordingly.
16. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify Agent Users by email and/or by posting a prominent notice on the Platform prior to the changes becoming effective. Your continued use of the Platform after the effective date of any changes constitutes your acceptance of the updated Privacy Policy.
17. Contact Information
If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:
Rebbit.AI Private Limited
U.S. Office: 135, 505 E Huntland Drive, 1st Floor, Austin, Texas 78752, United States
India Office: 53/B, Ward Number 57, 1st Main Road, JP Nagar Phase 3, Sarakki Industrial Layout, Bengaluru, Bengaluru Urban, Karnataka 560078, India
Email: hileads@rebbit.ai
At-a-Glance Privacy Guarantees
A quick summary of the privacy, security, and data ownership
guarantees you receive by default.