Privacy Policy

Effective date: August 25, 2026

Foremost (“Foremost,” “we,” “us,” or “our”) is operated by Roman Gurov, an individual based in Bali, Indonesia. This Privacy Policy explains how information is handled when you use the Foremost mobile application, this website, and related services (the “Service”). Roman Gurov is the controller of personal information processed for Foremost.

1. Information We Handle

Account information

When you sign in with Apple, Apple and our authentication provider, Supabase, provide or process an account identifier, authentication tokens, and, depending on your Apple settings and what Apple makes available, your email address and name. We use this information to create and authenticate your Foremost account. We also keep, on our Supabase backend, the Apple refresh token issued for your sign-in, encrypted at rest and used for one purpose only: when you delete your Foremost account, we present it to Apple to revoke Foremost’s Sign in with Apple authorization, as Apple requires. It is deleted with your account.

Mailing list

If Apple makes an email address available, we keep a contact record holding that address alongside your account identifier, so that we can send you occasional emails about Foremost, such as new features and release announcements. If you chose Apple’s Hide My Email option, the address we hold is the forwarding address Apple generated, and messages reach you through Apple’s private email relay rather than directly. Every such email carries an unsubscribe link, and unsubscribing does not affect your account or your use of the Service. We do not send marketing email on behalf of anyone else.

Waitlist

Before Foremost was released, this website carried a waitlist form. The form is gone, and the site no longer collects an email address. If you entered your address into it, we still hold that address so that we can tell you about Foremost. That is the only thing it is used for, and entering it was the whole of the consent we rely on — there is no account, no profile, and nothing else collected with it. The form recorded the address and the moment you submitted it. The page sets no cookies; the only third party it loads is the visit counter described next. You can unsubscribe from the release email when it arrives, or ask us to remove the address at any time using the contact address below. If you later create a Foremost account with the same email address, the two records become one.

Website analytics

Pages on this website load Cloudflare Web Analytics, which counts visits without cookies, without local storage, and without building a profile of you across sites. Cloudflare receives the page you opened, the site you arrived from, and the coarse technical details any browser sends with a request — country, browser and device type, and how quickly the page loaded. It does not receive your email address, and nothing it collects is joined to a waitlist entry or to a Foremost account. There is no cookie to refuse, which is why this site asks you to accept nothing.

Onboarding and product-use information

During onboarding, you may answer questions about your goals, occupation, distractions, focus habits, tasks you postpone, prior focus methods, estimated time spent on distracting apps, and preferred task source. We also collect information about how the Service is used, such as onboarding progress; connection of a task service; task creation or completion events and the selected task-source type; Screen Time permission results; counts of selected apps and categories; block-list mode and schedule choices; trial and paywall interactions; product identifiers for purchases; and account-deletion events. We do not send task titles to our analytics provider through the product events implemented in the current version. The one place a task title does leave the device for a purpose other than your task service is the paywall profile described under “Subscription information” below.

Tasks and task-service information

  • If you use manual tasks, task titles and app-generated task identifiers are stored on your device.
  • If you connect Apple Reminders, Foremost requests Reminders permission and accesses the selected reminder list, including list identifiers and names and the identifiers, titles, and completion status of reminders needed to display, create, rename, and complete tasks. The selected list identifier and name are stored on your device and made available to Foremost’s iOS extensions so they can recount unfinished reminders.
  • If you connect Todoist, Foremost receives and stores OAuth access and refresh tokens and the identifiers, names, and types of your selected Todoist source and destination. Foremost uses these credentials to read relevant projects, filters, and tasks and to create, rename, or complete tasks at your direction. Tasks created through Foremost receive a foremost label in Todoist. Todoist credentials and source details are also available to Foremost’s iOS extensions so the app can recount unfinished tasks while the main app is not open.

Screen Time and blocking information

If you grant Screen Time authorization, Apple’s Family Controls interface supplies Foremost with opaque tokens representing the apps, app categories, or web domains you select. Foremost stores those tokens with your block-list settings, including schedule, blocking mode, limits, status, and app/category counts. Foremost uses this information on your device through Apple’s Screen Time frameworks to apply blocks and usage limits. Foremost does not receive the content of what you do inside selected apps, and the current implementation does not send your opaque app-selection tokens to our backend or analytics provider.

Subscription information

If you view a paywall, buy or restore a subscription, or manage a subscription, Apple, RevenueCat and Superwall process purchase and subscription information. Superwall decides which paywall you see and draws it; RevenueCat and Apple handle the purchase itself. Foremost receives entitlement and customer-status information needed to determine whether Foremost Pro is active. We also record paywall and purchase events, such as the product identifier, successful restore, dismissal, or an error message.

So that a paywall can be tailored and can refer to the plan you built, Foremost also sends Superwall a small profile: your account identifier once you sign in, the answers you gave during onboarding, which task source you connected, how many block lists and apps you chose, when you asked to be reminded before the trial ends, and the title of the task at the top of your list. That task title is text you wrote. If you would rather it were not sent, do not add a task before the paywall; you can add one at any time afterwards.

App install attribution

If you installed Foremost after tapping an ad we placed in the App Store, Apple can tell us which ad it was. On first launch Foremost asks Apple’s AdServices framework for a short-lived attribution token, and one of our Supabase server functions exchanges that token with Apple. Apple returns identifiers for the campaign, ad group, keyword, and ad, the country the tap happened in, and whether the install was a first download or a re-download. Those identifiers describe the ad rather than you: they are identical for everyone who arrived through the same ad, and they carry nothing about your device, your identity, or what you do in other apps. We keep the result on your device and attach it to the analytics described below, to our subscription provider, and to the paywall profile sent to Superwall, so that we can tell which ads bring people who go on to find Foremost useful. RevenueCat separately collects the same Apple token for the same purpose. This does not use Apple’s Identifier for Advertisers and does not involve the App Tracking Transparency prompt, because it measures our own advertising rather than following you across other companies’ apps and websites. If you did not arrive through one of our ads, nothing is recorded beyond the fact that no campaign applies.

Device and interaction analytics

When analytics is configured, PostHog receives the Foremost account identifier and email address, product-use events described above, native app lifecycle events, and automatically captured touch interactions. Screen autocapture is disabled in the current version. The PostHog SDK also stores analytics state on your device.

Crash and reliability information

When crash reporting is configured, Sentry receives crash reports and unhandled application errors, together with the Foremost account identifier when you are signed in, and technical information about the device and the app such as device model, operating-system version, and app version and build. The start and end of app sessions are recorded so that we can measure how often Foremost crashes. Your email address, task titles, and Screen Time selections are not sent to Sentry, and performance tracing and session replay are switched off.

2. How We Use Information

We use information to:

  • create, authenticate, support, and delete Foremost accounts;
  • provide task lists and carry out task actions you request;
  • configure and enforce your selected blocking schedules, limits, and task-completion rules;
  • maintain Todoist authorization and refresh access tokens;
  • determine trial and subscription access and provide purchase-management features;
  • understand onboarding, feature use, reliability, and conversion so we can operate and improve Foremost;
  • measure which App Store advertising campaigns lead to installs and subscriptions, so that we know which of our own ads are worth running;
  • send occasional emails about Foremost to the address associated with your account, unless you have unsubscribed;
  • tell you about the release, if you joined the waitlist before it; and
  • protect the Service, diagnose errors, and respond to account-deletion requests.

3. Where Information Is Stored

Much of Foremost’s functional data is stored locally on your device. This includes manual tasks, block lists and schedules, selected Screen Time tokens, selected task-source configuration, Todoist credentials, Apple Reminders list metadata, onboarding status, trial/access state, and the install-attribution result described above.

On iOS, information required by Foremost’s extensions is also stored in Foremost’s App Group container. This may include block-list settings and opaque Screen Time tokens, unfinished-task counts, usage-limit counters and pass expiration, access state, Todoist credentials and source details, or selected Apple Reminders list details. The App Group is shared only among the Foremost app and its Foremost extensions under Apple’s entitlement system.

Account data is processed by Supabase. Analytics data is processed through PostHog Cloud in the United States. Subscription and entitlement data is processed by RevenueCat and Apple, and paywall presentation data by Superwall. Crash and error reports are processed by Sentry in the United States. Todoist data is processed by Todoist when you connect that service. Apple Reminders and Screen Time information is also subject to Apple’s operating-system controls.

4. When We Share Information

We disclose information only as needed to operate the Service with the following categories of recipients:

  • Supabase, for authentication, account deletion, the server functions used in the Todoist OAuth and token-refresh flow, and the server function that exchanges the Apple attribution token described above;
  • PostHog, for product, interaction, and lifecycle analytics used to understand and improve Foremost;
  • Sentry, our crash-reporting provider, which processes the crash reports and error diagnostics described above;
  • RevenueCat and Apple, for purchases, subscriptions, entitlements, restore, and subscription management;
  • Superwall, for deciding which paywall to show, drawing it, and measuring how paywalls perform, using the profile described above;
  • Resend, our email delivery provider, which processes the email address and delivery and unsubscribe status for the emails described above;
  • Cloudflare, which serves this website and provides the cookieless visit counting described above;
  • Todoist, if you connect Todoist, to authorize access and read or modify Todoist data at your direction; and
  • Apple services and device frameworks, if you use Sign in with Apple, Apple Reminders, Screen Time, or App Store purchases, and Apple Ads, which receives the attribution token described above and returns the campaign that produced an install.

These providers process information under their own terms and privacy policies. We may also disclose information if required by law or when reasonably necessary to protect the rights, safety, and security of users, the Service, or others.

We do not sell personal information, share it for cross-context behavioral advertising, or use it to target advertising at you. We do use the campaign identifiers described above to measure how our own App Store advertising performs, which is measurement of ads we paid for rather than tracking of you across other companies’ services.

5. Permissions and Your Choices

Screen Time and Reminders access are controlled through Apple’s permission and device-settings interfaces. You may decline Screen Time access or skip app selection, although blocking features will not work without an app selection and the required authorization. You may decline Reminders access and use manual tasks or another supported source.

You may disconnect Todoist or Apple Reminders and change your task source in Foremost settings. Disconnecting removes the saved connection configuration from Foremost on that device, but it does not delete information already held by Todoist or Apple or necessarily revoke access at the provider level. You can also manage connected-app access through the relevant provider or device settings.

You may delete your Foremost account from Settings. Account deletion revokes Foremost’s Sign in with Apple authorization, deletes the Supabase authentication user, and then removes Foremost’s device-local account data, connected-task configuration, manual tasks, block lists, schedules, and native task-sync configuration from that device. Deleting your Foremost account does not cancel an App Store subscription; subscriptions must be managed through Apple or the subscription-management interface provided in the app.

You may stop receiving emails about Foremost at any time by using the unsubscribe link in any such message, or by emailing us at the address below. This applies equally to a waitlist address, which you may have removed on request even though it is attached to no account. Unsubscribing removes you from the mailing list only; it does not delete your account, and we may still contact you about your account, a purchase, or a security matter where that is necessary.

Foremost currently does not provide an in-app data-export tool or an analytics opt-out setting. You may ask to access, correct, delete, or restrict our use of your personal information, or object to its processing, by emailing [email protected]. We may need to verify your identity before completing a request. These choices do not limit rights that cannot lawfully be limited.

6. Retention

Device-local information is generally retained until you delete it through the relevant feature, disconnect an integration, sign out, delete your account, or remove the app, subject to device backups and operating-system behavior outside our control. Signing out and account deletion trigger removal of Foremost’s account-specific local data and blocking schedules from that device.

Supabase account data is retained while your Foremost account remains active and is deleted when you delete the account, including the mailing-list contact record described above. A waitlist address is kept until the release announcement has been sent, or until you ask us to remove it, whichever comes first. If you unsubscribe without deleting your account, we keep a record that you unsubscribed, because that is what stops us mailing you again. Limited copies may remain temporarily in provider backups or security logs under the provider’s standard retention practices. Analytics is retained only for as long as reasonably needed to understand and improve Foremost and is then deleted or aggregated. Cloudflare's website analytics is aggregate from the start and is kept under Cloudflare's own retention schedule; there is no record in it that identifies you. Subscription, transaction, security-log, and provider records may be retained for the periods required by Apple, RevenueCat, Superwall, Supabase, PostHog, applicable law, fraud prevention, or dispute resolution. Todoist and Apple may retain information under their own policies after you disconnect them from Foremost.

7. Security

We use technical measures visible in the Service’s implementation, including HTTPS connections for the remote endpoints used by Foremost, authenticated bearer tokens for protected requests, caller authentication before server-side account deletion, and Apple App Group entitlements to scope data shared between Foremost and its extensions. Some sensitive functional data, including authentication sessions and Todoist credentials, is stored in the app’s local storage; the current application code does not add a separate encryption layer to that storage. No method of storage or transmission is completely secure.

8. Children

Foremost is not directed to children under 16. We do not knowingly collect personal information from children under 16. If you believe a child under 16 has provided information to us, contact [email protected].

9. International Processing and Legal Bases

Foremost is operated from Indonesia. Our service providers may process information in the United States and other countries where they operate. Those countries may have data-protection laws different from the laws where you live. Where applicable law requires it, we rely on contractual or other recognized safeguards for international transfers.

Where a legal basis is required, we process information as necessary to provide the Service and perform our agreement with you; to comply with legal obligations; with your consent when requested for device permissions, connected services, or the waitlist; and for our legitimate interests in securing, maintaining, and improving Foremost, provided those interests are not overridden by your rights.

10. Changes to This Policy

We may update this Privacy Policy when our practices or the Service change. We will post the updated policy and change the effective date above. If applicable law requires additional notice or consent for a material change, we will provide it.

11. Contact

Roman Gurov
Tirta Property
Petulu, Ubud District
Gianyar Regency, Bali 80571
Indonesia
Email: [email protected]