Privacy Policy

Published at osp.zira3a.net/privacy/ · Last updated

This policy explains how Offline Start Page (“OSP”, “the extension”) handles information. OSP is a Chrome new-tab extension that provides a private, local-first dashboard.

1. Summary

2. Data stored on the device

Depending on the features used, OSP stores the following in Chrome extension storage on the device:

This information stays on the device unless the user enables Chrome Sync, exports a backup, or uses a network-backed feature described below.

3. Google Tasks and Google account access

Google Tasks is optional. Access begins only when the user selects Connect in a Google Tasks widget.

OSP uses Chrome Identity to request this Google OAuth scope:

https://www.googleapis.com/auth/tasks.readonly

The scope is read-only. OSP reads Google Tasks lists and tasks, including task titles, notes, status, due dates, completion dates, parent relationships, positions, and update metadata. OSP does not create, edit, complete, or delete tasks in the user’s Google account.

OSP may access the Google account identifier and email address associated with the connected Chrome profile so it can bind the connection to the selected account and show which account is connected.

OSP stores the connected account identifier, email address, connected service name, selected task-list identifiers, list names, and cached task data in device-local extension storage. Google OAuth access tokens are managed by Chrome Identity and are not placed in OSP’s dashboard data, Chrome Sync payload, JSON exports, or revision backups.

When the user disconnects Google Tasks, OSP removes its local connection binding, selected-list metadata, and task caches. If no other OSP Google service uses the connection, OSP asks Chrome Identity to clear its cached authorization tokens.

The following Google Tasks information is excluded from Chrome Sync, dashboard exports, and revision backups:

An opaque task-list identifier and the widget’s display settings may remain in the dashboard so the widget can reconnect to the selected list. The user can remove the widget or disconnect Google Tasks to remove the connection and caches from the device.

4. Calendar subscriptions

Calendar widgets use direct HTTPS .ics subscriptions. OSP does not use the Google Calendar API or Microsoft Graph.

When a user connects a calendar, OSP requests Chrome host permission for that calendar host only. OSP fetches the published URL without credentials and rejects redirects. The subscription URL may contain a secret token; anyone with the URL may be able to read the calendar. Users should treat the URL like a password.

OSP stores the ICS source URL and parsed upcoming events locally. Calendar source URLs, event titles, event times, notes, and event caches are excluded from Chrome Sync, dashboard exports, and revision backups. Disconnecting the calendar removes its source URL and cache and releases its optional host permission when no other OSP calendar uses that host.

5. Home Assistant Alerts

The Home Assistant Alerts widget is optional. It connects to an HTTPS alert service selected and operated by the user, not by the OSP developer. Loopback HTTP addresses (localhost, 127.0.0.1, and [::1]) are accepted for local testing.

When a user connects an Alerts widget, OSP sends the dedicated read token to the alert service URL the user chose. The user’s Home Assistant can send selected notification text to that service through a separate write credential. OSP does not receive Home Assistant administrative credentials or the write credential and cannot control Home Assistant. OSP limits its local alert cache to alerts less than 24 hours old; the reference self-hosted service bundled with OSP also expires records after 24 hours. Other compatible services may apply different retention.

OSP caches alert text and read and notification markers in device-local Chrome storage. The active inbox lasts 3 hours and History lasts up to 24 hours. The service URL, read token, alert cache, and markers are excluded from Chrome Sync, dashboard exports, and revision backups. Disconnecting removes the URL, token, and cached alert text. Non-content read/delivery markers and the optional origin permission may remain until the user clears them; they contain no alert text.

Optional desktop notifications require Chrome’s notification permission. Popup text is generic and does not include alert details. No popup is created for an alert that was already read or that is more than 3 hours old.

6. Other network-backed features

OSP makes network requests only when needed for features the user enables:

These services may receive standard network information such as the user’s IP address, request headers, requested domains or URLs, and timestamps. Their own privacy policies and retention practices apply.

OSP does not sell user data, use it for personalized advertising, or transfer it for creditworthiness or lending decisions.

7. Chrome Sync

Chrome Sync is optional and disabled by default. When enabled, OSP uploads supported dashboard data to the user’s Chrome Sync storage through Google. Google Tasks content, Calendar source URLs and events, Home Assistant Alerts credentials and content, account credentials, and device-local caches are excluded from the OSP Chrome Sync payload.

Chrome Sync is provided by Google and is subject to Google’s terms and privacy policies.

8. Backups and exports

Users can create local automatic backups, download JSON backups, and import backups. Exports are created only when the user requests them. Google Tasks content, Calendar source URLs and events, alert-service credentials and content, and authentication credentials are excluded from OSP-generated dashboard backups and exports.

Downloaded backup files are outside OSP’s control and may be stored or shared by the user or by other software on the device.

9. Retention and deletion

Local OSP information generally remains in Chrome until the user deletes the relevant widget or page, disconnects the integration, clears extension data, removes local backups, or uninstalls the extension. OSP keeps a bounded set of automatic local backups; users can manage revision history and exports through the extension.

Uninstalling an extension normally causes Chrome to remove its extension storage, subject to Chrome’s behavior and any device or account backups outside OSP’s control. OSP cannot guarantee deletion of copies that the user downloaded, shared, or stored outside the extension.

The developer does not control retention by third-party services the user chooses to connect. Those services apply their own policies.

10. Permissions

OSP uses Chrome permissions for features the user invokes:

Optional host access is requested for the specific origin needed by the user’s action. OSP does not request broad optional host access merely by installing or opening the dashboard.

OSP does not include a web-search provider and does not request the Chrome search permission. The Ctrl+K command palette searches saved links, pages, and commands locally.

11. Google API Services User Data Policy

OSP’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

OSP uses Google Tasks data only to provide the user-facing Google Tasks widget, its local offline cache, and connection management. OSP does not use Google user data for advertising, profiling, sale, or unrelated purposes.

12. Changes

Material changes to data handling will be reflected on this page with an updated effective date. Continued use of the extension after a policy update means the user accepts the updated policy.

13. Contact

Questions about this policy can be sent to info@zira3a.net.