Privacy Policy — feelnewz

Overview

The short version: feelnewz stores a small amount of data locally in your browser to remember your preferences. None of it ever leaves your device.

The bottom line

feelnewz has no servers, no user accounts, no analytics, and no advertising. All data is stored in chrome.storage.local — on your device only — and can be cleared at any time by removing the extension.

feelnewz is a Chrome new tab extension published by GoManzanas. It replaces your new tab page with a mood check-in, mood-matched Spotify music, news headlines from public sources, mini games, and quotes. This policy covers what data the extension stores, why, and how it behaves with respect to third-party services it loads content from.

What feelnewz stores locally

All storage is in chrome.storage.local — it is local to your browser, on your device, and is never transmitted to any server.

Storage key	What it contains	Why
`vcQuoteIndices`	A counter per mood tracking which quote you last saw	So you get a new quote each time instead of the same one
`customPlaylist_*`	A Spotify playlist ID you chose to save (one per mood, optional)	To remember your preferred playlist across tabs
`bookmarks`	URLs and titles of articles you starred	To persist your bookmark list between sessions
`articleCache`	Fetched news headlines and their timestamps	5-minute cache so tabs load instantly without re-fetching
`theme`	`"light"`, `"dark"`, or unset (follows system)	To remember your theme preference
`enabledSources`	Which news sources you have turned on or off	To remember your source preferences
`customSources`	Any custom news sources you added (name, URL, selector)	To persist your custom scraper configuration
`shortcuts`	Any browser shortcuts you pinned to the home view	To persist your shortcut list across sessions

How to clear this data

Go to chrome://extensions, find feelnewz, click "Details", then "Extension options" (if available), or simply remove the extension. Removing the extension deletes all associated chrome.storage.local data from your device automatically.

What is not stored

feelnewz does not store your browsing history, the URLs of pages you visit, your identity, any personal information, financial data, health data, authentication credentials, or communication content. The mood you pick each new tab is used only to render the current tab's content and is not persisted.

What we don't collect

feelnewz has no backend. There is no server that receives data from your browser.

No usage analytics. We do not track which features you use, how often you open a new tab, or what moods you select.
No crash reporting. Errors are logged only to the browser's internal console — not sent anywhere.
No advertising identifiers. feelnewz contains no ad SDKs, trackers, or fingerprinting scripts.
No browsing history. The extension never reads, stores, or transmits the URLs you visit.
No personal information. There are no sign-up flows, email fields, or accounts of any kind.
No data sharing. Because we collect nothing, there is nothing to sell or share with third parties.

Permissions explained

feelnewz requests the minimum Chrome permissions needed to work. Here is what each one is for.

Permission	Why it's needed
`storage`	To read and write `chrome.storage.local` — bookmarks, theme, quote state, article cache, and your custom playlists. All data stays on your device.
`alarms`	Reserved for scheduling periodic cache refreshes using Chrome's alarm API. No data is transmitted.
`host_permissions` (news sites)	Allows the background service worker to `fetch()` HTML from the listed news sites (TechCrunch, The Verge, Ars Technica, Reuters, AP News, BBC, CNBC, Al Jazeera, The Guardian, Deutsche Welle, MarketWatch, FT) to extract headlines. No user data is included in these requests — they are plain HTTP GET requests to public pages, identical to visiting the site in your browser.

Why host_permissions?

Chrome extensions with declared host_permissions can bypass the browser's Same-Origin Policy for fetch() calls in the background service worker. This is how feelnewz retrieves headlines without a proxy server — the fetch goes directly from your browser to the news site.

Third-party content

feelnewz embeds content from external services. Those services have their own privacy policies.

Spotify

The music card embeds playlists via open.spotify.com/embed/playlist/…. When the iframe loads, your browser connects directly to Spotify's servers. Spotify may set cookies and collect usage data according to their own privacy policy. feelnewz does not intercept, log, or transmit anything from these Spotify connections.

You can prevent the Spotify iframe from loading by hiding the player using the ⏸ button in the mini bar. No Spotify playlist data loads until the music card is rendered on screen.

YouTube

The Videos card shows thumbnail images loaded from img.youtube.com and, when you click a video, an embedded player from youtube.com. These are standard YouTube embed URLs with no tracking parameters added by feelnewz. YouTube's privacy policy applies to these connections.

News websites

Headlines are scraped by the background service worker using plain fetch() requests to the public homepages of the listed news sites. These requests look like a normal browser visit. The extension does not share any user data with these sites — it simply reads the public HTML to extract headlines. No cookies from the news sites are available to the extension's service worker context.

Google Fonts

The new tab page loads the Fredoka font from fonts.googleapis.com. This is a standard Google Fonts request. Google may log this request per their privacy policy.

Service	What loads	Their privacy policy
Spotify	Playlist embed iframe	spotify.com/legal/privacy-policy
YouTube / Google	Video thumbnails + embed player (on click)	policies.google.com/privacy
Google Fonts	Fredoka typeface	policies.google.com/privacy
News sources	Public HTML headlines via fetch()	Each site's own privacy policy

Your rights & controls

You have full control over every piece of data feelnewz touches.

Deleting your data

Because all data is stored locally in chrome.storage.local, you can delete it at any time by:

Removing the feelnewz extension from Chrome (chrome://extensions → Remove). Chrome automatically purges all storage data for a removed extension.
Clearing site data in Chrome settings (Settings → Privacy and security → Clear browsing data → Hosted app data).

Custom playlists

If you've saved a custom Spotify playlist, you can reset it at any time using the "Reset to default" link inside the music card for that mood.

Bookmarks

Bookmarks can be deleted individually from the Bookmarks tab in feelnewz, or all at once by removing the extension.

No account → no data request needed

Because feelnewz has no accounts and no servers, there is no personal data held by GoManzanas to request, export, or erase on your behalf. The only copy of your data is the one on your device.

GDPR / CCPA note

feelnewz does not process personal data as defined by GDPR or CCPA because it does not collect, transmit, or store any data that identifies you. There is no data controller relationship — you are the sole custodian of data stored locally in your browser.

Changes to this policy

We'll tell you when things change.

If we materially change how feelnewz handles data, we will update this page and increment the "Effective Date" at the top. Significant changes (such as introducing any form of data collection) will also be noted in the Chrome Web Store release notes for the relevant extension version.

Minor clarifications or formatting updates that don't change the substance of our practices will be updated silently.

Contact

Questions about this policy? Reach us directly.

For privacy questions, data inquiries, or anything related to feelnewz:

Channel	Details
Email	extensions@gomanzanas.com
Issues tracker	github.com/GoManzanas/extensions/issues
Publisher	GoManzanas

Response time

We aim to respond to privacy inquiries within 5 business days.