Skip to content
Legal

Privacy Policy

How we collect, use, and protect your data.

Last updated: November 16, 2026

1. Introduction

PadVox ("we," "our," or "us") is operated by PADHUB, S.L., a Spanish limited liability company with tax ID (NIF) B93855179 and registered office at Paseo de la Castellana, 194, planta baja, puerta B, 28046 Madrid, Spain. PADHUB, S.L. is the data controller. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use the PadVox mobile application (iOS) and web platform at app.padvox.com (collectively, the "Service").

By using the Service, you agree to the collection and use of information in accordance with this policy. If you do not agree, please do not use the Service.

2. Information We Collect

2.1 Information You Provide

  • Account information: name, email address, and profile photo when you sign up via email or Apple Sign In.
  • Project data: project profiles, event details, setlists, stage plots, riders, checklists, contracts, tour information, and financial records you create within the Service.
  • Media: photos, audio files, and documents you upload to the Service.
  • Payment information: when you subscribe to a paid plan, payment is processed by Stripe. We do not store your credit card details. Stripe handles all payment data securely under their own privacy policy.

2.2 Information Collected Automatically

  • Firebase Analytics: if you allow it, we use Google Firebase Analytics to collect usage data linked to your account, such as app opens and feature usage. This helps us improve the Service. It is off by default and you can change it in Settings → Privacy.
  • Firebase Crashlytics: we collect app crash reports linked to your account, to fix bugs and to be able to reply if you contact us.
  • Device information: device type, operating system version, and app version for compatibility and debugging purposes.
  • Push notification tokens: if you enable notifications, we store your device token to deliver event reminders and updates.

2.3 Information operators may provide about their musicians

When an operator (project owner, manager, or similar) uses PadVox to manage a roster of musicians, they may upload the following data about each member:

  • Legal identity documents: passport, DNI, or national ID card data (including document numbers, expiry dates, nationality, and uploaded file scans), used for hotel police registration (carta policial) and border / travel compliance.
  • Home address and date of birth: used for legally required registrations (hotel check-in, tax forms, contracts).
  • Private operator notes: journal-style observations the operator writes about each musician (e.g., reliability comments). These notes are visible only to the operator and are not shown to the musician.
  • Availability periods with optional reasons: musicians and operators can mark unavailable dates. When an operator records a medical leave, the reason field may contain health-related information.
  • Fee / rate information: base per-event fees and rate data associated with each member. Private to the operator.
  • Check-in timestamps: when a musician confirms arrival at a venue, a timestamp is recorded for optional presence tracking.
  • Profiling metrics (reliability statistics): aggregated counts computed from lineup history: total assignments, confirmation rate, last-minute declines, and attendance rate.

Musicians added as project members may review all data held about them via our data export endpoint (see Section 8). Where availability reasons or operator notes contain health indications or other special categories of personal data, such data is processed under Article 9(2)(b) GDPR (processing necessary for carrying out obligations in the field of employment, social security, and social protection law), or under equivalent contractual basis, and is retained only for as long as operationally needed.

2.4 Identity documents you upload yourself

If you choose to use Personal Documentation (Account → Edit Account → Personal Documentation), you can store your own identity documents — such as a passport or national ID card — in your private account. This is optional and requires your explicit in-app consent before any upload.

  • What we collect: the document image(s) you upload or capture with your camera, and the fields extracted from them — legal name, document number, date of birth, expiry date, nationality, and home address.
  • Automated extraction (AI): when you scan a document, the image is securely transmitted to our servers and then to our AI provider, Anthropic (Claude), which reads the document and extracts those fields so we can pre-fill them for you. This only saves you typing — you review and correct every field, and no decision affecting you is made solely by automated means. Anthropic processes the image as our subprocessor, under contract, solely to perform the extraction, and does not use it to train its models. We do not store the image used for this scan: it is processed transiently in memory and discarded once the fields are returned.
  • Private by default, shared only on your instruction: your documents are visible only to you unless you explicitly grant a specific project access. When you grant access, a copy of the relevant data and files is shared with that project's managers for their organizational and legal obligations (e.g. accreditation, hotel police registration). You can revoke access at any time — removing your documents from that project — and delete your documents from your account entirely.

Legal basis (where GDPR applies): your explicit consent, which you may withdraw at any time, and the arrangement between you and the organizers you choose to share with. Because our AI provider operates in the United States, scanning involves an international transfer of your data, carried out under the safeguards described in Section 6.

2.5 If you buy a ticket to an event

You can buy a ticket without having a PadVox account. In that case you are not a user of the Service: you are a customer of the organiser selling the event, and PADHUB, S.L. acts as data processor on that organiser's behalf, except as noted below.

  • What we collect: the name and email address you type on the checkout page, your order details (ticket types, quantities, amount and currency), the language the page was shown in, the date and time of purchase, and the state of the marketing checkboxes together with the version of the legal text you were shown. We also generate a signed QR code per ticket and record whether it was used at the door, when, and by which scanning device.
  • Why: to issue and send you the ticket, let you recover it if you lose the email, validate entry on the day, handle refunds and incidents, and meet our accounting and tax obligations. None of these purposes needs your consent: they are necessary for the contract you enter into with the organiser and to comply with the law.
  • Your card details never reach us. Payment is processed by Stripe in its own environment; PADHUB does not see, receive or store your card number.
  • Marketing communications (optional): the checkout page has two independent checkboxes, both unticked by default. Ticking either is voluntary and is not a condition of purchase. The first authorises the organiser to write to you about their upcoming events; the second authorises PADHUB, S.L. to write to you about gigs and events. They are two different controllers and two different consents: ticking one does not imply the other, and ticking neither does not affect your ticket. The legal basis is your consent (GDPR art. 6(1)(a) and art. 21 LSSI).
  • How to unsubscribe: every marketing email includes an unsubscribe link that works in one click without identifying yourself. You can also write to privacy@padvox.com. Unsubscribing is immediate and does not affect your ticket emails, which you will keep receiving because they are not advertising.
  • Who sees your data: the event organiser can access the name, email and purchase details of everyone who bought their tickets, and can export them. PADHUB does not use that data for its own marketing unless you expressly ticked the second checkbox.

For the second checkbox — the PadVox one — PADHUB, S.L. acts as controller, not as processor. For everything else related to your ticket the controller is the organiser: requests to access, rectify or erase your purchase data should go to them first, though we can help you find them.

Door staff. To validate tickets at the door, the organiser opens scanner sessions with an access code. We record the email of whoever starts that session, when it begins and ends, and which tickets it validates, so the organiser can audit access control. Sessions expire automatically after 12 hours.

2.6 Tour alerts on WhatsApp and Telegram

If you are on a project's team, whoever runs it can send you a tour's operational alerts on WhatsApp or Telegram: flights, transfers, hotel check-in and check-out, load-in, soundcheck and show time. It is optional and off by default.

  • Your phone number. We store it on your member card for that project. You can type it yourself, and so can whoever runs the team, which is what normally happens when you do not have the app installed.
  • You give the permission, not the person who added you. Nobody can switch it on for you. To give it, you send an opt-in message to the PadVox number from your own phone; that message is the proof that the number is yours and that you accept the alerts. Whoever runs the team can withdraw it for you, but never grant it.
  • Consent record. We store when you gave or withdrew it, through which channel, and the exact number it refers to. Meta requires us to be able to evidence this consent, and it lets you check what you authorised. If you change your number the permission is withdrawn automatically: it is tied to the number you gave it with.
  • What travels in each message. Your name, the tour name and the details of the fact being announced: times, airports, hotel or pickup address and, for a transfer, the driver's name and phone. We do not send payment data, identity documents, or information about other members that you do not need.
  • What you reply. If you answer one of those messages, or press one of its buttons, we store your reply and notify the tour's road manager so they can deal with it. We do not use those replies for anything else.
  • How to opt out. Send BAJA on WhatsApp at any time, or switch it off from your card in the app. Opting out by message takes effect across every project where that number appears, not just one. It is immediate and needs nobody's approval.
  • These alerts are never marketing. They are operational information about the work you were hired for. We do not use this channel to send you offers or commercial messages, ours or anyone else's.

2.7 If you connect your Google Calendar

You can connect your Google account from Settings → Calendar in the web app. It is optional and only you can switch it on. We ask Google for a single, read-only calendar permission (calendar.readonly), plus your email address so we know which account you connected. PadVox never creates, changes or deletes anything in your Google Calendar.

  • Your personal schedule on the Dashboard. We read from Google, on the spot, the events of the calendars you choose for the dates on your screen, and show them on your Dashboard. Only you see them: they are not shown to the other members of your projects and are not copied into any project. We do not store them in our database; the server keeps them in memory for at most a minute so it does not repeat the same request.
  • A calendar that feeds a project. If you manage a project, you can pick one of your calendars so its entries become events of that project. It is an explicit choice you make, one calendar at a time. From each entry we copy only the title, the start and end date and time, the time zone, the location and whether it is cancelled, and the project's members see it like any other event. We do not copy the description, guests, attachments or video-call links. To keep them up to date, Google tells us when something changes in that calendar and we read it again.
  • What we keep about the connection. The email address of the Google account, which calendars you chose, and the token Google gives us to read them, encrypted (AES-256-GCM, with the key held separately in a secrets manager). That token is not visible to anyone, including the other members of your projects.
  • What we do not use it for. The data we receive from Google is used only to show you your schedule and to keep the events of a calendar you connected to a project up to date. We do not sell it, use it for advertising or profiling, or use it to train artificial-intelligence models, ours or anyone else's, and no one at PadVox reads it unless you ask us to in order to fix a problem, the law requires it, or it is needed for security.
  • How to disconnect. Settings → Calendar → Disconnect. We revoke the permission at Google and delete the token and the connection. You can also remove it from your Google account's permissions. If you disconnect a calendar that fed a project, it stops syncing: the events already created stay in the project as ordinary events, and whoever manages it can delete them.

PadVox's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

2.8 Roady, the PadVox assistant

Roady is the PadVox assistant. You can write or talk to it from the app, the web app and Siri and, if you connect them, from Telegram and WhatsApp. It answers with the information in your projects and helps you prepare changes to them.

  • What it sees. Only what you can see in PadVox with your account. Each conversation is yours: Roady doesn't mix what it knows about different people.
  • What it does for you. Roady asks for your confirmation before saving, changing or sending anything. It only jots down notes and tasks without asking, and you can undo them. And it can never do more than your role in the project allows.
  • Who processes it. Your messages and the project data Roady needs to answer are sent to our AI provider, Anthropic (Claude), in the United States. Anthropic processes them as our subprocessor, under contract and Standard Contractual Clauses, only to generate the answer, and does not use them to train its models.
  • What we keep. The history of each conversation, per person and channel, so Roady can follow the thread (older messages are summarized), deleted in the days after 7 days without you writing to it, and which you can delete whenever you like: in the app and on the web, with "Delete conversation", in Roady's menu; on WhatsApp or Telegram, by sending NEW; a log of the actions Roady takes for you (what, when and through which channel), for security, deleted in the days after it turns 90 days old; and how much you use it, to apply your plan's limits.
  • On WhatsApp or Telegram. Meta or Telegram also process the messages to deliver them. WhatsApp is switched on when you send your sign-up message from your own phone and switched off by sending BAJA. What reaches us through WhatsApp is deleted after 30 days.
  • The WhatsApp trial. If you use Roady's 5 trial questions on WhatsApp, we keep a fingerprint of your number for 12 months (a code computed from it with a secret key, not the number itself), so the trial can only be used once per number. The counter linked to your account is deleted if you delete your account.
  • If you delete your account, everything related to Roady is deleted too: conversations, drafts and the action log.

2.9 If we send you a presentation or invite you to a demo

When someone asks us for information or to see PadVox working for their case, we sometimes prepare a personal presentation and, if they want to try it, a demo. Both use the same personal link. If that is you:

  • What we keep. Your first name; the name of your band or company, if you told us; whether you are a manager or a musician; your language; the note Carlos, our founder, writes for you; which parts of the presentation we show you, and a random code that goes in your link. We enter this ourselves when we prepare the invitation. Neither your name nor your email is in the link. We only keep your email if we send you the presentation by email, to send it. We do not keep your phone number or your Instagram username: if it reaches you on WhatsApp or Instagram, Carlos sends it in the same conversation where you asked for it.
  • What we see about your invitation. When you open the presentation (the first and last time, and how many times), whether you press "Download PDF", "Try the demo" or "Talk to Carlos" and, if you sign in to the demo, which steps you complete, whether you connect Roady, how many messages you send it (not what you say) and whether you move to a paid plan. Your browser records the opening once the page has been open for a few seconds, without cookies. Our emails carry no open or click tracking from our email provider. We use this to learn whether the presentation and the demo work and to write to you over the following days, unless you tell us not to.
  • If you sign in to the demo. You create your own PadVox account, with Google or your email, and from then on the rest of this policy applies to your account. Your account is marked as coming from an invitation, so we do not mix it with the rest in our sign-up figures.
  • The demo. Its people, venues, hotels, companies, emails and phone numbers are made up. Nothing is sent from a demo to anyone but you: no tour updates and no Roady messages to third parties. The demo is deleted entirely 21 days after you sign in.
  • Roady on WhatsApp in the demo. It works as described in section 2.8: it is switched on when you send your sign-up message from your own phone and switched off when you send BAJA. In the demo it has a limited number of messages.
  • How long we keep it. If you never sign in to the demo, we delete the invitation, including your email if we had it, 30 days after the link expires. If you sign in and do not move to a paid plan, we delete it 90 days after the demo is deleted; your account stays until you delete it. Your account only keeps the mark that it came from an invitation, without your name.
  • If you do not want to continue. Reply to the message your invitation came in, or write to us at the address in section 12, and we will delete the invitation and stop writing to you.

3. Our Role: Data Controller vs Processor

PadVox plays two different legal roles depending on how you use the Service:

  • PadVox as Data Controller: when you sign up for PadVox with your own email and create your own projects, PadVox is the Data Controller for your personal account data (name, email, login credentials, billing data).
  • PadVox as Data Processor: when an operator adds you as a member to their project and uploads data about you, that operator is the Data Controller and PadVox acts as the Data Processor on their behalf. Requests to access, correct, or delete operator-uploaded data should be directed to the operator first. PadVox can facilitate these requests but the operator decides and remains accountable.
  • PadVox towards ticket buyers: the organiser is the Data Controller for their buyers' data and PadVox acts as Processor, as above. The one exception is the PadVox marketing checkbox: if you tick it, PADHUB, S.L. processes your email as Controller, for that purpose and that purpose only. See Section 2.5.

Operators who use PadVox in a professional capacity are required to sign a Data Processing Agreement (DPA). Our standard DPA is available at /dpa.

4. How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve the Service.
  • Manage your account and process subscriptions.
  • Send event reminders, checklist notifications, and tour day sheets.
  • Enable collaboration between project members.
  • Generate tickets, passes, and documents (riders, contracts, stage plots).
  • Analyze usage patterns to improve features and fix bugs.
  • Respond to support requests.
  • Automated profiling for reliability indicators: confirm rate, attendance rate, and last-minute declines are computed by scheduled Cloud Functions from lineup history. You have the right under GDPR Article 22 to object to profiling. Contact privacy@padvox.com.
  • Email notifications: we send transactional emails to musicians when lineups are published and weekly digests of upcoming assignments, delivered through our email subprocessor (see Third-Party Services).

4.1 Legal Basis for Each Purpose

Under GDPR Article 6 we must tell you not only what we do with your data, but under which legal basis. Purpose by purpose:

Purpose Legal basis
Sending you tour alerts on WhatsApp or Telegram Consent (art. 6.1.a) — you give it from your own phone and can withdraw it whenever you like by sending BAJA, without affecting anything else in the Service.
Answering you and preparing changes with Roady, the assistant Performance of a contract (art. 6.1.b): it is a feature of the Service that you use when you want. On WhatsApp, also with your consent (art. 6.1.a), which you withdraw by sending BAJA.
Preparing and sending you a presentation or a demo you asked for, learning whether you opened it and writing to you over the following days Pre-contractual steps at your request (art. 6.1.b), because you asked for it; and legitimate interest (art. 6.1.f) for learning whether you opened it and following up, with the minimum data. You can object at any time by replying to the invitation message.
Providing the Service, managing your account, enabling collaboration, generating documents and tickets Performance of a contract (art. 6.1.b) — we cannot deliver what you signed up for without this.
Showing you your Google Calendar and syncing the calendar you choose with a project Consent (art. 6.1.a) — you give it when you connect your Google account and withdraw it when you disconnect.
Processing subscriptions and payments Performance of a contract (art. 6.1.b) and legal obligation (art. 6.1.c) for invoicing and accounting records.
Transactional emails and push notifications: event reminders, lineup publications, day sheets Performance of a contract (art. 6.1.b) — they are part of the Service, not marketing.
Responding to support requests Performance of a contract (art. 6.1.b) or legitimate interest (art. 6.1.f) in assisting the people who use PadVox.
Usage analytics to improve features and fix bugs Consent (art. 6.1.a). Off by default; you turn it on in Settings → Privacy and can turn it off at any time.
Marketing emails about PadVox to account holders: plans, trials and Service news Prior contractual relationship (art. 21.2 LSSI) and legitimate interest (art. 6.1.f). You can unsubscribe in any email, when creating your account or in Settings.
Reliability indicators computed from lineup history (profiling) Legitimate interest (art. 6.1.f) of the operator in staffing events reliably. You may object at any time under art. 22.
Scanning identity documents you upload Explicit consent (art. 6.1.a), requested separately in the app before anything is uploaded.
Security, abuse prevention and service integrity Legitimate interest (art. 6.1.f) in keeping the Service safe and available.
Keeping records to defend against legal claims Legal obligation (art. 6.1.c) and legitimate interest (art. 6.1.f).

Where we rely on legitimate interest, we have weighed that interest against your rights and freedoms, and you may object at any time by writing to privacy@padvox.com. Where we rely on consent, you may withdraw it at any time, and doing so is as easy as giving it — withdrawal does not affect the lawfulness of processing carried out beforehand.

5. Data Sharing and Disclosure

We do not sell your personal information. We may share data with:

  • Service providers: Firebase (hosting, database, authentication, analytics), Stripe (payment processing), and cloud infrastructure providers that help us operate the Service.
  • Your project members: when you join or create a project, other members can see shared project data such as events, setlists, and stage plots.
  • Event attendees: if you publish public events with ticketing, limited event details (name, date, venue) are publicly visible.
  • Legal requirements: we may disclose information if required by law, legal process, or to protect the rights and safety of PadVox and its users.

6. Data Storage and Security

Your data is stored securely using Google Firebase (Cloud Firestore and Cloud Storage), hosted in the United States. We implement industry-standard security measures including encryption in transit (TLS) and at rest, role-based access control, and Firestore security rules to protect your data.

International transfers: PadVox data is stored in Google Cloud infrastructure in the United States. Transfers of personal data from the European Economic Area (EEA) to the United States are made under Google's Standard Contractual Clauses (SCCs) as approved by the European Commission. A copy of the SCCs is available from Google Cloud's legal documentation. Where you use AI document scanning, the document image is also transferred to our AI provider (Anthropic) in the United States to extract the fields, under equivalent Standard Contractual Clauses; the image is not retained after extraction.

While we strive to protect your information, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security.

7. Data Retention

We retain your data for as long as your account is active or as needed to provide the Service. If you delete your account, we will delete your personal data within 30 days, except where retention is required by law or for legitimate business purposes (e.g., financial records for tax compliance).

Project data shared with other members (events, setlists, etc.) may persist in those projects even after your account is deleted, as it is shared collaborative content.

Messaging alerts. Your consent record is kept while it stands and for three years after you withdraw it, which is the window in which we could be asked to evidence that we had it. Sent messages and their delivery states are kept while the project stays active, and the technical copies the Meta integration produces delete themselves after a few days.

Google Calendar. The events of your personal schedule are not kept. The Google connection and its encrypted token are kept until you disconnect it or delete your account. Events that a connected calendar created in a project follow the same rules as any other project event.

Ticket sales data. Someone who buys a ticket has no account to delete, so their retention runs separately. Orders and issued tickets are kept while the organiser keeps their project active and, in any case, for the periods required by accounting and tax law (six years in Spain for transaction records). Door validation records and scanner sessions are kept for twelve months after the event, long enough to settle any access dispute. Emails opted in to marketing are kept until you unsubscribe or withdraw consent, and are reviewed every three years in any case: with no interaction in that period, they are deleted.

Presentations and demo invitations. The demo is deleted entirely 21 days after you sign in. The invitation (your first name, your band or company, your email if we sent it by email, the note, your language and what you did with it) is deleted 30 days after the link expires if you never sign in to the demo, and 90 days after the demo is deleted if you sign in and do not move to a paid plan. Your account follows the rules for any account.

8. Your Rights

Depending on your jurisdiction, you may have the right to:

  • Access, correct, or delete your personal data.
  • Export your data in a portable format.
  • Withdraw consent for data processing.
  • Object to or restrict certain processing activities.
  • Lodge a complaint with a data protection authority. Our lead supervisory authority is the Agencia Española de Protección de Datos (AEPD), C/ Jorge Juan, 6, 28001 Madrid (https://www.aepd.es). If you live elsewhere in the EU you may also complain to the authority of your own country.
  • Object to automated decision-making, including profiling (GDPR Article 22).

To exercise these rights, contact us at privacy@padvox.com. We answer within one month, extendable by two further months for complex requests, in which case we will tell you within the first month. Exercising your rights is free of charge. You can also export your data and schedule the deletion of your account yourself, without writing to anyone, from Settings → Privacy in the web app.

9. Children's Privacy

The Service is not intended for children below the applicable minimum age in their jurisdiction. In the United States, we do not knowingly collect personal information from children under 13 years of age (COPPA). In the European Union, the default minimum age is 16 years, unless a member state has lowered it by law. For example, Spain sets the minimum age at 14. If we become aware that we have collected data from a child below the applicable age without verifiable parental consent, we will take steps to delete it promptly.

10. Third-Party Services

The Service integrates with the following third-party services:

  • Google Firebase / Google Cloud: authentication, database, storage, analytics, push notifications, scheduled Cloud Functions (weekly digests, reliability computation), and Firebase Mail Extension. Firebase Privacy Policy
  • Google Calendar: optional. If you connect your account, we read your calendars with read-only permission to show them to you and to sync the one you choose with a project. See Section 2.7. Google Privacy Policy
  • Stripe: payment processing for subscriptions and ticket sales. Stripe Privacy Policy
  • Telegram: optional channel for the PadVox assistant and for tour alerts. If you link your account to the bot, Telegram carries the messages you exchange with it and gives us your user identifier. It is only active if you link it yourself. Telegram Privacy Policy
  • WhatsApp (Meta Platforms Ireland Limited): optional channel for tour alerts and for Roady, the assistant. If you give your permission, Meta processes your phone number and the messages you exchange with the PadVox number in order to deliver them. It is only active if you authorise it yourself from your own phone, and it stops when you send BAJA. WhatsApp Privacy Policy
  • Printful: manufacturing and shipping of merch orders. Receives the buyer's shipping details when an order is placed in a merch store. Printful Privacy Policy
  • Apple Sign In: optional authentication method. Apple Privacy Policy
  • SendGrid (Twilio): transactional email delivery via the Firebase Mail Extension (assignment emails, weekly digests). SendGrid / Twilio Privacy Policy
  • Anthropic (Claude): AI provider (United States) used for two things: running Roady, the assistant, and extracting the fields from identity documents you choose to scan. Processes messages and images as our subprocessor and does not use them to train its models. Anthropic Privacy Policy

See the full list of subprocessors at /subprocessors.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by posting the updated policy on this page and updating the "Last updated" date. Your continued use of the Service after changes constitutes acceptance of the updated policy.

12. Contact Us

If you have questions or concerns about this Privacy Policy, please contact us at:

PADHUB, S.L.
Spanish tax ID (NIF): B93855179
Paseo de la Castellana, 194, planta baja, puerta B
28046 Madrid, Spain
Registered at the Commercial Registry of Madrid (Registro Mercantil de Madrid), sheet M-894144, entry 1
Email: privacy@padvox.com
Phone: 645 575 886
Website: www.padvox.com


This document is provided for informational purposes. For legally binding advice consult a qualified attorney in your jurisdiction.