Data Safety

Breesy has completed a SOC 2 Type II audit and is SOC 2 Type II compliant. An independent auditor has examined and verified our controls for security, availability, and confidentiality over a sustained period of operation.

Reliability and availability. Breesy runs on multi-cloud, multi-region infrastructure with redundancy and failover, so the answering, intake, and communication your team depends on stays available even if a single cloud provider or region has an outage.

At Breesy LLC ("Breesy," "we," "our," or "us"), safeguarding your data is central to how we design, build, and operate our AI communication platform. This Data Safety page describes what data we collect, how we use it, how we protect it, and the controls available to you. It also includes required disclosures for Google OAuth and Google API integrations.

This page should be read alongside our Privacy Policy and Terms & Conditions.

1. What Data Breesy Collects

Breesy collects data in three categories:

1.1 Data You Provide

• Business / account information (name, company, email, phone)
• Staff directory information
• Call routing rules, business hours, and workflows
• Messages, support inquiries, demo requests

1.2 Data From Customer's End Users

When your customers call, text, or interact with Breesy's AI assistant, we may process:

• Caller name and phone number
• Call audio and metadata
• AI-generated transcripts
• Lead details or job request information
• Scheduling or appointment details provided voluntarily

We process this information on your behalf only.

1.3 Data from Integrations

If you authorize integrations (e.g., telephony, Slack, Teams, Google Calendar, Outlook, CRM systems), we may receive:

• Basic user profile information (e.g., name, email)
• Availability or scheduling metadata
• Job status or workflow triggers
• Calendar identifiers and event metadata (only for events created through Breesy)

We request and use only the minimum required data.

2. How Breesy Uses Data

We use data strictly to provide and improve our services, including:

• Answering and triaging calls
• Routing messages to your team
• Scheduling and updating appointments
• Generating transcripts and event summaries
• Improving AI accuracy and performance
• Detecting fraud or misuse
• Providing customer support
• Meeting legal compliance requirements

We do not sell or rent data, use it for advertising, or share it with third parties for the purpose of training AI or machine learning models.

3. How Breesy Protects Data

We use industry-standard security measures, including:

• Encryption in transit (HTTPS / TLS)
• Secure cloud infrastructure
• Role-based access controls
• Access logging and monitoring
• Firewalls and intrusion detection
• Regular security reviews
• Limited internal access on a need-to-know basis

We also comply with:

• Google API Services User Data Policy (including Limited Use requirements)
• Applicable U.S. data protection laws
• Industry best practices for SaaS security

4. How Breesy Shares Data

Breesy only shares data under these circumstances:

4.1 With Service Providers

Trusted vendors who help us operate telephony, hosting, messaging, analytics, and payment systems. They may only access data needed to perform their role.

4.2 With Customer-Authorized Integrations

Examples include:

• Slack / Microsoft Teams (for notifications)
• Google Calendar / Outlook Calendar (for scheduling)
• CRMs or job management systems

Only the data required to execute the integration is shared.

4.3 Legal Requirements

We may disclose data if required by:

• Subpoena
• Court order
• Legal authority
• Protection of rights, safety, or property

4.4 No Sale or Advertising

Breesy does not:

• Sell data
• Share data with advertisers
• Use data to build advertising profiles

5. Google User Data

When you connect Google Calendar to Breesy, we may access limited Google User Data solely to provide scheduling features.

5.1 Data We Access

• Calendar metadata (calendar ID, time zone, availability)
• Events created or modified by Breesy
• Basic profile information (name, email)

We do not access:

• Events not created by Breesy
• Event descriptions, attendees, or content
• Gmail, Drive, Photos, Contacts, or any unrelated Google services

5.2 How Google User Data Is Used

Only to:

• Create and modify events
• Check availability
• Display events created through Breesy
• Maintain scheduling accuracy

We never use Google User Data for:

• Advertising
• Marketing
• Profiling
• Reselling
• Sharing with third parties except essential service providers

5.3 Limited Use Compliance

Breesy complies with:

• Google API Services User Data Policy
• Limited Use Requirements
• All restrictions on storing, sharing, transferring, or using Google User Data

5.4 Storage

We store only the minimum calendar metadata needed for Breesy's scheduling features. We do not store other calendar content.

5.5 Revoking Access

You may revoke Google access at any time:

• Inside Breesy's settings
• Or via: https://myaccount.google.com/permissions

Once revoked, Breesy immediately loses access.

6. Data Retention

We retain data only as long as necessary to:

• Provide the Breesy service
• Comply with legal obligations
• Resolve disputes
• Enforce agreements

Customers may request deletion at any time unless retention is legally required.

7. Your Rights and Controls

Depending on your location, you may have rights to:

• Access your data
• Correct inaccurate data
• Request deletion
• Restrict processing
• Export your data

For assistance, email: privacy@breesy.ai

Customers are also responsible for communicating rights to their own end users.

8. Children's Data

Breesy does not knowingly collect information from individuals under 18. If we learn that a child's data was submitted, we will delete it promptly.

9. Changes to This Data Safety Page

We may update this page to reflect changes in our data practices or legal requirements. Changes take effect immediately upon posting.

10. Contact Information

For questions about data safety or security:

Breesy LLC privacy@breesy.ai www.breesy.ai