
Privacy Policy & Cookie Notice
Last updated:
1. Who we are and how to contact us
Mobrool™ (mobrool.live) is operated by Mobrool Ltd. Mobrool Ltd is the controller of personal information used for its own account administration, billing and support. Artists remain responsible for their own booking and client-data practices.
Mobrool Ltd is registered in England and Wales. Company number: 17532365.
Registered office: 3 Sweethay Close, Trull, Taunton TA3 7HG.
This policy explains personal information used for band and production management, shared diaries, bookings, song and setlist management, subscriptions, and interactive shows. It also covers visitors, booking clients and audience members who use those features without a Mobrool account.
For privacy questions or requests, email admin@mobrool.live. Please identify the relevant artist account or booking where possible, without sending passwords, payment-card details or Google authorisation tokens.
2. Information we collect
- Accounts and teams: names, usernames, email addresses, contact details supplied to the service, account roles, permissions and artist settings. Passwords are stored as hashes, not as recoverable encrypted passwords.
- Regional eligibility: for invited customer signup, we retain the customer country as GB and the affirmative UK-based customer declaration, including its confirmation time and policy version, to administer regional eligibility. The declaration is self-reported and is not an independent verification of tax residence.
- Diaries and bookings: client and performer contact details, dates, availability, venues, event requirements, notes, fee and deposit information, booking correspondence and generated documents. Artists may include their payment instructions in booking documents.
- Shows and repertoire: songs, setlists, settings, votes, survey responses, audience messages, participation identifiers and uploaded images or videos.
- Billing and support: subscription and payment-status information, billing identifiers, and information you provide when requesting help or exercising privacy rights.
- Technical information: session identifiers, relevant request and error logs, IP addresses and browser/device information used to operate the service, prevent abuse and troubleshoot problems.
Artists and authorised team members can enter information about other people, including clients and performers. They should have an appropriate reason to do so and explain their own booking and band-management practices to those people.
3. Optional Google connections
You choose whether to connect Google and which supported features to enable. We receive your Google account email address and the permissions granted, and store encrypted access and refresh tokens so enabled features can work without asking you to sign in for every request.
- Gmail sending: when you select Gmail, Mobrool sends booking emails, documents and test emails through your connected account to the intended recipients. We may retain the outgoing content, recipient, attempt status and the message identifier returned by Google for booking history and safe retry handling.
- No mailbox reading: Mobrool does not read your Gmail inbox, import incoming replies or search your Sent folder. If sending is uncertain, you must check Sent items before deciding whether to resend.
- Google Calendar: we list accessible calendars so you can choose destinations and availability sources, read or change selected calendar properties for status labels, and create, update or remove Mobrool-managed gig events. Selected availability imports use event information such as dates, times, titles and source identifiers, which may be stored in the diary.
Calendar information is used for the diary features you select. Imported event-title details are restricted to authorised booking roles; other diary readers may see unavailable dates without those private titles. Booking emails share their content and attachments with the chosen recipients, and Google processes the information needed to provide its connected services.
Older connections may retain broader Google grants until you revoke them. You can remove access in your Google Account connections. This can interrupt both Gmail and Calendar. To disconnect in Mobrool, disable Calendar sync first and then disconnect the Google connection; this removes its locally stored connection tokens. Neither revoking access nor disconnecting automatically deletes previously stored diary or booking data.
4. Google data and Limited Use
Mobrool's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Google-derived information is used only to provide or improve the visible, user-facing features you have authorised. It is not sold or used for advertising, credit decisions, or training general-purpose artificial-intelligence models.
Sharing is limited to delivering those authorised features with your consent, necessary security purposes, legal obligations, or another transfer permitted by Google's policy. Human access is limited to user-authorised feature access, specific support access with documented consent, necessary security investigations, legal requirements, or permitted anonymised and aggregated use.
5. How and why information is used
We use information to manage accounts and permissions; organise diaries, bookings and setlists; send booking communications; deliver audience interactions; manage subscription access; answer support requests; and maintain security and prevent duplicate voting or other abuse.
Depending on the activity, processing is necessary to provide the service under our agreement, supports legitimate interests in operating and securing the service and administering bookings, fulfils a legal obligation, or relies on consent where required. Optional Google access requires your authorisation and remains subject to the additional restrictions above.
6. Who receives information
We do not sell personal information. Information is made available according to the feature, intended recipient and account permissions—not simply to every person using Mobrool.
- Artists, team members and clients: authorised people receive the diary, booking or show information needed for their roles. Selected repertoire and booking documents may be emailed to clients. Messages and media submitted for a show may be presented to its audience.
- Hosting and storage: the production application is hosted on AWS, with its PostgreSQL database on AWS RDS. Hosting, file-storage and operational service providers process information needed to run the service.
- Email services: Google handles emails sent through connected Gmail accounts. Mobrool's platform email-delivery service handles applicable notifications and emails, including their recipient addresses, content and attachments.
- Payments: Stripe processes subscription checkout and payment information. Card entry in Stripe checkout takes place with Stripe. Mobrool uses billing identifiers and payment/subscription statuses to manage access. See Stripe's privacy policy.
- Support, security and legal requirements: information may be accessed or disclosed where necessary for permitted support, abuse investigation or legal obligations. Google-derived data remains subject to the stricter Limited Use rules above.
Third-party services may also process information under their own policies. Some providers may process data outside the United Kingdom; where international-transfer requirements apply, appropriate safeguards are required. Contact us for information about relevant providers and transfers.
7. Retention, disconnection and deletion
Invitation requests: we collect your email, band or business name, UK town or region, intended use, UK customer declaration and contact-permission record to review and reply to your request. This is not permission for general marketing. We do not collect your IP address in this queue. Duplicate requests do not replace the original details or extend retention. Requests are removed six calendar months after submission, with daily cleanup while the service runs and cleanup when the queue is next used. You may withdraw permission or request earlier removal at admin@mobrool.live. A request does not create an account, issue an invitation or promise complimentary access. Invitation and account records, if separately created, have their own retention purposes.
International availability interest: if you register interest, we collect your email address, country, optional band or business name, and a record of your consent. We use these details only to consider international availability and, with your permission, contact you about that availability. This does not create an account or invitation, trigger an automatic email, or permit unrelated marketing. The information may be removed by an operator following a request to admin@mobrool.live.
We retain information while it is needed for the purposes described here, including maintaining an active account and its diary or booking history, providing support, resolving disputes, protecting the service and meeting applicable legal or accounting obligations. A gig ending does not itself erase its booking history.
Google connection tokens remain while the connection record exists and are removed by disconnecting that connection in Mobrool. Imported diary information and booking or delivery records are separate records and may remain until separately deleted or no longer needed.
Request account closure or deletion of specific personal information by emailing admin@mobrool.live. We may need to verify your identity and consider records shared with other account members, legal retention requirements and the scope of your request. No universal fixed retention period is promised for every category.
If backup copies exist, their removal follows the relevant backup lifecycle rather than immediate deletion from every copy. Emails already delivered to recipients, Google's own records and Stripe's records are not automatically erased by deleting data from Mobrool.
8. Security
We use account permissions, password hashing and encrypted storage of Google authorisation tokens as part of protecting information. Access is limited according to roles and service needs. This does not mean every stored item or session record is encrypted in the same way, and no online service can guarantee absolute security.
Media access depends on how it is used and shared: material selected for an audience presentation is not subject to the same visibility as private booking or account information.
9. Cookies and browser storage
Cookies and browser storage support sign-in, account context, preferences and applicable show participation or duplicate-vote controls. Essential storage is needed for the requested features. Preferences may use browser storage rather than cookies.
The login session cookie uses a rolling 24-hour expiry: activity can extend it. Other storage can have a different lifetime, so this is not a promise that all session or browser data disappears exactly 24 hours after login.
You can manage cookies and local storage through your browser. Blocking essential storage may prevent sign-in or other features from working. Where non-essential storage requires consent, that consent must be obtained before it is used.
10. Your rights and concerns
Subject to applicable law and relevant exceptions, you can request access, correction, deletion, restriction or a portable copy of your personal information, object to certain processing, and withdraw consent where processing relies on it. Withdrawing consent does not undo lawful processing that already occurred.
Contact admin@mobrool.live to make a request or raise a concern. For booking decisions made by an artist or band, you may also need to contact that artist directly. You can complain to the UK Information Commissioner's Office or your relevant data-protection authority.
Artists organising events involving children should take particular care with personal information, messages and uploaded media. If you believe a child's information has been supplied without appropriate authority or shared inappropriately, contact us so the concern can be reviewed.
11. Changes to this policy
Changes will be published here with an updated date. Material changes to data use will be communicated where required, and fresh consent will be requested where necessary. This notice describes the service's practices; it is not legal advice or a guarantee of Google verification.