DailyDock Privacy Policy
Privacy practices for the DailyDock Chrome extension — a personal new-tab dashboard with optional browsing activity, Arcade, and no WAVFin backend; your settings stay on your device.
Last updated — July 6, 2026
Publisher:WAVFin Audio (“we,” “our,” “us”) — operated by an independent developer based in Waterville, Maine, United States.
Product: DailyDock — Chrome/Chromium new-tab extension.
Contact: support@wavfinaudio.com
We have written this policy to satisfy the EU/UK GDPR, the California Consumer Privacy Act/California Privacy Rights Act, COPPA (15 U.S.C. §§ 6501–6506; 16 C.F.R. Part 312), and Chrome Web Store disclosure requirements, and to stay readable. This page is not legal advice.
Overview
DailyDock replaces your browser’s new-tab page with a personal dashboard (news, tasks, notes, weather, search shortcuts, top sites, optional local browsing-activity stats, optional Google Calendar, and an optional Arcade widget). We do not operate a DailyDock backend server. Your settings and content are stored on your device using Chrome’s extension storage. We do not sell your data. If you contact WAVFin Audio through the website support form or by email, that communication is handled under the WAVFin site privacy policy, not this extension policy.
Information the extension handles, why, and on what legal basis
Depending on which features you use, the extension may access or store the data below. The lawful basis under GDPR Art. 6(1) is listed alongside the CCPA category for each row.
| Data | Purpose | Where it goes | Lawful basis (GDPR) | CCPA category |
|---|---|---|---|---|
| Preferences & dashboard data | Theme, layout, module visibility, tasks (kanban), notes, pinned sites, RSS settings, read/saved articles, search engine choice, recent searches, weather ZIP, arcade high scores, browsing-activity preferences, caches. | chrome.storage.local on your device; optional chrome.storage.sync to your signed-in Google account if you enable sync in Settings. | Contract / consent (Art. 6(1)(b)/(a)) | Inferences (preferences) |
| Frequently visited sites | Top Sites module (chrome.topSites: URL and title). Separate from optional Browsing Activity below. | Stays on device; not sent to WAVFin. | Consent (Art. 6(1)(a)) | Internet activity |
| Site favicons | Icons for Top Sites shortcuts (_favicon API / favicon permission). | Loaded for displayed URLs only; not collected by WAVFin. | Consent (Art. 6(1)(a)) | n/a (intermediate content) |
| Browsing activity (optional, off by default) | When enabled in Settings → Privacy: aggregate local visit counts by domain for the last 7 or 30 days (top three domains with share bars). Uses chrome.history.search in the MV3 service worker only while the toggle is on. | Stays on device; aggregated stats only; never sent to WAVFin. Disable anytime in Settings or remove the extension. | Consent (Art. 6(1)(a)) | Internet activity |
| Location (optional, explicit) | Weather when no ZIP is set: device geolocation → forecast (Open-Meteo) and city label (BigDataCloud). | Coordinates sent only to Open-Meteo / BigDataCloud for that feature; you can use a ZIP in Settings instead and disable location entirely. | Consent (Art. 6(1)(a)) | Geolocation (precise — only on explicit user action) |
| Google account (optional) | If you connect Google Calendar: email for account labelling, OAuth tokens, calendar list and events. | Between your browser and Google APIs; tokens and cache stored locally on your device. | Consent (Art. 6(1)(a)) | Identifiers; calendar contents |
| RSS / web content | Public feed XML (titles, links, summaries) from feeds you enable or add. | Fetched from feed publishers’ servers; cached locally on your device. | Consent (Art. 6(1)(a)) | Internet activity |
We do not intentionally collect passwords, payment information, or health data. Optional browsing activity reads your local Chrome history only when you turn it on in Settings → Privacy; we do not receive that history on our servers. Top Sites uses only what Chrome exposes via chrome.topSites.
Chrome permissions
DailyDock requests only the permissions its features need. You can disable optional features (browsing activity, Calendar, location-based weather) without uninstalling.
- storage — save preferences and dashboard content locally.
- topSites — show frequently visited shortcuts.
- favicon — display site icons for Top Sites and activity stats.
- history — optional browsing-activity stats only when the Settings → Privacy toggle is on (not used for Top Sites).
- geolocation — optional weather when you allow location instead of entering a ZIP.
- identity / identity.email — optional Google Calendar connection.
Third-party services and cross-border data flows
The extension may contact the services below, and only when you use a feature that needs them. Each service has its own privacy policy. Where these services may process your data outside your device or country, the transfers happen between your browser and the third party directly — WAVFin does not relay the data.
- Open-Meteo (Germany/EU) — weather and US ZIP geocoding.
- BigDataCloud (Australia/EU) — reverse geocoding for weather location labels.
- Picsum Photos — optional rotating background images.
- RSS publishers — default and custom feed URLs (custom feeds may request optional host permission after your approval).
- Google — OAuth 2.0 and Calendar API when you connect a Google account. Subject to Google’s privacy policy.
Remote code
All extension code is packaged in the extension bundle. Network responses are data (JSON, XML, images), not executable scripts loaded from the web.
Data sharing and sale
We do not sell or rent user data. We do not use DailyDock data for credit decisions or unrelated advertising. Data is used only to provide the new-tab dashboard features you enable.
Retention and deletion
Data remains in extension storage until you change it, clear extension data in Chrome, disable or remove the extension, or use in-extension backup / reset options where available. Browsing-activity stats are not stored separately — they are recomputed from local history when the toggle is on. chrome.storage.sync items are held by Google under your signed-in Google account for as long as sync is enabled; remove via Chrome’s sync settings. To stop Calendar API access, disconnect Google Calendar in the extension’s Settings, and revoke the app in your Google Account permissions if desired.
Because no DailyDock data is held by us on a server, uninstalling the extension removes the local copy of saved preferences and caches. There is no separate WAVFin delete request needed for the extension itself.
Children
DailyDock is not directed at children under 13 (COPPA) or under the age of consent in your jurisdiction (16 in most EU member states; 13 in the UK). We do not knowingly collect personal information from children. Because the extension stores data only on the local device, parents and guardians can remove allDailyDock data by uninstalling the extension from the child’s browser profile. If the optional Google Calendar connection was used, revoke the app in the Google account’s permissions page.
Your rights (GDPR / CCPA / state laws)
Even though we do not hold DailyDock data on our servers, you have the same rights described in the WAVFin site Privacy Choices section in respect of any data WAVFin does hold (for example, if you emailed us from a DailyDock support channel). To exercise those rights, use the privacy request form or email support@wavfinaudio.com. For data stored only on your device by the extension itself, use the extension’s Settings panel and Chrome’s site-data controls.
Changes
We may update this policy. The “Last updated” date will change. Continued use after updates means you accept the revised policy.
Contact
Questions: support@wavfinaudio.com.