Last updated: November 16, 2026
Welcome to GigBook. We respect your privacy and are committed to protecting your personal data. This privacy policy explains how we collect, use, store, and protect your information when you use our app.
When you create an account, we collect:
If you set up a musician profile we store the photo, name, handle, bio, instruments, genres, agencies and home area you enter. Your home area is whatever place you type (for example a town); GigBook never reads your device's location for it. Your profile is private until you turn on “Let other GigBook musicians find me”. While that is on, other signed-in GigBook users can find you by name, handle, home area, instruments or genres and see these details. People you have added can see your profile even when it is off, and people who have added you always see your profile name. Profiles are never shown to anyone who is not signed in, and your gigs and fees are never shown.
Profile photo. Your photo is stored privately and is only shown, through the signed-in app, to people who can see your profile. We remove location and other metadata from photos when they are uploaded. A replaced or removed photo is deleted.
People you've played with. To suggest people you may want to add, we match the musician names on your own gigs against the names on findable profiles. The other person is not told. If you tap “Not them”, we store that choice so the suggestion doesn't come back.
Connections. When you add someone (including linking a saved musician to their profile), we store that link with your data and show them in the app that you added them. Links saved before Connections was introduced stay private and are never shown to the other person. If you choose to share your phone number or email, we store them and show them only to the people you picked (anyone who adds you, or only people you have added too); nothing is shared until you choose, and you can stop at any time in Connections. Turning off “Let other GigBook musicians find me” does not stop sharing with people who have already added you. If you block someone, we store that block so neither of you can find or see the other's profile or contact details; they are not told. Your gig records stay yours: adding, removing or blocking someone never changes them.
Musician lists. Lists you make of saved musicians, their order and any private notes you add are stored with your account and shown only to you. The people on them are never told.
Reports. When you report a profile we store the report, including the reason you give and which account made it, so we can review it, avoid duplicate reports and stop showing you that profile. The report details (without who made it) are emailed to GigBook's operator for review. The person you report is never told who reported them.
Leaderboards (optional, off by default). Nothing is shared unless you switch leaderboards on in Settings. You choose each metric separately (completed gigs, and fees earned in EUR), the name shown (your name or a pseudonym) and who can see it: signed-in GigBook users, or anyone on the internet. We then show only totals per period, calculated from your own gig records each time the leaderboard is viewed; never your gigs, dates, venues, clients, contact details or invoices, and never a link to your profile. A pseudonym is not anonymity. Entries shared with anyone on the internet can be seen by people who are not signed in, including people you have blocked; blocking only hides entries between signed-in users. Turning leaderboards off removes your entry at once, but we cannot remove copies other people already saw or saved. If someone reports your leaderboard name we store the report the same way as a profile report.
Company directory. A GigBook admin can list a business (for example a booking agency) with contact details the admin enters, for signed-in users or for anyone on the internet. It never includes your own client records, fees, commission, invoice settings or notes, and a client you added is never published with your details.
Your profile, photo, shared contact details, connections, blocks, reports, leaderboard choices, suggestion choices and musician lists are deleted when you delete your account (the photo file shortly after). Other users' own records, such as your name on their gigs or saved musicians, are their data and are not changed.
To provide our services, we collect or process:
Updated mobile apps report a random installation identifier, platform, device name, publishing setting, selected calendar and account labels, calendars deliberately kept after a destination change, and report and local-update times. These labels may include email addresses. This lets you see which of your devices may be publishing gigs. Reports are visible only to your signed-in GigBook account, can be downloaded from Calendar connections on the web, and are deleted when you delete your account. They do not include your other calendar events or calendar-provider credentials. Reports are last-known information; they do not confirm delivery to Google or iCloud.
When you obtain or use managed AI credits, we receive or create:
Apple, Google or Stripe processes payment details, depending on your platform and the checkout offered to you. GigBook does not retain raw payment-card details, raw store receipts or signed webhook bodies.
We collect information directly when you create an account, enter or select data, record audio, upload or import content, make a purchase, or submit an AI request. Clerk provides the authentication and account identifiers used to sign you in. Apple, Google or Stripe sends us verified purchase identifiers and status facts after a purchase or refund event. The app automatically sends device/delivery tokens when you register notification features and sends scrubbed diagnostics when an error or sampled performance event occurs. GigBook also creates account-scoped sync, Assistant-history, managed-AI operation and credit-ledger records as you use those features.
If you use managed voice gig entry, GigBook accesses your microphone only while you are actively recording. Granting AI permission does not upload a recording. After you explicitly start the managed voice action, the completed recording is sent through GigBook to the managed transcription provider when recording stops. That request also includes the bounded spelling and language hints described below. The returned transcript is shown for review before it is used to propose structured gig details.
We use your information to:
We do NOT: Sell your data, share it for advertising, or use it for marketing purposes.
GigBook offers optional AI-assisted features: Ask GigBook Assistant, editing a selected gig from an instruction, importing gig history from files, creating gigs by voice or typed description, parsing gigs from screenshots, and extracting expenses from receipt photos or PDFs. These features only run when you actively use them, and only after you have given explicit permission inside the app (revocable at any time in Settings → AI). Granting permission alone does not start a provider request; each send follows a separate, explicit start or submit action in the relevant feature.
What is sent:
The voice hints are used to preserve the spelling of names that are actually spoken. GigBook does not initiate new AI work from them in the background.
Who it is sent to and why: GigBook's server relays the disclosed content to OpenAI, GigBook's current managed AI service provider, using GigBook's provider account. GigBook sends it to fulfill the user-requested transcription, extraction, Assistant planning or gig-edit operation. OpenAI processes the content under its applicable service terms and data controls. Under the applicable OpenAI business/API agreement and data-protection terms, GigBook requires OpenAI to use it only to provide and secure the requested service or meet legal obligations, and to provide the same or equal protection described in this policy and required by applicable law. If you choose a DeepSeek model in Settings, and only after you allow the current AI disclosure that names DeepSeek, GigBook instead relays text-only requests (Ask GigBook, Edit with AI, typed gig requests and text imports) to DeepSeek, a separate third-party AI provider, using GigBook's DeepSeek provider account. Images, files sent as images, receipts, invoices and voice recordings are never sent to DeepSeek; they always use OpenAI. DeepSeek processes that text under its own API terms and privacy policy, which set how and where it is processed and how long it is kept (see Third-Party Services). DeepSeek's API also caches request content on disk automatically, usually for a few hours to a few days. GigBook may retain an encrypted provider result and limited operation records needed for safe replay, billing and audit. GigBook stores Assistant conversations in your account history so you can reopen them, and an action you approve may save the resulting gig or expense to your account. Proposed gigs, edits and expenses are shown for review before you choose to save or apply them. Personal provider keys are retired and are never used for new AI work.
Managed AI: before work starts, GigBook reserves a server-calculated maximum from your non-expiring AI-credit balance, then settles verified usage or releases the reservation. The exact debit varies with the content you send and the managed model that runs; Credit history records the completed-task debit. Provider credentials, payment evidence and wallet data are never included in model prompts.
Purchases: Apple, Google or Stripe processes payment details. GigBook retains provider identifiers, cryptographic hashes, verified amount/state facts and an append-only credit ledger for security, refunds and accounting. We do not retain raw receipts, card details or signed webhook bodies.
Trial promotions: if GigBook issues one-time trial credits, we retain the campaign and economic-policy version, retail value, credit amount and pseudonymous wallet ledger proof needed to enforce the global budget and prevent a second grant. We do not add email matching or device fingerprinting for this purpose.
Your control: granting AI permission does not itself send data; every provider request follows an explicit start or submit action. A managed voice recording is sent when recording stops. Withdrawing consent in Settings → AI blocks new AI requests but does not cancel a request already started or delete saved account data, purchase records or credit history. Account deletion is a separate control in your account settings.
We use the following third-party services. Where a company acts as GigBook's processor under applicable contracts and data-protection terms, GigBook requires purpose-limited processing, appropriate security, and the same or equal protection of personal data described in this policy and required by applicable law. A service identified below as an independent controller handles the limited information it receives under its own published terms and privacy policy rather than GigBook's processor instructions.
Receives the specific content described in the AI section above to provide the managed AI operation you request. OpenAI's business/API processing is governed by its applicable Services Agreement and Data Processing Addendum; its API data controls explain API storage and retention controls.
Receives only the text of AI requests you make while a DeepSeek model is selected, as described in the AI section above, to provide that operation. GigBook never sends DeepSeek images, files sent as images, receipts, invoices or audio. DeepSeek handles that text under its Open Platform Terms of Service. DeepSeek's Privacy Policy describes its own services and says it does not cover how apps built on DeepSeek, such as GigBook, process their users' data, so it is not a specific commitment about this text. DeepSeek's API caches request content on disk automatically (context caching); DeepSeek says unused cache is usually cleared within a few hours to a few days. GigBook makes no separate promise about whether DeepSeek uses that text for training or how long DeepSeek keeps it.
When you send or schedule an invoice email, GigBook sends Resend the recipient, sender, BCC and reply-to addresses used for that delivery, the subject and message body, and the completed invoice PDF, including the business, client, line-item, payment and bank details displayed in it. Resend delivers the message and returns identifiers and delivery status used to operate and troubleshoot the feature. Resend acts under its applicable service and data-processing terms; see also its privacy policy.
If a known venue has no saved address and you ask the Assistant where it is, GigBook's server may send the venue name and an optional city hint derived from your saved timezone to the public Nominatim search service operated by the OpenStreetMap Foundation. A confident result may be saved to that venue for future answers. The Foundation receives normal request metadata from GigBook's server and acts as an independent controller, not as GigBook's contracted processor. See its privacy policy and Nominatim usage policy.
Handles user authentication and account security. Read their privacy policy: clerk.com/privacy
Stores your app data securely. Read their privacy policy: neon.tech/privacy-policy
Hosts the app infrastructure. Read their privacy policy: vercel.com/legal/privacy-policy
Receives scrubbed crash, error and sampled performance events (performance timings from the website only) when diagnostics are configured, and, from the iPhone and Android apps, reports when the app freezes or stops responding. An event includes the error type and code location, the app version and build, the device model and operating system (or browser) name and version. GigBook disables session replay, screenshots and default personal-information capture, and removes raw messages and error text, user/request context, web addresses, breadcrumbs, attachments, locale and timezone before sending diagnostic events. The mobile apps' diagnostics library also counts crash-free app sessions using a random identifier it creates for the app installation; GigBook never links it to your account. Read their privacy policy: sentry.io/privacy
Receives device or Live Activity delivery tokens and the notification payload needed to deliver reminders and Live Activity updates you enable.
Process payment details and return verified transaction, purchase-state and refund facts to GigBook for purchases available on your platform.
Under GDPR and other privacy laws, you have the right to:
To exercise any of these rights or for questions, contact us at privacy@gigbook.xyz
GigBook is intended for users aged 16 and over. We do not knowingly collect personal information from anyone under 16. If you are under the age of majority where you live, you may use GigBook only with the agreement of a parent or legal guardian. If you believe someone under 16 has given us personal information, please contact us at privacy@gigbook.xyz and we will delete it.
Your data may be processed in countries outside your own. We ensure adequate safeguards are in place to protect your data in compliance with GDPR and other applicable privacy laws.
We may update this privacy policy from time to time. We will notify you of any significant changes by email or through the app. Your continued use of GigBook after changes means you accept the updated policy.
If you have questions about this privacy policy or your data, contact us:
This privacy policy applies to the GigBook mobile app and web application. By using GigBook, you agree to the collection and use of information in accordance with this policy.