1. Who operates Playloudr
Extra Life Records Ltd, trading as Playloudr, is the data controller responsible for the personal information described in this Privacy Policy. The website is playloudr.com.
2. How to contact us
For privacy questions, rights requests, deletion requests, or questions about this policy, email hello@extraliferecords.com. Please do not include passwords, access tokens, or other unnecessary sensitive information in an initial email.
3. Information you provide directly
Depending on how you use Playloudr, you may provide your name, email address, account details, artist or label details, release and campaign information, public copy, destination links, uploaded media, reward files, fan sign-up details, and messages sent to us.
If you submit a fan email through a Smart Link, Pre-Save, Promo Gate, or artist page, that email and any name or campaign context you provide may be stored for the relevant artist or campaign.
4. Account and authentication information
Playloudr uses Firebase Authentication for account sign-in. The application supports email-and-password accounts and Google sign-in. Authentication records can include an account identifier, email address, display name, profile image, provider identifier, sign-in timestamps, and security state.
Passwords are submitted to and managed by the authentication provider; Playloudr does not use its Firestore product database as a password store.
5. Campaign, release, Smart Link, Pre-Save, and uploaded-content data
Artist workspaces can contain release plans, catalogue identifiers, public routes, Smart Links, Pre-Saves, Promo Gates, fan rewards, artist profile information, social and streaming destinations, campaign settings, analytics summaries, and media uploaded to Playloudr storage. The precise fields depend on the feature and the information an artist chooses to enter.
Public pages can display the campaign content an artist publishes. Artist-owned records are scoped by the application’s account and artist ownership checks.
6. Technical, browser, device, log, and usage information
Public campaign pages and their measurement endpoints may receive a visitor identifier, page and campaign identifiers, event names and timestamps, referring URL, page URL, country information supplied by the hosting platform, browser user-agent, IP address, and performance or error information. The public tracking code also reads the Meta _fbc and _fbp cookies when present.
Playloudr uses browser storage for a visitor identifier and conversion-session state so that a page can distinguish a reload from a new campaign interaction. Some static marketing pages can load Google Analytics 4 when a measurement ID is configured for that deployment. Whether that optional configuration is enabled for a particular release should be confirmed in the deployment environment.
7. Information received through connected services
When an artist chooses to connect an external service, Playloudr may receive the identifiers, permissions, account or asset metadata, access credentials, and content needed for the authorised feature. Repository-confirmed integrations include Spotify for release metadata and Pre-Save fulfilment; Apple Music and MusicKit for Apple Music Pre-Save flows; YouTube for channel and video metadata; Meta for advertising and measurement; Klaviyo for optional fan-list synchronisation; and Resend for transactional email delivery.
Playloudr also uses external metadata lookups for some release and destination resolution. Not every integration or feature is enabled for every account or deployment.
8. Meta Platform data
Meta, Facebook, and Instagram features are optional and are used only when an artist authorises the relevant Playloudr feature. Based on the current implementation, Playloudr may access or store:
- a Meta account identifier, display name, avatar, granted permission scopes, and connection status;
- Business Portfolio and advertising-account identifiers, saved-audience identifiers, tracking dataset or Pixel identifiers, and eligibility or capability status;
- Facebook Page identifiers and linked Instagram professional-account identifiers selected for an artist;
- campaign, ad-set, advert, creative, launch-status, review-status, and advertising-performance or Insights data needed to prepare and monitor authorised campaigns; and
- a server-side Meta access token or credential used by the authorised connection. Tokens are kept in server-side credential storage rather than rendered into public pages.
Playloudr does not use this implementation to read Instagram messages or general Instagram content. It uses Meta data for authorised connection and asset selection, campaign creation or management where that feature is enabled, and advertising-performance measurement.
On public campaign pages, the Meta Pixel and Conversions API integration can send campaign events to Meta. Those events can include event identifiers, page or campaign identifiers, event source URL, timestamp, browser user-agent, IP address, referring URL, _fbc/_fbp values, and hashed visitor or country identifiers. The code does not indicate that fan email addresses are sent to Meta through this tracking path.
9. Why we process information
We process information to:
- create and secure accounts and artist workspaces;
- provide Smart Links, Pre-Saves, Promo Gates, artist pages, release planning, fan capture, and related analytics;
- connect and operate services an artist has chosen, including authorised Meta advertising features;
- send requested release reminders, reward emails, or service messages;
- prevent abuse, fraud, unauthorised access, and misleading or broken public measurement;
- diagnose errors, improve reliability, and maintain the service; and
- respond to support, privacy, deletion, and legal requests.
10. Lawful bases under UK data-protection law
Depending on the context, the possible lawful bases are performance of a contract or steps requested before entering a contract; consent where a person has made a voluntary choice, such as an optional marketing or connected-service action; legitimate interests in operating, securing, measuring, and improving Playloudr; and compliance with a legal obligation. The appropriate basis depends on the particular processing, product setting, and relationship with the person. The operator should confirm the final basis assessment with its legal adviser before relying on this policy as a complete legal notice.
11. Service providers and processors
The repository confirms the use of Firebase and Google Cloud services for hosting, authentication, database storage, file storage, and server-side functions. Depending on the feature and configuration, external services include Meta, Spotify, Apple Music, YouTube, Klaviyo, Resend, Google Analytics 4, and release-metadata providers. These services may process information on Playloudr’s behalf or as separate services selected by an artist.
The exact processor list, contractual terms, sub-processors, and transfer mechanisms are not fully recorded in this repository and must be confirmed by the operator before publication as a final legal notice.
13. Sale of personal information or Meta Platform data
The current implementation does not provide a feature for selling personal information or Meta Platform data. Playloudr does not sell personal information or Meta Platform data.
14. Data retention
Playloudr stores account, artist, campaign, fan, analytics, and uploaded-content records in its managed data stores while they are needed to provide the service or support a campaign. The repository does not define one complete, fixed retention schedule for every record type. Operational logs, delivery records, security records, and backups may therefore remain for different periods.
When a deletion request is accepted, we take reasonable steps to remove or anonymise the requested information, subject to records that must be retained for legal obligations, security, fraud prevention, billing if applicable, disputes, or the establishment or defence of legal claims. Exact retention periods require confirmation by the operator.
15. Security
Playloudr uses managed Firebase and Google Cloud services, server-side secrets, account and artist ownership checks, access-controlled provider credentials, and encrypted connections to external APIs. These measures reduce risk but cannot guarantee absolute security. Please do not send passwords, access tokens, or private keys by email.
16. International data transfers
Playloudr and its service providers may process information outside the United Kingdom. The repository does not contain a complete map of provider processing locations or transfer safeguards. The operator should confirm the applicable transfer mechanisms and add them to the final legal documentation where required.
18. Your rights under UK data-protection law
Subject to legal conditions and exceptions, you may have rights to request access to your personal information, correction, erasure, restriction, portability, or objection to particular processing, and to withdraw consent where processing relies on consent. To exercise a right, contact hello@extraliferecords.com and describe the request. We may need information to verify identity and protect another person’s information. You can also complain to the UK Information Commissioner’s Office.
19. How to disconnect Meta
If the Meta connection feature is enabled for your account, use the Disconnect Meta action in the Meta account panel in the Playloudr campaign or release advertising workspace. The implemented Playloudr action deletes the stored Playloudr provider connection and its server-side credential for the selected artist; existing Meta campaigns are not deleted by that action.
You can also remove Playloudr from Meta’s Business Integrations settings. Removing the integration in Meta is separate from deleting records already stored by Playloudr. The repository does not show a remote Meta token-revocation call, so removal in Meta is the additional step to invalidate the connection with Meta itself.
20. Account and data deletion requests
Signed-in account holders can delete their own account, and download a copy of their data, from the Account profile page inside Playloudr — see the data-deletion instructions. Anyone can also request deletion without signing in by emailing hello@extraliferecords.com with the account email or other information needed to identify the relevant artist or campaign. We will verify the request before acting and will not ask you to send a password or access token.
21. Children’s privacy
Playloudr is intended for artists, labels, and campaign teams, not for children. Do not use the service or submit information about a child unless you are authorised to do so. If you believe a child’s information has been submitted, contact us so we can review it.
22. Changes to this policy
We may update this policy when the service, integrations, or legal requirements change. We will publish the new version on this page and update the date below. If a change is material, we may provide additional notice where appropriate.
23. Effective and last-updated dates
Effective date: 1 August 2026
Last updated: 5 August 2026
Email hello@extraliferecords.com or read the related pages: TermsData deletion.