Privacy Policy
Up Next is an article-to-audio service. This policy explains the data we handle when you use it and why. We have written it in plain language to describe the service as it works today.
1. What we collect when you sign in
Up Next offers sign-in with Google. When you sign in, we store the name, email address, and avatar URL provided through your Google account. We also store the Google OAuth account identifier, access token, refresh token, ID token, and granted scope on our servers so the sign-in connection can work.
We store session records that include a session token, expiry information, IP address, and browser user-agent. Sessions last for seven days.
2. Using Up Next without an account
You can use Up Next as a guest. Your browser creates a guest identifier in local storage with the format guest_…. We use that identifier to associate your queue, listening history, and preferences with you on our servers without requiring an account.
If you later sign in, we migrate that guest data to your account and remove the guest identifier from your browser after a successful migration.
3. Content you submit
When you submit an article, we store its URL, extracted text, and related metadata such as its title, author, site name, image, description, publication date, and word count. We also store the AI-generated summary and the generated audio file.
Articles are deduplicated and shared across users by URL. That means a submitted article is not private to the person who submitted it. Please do not submit a URL if the existence of that URL is sensitive.
4. Playback and preferences
We store your queue position, listening progress, completion state, and playback history. We also store your playback speed and autoplay setting. This applies to both account holders and guests, using the identity described above. Your appearance theme is stored only in your browser's local storage and is not synced to our servers.
5. Who processes your data
We use the following providers to operate Up Next. Extracted article text is sent to AI providers for summaries, summary scripts are sent for audio, and submitted URLs pass through article-fetching infrastructure.
Google: Google provides sign-in and supplies the profile details described above. Google Gemini processes extracted article text for summarization and summary scripts for text-to-speech.
Groq and OpenAI: Groq is a summarization fallback and receives article text when used. OpenAI is a text-to-speech fallback and receives summary scripts when used.
Cloudflare: Cloudflare hosts the service and provides our Workers, D1 database, R2 audio storage, KV rate limiting, processing workflows, and operational logs.
Crawl4AI and Pydoll: These self-hosted scraping services run on Google Cloud Run and receive submitted URLs to fetch articles.
Bright Data:Some article-fetching requests use Bright Data's proxy service, which receives the submitted URL.
6. What we do not do
We do not use third-party analytics or advertising trackers, and we do not sell your data.
7. Cookies and local storage
We use better-auth session cookies to keep signed-in users authenticated, including a short-lived session-data cookie. Your browser's local storage may contain up-next-user-id for the guest identifier, upnext_guest for guest interface state, and theme for your appearance preference. Session storage may contain upnext:watch-article, an ephemeral playback trigger.
For abuse prevention, we briefly store normalized visitor IP addresses in Cloudflare KV using time-windowed rate-limit records.
8. Data retention and deletion
Up Next does not currently offer self-serve account or data deletion. To request deletion of your account and associated data, contact us at support@upnx.net. We handle deletion requests manually.
9. Changes to this policy
We may update this policy as Up Next changes. We will post any updates on this page.
10. Contact
For privacy questions or deletion requests, contact us at support@upnx.net.