Privacy policy

Information Breeze handles

Breeze handles business account details and the client, event, communication, planning, invoice and payment records a DJ business chooses to manage in the service. Payment card details are handled by the payment provider and are not stored by Breeze.

How information is used

We use information to provide, secure and support Breeze; deliver the communications and workflows configured by the DJ business; process payments; diagnose faults; and meet legal obligations. We do not sell personal information.

Who controls client records

The DJ business decides what client and event information it puts into Breeze and how it uses that information. Breeze generally processes those records for the DJ business. Breeze separately controls information needed to operate accounts, secure the service, provide support and meet its own legal obligations.

Overseas disclosure and processing

Breeze's primary file-storage region is Sydney, Australia. To operate the service, personal information may also be disclosed to or processed by service providers outside Australia, including in the United States and other countries where those providers operate. These providers support functions such as cloud infrastructure, email and SMS delivery, payments, monitoring, calendar and accounting integrations, and AI features when a business enables them.

Before disclosing personal information overseas, Breeze takes reasonable steps appropriate to the circumstances to require suitable privacy and security handling. Overseas laws may differ from Australian law, and Breeze may remain accountable under Australian Privacy Principle 8 for how an overseas recipient handles disclosed personal information.

Service provider and location register

The providers used for a record depend on which features the DJ business enables. “Likely locations” describes provider documentation and configuration; it is not a promise that every support operation or subprocessor stays in one country.

• Amazon Web Services: application infrastructure and file storage. Breeze configures file storage in the Sydney region; AWS documents that Australian customers can keep selected regional content in Sydney or Melbourne. Provider operations and subprocessors may still involve other countries. AWS Australia region guidance.
• OpenAI: optional AI-assisted features. Relevant prompts and business context may be processed by OpenAI and its subprocessors. Australian data residency is available only to eligible customers that configure it; without a verified residency configuration, processing may occur in the United States and other listed subprocessor locations. OpenAI data residency and subprocessor list.
• Twilio: optional SMS delivery and phone services. Message and account data may be transferred through the United States, European Union and other locations needed to provide the selected service. Twilio transfer information.
• Stripe: optional payment processing. Stripe may process personal data in the United States and other countries where it, its service providers or payment partners operate. Breeze does not store full payment-card details. Stripe Privacy Center.
• Google: optional sign-in, Gmail and Calendar connections. Google operates servers globally, so connected-account and event data may be processed outside Australia, including in the United States. Google data-transfer framework.
• Xero: optional accounting sync. Xero says personal data may be processed in countries including Australia, New Zealand and the United States, and publishes a current subprocessor register. Xero Legal Centre and subprocessors.
• Spotify and Sentry: optional playlist integration and error monitoring. Spotify platform data is governed by its developer data-protection terms. If monitoring is enabled, Sentry documents region-specific United States and Germany hosting endpoints. Spotify Developer Terms and Sentry region documentation.

Access, correction and questions

For access, correction, deletion or a privacy concern, email hello@usebreeze.app. We may need to verify your identity and, for client records, coordinate with the DJ business that controls the record.