Privacy Policy

Your information matters. Here is how we handle it.

Last Updated: November 17, 2026

Birch & Co. Brokerage LLC respects the trust agents and clients place in us when they use our Agent Hub, brokerage services, and connected tools. This policy explains what information we may collect, how we use it, when it may be shared, how long we keep it, and the choices available to you.


1. Information We Collect

The information we collect depends on how you interact with Birch. Some information is provided directly by you; other information is created when you use the Agent Hub, connect an account, or complete a transaction.

1.1 Agent and Account Information

When an agent joins the brokerage or uses the Agent Hub, we may collect information needed to establish and administer the account, support brokerage affiliation, administer commissions, and meet brokerage requirements, including:

  • Full legal name, contact details, date of birth, and mailing or residential address.
  • Real estate license details, license status, license number, and expiration dates.
  • REALTOR® association or MLS membership information and related professional details.
  • Tax, payment, and commission-disbursement information, which may include taxpayer identification details and bank account information where needed.
  • Team membership, brokerage plan, account preferences, and onboarding information.

Sensitive information, such as Social Security numbers or banking details, is requested only when needed for a legitimate brokerage, payment, tax, identity, or legal purpose. Access is limited to authorized personnel and systems with a business need.

1.2 Client and Transaction Information

When agents use Birch systems to manage real estate business, we may process information included in transaction files and client records, such as:

  • Names and contact information for buyers, sellers, landlords, tenants, and other transaction participants.
  • Listing agreements, buyer representation agreements, purchase contracts, lease agreements, addenda, and disclosures.
  • Property addresses, transaction dates, offer terms, signatures, and closing documents.
  • Compliance records, title or closing communications, commission details, and documents required for the brokerage file.

1.3 Information Created Through Platform Use

To operate, troubleshoot, and protect the Agent Hub, we may collect routine technical and activity information, including:

  • IP address, browser, device type, operating system, and session information.
  • Login activity, page and feature usage, file access events, and system request logs.
  • Security events, error reports, and information needed to investigate suspected misuse.

1.4 Connected Email Accounts and Other Integrations

If an agent chooses to connect an external email account or another service, Birch may collect or process the information needed to establish and operate that connection. For an email account, this may include:

  • Email address, account username, provider name, and IMAP/SMTP server settings, such as hostnames, ports, and connection-security settings.
  • Authentication information supplied for the connection, such as a password, provider-generated app password, or authorization token, depending on the provider and authentication method.
  • Email message content and related message information, such as sender and recipient addresses, subject lines, dates, message identifiers, and conversation/thread headers, when needed to synchronize and match lead replies.
  • Synchronization status, mailbox checkpoints, processing results, and error information needed to operate and troubleshoot the connection.

Email connections use standard IMAP to retrieve incoming messages and SMTP to send messages when an agent uses the applicable Birch features. Agents may connect providers that support the required protocols and authentication method. Some providers require app-specific passwords or OAuth; others may permit a regular account password. Authentication requirements are set by the email provider, not by Birch.

Birch may also process Google account information and Google API data for separate Google integrations that an agent chooses to connect, such as supported Google Calendar synchronization or Google Contacts features. Birch's lead-reply email synchronization is not dependent on Gmail API access or the Gmail read-only OAuth scope.

If an agent connects their own Twilio account, Birch may also process Twilio account identifiers and API credentials or tokens, configured phone numbers, communication settings, message or call content, sender and recipient details, delivery or call status, timestamps, webhook or event data, and related error or technical information. If an agent enables a feature that records or transcribes calls or voicemail, the associated recording or transcript may also be processed. Agents connect and use their own Twilio accounts; Birch does not provide a shared Twilio account for agents.

Other integrations may process information such as property addresses, search criteria, or content submitted to Birch Intelligence for AI-assisted tasks.

2. How We Use Information

We use information to run the brokerage, provide the tools agents request, support clients and transactions, and keep our systems dependable. For example, information may be used to:

  • Brokerage operations and compliance: Review transaction files, track required documents, monitor license information, and complete broker oversight.
  • Commission and tax administration: Calculate applicable fees, prepare commission authorizations, maintain payment records, and support required tax reporting.
  • Agent Hub features: Provide transaction management, CRM functions, lead organization, analytics, document tools, email synchronization, and other features agents choose to use.
  • Email synchronization and communications: Connect an agent's chosen email provider, retrieve new messages for applicable lead-reply workflows, associate messages with lead records, and send agent-authorized email through the agent's configured SMTP account.
  • Agent-connected Twilio communications: Enable supported calling or messaging features through an agent's own Twilio account, process the information needed to route and manage those communications, and display relevant statuses or activity in Birch. The agent's Twilio account is used for the applicable Twilio services and charges.
  • Birch Intelligence: Generate requested email drafts, lead summaries, suggested next steps, and other AI-assisted content. Relevant message content and context may be sent to OpenAI for processing when an agent requests an AI feature. Agents should review AI-generated content before relying on it or sending it.
  • Property research and CMA tools: Retrieve and display property, rental, and comparable-property information to help agents research and evaluate real estate.
  • Connected Google features: Provide the specific Google Calendar, Google Contacts, or other Google API features that an agent has chosen to connect and authorize.
  • Security and support: Authenticate accounts, investigate suspicious activity, fix errors, respond to support requests, and protect the platform.

3. Services That Help Power Birch

Some Birch features rely on outside providers. When an agent uses one of these features, the information needed to complete the requested action may be processed by that provider under its own privacy policy and service terms. We aim to share only information reasonably needed for the feature being used.

Email Providers — IMAP and SMTP Connections

Agents may connect an email account from a provider that supports the protocols and authentication methods required by Birch. Birch uses IMAP to retrieve incoming messages for supported synchronization and lead-reply workflows, and SMTP to send email when an agent uses an applicable sending feature. The provider may be Gmail, Zoho, Apple iCloud, Microsoft, or another compatible service; availability and authentication requirements depend on that provider.

The agent's email provider continues to host and control the agent's mailbox under its own terms. Birch processes the message information made available through the connected account to provide the requested features. Birch does not need Gmail API read-only authorization to perform this IMAP-based lead-reply workflow. Email account passwords, app passwords, or tokens are connection credentials; they are not submitted to OpenAI as part of AI drafting.

Agents are responsible for ensuring they have the right to connect their email accounts and use the messages and contact information processed through Birch. Agents should follow applicable privacy, marketing, consent, and email communication requirements.

RentCast — Property Data and CMA

Birch may use RentCast to retrieve property details, rental information, comparable-property data, and other real estate information requested through CMA and property evaluation tools. This may involve sending property addresses or search criteria to RentCast. Returned information is intended to assist an agent's research; it is not an appraisal, inspection, or guarantee of value, rent, condition, or investment performance. Agents should independently review and verify important information before sharing it with clients or relying on it when advising them.

Provider information: RentCast Privacy Policy · RentCast API Terms

OpenAI — Birch Intelligence

Birch Intelligence uses the OpenAI API to provide AI-assisted features. When an agent requests an AI-generated lead-reply draft, Birch may send the relevant email message content and the context needed for the requested task to OpenAI for processing. Other Birch Intelligence features may process information that an agent submits or makes available to the feature. Email account credentials, including IMAP/SMTP passwords and app passwords, are not part of the content sent to OpenAI for drafting.

The AI-generated suggestion is returned to Birch and presented to the agent for review. The agent decides whether to edit, approve, or send the response. When an agent chooses to send an email through the connected email feature, Birch uses the agent's configured SMTP connection. AI drafting does not itself authorize Birch or OpenAI to send an email.

OpenAI states that data submitted through its API is not used to train or improve its models by default unless the API customer explicitly opts in. OpenAI may retain API content in abuse-monitoring logs for up to 30 days by default, subject to exceptions described by OpenAI. Retention of application state may also depend on the API endpoint, features used, and account settings. Birch does not promise zero retention by OpenAI unless the applicable eligibility and account controls have been confirmed and enabled.

Agents should avoid submitting sensitive information that is not necessary for the requested task and should review AI-generated content before using it.

Provider information: OpenAI API Data Controls

Twilio — Agent-Connected Communications

Birch supports communication features that allow an agent to connect the agent's own Twilio account using credentials or API configuration supplied by that agent. Birch uses the connection to provide the Twilio-enabled calling or messaging functions the agent chooses to use. The agent, not Birch, supplies and controls the connected Twilio account and is responsible for its account relationship, billing, phone numbers, configuration, and compliance with applicable communication laws and Twilio terms.

Depending on the feature used, Birch and Twilio may process account identifiers, API credentials or tokens, phone numbers, message or call content, sender and recipient details, timestamps, delivery receipts, call status, webhook or event information, and technical logs needed to operate, troubleshoot, and display communication activity. If an agent enables a feature that records or transcribes calls or voicemail, the associated recording or transcript may also be processed. Birch does not represent that every communication is recorded or transcribed; this depends on the feature and settings actually enabled by the agent.

Twilio provides the underlying communications infrastructure and processes information under its own terms and privacy practices. Information sent through Twilio is subject to Twilio's handling and retention practices as well as the agent's configuration. Birch does not operate a single shared Twilio account for all agents. Agents should protect their API credentials, use only authorized contact lists, obtain any legally required consent, and follow applicable rules for calls, texts, recording, and do-not-call or opt-out requests.

Provider information: Twilio Privacy Notice · Twilio Terms of Service

Google APIs — Connected Google Services

If an agent connects a Google account, Birch accesses Google user data only for the Google features the agent chooses to connect and authorize, such as supported Google Calendar synchronization or Google Contacts functionality. The specific information accessed depends on the Google API scopes and permissions presented during authorization. Birch's IMAP-based lead-reply email synchronization does not use the Gmail API or the Gmail read-only OAuth scope.

Google user data is used only to provide or support the authorized, user-facing Google feature. It is not sold, used for advertising, or used to train or improve generalized AI or machine-learning models. Google API data obtained through Calendar, Contacts, or another Google integration is not used as input to Birch Intelligence unless a feature specifically requires it and the use has been disclosed and authorized. Separately, when an agent connects a Gmail mailbox through IMAP and requests an AI-generated email reply, the relevant email message content may be sent to OpenAI as described in the OpenAI section above. That email workflow uses the agent's mail connection, not Gmail API authorization.

Birch's use of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements where applicable. Access is limited to the scopes required for the Google features the agent has authorized.

Google data retention and deletion

Birch retains Google-derived information only for as long as reasonably necessary to provide the Google feature for which it was obtained, maintain the agent's requested synchronization, meet applicable legal or regulatory obligations, resolve disputes, and protect the service. Retention may differ by data type and feature. Google data may be deleted earlier when an agent uses an available deletion control or makes a verified deletion request, unless Birch is required or permitted to retain it for a stated legal, security, or operational reason.

Disconnecting a Google integration stops Birch's future access through that connection. Disconnecting does not necessarily delete every previously imported or synchronized record, transaction record, backup copy, or item retained by an independent provider. Agents should use available in-product deletion controls or contact Birch to request deletion of Google-derived information held by Birch. Google continues to retain information in the agent's own Google account under Google's policies.

Policy information: Google API Services User Data Policy · Google OAuth Verification Requirements

Third-party services have their own rules

Email providers, Twilio, RentCast, OpenAI, Google, hosting providers, and other integrated services may collect or process information under their own terms and privacy notices. Their services, features, and retention practices may change. Birch does not control every aspect of a third-party provider's systems or guarantee uninterrupted availability.

4. When Information May Be Shared

We do not sell agent or client personal information to data brokers or outside marketers. We may share information when it is needed to provide brokerage services, operate the Agent Hub, complete a transaction, protect people and systems, or meet a legal obligation.

Information may be shared with:

  • Service providers: Technology, hosting, AI, email, analytics, payment, identity, document, property-data, and other vendors that help us operate our services. They may process information as needed to provide their services and under the terms that apply to the relationship.
  • Title companies and closing professionals: Transaction documents, commission authorizations, and closing details needed to complete a transaction.
  • Regulators and professional organizations: Information required for DBPR, MLS, REALTOR® association, audit, or other applicable regulatory and professional obligations.
  • Law enforcement and legal proceedings: Information when required by law, valid legal process, or when reasonably necessary to investigate fraud, protect safety, or defend legal rights.
  • Business transfers: Information involved in a merger, restructuring, financing, or sale of all or part of the business, subject to applicable legal requirements and appropriate safeguards.

We do not authorize service providers to use brokerage or client information for their own unrelated marketing. We do not share mobile numbers, text-message opt-in data, or SMS consent records with third parties or affiliates for their own marketing or promotional purposes. Information may still be shared with communications providers and carriers as needed to deliver messages and operate a service, if such messaging features are made available.

5. Client Funds and Escrow

Birch & Co. does not hold or manage client escrow funds. This helps keep client funds separate from brokerage operating accounts.

  • The brokerage does not maintain a central escrow bank account for client deposits.
  • Agents should not enter or store payment-card or bank-account credentials for earnest money deposits in Birch systems.
  • Earnest money and other contract deposits must be delivered directly to the title company, escrow agent, or attorney identified in the contract.

Follow the contract instructions and applicable Florida requirements for every deposit. This section does not change any duties imposed by law or the transaction documents.

6. How We Protect Information

We use administrative, technical, and organizational safeguards designed to protect information from unauthorized access, loss, misuse, or disclosure. These measures may include access controls, authentication, encryption, monitoring, and restrictions on who can access brokerage records. Connected email credentials are used to authenticate the agent's configured mail connection and are not intentionally exposed in the Agent Hub interface or included in AI-drafting prompts.

No website, application, device, or method of transmitting information is completely risk-free. We work to protect the systems we operate, but cannot promise that a security incident will never occur.

Your part matters too

Keep your password private, use your own account, secure your devices, sign out on shared devices, and tell us promptly if you suspect unauthorized access. Use provider-recommended authentication methods, keep app passwords confidential, and revoke credentials with your email provider if you believe they have been exposed. Avoid accessing client files over open public Wi-Fi. When working remotely, use a trusted secure network or personal hotspot, and follow any additional brokerage security instructions.

7. Security Incidents and Florida Law

If we become aware of a suspected security incident, we will take reasonable steps to investigate, limit further exposure, secure affected systems, and determine what information may have been involved. Depending on the situation, those steps may include disabling credentials, restricting access, working with service providers, and preserving relevant records.

When a breach involving personal information is subject to the Florida Information Protection Act (FIPA), Birch will provide notices to affected individuals and government authorities as required by applicable law. Florida law generally requires notice to affected individuals as expeditiously as practicable and no later than 30 days after determining that a qualifying breach occurred, subject to statutory exceptions and permitted delays. The timing and recipients of any notice depend on the facts and legal requirements that apply.

Florida law: Florida Statutes, Section 501.171

8. How Long We Keep Information

We keep information for as long as reasonably needed to provide our services, maintain brokerage and transaction records, meet legal and tax obligations, resolve disputes, protect our systems, and enforce agreements. Retention periods vary by information type and purpose.

Florida real estate broker transaction records are generally subject to a five-year retention requirement under applicable Florida law. Some transaction and compliance records may therefore need to remain available after an agent leaves the brokerage or a client relationship ends. Other information, such as account logs, support requests, synchronized email content, and integration data, may follow different retention periods based on their purpose and applicable requirements.

Email account and synchronized message data

While an email account is connected, Birch may periodically retrieve new messages through IMAP, including through scheduled background synchronization and an agent-initiated sync action. Birch processes relevant message content and metadata to identify lead replies, associate messages with lead records, and support AI-generated response drafts. Birch may retain synchronized message information, associated drafts, and processing records in its systems for as long as reasonably needed to provide these features, maintain the agent's workspace, support brokerage operations, and meet legal or security requirements.

Disconnecting an email account stops future synchronization through that connection. Disconnecting does not, by itself, necessarily delete messages, drafts, lead records, transaction records, logs, or copies already stored in Birch's systems. Agents may use available deletion controls or contact Birch to request deletion of information that Birch is not required or otherwise permitted to retain. The email provider may continue to retain the original messages in the agent's mailbox under that provider's policies.

Twilio-connected communication data

Information processed through an agent's connected Twilio account may be retained by Birch or Twilio according to the feature used, the agent's settings, provider configuration, applicable legal requirements, and operational needs. Birch's retention of any communication content, activity details, or integration records depends on what the applicable Birch feature stores and how long that information is needed for the requested service, support, security, or legal obligations. Disconnecting Twilio stops future use of that connection through Birch, but does not itself delete records already held by Birch or Twilio. Agents may need to manage or request deletion from each service separately.

Google API data

Google-derived information is retained only for as long as reasonably necessary for the Google feature for which it was obtained, subject to applicable legal, regulatory, security, and operational needs. Disconnecting a Google integration stops future access through that connection but does not necessarily remove every previously synced record or backup. Agents may use available deletion controls or contact Birch to request deletion of Google-derived information maintained by Birch. Google retains information in the agent's own Google account under Google's policies.

When information is no longer needed and no legal, regulatory, security, or legitimate business reason requires it to be retained, we will take reasonable steps to delete it or make it no longer identify an individual. Copies may remain temporarily in protected backups or provider systems until their normal deletion cycles or contractual retention periods are completed. Where a legal or regulatory record must be retained, that record may remain even after an integration is disconnected.

9. Your Privacy Choices and Requests

You can contact us with questions or requests about personal information that Birch maintains. Depending on the information and applicable law, you may ask us to:

  • Confirm whether we maintain certain personal information about you.
  • Correct information that is inaccurate or out of date.
  • Request deletion of information when we are not required or otherwise permitted to retain it.
  • Ask about the categories of information we collect, use, or share.
  • Disconnect a connected email account, Google integration, or agent-connected Twilio account to stop future access or use through that connection in Birch.
  • Request deletion of synchronized email information, Google-derived information, Twilio-related information, or other connected-account data held by Birch, subject to applicable retention obligations.

Disconnecting an account may limit or disable features that rely on that connection. A disconnection request is different from a deletion request: previously synchronized information may remain until deleted through an available control or following a verified privacy request, unless Birch must or may retain it for a legal, regulatory, security, transaction, or other permitted purpose.

We may need to verify your identity or authority before completing a request. Some information cannot be deleted while it is needed for transaction records, legal compliance, tax reporting, security, dispute resolution, or other permitted purposes.

To submit a privacy request, contact compliance@birchandcobrokerage.com. Please do not email passwords, app passwords, full Social Security numbers, bank account details, or other highly sensitive information.

10. Changes to This Policy and Contact

We may update this policy as Birch's services, technology, integrations, or legal requirements change. When we make an update, we will post the revised policy here and update the date at the top. If a change materially affects how information is handled, we will provide additional notice when appropriate.

If you have a privacy question, want to make a request, or need help understanding how a connected service handles information, please contact us. We would rather help clarify than leave you guessing.

Birch & Co. Brokerage LLC

Privacy & Compliance

compliance@birchandcobrokerage.com