QueueFy

Privacy Policy

This policy explains what information is collected when you use QueueFy, how it is used, and what choices you have.

Effective date: August 20, 2026

Who we are

QueueFy is a product operated by rilo.cc, a company based in Brazil.

QueueFy helps you save and organize links to media from third-party platforms such as YouTube, X, Netflix, and Apple Podcasts into a personal queue. QueueFy does not own or operate those third-party media services.

This Privacy Policy applies to the QueueFy website, app, and browser extension where it is shown or linked.

For privacy questions, requests, or complaints, contact support@rilo.cc.

Information we collect

QueueFy currently collects limited information depending on how you use the service.

Waitlist information: your email address and UTM / campaign attribution data when you join the waitlist.

Account and access information: your email address and authentication-related information when you sign in using Google sign-in through Firebase.

Product analytics information: usage and event data collected through analytics tools such as Firebase Analytics and PostHog. These tools may use cookies or similar technologies.

User content: the links and related queue and list data you choose to save inside the product. Your saved content is private — you can access only your own saved links and queue data, and no user data is intentionally shared with other users at this stage.

How we use information

We use collected information to operate and maintain the product, authenticate users, and secure access.

We use waitlist information to manage the waitlist and communicate about access to the product.

We use analytics information to understand product usage, improve the service, and diagnose bugs, performance issues, and abuse.

We may also process information where necessary to comply with legal obligations.

Third-party services

QueueFy uses third-party service providers to help operate the product, including providers for authentication, infrastructure, and analytics.

These currently include Firebase and Google sign-in services for authentication and infrastructure, and Firebase Analytics and PostHog for product analytics.

Those providers may process certain information on QueueFy's behalf according to their own terms and privacy documentation.

YouTube integration

QueueFy uses YouTube API Services. If you connect your YouTube account, QueueFy can import playlists from your channel into QueueFy and keep a QueueFy folder and a YouTube playlist in sync with each other.

By using QueueFy's YouTube features, you agree to be bound by the YouTube Terms of Service. Google's own handling of your information is described in the Google Privacy Policy.

What QueueFy accesses: connecting your account grants QueueFy permission to see, create, and modify the playlists on your YouTube channel and the videos in them. QueueFy requests a single permission for this (the youtube.force-ssl scope) and uses it only to read the playlists you choose to import and to write the changes you make in QueueFy back to the matching YouTube playlist. QueueFy does not access your watch history, your subscriptions, your comments, or your channel analytics.

What QueueFy stores: your Google authorization tokens, the identifiers of the playlists you chose to sync, and basic information about the videos in those playlists — the video link, title, thumbnail, channel name, and duration.

How long QueueFy keeps it: information read from your YouTube account is refreshed from YouTube's public API, or deleted, at least every 30 days. Your saved links and folders are your own content and are kept until you delete them.

How to disconnect: you can disconnect your YouTube account at any time from the YouTube integration settings inside QueueFy. Disconnecting revokes QueueFy's authorization with Google, deletes the authorization tokens QueueFy stored for you, and removes the video information QueueFy read from your YouTube account. Your folders and saved links stay in QueueFy. You can also review and revoke QueueFy's access directly from the Google security settings page.

How we share Google user data

“Google user data” means the information QueueFy receives from your Google Account when you sign in with Google or connect your YouTube account — your email address, basic profile information, and, if you connect YouTube, access to the playlists on your channel.

QueueFy does not sell Google user data, does not share it for advertising, and does not use it to develop, improve, or train generalized artificial-intelligence or machine-learning models.

Google user data is disclosed only to the following service providers, and only so they can operate QueueFy on our behalf:

Google LLC (Firebase Authentication, Cloud Firestore, Cloud Functions, and Firebase Hosting) — stores your account, your queue, and, if you connect YouTube, the authorization tokens that let QueueFy manage the playlists it creates for you. This data stays inside Google's own platform.

PostHog, Inc. (product analytics, hosted in the United States) — receives your email address as the identifier for your analytics profile, together with product usage events. It does not receive your YouTube authorization tokens, and it does not receive the contents of your playlists.

No other party receives Google user data. We may disclose it outside this list only where we are legally required to, such as in response to a valid legal request, or where necessary to investigate abuse or protect the rights and safety of users.

QueueFy's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect Google user data

Google user data, including your YouTube authorization tokens, is treated as sensitive and is protected by the following measures.

Encryption in transit: all traffic between QueueFy's apps, its browser extension, and its backend travels over HTTPS/TLS. QueueFy requests the YouTube scope in its SSL-only form, so requests to the YouTube API are never sent unencrypted.

Encryption at rest: account data and YouTube authorization tokens are stored in Google Cloud Firestore, which encrypts stored data at rest by default.

Access control: each user's data is stored under their own account identifier, and database security rules allow a signed-in user to read or write only their own records. YouTube authorization tokens are never exposed to the browser, the extension, or other users — they are used only by QueueFy's backend.

Minimum access: QueueFy requests only the scopes its features need, and uses the YouTube authorization solely to create and maintain the playlists it syncs for you. It does not read, modify, or delete your videos, comments, captions, or ratings.

Revocation and deletion: disconnecting YouTube in the app revokes the authorization with Google and deletes the stored tokens from our database. You can also revoke access at any time from the Google security settings page.

Operational access: access to production systems is limited to the people who operate QueueFy and is protected by the account controls of the underlying Google Cloud project.

Browser extension permissions

The QueueFy browser extension is built on Chrome's Manifest V3 and requests only the permissions its features need. All of the extension's code runs locally on your device — it does not download or run code from remote servers.

The table below lists each permission the extension requests and why it is used. Some permissions power optional features that you can turn off in the extension's settings. What information the extension collects, and the third-party services that process it, is described in the sections above.

Website access
Displays QueueFy's “add to queue” button on the pages you visit — including YouTube thumbnails and embedded YouTube players on other websites — and shows the floating mini-player on whatever tab is playing a queued item. You can limit the add button to supported sites (such as YouTube and Spotify) in the extension's settings.
Storage
Saves your queue, sign-in session, and extension preferences on your device.
Tabs
Detects and controls the tab that is currently playing a queued item so playback and the mini-player stay in sync.
Active tab
Reads the media on the page you are viewing when you choose to add it to a queue.
Scripting
Adds QueueFy's on-page controls (the add button and the mini-player) to the pages where you save or play media.
Context menus
Provides the right-click “Add to QueueFy” option on videos and links.
Offscreen documents
Runs the background audio, media-session, and queue-sync tasks the extension needs while it plays your queue.
Clipboard (read)
Lets you paste a link to add it to a queue.
Debugger
Used only to start and control playback on sites that block automatic playback (such as Apple Podcasts, Spotify, Netflix, Instagram, and Facebook), so your queue can continue hands-free and keep picture-in-picture playing. This feature is optional: if you turn off automatic playback / picture-in-picture in the extension's settings, QueueFy does not use it. Chrome shows a “QueueFy started debugging this browser” notice while it is active.
Google and Firebase services
Connects to Google and Firebase to sign you in and sync your queue across your devices.

Legal basis and international use

QueueFy is operated from Brazil and aims to handle personal data using a conservative, privacy-respectful approach suitable for users in different regions.

Where applicable, data is processed to provide the service, for legitimate business operations such as security and analytics, and based on your own actions such as joining the waitlist or signing in.

Data retention

QueueFy keeps personal data for as long as reasonably necessary to operate the service, maintain security, comply with legal obligations, resolve disputes, and enforce agreements.

Waitlist data may be deleted or minimized when it is no longer needed, including after the waitlist is discontinued.

Your choices and rights

Depending on your location, you may have rights to request access to, correction of, or deletion of your personal data, or to ask questions about how your data is handled.

QueueFy will review and respond to reasonable requests in accordance with applicable law.

To exercise these rights, contact support@rilo.cc.

Security

QueueFy uses reasonable technical and organizational measures appropriate for an early-stage product to protect information against unauthorized access, misuse, or loss.

No method of storage or transmission is completely secure. If you believe your account has been compromised, contact us so we can investigate and help secure access.

Children's privacy

QueueFy is not intentionally designed for children.

If QueueFy learns that personal data was provided in a way that creates a legal issue under applicable law, it may take steps to remove that information.

Changes and contact

This Privacy Policy may be updated from time to time. When changes are made, the updated version will be posted on this page with a revised effective date.

Questions or requests about privacy may be sent to support@rilo.cc.