Blyte Focus · Privacy
A clear view of your data.
The local planner works without an account. Account services, cloud sync, league participation, support requests, and purchases each involve additional information. This policy explains the difference.
Effective date: 2026-11-16
1. Who is responsible
Blyte Focus is operated by Rodelyn Almazor, based in United States of America. Contact and address information: RODELYN ALMAZOR,
UNITED STATES,
[email protected]. For privacy questions or requests, contact [email protected].
This policy covers the Blyte Focus application, its account services, and this website. Payment services, app stores, email services, and destinations you choose for sharing also process information under their own policies.
2. Information on your device
Your local workspace includes tasks and subtasks, projects, focus history, completed tasks, alarms and reminders, timer state, scratchpad text, settings, your chosen display name, and companion progress. These records provide the planner, statistics, reminders, and cat experience. You can use the local tools without creating an account.
Native apps save the workspace in the application's data folder. The browser version saves it in that browser's local storage. Imported alarm sounds are stored separately on that device. Workspace files and exported backups are readable data files; protect access to your device and any backups you keep.
Signing out or deleting a cloud account does not erase this local workspace. Clearing browser site data removes that browser's local copy. Native app data and any exported files must be managed separately. Uninstall behavior varies by platform, and an older app-data folder can remain after an upgrade.
Notifications use your operating system or browser permissions. Windows smart audio ducking checks whether other applications are playing audio and their playback levels. It does not record that audio, use microphone input, or read browser history or page titles.
3. Accounts and optional cloud sync
If you create an account, your email address, password, and display name are sent to Supabase's authentication service. Account identifiers, confirmation and recovery state, and sign-in sessions allow us to identify your account and control access. Passwords and recovery codes are not included in workspace backups. Native sign-in state uses the platform secure-storage service; browser sign-in tokens stay in memory.
Creating an account does not by itself upload your workspace. Pro sync starts after a deliberate sync action. It sends a complete workspace snapshot, including task content, notes, focus history, alarms, settings, and companion progress, to the Blyte Focus backend. Imported audio files are not included; their setting identifiers may be. Background sync checks follow while enabled.
Cloud sync keeps a current, revisioned account copy so devices can exchange a workspace and detect competing changes. Some device preferences are preserved when another copy is imported, but those preferences can still be present in the uploaded snapshot. Sync is not end-to-end encrypted: authorized service operators can access stored information. Keep a separate backup when you need an independent copy.
4. League profiles and deliberate sharing
The league is optional. Joining requires accepting the community rules. Participation sends server-confirmed session information, including timing and credited focus, to calculate rankings. Other signed-in league users can see your approved display name, optional profile thumbnail, public member identifier, rank, focus totals, and session counts. Your email, tasks, and scratchpad are not included in league responses.
Proposed names and photos are held for manual review before first publication. When you change a profile, the last approved version can remain visible while the new version awaits review. Removing a photo clears both the proposed and approved copies. Leaving the league hides your profile from league responses and deletes your ranked sessions.
Uploaded account pictures are cropped and re-encoded as small thumbnails with image metadata removed. We store proposed and approved copies, review status and notes, community-rule acceptance, and moderation state. Blocks and community reports help manage participation. Blocking hides the two members from each other's league results; it does not automatically send a report.
Share cards are a separate choice. Including a name or picture is optional; cards do not include your tasks, notes, or email. You choose whether and where to save or share them. A picture selected for a share card does not automatically update your league profile. Copies you or other people save cannot be remotely erased by Blyte Focus.
5. Support and purchase information
Signed-in support requests contain your account association, category, subject, message, reference, status, timestamps, and the latest support reply. A community report can identify the reported member. Authorized support operators can read these records. Replies appear in the app when you refresh or reopen support; this process does not automatically send an email or push notification.
Technical details are optional and off by default. The app can attach a small set of fields such as version, platform, language, delivery mode, and build mode; the service also permits a notification-permission category. It does not automatically attach tasks, notes, passwords, photos, logs, or files. Information you deliberately type into a message is part of that request.
The website's contact tools prepare email text. Opening a draft does not send it; you send it through your own email service. That correspondence is handled separately from the in-app support inbox.
Purchases involve payment or store services. The backend keeps entitlement status, provider identifiers, purchase or order references, checkout state, relevant amounts and currency, and verification timestamps. A checkout can receive your account email and a purchase-linking identifier. Card entry is handled by the payment provider or store rather than stored in your workspace.
6. Why we use data and who receives it
We use the information described above to operate requested features, authenticate accounts, synchronize workspaces, calculate league results, review content, answer support requests, verify purchases, handle refunds or revocations, prevent duplicate payment processing, and protect the service from misuse. Applicable legal grounds for these activities: We process account credentials, synced tasks, and focus logs under Contractual Necessity to provide the core app and cloud synchronization service. We process security logs, rate-limiting data, and community moderation reports under Legitimate Interests to keep the service secure and prevent abuse. Public Focus League display names and profile photos are processed strictly on the basis of Explicit User Consent (opt-in only), which can be withdrawn at any time..
Supabase provides authentication, database storage, and server functions. Backend hosting region: Europe. Account email delivery provider: Resend (configured via custom SMTP for account verification and password recovery). Public self-registration is not yet open; email delivery is currently active for invited Windows beta testers only.. Payment providers applicable to the available purchase channels: Paid purchases are not open yet. No live payment processors or app store billing channels are currently enabled; Blyte Focus Pro sync is currently tested using development entitlements only.. Authorized support and moderation personnel receive the information needed for their work.
Website hosts and online service providers can process connection information such as IP addresses, request times, and security logs. Blyte Focus does not include third-party advertising or analytics SDKs. This does not mean that account requests, purchases, or hosting generate no technical records. Browser workspace storage is needed for local app features; it is not an advertising tracker.
This public website is hosted on Cloudflare Pages. Its pages use self-hosted fonts and images, with no advertising cookies or third-party analytics added by Blyte Focus. Text entered into the email composers stays in the page until you open a draft or copy it; this static website does not submit a support ticket or deletion request by itself.
Services may process information outside your country. The backend location and providers listed here identify the relevant arrangements; a hosting location alone does not determine every processing location. International processing and applicable safeguards: Cloud database, authentication, and hosting services are processed via Supabase, Cloudflare, and Resend infrastructure (located in the United States and European Union). Where cross-border data transfers occur, transfers rely on standard contractual safeguards provided by our infrastructure vendors.. Data may also be disclosed when required by law or necessary to respond to a legitimate security or legal request.
7. Retention and deletion
Local files remain until you remove them. Cloud workspace and account records remain while the account exists unless removed earlier. In-app support and moderation records have no automatic age-based expiry in the current service. Your own support tickets and replies are removed with account deletion. Leaving the league removes ranked sessions without deleting your account.
Successful account deletion removes the authentication account, profile and photo copies, cloud workspace, account-linked entitlements and checkout records, trial records, ranked history, blocks, and your own support requests. It does not remove local files or other people's saved exports.
Some records are separate. Payment-event identifiers and processing timestamps remain to recognize previously handled events; these are not necessarily anonymous. Payment providers keep their financial records. Reports made by other users can remain with the deleted member's reference cleared, while their message text may still mention that person. Email correspondence follows the support mailbox's retention arrangements.
Backup retention: When an account is deleted via the in-app deletion tool or support request, live database records are removed immediately. If manual point-in-time exports exist for maintenance, deleted account records are purged from any retained export within 30 days.. Service-log retention: Supabase retains API and authentication request logs for 1 day (24 hours) on our current plan for debugging and abuse prevention. Cloudflare Pages retains standard edge access logs transiently for security and routing, and Resend retains email delivery logs for up to 3 days to troubleshoot failed confirmation or recovery emails.. Financial and payment-event retention: Because live payment channels are not yet enabled, no real customer payment records are currently collected. Once live payments launch, non-reversible payment event identifiers, transaction timestamps, and processor references in the payment_events table—along with records held by external payment processors—are retained for up to 7 years (or as required by applicable tax and accounting laws) to prevent fraud, handle chargebacks, and meet statutory bookkeeping duties.. Support correspondence and retained reports: In-app support tickets submitted by a user are permanently deleted when their account is deleted. Direct support emails sent to our support inbox are retained for up to 12 months to track unresolved bugs and service history, after which they are deleted. Moderation reports filed by other users against public community profiles may remain in de-identified moderation logs for up to 12 months to enforce safety and prevent repeat abuse.. Deletion processing expectations: Authenticated users can trigger immediate deletion directly inside the app's account settings. For web or email deletion requests, we verify ownership by replying to the user's registered account email address and complete manual removal within 7 business days, sending a final confirmation email once finished (subject only to mandatory legal or anti-abuse log exceptions stated above).. See Delete your account for the request route and practical limits.
8. Your choices and rights
You can use local tools without an account, choose whether to sync, leave the league, remove a profile photo, change notification permissions, omit optional diagnostics, export a workspace backup, or delete your cloud account. Exported backups contain private workspace content, so share them carefully.
Depending on where you live and the applicable law, you may have rights to access, correct, delete, or receive personal information, restrict or object to processing, withdraw consent, or complain to a data-protection authority. Withdrawal does not undo processing already lawfully completed. Contact [email protected]; we may need proportionate verification before disclosing or deleting account data.
Audience and age requirements: Blyte Focus is intended for individuals aged 13 and older (or the minimum digital consent age in the user's jurisdiction). Users under 13 are not permitted to create cloud accounts or opt into public Focus League community features. If we discover that personal data has been collected from a child under the applicable age threshold without verified parental consent, we will promptly delete the account and associated data.. Do not send passwords, recovery codes, full payment-card details, or identity documents with an initial request. If you cannot access your account email, explain that so we can discuss an appropriate recovery route. Contact us if you believe a child has supplied personal information that requires attention.
9. Changes and questions
We will update this page when the service or its data practices change and revise the effective date. Material changes will be communicated as required by applicable law. For product help, use Support; for privacy matters, contact [email protected].