Privacy Policy

Extension: Focusly – Block YouTube Creators, Shorts & Distracting Websites
Developer: Kamil Rzeźnik
Contact: support@focusly.site
Last updated: May 13, 2026

  Focusly is a Chrome extension that helps you stay focused by blocking distracting websites, tracking browsing time, and running focus rituals (Pomodoro-style timers). This policy explains exactly what data we collect, how we use it, where it is stored, and who we share it with.

1. Data We Collect

1.1 Account Data (optional – only if you sign in)

If you create a Focusly account or sign in with Google, we collect:

Email address – used to identify your account and send transactional emails (e.g. password reset).
Display name and profile photo URL – obtained from your Google account if you use Google Sign-In; used only to display your name in the extension interface.
Firebase User ID (UID) – a randomly generated identifier used to associate your settings and block lists with your account in our database.

You can use Focusly without an account. Account creation is optional and only required for cross-device sync or premium features.

1.2 Block List and Settings Data

The extension stores the configuration you create, including:

Domains and URLs you choose to block.
Blocking mode for each site (e.g. permanent block, daily time limit, Focus Ritual only, YouTube creator filter, YouTube Shorts filter).
Daily time limits, schedules, and categories you define.
Focus Ritual settings (number of cycles, work/break durations, target cycles).
App preferences: language, theme, notification settings, password protection settings.
YouTube creator handles and channel names you add to block lists (fetched from YouTube's public pages, see Section 1.4).

This data is stored locally in your browser (chrome.storage.local and chrome.storage.sync) and, if you are signed in, synced to our cloud database (Firebase Firestore) so your settings are available across devices.

1.3 Usage Statistics

The extension tracks how much time you spend on blocked or monitored sites. Specifically:

Daily time spent (in seconds) per domain – used to enforce daily time limits and display usage statistics in the dashboard.
Date of measurement – used to reset daily counters at midnight.

Usage data is stored locally in your browser. If you are signed in, aggregated daily usage totals (seconds per domain, date) are also synced to Firestore to allow cross-device consistency. We do not collect, transmit, or store the specific URLs or page titles of websites you visit — only the domain names of sites that are in your block list.

1.4 YouTube Creator Search Data

When you use the "Block YouTube Creator" feature and search for a channel handle (e.g. @channelname), the extension makes a network request to YouTube's public website (https://www.youtube.com/) to retrieve the channel's public name and profile thumbnail. This request:

Is made from your browser directly to YouTube.
Does not include your account credentials or viewing history.
Returns only publicly visible metadata (channel name, thumbnail image URL).
Is stored locally as part of your block list configuration and synced to Firestore if you are signed in.

We do not store YouTube search queries on our servers. YouTube's own privacy policy governs YouTube's handling of this request.

1.5 Payment Data

Premium subscriptions are processed by Stripe via our Firebase Cloud Functions backend. When you upgrade:

Your Firebase ID token (a temporary authentication token, not your password) is sent to our server-side Cloud Function to verify your identity.
The Cloud Function creates a Stripe Checkout session and returns a Stripe-hosted URL. You are redirected to Stripe's website to enter payment details.
We never see, handle, or store your credit card number, CVV, or bank details. All payment data is handled exclusively by Stripe.
After a successful payment, Stripe notifies our backend via webhook. We record your subscription status (active/inactive, plan type, expiry date) in Firestore.

1.6 Technical and Diagnostic Data

The extension does not automatically collect crash reports, telemetry, or analytics. We do not use any third-party analytics SDK (e.g. Google Analytics) inside the extension. Console logs are written locally to your browser's developer tools only.

2. How We Use Your Data

Data	Purpose
Email address, UID	Account authentication; sending password reset emails; associating your data with your account in Firestore.
Block list and settings	Enforcing website blocks; displaying your configuration in the dashboard; syncing across devices (if signed in).
Daily usage statistics	Enforcing daily time limits; displaying usage charts in the analytics dashboard; syncing across devices (if signed in).
YouTube creator handle / thumbnail	Identifying the correct YouTube channel to block; displaying the channel avatar in the block list UI.
Subscription status	Unlocking premium features; verifying your plan in the extension UI.
Language preference, locale	Displaying the extension in your preferred language (English, Polish, Spanish).

3. Data Storage

3.1 Local Storage (in your browser)

The majority of Focusly's data lives entirely on your device in Chrome's built-in storage APIs:

chrome.storage.local – block lists, Focus Ritual state, daily usage counters, cached Firebase tokens, password protection settings.
chrome.storage.sync – language preference; small settings that Chrome automatically syncs to your signed-in Google account via Chrome Sync (not our servers).

Data in chrome.storage.local stays on your device and is never transmitted to our servers unless you are signed into a Focusly account (see Section 3.2).

3.2 Cloud Storage (Firebase Firestore) – signed-in users only

If you create a Focusly account and sign in, the following data is stored in Google Firebase Firestore under your unique user ID:

Your block list configuration (domains, modes, limits).
App preferences (language, notification settings, theme).
Daily usage totals per domain.
Subscription status (plan type, expiry).
Metadata: extension version, platform (chrome-extension), timestamps for createdAt, lastActiveAt, updatedAt.

Firestore data is stored on Google's servers in the us-central1 region (United States). Google's data processing terms apply: firebase.google.com/support/privacy.

Data is retained for as long as your account is active. If you delete your account, all associated Firestore documents are deleted.

3.3 Data Retention

Local data – retained until you uninstall the extension or clear extension data from Chrome settings.
Firestore data – retained while your account is active. Deleted within 30 days of account deletion.
Daily usage counters – reset daily; historical aggregates are kept for up to 30 days in Firestore.

4. Data Sharing

We do not sell, rent, or trade your personal data. We share data only with the following service providers, and only to the extent necessary to operate the extension:

Third Party	Data Shared	Purpose	Privacy Policy
Google Firebase (Auth + Firestore + Cloud Functions)	Email, UID, block list, usage stats, settings, subscription status	Authentication, cloud sync, subscription verification	firebase.google.com/support/privacy
Stripe	Firebase ID token (for identity verification); email for checkout pre-fill	Payment processing for premium subscriptions	stripe.com/privacy
YouTube (Google)	HTTP request for public channel pages (no personal data sent)	Fetching public creator name and thumbnail when you add a YouTube Creator block	policies.google.com/privacy

We do not share data with advertisers, data brokers, or any other parties not listed above.

5. Chrome Extension Permissions

Focusly requests the following Chrome permissions and uses them only as described:

Permission	Why it is needed
`declarativeNetRequest`	Block network requests to domains in your block list without reading your network traffic.
`storage`	Save your block list, settings, and usage statistics locally in Chrome.
`scripting`	Inject the blocked-page overlay into tabs that navigate to a blocked domain.
`tabs`	Detect which domain is open in the active tab to enforce blocks and track usage time.
`webNavigation`	Detect page navigations (e.g. YouTube SPA transitions) to correctly enforce blocks and timers.
`alarms`	Schedule Focus Ritual timers and daily usage resets.
`notifications`	Show browser notifications for Focus Ritual phase changes (work → break → work).
`identity`	Support Google Sign-In via Chrome's OAuth flow.
`activeTab`	Access the URL of the currently active tab when you open the extension popup.
`offscreen`	Run Firebase Auth in a background offscreen document (required by Manifest V3).
Host permissions: `http:///`, `https:///`	Enable blocking rules and content script injection on any website you add to your block list.

6. Data You Can Access, Correct, or Delete

View your data – all local data is visible in the Focusly dashboard (Settings → Analytics).
Delete local data – uninstall the extension or use Chrome's "Clear extension data" option in chrome://extensions.
Delete cloud data – email us at support@focusly.site to request deletion of your Firestore account data. We will process the request within 30 days.
Export your data – contact us at the email above to request a copy of your stored data.

7. Children's Privacy

Focusly is not directed at children under 13. We do not knowingly collect personal data from children. If you believe a child has provided us with personal information, please contact us and we will delete it promptly.

8. Changes to This Policy

We may update this privacy policy from time to time. We will update the "Last updated" date at the top of this page. For significant changes we will notify signed-in users via the extension's settings panel.

9. Contact

Kamil Rzeźnik
Email: support@focusly.site
Website: focusly.site