Privacy Policy

Last updated: 2025-06-25

This Privacy Policy explains how LetsPlayDB collects, uses, stores, and protects personal data in accordance with the EU General Data Protection Regulation (GDPR), Swedish data protection law, and applicable requirements for use of the YouTube API Services.

Data Controller

LetsPlayDB is operated as a personal project hosted in Sweden. For data protection enquiries, privacy questions, or requests to exercise your rights, contact us via the LetsPlayDB GitHub repository or the email address associated with the project/account.

Infrastructure

The Service is self-hosted on servers located in Sweden. Traffic is routed through Cloudflare’s content delivery network (CDN) for performance, security, and DDoS protection. Cloudflare may process IP addresses and request metadata in transit. Please see Cloudflare’s Privacy Policy for more information:

https://www.cloudflare.com/privacypolicy/

Analytics

LetsPlayDB uses Rybbit, a privacy-first, self-hosted analytics tool. Rybbit does not use cookies, does not track individual users across sessions, and does not collect personally identifiable information. Analytics data consists solely of anonymised aggregate statistics, such as page view counts. No cookie consent is required because no personal data is processed by the analytics system.

Data We Collect

When you create an account, LetsPlayDB collects:

• Your email address
• Your display name
• If using Google OAuth, a Google subject identifier

LetsPlayDB may also store:

• Channels you follow
• Channel access requests you have submitted
• Browser push notification subscriptions, if you opt in
• Strictly necessary authentication session data
• Anonymised security or audit log entries

We do not sell your personal data. We do not share your personal data with third parties except where necessary to operate the Service, comply with legal obligations, protect the Service, or provide infrastructure such as hosting, CDN, security, or authentication.

Authentication Cookies

LetsPlayDB uses a single strictly necessary authentication cookie to keep you logged in. This cookie does not track your behaviour across other websites and is deleted when you log out or delete your account. Because this cookie is essential to the operation of the Service, it does not require your consent under GDPR.

Google OAuth

If you choose to sign in using Google OAuth, LetsPlayDB receives the information required to authenticate your account, such as your email address, display name, and Google subject identifier. LetsPlayDB does not receive or store your Google password.

You can revoke LetsPlayDB’s access to your Google account at any time through your Google account permissions page:

https://myaccount.google.com/permissions

Google’s Privacy Policy is available here:

https://policies.google.com/privacy

YouTube API Services

LetsPlayDB uses YouTube API Services, including the YouTube Data API, to collect, index, organize, and refresh publicly available YouTube metadata related to gaming and “Let’s Play” content.

By using LetsPlayDB, you acknowledge that LetsPlayDB uses YouTube API Services and that YouTube’s own terms and privacy policies may apply. You can review YouTube’s Terms of Service here:

https://www.youtube.com/t/terms

You can review Google’s Privacy Policy here:

https://policies.google.com/privacy

YouTube Data We Access, Collect, and Store

LetsPlayDB may access, collect, store, and display publicly available YouTube information, including:

• YouTube video IDs
• Video titles
• Video descriptions
• Video thumbnails
• Publication dates
• Channel names and channel IDs
• Playlist names, playlist IDs, and playlist item relationships
• Video, channel, and playlist metadata
• Public statistics where available, such as view counts or playlist item counts
• Video availability or status information
• Other public metadata returned by the YouTube API Services

LetsPlayDB uses this information to build and maintain a searchable catalog of Let’s Play and gaming-related YouTube content.

LetsPlayDB does not rehost YouTube videos, download YouTube audiovisual content, provide offline playback, or replace YouTube as the source of the content. When users choose to watch a video, they are directed to YouTube or shown the official YouTube embedded player where applicable.

How We Use YouTube Data

LetsPlayDB uses YouTube API data to:

• Identify and organize videos, playlists, channels, creators, games, series, and episodes
• Keep LetsPlayDB’s catalog accurate and up to date
• Refresh metadata such as titles, thumbnails, descriptions, publication dates, statistics, and availability
• Help users search, browse, and discover Let’s Play content
• Attribute YouTube as the source of YouTube videos, thumbnails, channels, playlists, and related metadata

We do not sell YouTube API data. We do not use YouTube API data to create misleading replacement metrics for YouTube. If LetsPlayDB displays information that is created by LetsPlayDB rather than provided by YouTube, we treat that information as separate from official YouTube data.

YouTube Data Retention and Refreshing

LetsPlayDB stores YouTube API data only as needed to operate and maintain the LetsPlayDB catalog.

Because YouTube metadata can change over time, LetsPlayDB periodically refreshes stored YouTube data to keep it consistent with the current data available through the YouTube API Services. Where required by the YouTube API Services policies, stored YouTube API data is refreshed or deleted within the applicable retention period, including the 30-day refresh/delete requirement for certain YouTube API data.

If a YouTube video, playlist, or channel becomes unavailable, is deleted, or has updated metadata, LetsPlayDB makes reasonable efforts to update its records during normal refresh and maintenance processes.

YouTube Embedded Player

LetsPlayDB may display YouTube videos using the official YouTube embedded player. When a page containing an embedded YouTube player loads, or when a user interacts with or plays an embedded YouTube video, YouTube and Google may collect information according to their own policies.

For more information about how Google collects and uses data, please review Google’s Privacy Policy:

https://policies.google.com/privacy

Data Deletion

You may delete your LetsPlayDB account and associated personal data via Account Settings where available, or by contacting us through the LetsPlayDB GitHub repository.

Upon account deletion, your email address, display name, Google subject identifier, follows, channel access requests, push notification subscriptions, and other personal associations are permanently removed. Anonymised audit log entries recording that an action occurred, without identifying information, may be retained for up to 90 days for security purposes.

If you request deletion of data stored by LetsPlayDB, we will delete the applicable stored personal data as soon as reasonably possible. Where the data is subject to YouTube API Services policies, we will delete applicable stored user data as soon as possible and within 7 calendar days where required.

Deleting data from LetsPlayDB does not delete data from YouTube or Google. To delete or manage content stored by YouTube or Google, you must use YouTube’s or Google’s own account controls and tools.

You can manage or revoke Google account access here:

https://myaccount.google.com/permissions

Your GDPR Rights

Under GDPR, you have the following rights regarding your personal data:

• Right of access — you may request a copy of the data we hold about you.
• Right to rectification — you may correct inaccurate data.
• Right to erasure — you may delete your account and associated personal data.
• Right to restriction — you may ask us to restrict processing in certain circumstances.
• Right to data portability — you may request your data in a machine-readable format.
• Right to object — you may object to certain types of processing.

To exercise these rights, please contact us via the LetsPlayDB GitHub repository or the project contact email.

Security

LetsPlayDB uses reasonable technical and organizational measures to protect stored data from unauthorized access, use, or disclosure. Access to YouTube API credentials, Google OAuth data, and stored API data is limited to what is necessary to operate, maintain, and improve LetsPlayDB.

Contact

For data protection enquiries, privacy questions, or requests to exercise your rights, please send a mail to [email protected].