1. Information we handle
- DJ accounts: email addresses and authentication information processed through Supabase Auth.
- Artist profiles: artist names, URL slugs, biographies, genres, event types, timezones, photos, and social, music, or press-kit links you provide. Published profiles are public. Uploaded artist photos use public storage; anyone with a photo’s URL can view it, including after a profile is unpublished.
- Booking requests: client names, email addresses, event types, dates, times, and locations, plus any organization, phone number, attendance, budget, and additional details the client submits. GigFlow also stores the DJ’s booking decisions, internal notes, and synchronization status.
- Google connections: the connected account’s email address, selected calendar identifiers and settings, encrypted refresh tokens, and identifiers of Google events linked to bookings. Calendar information we access is described below.
- Technical information: our hosting and authentication providers may process IP addresses, browser information, request times, and diagnostic or security logs. Spam protection stores a hash of the submitted email address and request counters. If enabled, Cloudflare Turnstile processes challenge responses and associated browser or network signals to detect abuse.
2. How we use information
We use information to authenticate DJs, display artist profiles, deliver booking inquiries to the artist’s account, manage gigs, check scheduling conflicts, and sync confirmed bookings to Google Calendar. We also use information to protect the service, diagnose failures, and respond to support and privacy requests.
Submitting a request shares your information with the DJ who owns that artist profile so they can evaluate the event and contact you. It does not automatically confirm a booking. Avoid including sensitive information that is unnecessary for planning your event.
3. Google Calendar access
Connecting Google Calendar is optional and requires your authorization. GigFlow identifies the connected Google account, lists calendars so you can choose them, and checks busy periods in selected calendars. When rescheduling a linked gig, it may read event information from the relevant calendar to exclude that gig’s own event from the conflict check. Private Google event titles and details are not displayed on public booking pages; clients receive availability results only.
When you confirm, reschedule, or cancel a booking, GigFlow creates, updates, or deletes its linked event. Events include the artist name, event type, location, times, booking reference, a link back to GigFlow, and reminders. Visibility of those events also depends on your Google Calendar sharing settings. GigFlow stores linked event identifiers and sync results; it does not maintain a separate copy of your entire Google Calendar. Independent edits made in Google do not sync back into GigFlow in this version.
Google data is used only to provide these scheduling features and related support and security functions. We do not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. Human access to Google user data is limited to your affirmative permission for support, necessary security or bug investigations, or legal requirements.
GigFlow’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
5. Cookies and security
GigFlow uses cookies for sign-in sessions and a short-lived cookie to protect the Google authorization flow. Blocking these cookies can prevent login or Calendar connection. The application does not include advertising trackers.
Account access controls and database row-level security restrict private data by DJ account. Google refresh tokens are encrypted before storage and are kept outside browser-accessible records. We use HTTPS for the production service. These measures reduce risk, but no online service can guarantee absolute security.
6. Retention and deletion
GigFlow keeps account, profile, and booking records to operate the service and maintain booking history. Cancelling a gig does not delete its GigFlow booking record. Disconnecting Google removes the stored refresh token when the operation completes, but does not delete booking history, calendar settings, or existing Google events.
To request deletion of your account, photos, bookings, or stored Google connection information, email contact@aust1nday.com. Deletion is handled by support; there is no self-service account-deletion feature in this version. We may need to verify your identity and clarify which records your request covers. Limited records may need to be retained for legal or security reasons, and provider backup or log copies may remain until those systems expire them. Copies already received by a DJ or stored in Google Calendar must also be addressed with that DJ or Google, as applicable.
7. Your choices
DJs can edit or unpublish artist profiles in their account. To stop Calendar access, use Settings → Google Calendar → Disconnect Google in GigFlow, or remove GigFlow’s access through your Google Account connections. Revoking Google access stops future authorized requests but does not itself erase existing GigFlow records or Google events. Delete unwanted Google events in Google Calendar or cancel a linked gig through GigFlow while its connection is working.
For access, correction, or deletion requests, contact contact@aust1nday.com. Depending on where you live, additional privacy rights may apply. Booking clients can also contact the DJ who received their inquiry about that DJ’s records.
8. Children
GigFlow is not directed to children under 13. If you believe a child has provided personal information through the service, contact us to request its removal.
9. Changes and contact
We will post policy updates on this page and update the date above. If our use of Google data changes, we will provide notice and obtain additional consent where required before using that data for a new purpose.
Privacy contact: contact@aust1nday.com.