WardenWho to contact
This notice covers the Warden website and its connected app services. Send privacy questions, correction requests, or requests to leave the launch list to contact@warden.to. Use the email associated with your account where possible; never send a password.
Visiting the website
We use Microsoft Clarity to understand how visitors use the public website through usage metrics, heatmaps and session recordings. Clarity may use cookies and other tracking technologies and shares usage data with Microsoft to help us improve the site. See the Microsoft Privacy Statement for how Microsoft uses this data. Images and fonts are served by the site or your device. Hosting and security services still process network requests, including technical connection information, to deliver and protect the service.
We ask before loading Clarity in the European Economic Area, United Kingdom and Switzerland. Elsewhere, Clarity starts automatically unless you decline or your browser sends Global Privacy Control. If your region cannot be determined, Clarity stays off until you accept. Use Analytics preferences in the footer to change your choice, saved for 180 days. Withdrawing clears this site's Clarity cookies and refreshes the page to stop recording. Advertising storage remains denied.
Website marketing analytics use PostHog and Google Analytics for Firebase in your browser, under the same analytics preference and Global Privacy Control checks. They measure public page visits, selected signup/contact links, scroll depth and form outcomes. Analytics include source/campaign labels, landing-page paths, language, timezone, screen dimensions and browser/operating-system details; PostHog also receives the browser user-agent. The providers process connection information and may derive approximate geography. We do not send form names, emails or message contents as analytics properties. We discard URL query strings except for approved campaign labels and do not enable additional PostHog session replay or form autocapture. Website events and identifiers are marked separately from app analytics. A random visit identifier and first-arrival details are kept in tab session storage for 30 minutes; Google Analytics also uses analytics cookies. Firestore keeps only a compact attribution summary alongside a submitted form, not a separate visitor/event log. Reports may undercount when analytics are declined, blocked or unavailable.
A clean visit does not need an account. Security or sign-in features can use essential browser storage when you request them.
The launch list
Joining requires your email and an explicit choice to receive a Warden launch email. We record the wording/version of that choice, its displayed language and when it was made. When Vercel provides it, we also record an approximate city, region and country; we do not request GPS access, store coordinates or retain your IP address. We also store a broad device category and the operating-system version reported by the browser. These may be approximate. When analytics are allowed, first-arrival source, landing page and campaign labels are attached to your signup as described above. A name is not needed. Joining does not buy anything or enroll you in unrelated marketing.
The email is used for the launch notice you requested. Ask to leave the list through the contact page or by email. A duplicate submission does not overwrite a recorded withdrawal. We do not promise a deletion schedule that the system does not implement.
Contact messages
We store your reply email, chosen subject, message, a broad device category and the operating-system version reported by the browser so we can respond and understand requests. Your name is optional. When analytics are allowed, first-arrival source, landing page and campaign labels are attached to your message as described above. We do not store the full user-agent, browser version, device model, a device identifier, approximate location, GPS, or a permanent IP identifier with your message. Contact messages do not subscribe you to marketing.
A separate abuse-prevention counter uses a hashed request identifier to limit repeated submissions. Messages are stored in Firebase and may be delivered to the support mailbox through Brevo. They remain until removed by an administrator; you can request removal.
Using the app and connected services
Signing in can store an account identifier, provider and email, profile answers, timezone, device push tokens, and subscription status. Connected features also store pairings, requests, messages you choose to send, decisions, streak/progress events, emergency-use records, and referral records. These support account recovery, personalization, notification delivery, purchases, and the agreement between you and your Warden.
Screen Time reports are processed in Apple's private report system. Where Apple's separately authorized data access is available, the app can use that permitted information on the device. We do not describe the product as technically incapable of displaying app names or usage. Your Warden receives request and relationship information, not a live feed of your screen, messages, or browsing.
Firebase Analytics and PostHog receive app interaction events, including onboarding, rule changes, access modes, configured allowances, requests, focus sessions and purchase outcomes. Events can be linked to your account and random installation identifier. They do not contain selected app names or Apple's app-selection tokens. Background protection check-ins are distinct from app opens. Network country is approximate, not GPS location. Website analytics preferences do not control app analytics.
Firebase Crashlytics receives crash and error reports, device details and analytics breadcrumbs that can include account-associated installation, event, rule and request identifiers. Diagnostics are not necessarily anonymous. The updated iOS app has no Microsoft Clarity mobile integration and does not enable mobile session recording. Microsoft Clarity on this website is separate and follows the website choices above.
Offers and product news are optional and off by default. This account-wide preference is separate from notification permission, essential service alerts and app analytics. If enabled, we use your preference, push token and Pro/access eligibility to select promotional sends. Turning it off stops future promotional sends but cannot recall notifications already accepted by Apple. Core app features do not require promotional consent.
Service providers
Vercel hosts the website and API. Google Firebase handles account authentication, database records and push infrastructure. Apple processes App Store payments and delivers iOS notifications; RevenueCat helps determine purchase entitlements. Brevo handles support and service email.
LinkForty supports referral links and install attribution. It receives language, time zone, screen dimensions, user-agent and app/OS version information for click-to-install matching, which its documentation describes as probabilistic. Warden does not supply an IDFA or IDFV. RevenueCat processes account-linked purchase and entitlement information. These providers have their own processing and retention terms.
Optional support-email drafting can send the support conversation an administrator chooses to OpenRouter and the selected model provider. Drafts require review before sending. This is not a claim of automatic training or a zero-retention agreement with those providers. Do not include sensitive information in a support message.
Providers can process data in countries other than yours. Their processing terms, international-transfer arrangements, storage locations and retention settings require ongoing operator review. We do not sell website visitor information to advertisers.
Retention and account deletion
In-app account deletion removes the primary service profile and linked device and installation records. It does not automatically erase Firebase Authentication or all analytics, attribution and purchase-provider records. Shared history, operational records, backups and goal records may remain. Retained goal records use a pseudonymous account handle and can include goals, a note, country and locale; they are not irreversibly anonymous. Contact contact@warden.to for access or further deletion requests. Deleting the app or account does not cancel an Apple subscription.
Provider records follow separate retention and deletion processes. Google states that Crashlytics keeps crash traces and associated identifiers for 90 days before removal begins from live and backup systems. Other retention depends on provider settings, plans and legal obligations; we do not promise a fixed period or completed provider deletion that has not been verified. Signing out or resetting a local analytics identity does not delete provider-held history.
Support and launch-list records are not currently subject to a universal automatic purge. Tell us when you want them removed. A minimal suppression record may be retained to honor an opt-out. Hosting logs, database backups and provider records can follow different retention schedules.
Your choices and rights
You can withdraw launch-email consent without affecting use of the website. Depending on the law that applies to you, you may also be entitled to access, correct, delete, export or restrict personal data, object to processing, or complain to your data-protection authority.
We use information to answer your request or provide the service, protect against abuse, meet legal obligations, and, for a launch email, act on your consent. We may need proportionate verification before disclosing or deleting account information. Contact us to exercise a right or ask about the applicable legal basis.
Children and parent-assisted setup
The website's launch list and account forms are not intended for independent use by children under 13. A parent's involvement in device setup is not, by itself, a complete child-account consent process. Please do not submit a child's name, age, or sensitive information through these website forms.
If you believe a child has supplied personal information, contact us so we can investigate and remove it as appropriate. Product availability and age requirements must follow the relevant platform and local rules.
Changes to this notice
Updated October 18, 2026. We update this notice when the practices described here change. A change that introduces optional tracking or a new consent-based purpose will require an appropriate choice before that processing starts.