Privacy Policy

Last updated: September 20, 2026

PleasePlay.Music lets audiences request songs from bands, duos, and solo performers, which we call “acts.” Pat Dryburgh owns and operates PleasePlay.Music and is responsible for the personal information handled by the service. In this policy, “we” and “our” refer to Pat Dryburgh operating PleasePlay.Music.

For privacy questions or requests, email ppm@patdryburgh.com.

You can request songs without an account or email address. Joining an act’s mailing list or verifying an existing subscription is optional. We use the email address you submit for that choice as described below. We do not sell personal information. Our application pages do not include advertising trackers or third-party analytics scripts.

Song Requests

When you request a song, we store the song’s identifier, title and artist, the request time, a randomly generated browser identifier, and its association with the current request session and any linked show. We use these records to run the queue, prevent duplicate requests, and produce show reports. The browser identifier lets us recognize requests across tabs and QR-code rescans; it is not an audience account. If you sign up for the newsletter or verify an existing subscription, we also associate your requests with a subscriber code for reporting and subscriber Boosts.

Song titles, artists, photos and photo credits, request counts, subscriber bonus totals, Boost totals, first-request times, and whether songs are available, requested, or played are available through the act’s public pages and song data. Act members can also view individual request times and member-only reports of song popularity and newsletter signups for their shows. Audience contact details, browser identifiers, and subscriber codes are not displayed in the public queue or included in live queue updates.

Optional Email Updates From An Act

When you leave the email field in an eligible pledge form, we check that address with the act’s newsletter service to see whether to offer signup. This lookup does not subscribe you, save the address in our newsletter records, or add Boosts. If signup is available, a separate, unchecked option lets you request it when you submit your pledge. Newsletter signup is processed independently of whether the payment succeeds.

Song requests do not require an email address. After requesting, you can separately choose to receive upcoming show dates and occasional updates from the act, or verify an existing subscription. The newsletter form asks for your email address, which passes through our server to the act’s selected service, Kit or Mailchimp. For Mailchimp, the form can also show the public audience fields configured by the act in Mailchimp, in Mailchimp’s display order. Any details you enter in those fields pass through our server to that Mailchimp audience with your consenting signup.

Both signup and “Already Subscribed?” check your subscription with that service. An active subscriber can add the number of Boosts displayed on the form to one request per show without another confirmation email. If the address is not subscribed, the action requests signup through the provider’s confirmation flow. Boosts are added only after the provider confirms an active subscription and while the selected song is still eligible. An existing subscriber’s Boosts cannot be used twice in the same show.

When a signup is submitted successfully or an active subscription is verified, we link it to all requests made with the same browser identifier during that show, including requests made before and after signup or verification. Once the service confirms an active subscription, we send show and requested-song tags to that service so the act can organize its list and follow up.

We store your email address encrypted in temporary confirmation and tagging records. Background cleanup is scheduled to clear that address from the live database once its record is seven days old. Earlier backup copies can retain it for the backup retention period described below. The subscriber code, browser and show associations, signup and verification status and times, and subscriber bonus records remain after the address is cleared. Request history stores the subscriber code rather than your email address. Contact profiles and email addresses are not displayed on public pages.

The act controls its mailing list and messages. Kit confirmation emails depend on the act’s form settings. New Mailchimp contacts receive a confirmation email; an explicit signup can also return an unsubscribed contact to pending confirmation. A provider failure does not remove an already accepted song request. Kit’s handling of subscriber information is described in its Data Processing Addendum; Mailchimp links to Intuit’s Privacy Statement.

For show reporting, we record which requests are associated with a successful signup or subscription verification. The subscriber code is generated from your email address using a server secret, separately for each act. It lets us count the same address once within a report and show which songs were associated with newsletter activity, without storing the email address itself in request history. These codes are not displayed in reports or public pages. Signup counts can include existing subscribers and people who have not yet confirmed their email; they are not a count of newly confirmed subscribers.

Emails an act sends through Kit or Mailchimp may track opens and link clicks to measure engagement. Kit explains its email open tracking and open and click reporting. Contact the act about its email practices. The application does not retrieve these email engagement reports.

Your browser tab remembers the email form value so you can continue without retyping it. Clearing browser data or closing the tab does not unsubscribe you. Use the unsubscribe link in the act’s emails or contact the act. Pat can help identify the relevant act.

Optional Pledges And Tips

If an act enables tips, you can choose a pledge or a thank-you tip in the currency shown after requesting a song. Stripe’s secure payment fields collect payment and billing details under the Stripe Privacy Policy. Our application does not collect or store your full card number or security code. Payment alone does not subscribe you to the act’s mailing list; newsletter signup requires a separate choice.

We send the selected payment processor the amount, currency, act name, song title, and identifiers for the act and pledge. We retain the pledge's association with your browser identifier, request and show, its amount and currency, awarded Boost value and award time, payment status and timestamps, payment processor, account and transaction identifiers, checkout details, and receipt link. These records support authorization, collection or release, recovery from interrupted checkout, and show reporting. Aggregate pledged amounts and Boosts are available in the public song data. Individual payment status and receipt links are available through your request confirmation; the act’s payment account also contains transaction and billing information provided to its processor.

When an act sets up payments, Stripe collects its account owner’s country, business, identity-verification, and payout information through its hosted onboarding. We store the act’s processor account identifier, setup attempt, and setup status, with connection information encrypted. Payment records have no scheduled expiry in our application and are included in database backups. Contact Pat about access or deletion requests; Stripe and the act separately control records held by Stripe.

Performer Accounts And Act Settings

Act members sign in with Google. We receive and store your Google account identifier, name, email address, email verification status, and profile image if provided. We also store authentication tokens, session records, and related expiry and activity times. Session records can include your IP address and browser information. We use this information to sign you in, maintain your account, and protect access. The application requests basic identity information; it does not request access to your Gmail, contacts, calendar, or Drive files. Google handles your sign-in under Google’s privacy policy.

We store your act memberships and invitation records, including who created an invitation and its creation, expiry, revocation, or redemption status. Other members of your act can see your name and email address. All members have equal access to the act’s settings, integrations, invitations, membership management, and request history.

Act information includes its name, public URL, logo, home screen icon, website and social links, song catalogue, show schedule, and integration settings. Branding, links, songs, artist photos and credits, and displayed show details are public. When a member sets an artist photo, we store its image URL, source URL, credit, the member’s identifier, and the update time. We fetch song and show information from feeds configured by act members, including BandHelper. We do not send audience contact details or request history to those feeds.

When an act connects Kit, we store its authorization tokens and connection information and read available forms so members can choose a signup destination. Kit receives an act identifier to associate the connection with the correct act. A member can disconnect Kit in the Newsletter tab; a successful disconnect revokes the authorization and removes the locally stored connection tokens. It does not delete subscribers already held in Kit.

When an act connects Mailchimp, we store its authorization token and API server location, and read its audiences and public signup fields so members can select an audience and review the form that fans will see. These credentials are encrypted. Public field labels, types, required status, help text, display order, and choices come from Mailchimp; unsupported optional fields are omitted, and an unsupported required field disables signup. Disconnecting Mailchimp in Newsletter removes this act’s locally stored connection, but does not delete contacts or revoke authorization at Mailchimp. An act member can separately remove the app from Mailchimp’s authorized applications; doing so may affect other acts using that authorization.

Cookies, Browser Storage, And Notifications

We use cookies needed for Google sign-in, maintaining an authenticated session, and completing invitation, Kit, and Mailchimp authorization flows. The sign-in session cookie normally lasts seven days and can renew while you use the service. Invitation cookies last up to 30 minutes; Kit and Mailchimp authorization cookies last up to 10 minutes. Signing out ends the current authenticated session.

For audience requests, local storage keeps a randomly generated, act-specific browser identifier across tabs until site data is cleared. Session storage keeps the current request, requested songs, email form value, and unfinished checkout identifier and amount for that tab, and can also hold the browser identifier. The email value is remembered as you type, even before you submit the newsletter form. Browser restoration may preserve a tab’s session. To remove remembered details, clear site data and close the site’s tabs without restoring the previous session. This does not erase server records or newsletter subscriptions. Blocking browser storage can prevent continuity across tabs or page visits.

For act members, local storage remembers the BandHelper linking preference for each act in the current browser until it is changed or site data is cleared.

If an act member enables notifications, we store the browser’s push subscription address, delivery keys, associated member identifier, and registration times. We use the browser’s push provider to deliver notifications containing song titles and artists. You can turn notifications off in your browser or device settings. Signing out alone does not cancel a push subscription.

Technical Information And Service Providers

Our servers process IP addresses and request information to deliver pages, limit excessive requests, and investigate errors or abuse. Hosting infrastructure and operational logs may record request URLs, timestamps, browser information, and errors. Railway hosts the application and database; Railway’s privacy policy describes its practices. Cloudflare R2 stores our database backups for recovery, as described under Retention And Security. See Cloudflare’s privacy policy for its practices.

We use Healthchecks.io to monitor backup runs and alert Pat to failed or missed backups. It receives a monitoring identifier, backup status and timing, and connection information from the backup server, such as its IP address. Our monitoring requests contain no database contents, audience or act-member contact details, or application logs. Healthchecks also processes Pat’s account and alert contact information under its privacy policy.

Pat and service providers supporting hosting, backup storage and monitoring, authentication, email signup, and push delivery may process information needed to operate their part of the service. Act members receive the information described above for their own act. Information may also be disclosed where required by law or where legally permitted and necessary to address fraud, abuse, or security incidents.

If you contact Pat, we receive your email address and the information you include in your message. We use that correspondence to respond, provide support, or handle your privacy request; it is also processed by the email services used to exchange those messages.

To find artist photos, our server sends catalogue artist names or public artist identifiers to Wikidata and Wikimedia Commons. These lookups do not include audience contact details, browser identifiers, or request history. Act logos, home screen icons, and artist photos may load directly from external hosts, including Wikimedia and hosts selected by act members. Those hosts receive connection information such as your IP address and browser information. Links to photo sources, act websites, social networks, maps, or BandHelper take you to services with their own privacy policies.

Hosting and other providers may process information outside your country, including in the United States. The processing countries depend on the provider and service configuration; Kit’s subprocessor list identifies providers that process subscriber data in the United States. Different privacy laws may apply, and information may be accessible to authorities under local law. Contact Pat for information about the service’s current storage and processing arrangements.

Retention And Security

Song-request history, browser identifiers linked to it, show reports, subscriber codes, and newsletter verification and bonus records have no scheduled expiry in the application, apart from the temporary email-address cleanup described above. Resetting the live queue, making a song available again, ending a show, or removing a song from an imported catalogue does not delete its reporting history. Account, membership, invitation, and artist-photo editing records have no automatic deletion schedule in the current application; expiry of a session or invitation does not necessarily remove its stored record. Contact Pat to request deletion.

Push subscriptions are removed following an authorized deletion request, when the associated member is removed from the act, or when a delivery attempt reports that the subscription is invalid or expired. Subscriptions retained from the older version of the service are inactive and require manual deletion. Turning notifications off may leave a stored subscription until one of these removal events occurs.

To help recover from data loss or service disruption, we schedule a full database backup each night and may also run backups manually. These copies are stored privately in Cloudflare R2 and include the information present in the database when the backup is made, including account and session records, request history, and any temporary newsletter contact records or stored integration credentials. Each backup is scheduled for automatic deletion 30 days after it is created; storage-provider processing may delay removal. This backup schedule does not change the retention of records still in the live database.

Deleting or correcting information in the live database does not immediately change earlier backups. Email addresses cleared by the seven-day cleanup and integration credentials removed on disconnection can therefore remain in older copies until those backups expire. We keep backups for recovery and related integrity checks. Mailing-list retention is controlled by the act and its selected email service. Deletion from our database does not automatically remove logs or another provider’s records, and the 30-day backup schedule does not apply to those records. Any applicable legal retention requirements may also limit deletion. Contact Pat to discuss these records and the scope of a deletion request.

We use authentication, membership checks, and separate act data areas to restrict access. Stored Kit and Mailchimp authorization tokens, temporary newsletter contact records, and the song feed URL configured in Song Library are encrypted by the application. Backup transfers to and from Cloudflare R2 use encrypted HTTPS connections, and Cloudflare encrypts stored backup files using keys it manages. These controls do not prevent the operator or authorized database administrators from accessing stored data, and no internet service can guarantee complete security.

Your Choices And Privacy Requests

You can decline marketing emails, unsubscribe from an act’s list, clear browser data, disable notifications, and disconnect integrations you manage. Act members can edit act settings and manage memberships. Removing a membership or disconnecting Google does not itself delete your PleasePlay.Music account.

To request access to, correction of, or deletion of your personal information, or to raise a privacy concern, contact Pat Dryburgh at ppm@patdryburgh.com. Include the relevant act and enough context to locate the information. For an audience request, its approximate time and song can help. For requests associated with newsletter signup or verification, we can use your email address to look up its act-specific subscriber code. We may need to verify your identity without exposing someone else’s information. For older requests or requests without newsletter activity, we may be unable to reliably identify which stored requests are yours.

We will respond in accordance with applicable privacy law and explain any limits on a request. Depending on where you live, you may have additional rights, including the right to complain to the privacy authority responsible for your jurisdiction. Contact us as well if you believe a child has provided personal information that should be removed.

Changes To This Policy

We will post updates on this page and change the date above. If a change introduces a new use or disclosure that requires consent, we will seek that consent before applying it.