1. Operator and contact
Focoach is operated by an individual using the Focoach / InlaeR brand. Email inlaer@inlaer.com for access, correction, deletion, consent withdrawal, or other privacy questions. We may request the minimum account or transaction details needed to verify your identity.
2. Accounts, subscriptions, and launch updates
Account registration and sign-in process your email, password or Google authentication, confirmation state, and account identifiers. Google sign-in verifies your basic Google profile and email through Supabase. Supabase provides authentication, and Resend delivers authentication emails. The app can register a profile, installation identifier, operating system, app version, and last-seen information. Passwords are not saved in app records. Desktop session-restoration tokens use operating-system secure storage. To keep you signed in between account and subscription pages, the website uses an essential HttpOnly cookie containing an encrypted session for up to 7 days and removes it when you sign out. Page JavaScript cannot read this cookie, and website authentication tokens are not stored in localStorage or sessionStorage. Website and app sign-ins are maintained separately. During Google sign-in, a one-use PKCE verifier and minimal flow identifiers and expiry metadata are temporarily kept in tab sessionStorage with a five-minute validity and removed when the matching callback is consumed.
Paddle processes your email and the payment and billing details entered at checkout for sales, taxes, fraud prevention, receipts, and subscription management. Focoach links your account to Paddle customer, transaction, and subscription identifiers, trial usage, subscription status, access periods, and processing events. Focoach’s billing database does not store full card numbers or security codes.
Launch-update signup stores your email, signup time, and consent record. These optional updates are separate from subscription and authentication messages.
3. Local records and permissions
Goals, focus sessions, conversations, and notes are stored by default in an account-specific location on your device. With operating-system permissions, the app can observe the foreground app, window titles, and active Chrome tab information. Screen images used for optical character recognition (OCR) are processed on your device; JEV requests send permitted text excerpts rather than images.
The service does not provide microphone or camera monitoring of your focus. General typed characters and clipboard contents are not collected in the learning dataset. Available observations depend on your permissions, sharing settings, and operating system.
4. AI assessment of your goal
When you allow goal and screen-text sharing and use automatic coaching, the session goal, app name, window title, and part of the screen’s OCR text are sent through Supabase to TypeSafe’s JEV model to assess relevance to the goal. Supabase checks authentication, subscription access, and request limits. The JEV input sent to TypeSafe does not include your authentication token or account email.
Focoach’s JEV processing code does not write the original goal or screen text to its database or application logs. Account-level request counts are processed separately for limits. Infrastructure and provider operational records follow their settings and agreements; we do not give a blanket guarantee of zero retention or no training across all providers. Excerpts can contain personal or workplace information visible on screen, so manage your sharing settings accordingly.
5. Optional improvement and training collection
Sharing usage information for improvement and AI training is off by default and separate from goal and OCR sharing. After you opt in, behavioral records and minimal usage statistics are collected during active focus sessions. Enabling the option does not automatically upload earlier local focus history.
Behavioral records can include app and window or page titles; complete HTTP(S) URL paths, queries, and fragments; search terms extracted from supported search-result URLs; normal or incognito tab status; activity intervals; key, click, and scroll counts; task categories; and structured reactions. URL username and password components are removed. This learning dataset excludes general typed characters, clipboard content, screen images, page bodies, and original goals, free-text replies, and notes.
Behavioral records are stored in Supabase and are not sent to GA4. Separate minimal statistics include random installation, focus-session, and event identifiers, platform, app version, timestamps, planned time, and actual time. Statistics are stored in Supabase and may then be sent server-side to GA4. These events exclude goals, conversations, app names, URLs, titles, email addresses, and authentication tokens.
Withdrawing consent stops further collection and deletes that device’s behavioral records and pending queue. To delete behavioral originals already received by the server, use Delete collection records in the app or contact us. Stop collection on each device to stop that device’s future uploads. Withdrawing consent alone does not automatically delete every previously received usage-statistics event.
6. Website analytics and security records
Vercel hosts the website and may process access, device, and network information to deliver and secure it. After you accept analytics cookies, the homepage, download, and blog pages may use Google Analytics to analyze visits, device and cookie identifiers, launch-update button clicks, successful signups, clicks from blog articles to the download page, and clicks on Mac and Windows installer links. Installer-click events add only the operating system, build architecture, and page language; they do not indicate a completed file download or app installation. Rejecting prevents the GA4 script from loading and analytics requests from being sent. Change your choice using Analytics cookie settings in the footer. The browser stores your choice to remember it. The email you enter is not included in analytics events.
Account, billing, and email-confirmation pages do not include the homepage’s GA4 analytics script. The essential sign-in cookie is used separately from analytics-cookie consent; blocking it prevents the website from keeping you signed in. Opening Paddle Checkout allows Paddle and its providers to process payment and security information. You can use your browser’s cookie and analytics blocking settings. See the provider policies below for their processing.
7. Providers and international processing
Supabase (authentication, databases, and server functions), Vercel (web hosting), Resend (authentication email), TypeSafe (AI assessment), Google Analytics (usage analytics), and Paddle (sales, payments, and subscriptions) process information to provide the service. Depending on the features you use, information may be transferred to or stored on these providers’ and subprocessors’ infrastructure outside your country.
The information and purposes depend on the features described above. Paddle’s own payment and legal-obligation processing follows its policies. Provider notices are maintained by those providers and do not replace this description of Focoach’s processing.
8. Retention and deletion
Local goals, sessions, notes, and other ordinary records may remain on your device until you delete them or remove the relevant local profile. Local behavioral records are limited to 7 days and 20 MiB, with cleanup when the app runs. Pending behavioral uploads are limited to 72 hours, 4,096 records, and 16 MiB. Server behavioral originals become eligible for scheduled cleanup 90 days after the event.
Accounts, subscription mappings, payment-processing records, and minimal usage statistics currently have no universal automatic expiry period. They are retained for as long as needed for accounts and service delivery, security, disputes, and legal obligations. After a deletion request, information no longer needed for those purposes is deleted or anonymized, while records needed for legal or payment obligations are restricted to the necessary scope.
Backups and provider records follow their operational and contractual retention cycles. We do not guarantee immediate deletion from every provider and backup within a fixed number of days. Deleting behavioral originals on the server is distinct from deletion of separately exported or processed training material; we will explain the applicable scope when handling your request.
9. Your choices and requests
Use app settings to manage goal and OCR sharing, optional improvement and training collection, and operating-system permissions. Contact us to exercise applicable rights such as access, correction, deletion, restriction, or consent withdrawal. An account-deletion request does not itself replace subscription cancellation; also confirm cancellation in subscription management to stop future charges.
We use only the identity verification necessary to handle your request and do not ask for your password or full card details. Send privacy requests to inlaer@inlaer.com. We will notify you before important processing changes and obtain consent where required.