hub-dashboard-extension

Privacy Policy for Hub Extension

Effective Date: September 16, 2026

This Privacy Policy describes how the Hub Chrome Extension (“Hub”, “we”, “us”, or “our”) handles your data. Hub is designed to be a privacy-first, local dashboard. We do not collect, store, or process your personal data.

Hub operates one backend service of its own: the Hub API, a Cloudflare Worker that supplies background images and daily quotes. It is described under “Hub API” below. No personal data, calendar data, location, or note content is ever sent to it.

Data We Access and How We Use It

Hub requests specific browser permissions to provide its core functionality. All data accessed through these permissions remains on your local device.

1. Google Calendar Data (identity permission)

Hub uses Chrome’s native identity API to authenticate with your Google account and requests read-only access to your Google Calendar (https://www.googleapis.com/auth/calendar.readonly). This scope is read-only and covers both your calendar list (needed so you can choose which calendars to display, and to show their colours) and the events on them.

• Usage: We fetch your upcoming events strictly to display them on your local dashboard.
• Storage & Sharing: Calendar data is processed temporarily in your browser’s memory. We do not store, log, transmit, or share your calendar events with any third parties. Hub’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

2. Location and Weather (geolocation permission)

To display local weather conditions, Hub needs an approximate location. It is resolved in this order, stopping at the first that succeeds:

1. The city you entered in the settings, if any.
2. Your device location via the browser’s geolocation API.
3. An approximate location derived from your IP address by GeoJS (get.geojs.io).
4. The last location successfully resolved, cached locally.
5. A default location (Budapest).

• Usage: The resulting coordinates are sent to Open-Meteo (weather) and, unless you set a city manually, to BigDataCloud (to turn the coordinates into a place name). If step 3 is reached, your IP address is exposed to GeoJS as part of that request.
• Storage: The most recent coordinates and weather result are cached on your device for 30 minutes to avoid repeat requests. We do not track your location history and no location data leaves your device except in the API requests described above.

3. Local Storage (storage permission)

Hub uses your browser’s storage to save:

• Your preferences — background search tags, background source (Unsplash photos or a custom image), background dimming level, weather location, selected calendars, countdown target, focus timer lengths, which widgets are hidden, language, and the Memos server address and default Memos tag — via chrome.storage.sync, which Chrome synchronises across devices where you are signed in.
• Your quick notes, in localStorage on the device only.
• Cached content in localStorage (the daily quote, weather, and background image metadata) and the background image itself in the browser’s Cache storage, to avoid re-downloading it. If you choose to use your own image as the background instead of an Unsplash photo, that file is stored in this same Cache storage, entirely on your device, and is never uploaded anywhere.
• If you connect the Memos widget, in chrome.storage.local on that device only: up to 200 of your own most recent memos, including their content, so the widget can show them when your Memos server cannot be reached; any memo you wrote that could not be sent, kept as a draft; the name of the Memos account you connected, the address of the server it is connected to, and a note of when that server was last contacted and whether the attempt failed. These sit alongside the access token described in section 6 and, like it, are never synchronised.

Hub does not store any API keys of its own on your device; the only credential it keeps is the Memos access token you enter yourself, described in section 6. This data is stored solely on your device (plus Chrome Sync, for preferences) and can be cleared at any time by uninstalling the extension or clearing your browser data.

The settings page can also export your preferences to a JSON file and read one back. The file is written to your own device by your browser’s normal download mechanism and is never transmitted anywhere; importing one reads it locally. Only the preferences listed above are included, the Memos server address and default Memos tag among them — not your notes, not your memos or your Memos access token, and not a custom background image.

4. Scheduled Background Prefetch (alarms permission)

Hub schedules a daily task that downloads the next day’s background image in advance, so opening a new tab never waits on the network.

• Usage: The task sends only your configured background search tags to the Hub API, exactly as the dashboard itself does. It reads no browsing data and runs no other work.
• Storage: The downloaded image goes into the browser’s Cache storage and its metadata into chrome.storage.local, both on your device only.

5. Focus Timer Notifications (notifications permission)

Hub includes an optional Pomodoro-style focus timer. When a work or break interval ends, Hub shows a local system notification to let you know.

• Usage: The notification is generated entirely on your device by the browser’s native notification system. No data about your focus sessions, timings, or usage is collected, stored remotely, or sent anywhere — this permission is used solely to display that one local notification.

6. Memos Widget (optional_host_permissions)

The Memos widget is off until you configure it. When you do, you supply the address of your own Memos server — we do not run one, and we never see it. Access to that server is requested only when you press Connect, and only for the single address you entered; if you never configure the widget, the extension is never granted access to any additional site.

• Usage: Once connected, the extension exchanges data with that server and nowhere else: it sends the memos you write, sends an archive request for each one you mark done, reads back your recent, non-archived memos, and reads which account your token belongs to — this last one on every refresh, because it is the only way to tell a token that still works from one that has expired. Every request is authenticated with the access token you entered. No memo content, token or server address is sent to the Hub API or to any other service.
• Storage: Your access token is stored with chrome.storage.local on the single device where you entered it. It is not synchronised to your other devices, and it is deliberately excluded from the settings export file, so a backup you share cannot contain it. The same local storage on that device also holds the name of the Memos account the token belongs to, read from your server when you press Connect; up to 200 of your own most recent memos, including their content, so the widget can show them while your server is unreachable; any memo you wrote that could not be sent, kept as a draft until you send it or clear it; the address of the connected server, kept beside the token so that a token is never sent to a different one; and a note of when the server was last contacted and whether that attempt failed, which is what lets a new tab use the cached memos instead of asking again. None of these is synchronised or included in the export either. All of it is removed when you press Disconnect in the settings, and when you uninstall the extension, which clears the extension’s local storage along with it.

Hub API

Background images are requested from the Hub API, a Cloudflare Worker we operate at hub-api.csiszaralex.workers.dev. It exists so that the Unsplash API key stays on the server instead of being shipped inside the extension. Daily quotes are also fetched through this same Worker, which proxies and caches them from the upstream Stoic Quote API on Hub’s behalf.

• What is sent: only the background search tags you configured (for example landscape,forest) for background images; the quote request sends nothing. No account identifier, location, calendar data, or note content is included. As with any web request, your IP address and standard browser headers are visible to Cloudflare.
• What is stored: the Worker caches pools of Unsplash image metadata, keyed by search tags, and caches the daily quote by date. Nothing user-identifying is written to that cache, and we keep no request logs beyond Cloudflare’s standard, short-lived operational logging.

Third-Party Services

Hub interacts with the following third-party APIs to fetch content. When Hub makes requests to these services, your IP address and standard browser headers are exposed to them as part of normal web traffic:

• Unsplash: Background images. The extension downloads the image files from images.unsplash.com; the search itself goes through the Hub API described above.
• Google Calendar API: Used to fetch your schedule.
• Open-Meteo: Weather forecasts, and city lookup when you type a city name in the settings.
• BigDataCloud: Turns coordinates into a place name for the weather widget.
• GeoJS: Approximate location from your IP address, used only as a fallback when the settings and browser geolocation do not provide one.

These third-party services have their own privacy policies governing the data they process during API requests.

Data Protection

Hub takes the following measures to protect sensitive data, particularly Google user data accessed via OAuth:

• OAuth 2.0: Authentication with Google is performed exclusively through Chrome’s built-in chrome.identity API using the OAuth 2.0 protocol. Hub never handles or stores your Google account credentials.
• HTTPS only: All API requests to Google services and third-party services are made exclusively over HTTPS, ensuring data is encrypted in transit.
• No server-side storage of user data: Google user data (e.g., calendar events) is fetched directly in your browser and never transmitted to, stored on, or processed by any server we control. The only server we operate is the Hub API described above, which never receives Google user data.
• Read-only access: Hub requests only a read-only scope (calendar.readonly), limiting the extent of access to your Google account to the minimum required for the feature.
• Token scope limitation: OAuth tokens are requested with the minimum necessary scopes and are managed entirely by the Chrome browser runtime.

Data Retention and Deletion

Hub does not retain Google user data beyond the immediate session:

• Google Calendar data: Calendar events are fetched on-demand and held only in your browser’s runtime memory for the duration of the current session. This data is never written to disk, local storage, or any external system, and is automatically cleared when you close or reload the extension.
• OAuth tokens: Google OAuth access tokens are managed by Chrome’s identity API. You can revoke Hub’s access to your Google account at any time via your Google Account permissions page. Revoking access immediately removes Hub’s ability to fetch any Google user data.
• Local preferences: Settings stored in chrome.storage and cached content in localStorage and Cache storage stay on your device (preferences additionally travel through Chrome Sync) and can be deleted at any time by clearing the extension’s storage via Chrome settings or by uninstalling the extension.
• No long-term retention: We do not collect or archive any Google user data — there is no data held by Hub beyond your local device that would need to be deleted.

Data Sharing and Selling

We do not sell, trade, rent, or otherwise share your personal information or browsing data with any third party. The extension operates entirely on your local machine.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be reflected by updating the “Effective Date” at the top of this document.

Contact Us

If you have any questions or suggestions about our Privacy Policy, please contact us at: hub@csalex.dev

This site is open source. Improve this page.