Privacy Policy

Last updated: 12 June 2026

YUL is designed to be private by default. Your routine photos, streak data, and journal stay on your device and in your personal iCloud. We don't run accounts, we don't see your photos, and your routine photos never leave your device through us. We do measure anonymous product usage (which features get used, not who used them), details below.

What we collect on our servers

Nothing personal. YUL has no user accounts and no server-side user database. We do not operate any backend that stores your routine history, photos, or identity. Everything you see in the app lives either on your device or in your own private iCloud container managed by Apple.

Routine photo (front camera)

When you finish a routine and tap Done, YUL captures a single still photo from your device's front camera and saves it as the first photo of that day's journal entry. The photo is your personal before/after record. It is stored on your device and synced through your own private iCloud, see "Routine photos and iCloud sync" below.

YUL does not analyze, verify, or run any face detection on this photo. There is no biometric processing, no face template, and no embedding. The photo is never uploaded to YUL, never sent to any third party, and never used to train anything. No network call leaves your device when you complete a routine.

Routine photos and iCloud sync

When you complete your routine, the captured still photo is saved to a sandboxed cache on your device with iOS file protection set to complete, meaning the file is unreadable while your device is locked. The cache is excluded from your iCloud device backup so the same image is not stored twice.

If you're signed in to iCloud, the photo and the corresponding routine metadata sync across your Apple devices through your private CloudKit container. This data is handled entirely by Apple. YUL operates no servers, so we cannot read, copy, or analyze your photos at any point, Apple's infrastructure delivers them between your own devices without ever passing through us.

You can disable iCloud sync for YUL at any time in your device's system Settings: Settings → [your name] → iCloud → Saved to iCloud → YUL. When you do, photos already synced remain in your iCloud container but no new ones are uploaded.

Your photos are yours. YUL has no ability to view, export, or share your routine photos. They live on your device and in your personal iCloud, both controlled by you and Apple.

App blocking (Screen Time / Family Controls)

YUL uses Apple's Family Controls and ManagedSettings frameworks to shield the apps you choose (TikTok, Instagram, etc.) until you complete your routine. The list of apps you've selected is represented by opaque tokens issued by Apple, YUL never sees the names of the apps you've chosen, and Apple does not share that information with us. The tokens are stored on your device and synced through your private iCloud container alongside other routine settings.

Notifications

If you grant notification permission, YUL uses it to schedule helpful local reminders, about your routine windows (window opening, close-warn 15 minutes before window end, streak status) and about the wellness pillars (hydration, movement, and UV/weather reminders that support your skincare routine). Every reminder is scheduled on-device, no push servers are involved and no notification data leaves your device. Each wellness reminder type can be turned off independently in the app's Settings, and you can revoke notification permission entirely in system Settings at any time.

Location & weather (optional)

YUL never asks for your location automatically. The weather card stays disabled until you tap "Enable Location" yourself. If you grant location access, YUL uses your coordinates solely to fetch local UV, humidity, and wind data from Apple's WeatherKit service, so the routine can adapt to current conditions. The weather request is handled by Apple; your location is never sent to our analytics, never linked to any identity, and never stored on our infrastructure (we operate no servers). You can decline the prompt, or revoke location access at any time in Settings → Privacy & Security → Location Services → YUL, the rest of the app works normally without it.

Health data (optional)

YUL can show your daily Movement ring using Apple's HealthKit framework. This is entirely opt-in: YUL only requests Health access when you tap to connect it in Settings, and never prompts otherwise. When connected, YUL reads your Active Energy (the calories behind your Move ring) to display your activity, it never writes any data to Health. Health data stays on your device, is never uploaded, never sent to our analytics, and never leaves your device through YUL. You can disconnect at any time in iOS Settings → Privacy & Security → Health → YUL.

Analytics (in the app)

This section is about the YUL iPhone app. Analytics on our marketing website, yulapp.com, works differently and is described separately under "Website analytics" below.

We use PostHog on its EU-hosted infrastructure for privacy-focused usage analytics. PostHog helps us see whether features are working, it does not build advertising profiles, and PostHog does not sell or share this data with anyone. (Separately, we send a small set of conversion events to Meta for ad attribution, see "Advertising attribution" below.)

What's sent: event names (for example, "Routine.completed", "Paywall.purchaseStarted", "Onboarding.completed") and a small set of bounded, non-identifying parameters that describe the event itself, such as which routine slot completed, which plan identifier was tapped on the paywall, an error-reason code drawn from a fixed vocabulary, or whether a window was on-time or postponed. No parameter is free-form text you entered.

What's never sent: your routine photos, the names of apps you've shielded, your name, your email, your iCloud identity, or advertising identifiers.

How you're identified: PostHog uses a randomly generated, per-install identifier that is not linked to your Apple ID and is reset when you delete and reinstall the app. We also enable PostHog's "Anonymize IPs" setting on the EU project, so IP addresses are discarded before any signal is stored. See PostHog's privacy policy for details.

EU hosting: Analytics data is processed on PostHog's EU-resident infrastructure (Frankfurt, Germany). Data is retained for 14 months and then automatically deleted.

Website analytics (yulapp.com)

This section is about our marketing website only (the pages at yulapp.com), not the YUL app. It is a separate context with its own tools and its own legal basis. Nothing here applies inside the app, and none of the app data described above is shared with the website tools below.

On the website we use two standard third-party measurement tools to understand how visitors find and use the site, and (in future) to measure whether advertising works:

This is browser tracking, and we treat it that way. Unlike the app (which uses Apple's privacy-preserving SKAdNetwork and sets no advertising identifier), these website tools use cookies in your browser. We are transparent about that here rather than describing the site as "no tracking."

What's collected: standard web-analytics signals, the pages you visit on yulapp.com, your approximate location (from IP, by the providers), browser and device type, and the cookie identifiers above. What's never collected here: your routine photos, journal, the apps you've shielded, your iCloud identity, or anything from inside the app, the website tools have no access to any of it.

EU/EEA/UK & Switzerland, no tags, no cookies. If you visit from the EU, the EEA, the UK, or Switzerland, neither the Meta Pixel nor Google Analytics is loaded at all, we strip both before the page reaches your browser, so no website-analytics cookie is set and no data is sent to Meta or Google. We do this instead of showing a cookie banner.

Everyone else, opting out. Outside those regions, you can opt out at any time: we honor the Global Privacy Control browser signal, and most browsers and extensions let you block these cookies directly. Honoring GPC or blocking the cookies stops Google Analytics and Meta measurement on the site.

Legal basis & providers: outside the EU/EEA/UK/Switzerland we rely on consent (which you can withdraw via GPC or by blocking the cookies, above) for these website cookies; inside those regions the tools are not loaded, so no such processing happens. Meta and Google act as independent controllers for the data their tools collect, see Meta's privacy policy and Google's privacy policy. The website itself is hosted on Cloudflare's edge network.

Advertising attribution in the app (Meta / SKAdNetwork)

This section is about ad attribution inside the YUL app. Ad measurement on the website uses a browser Meta Pixel and is described separately under "Website analytics" above, the two are independent.

If we run paid ads, we need to know whether they actually lead to sign-ups, without tracking you across other apps or websites. To do that, the app includes Meta's (Facebook's) SDK configured in a deliberately minimal, privacy-preserving way:

Consent in the EU/EEA & UK: for users in these regions, these attribution events are sent only after you opt in to analytics on the dedicated onboarding screen. If you decline, no events are sent to Meta. See Meta's privacy policy for how Meta handles SKAdNetwork data on its end.

Crash diagnostics

YUL uses Apple's MetricKit framework to receive crash and performance reports from iOS. MetricKit reports are generated and delivered on-device by iOS; the data they contain (stack traces, CPU/memory metrics, hang reports) is processed locally to help us understand stability issues. We do not pair these reports with any user-identifying information.

Payments

Subscriptions to YUL are processed entirely by Apple through the App Store. YUL never sees or stores your payment details. Your entitlement status is verified on-device using StoreKit 2.

Referral links

YUL supports invite links of the form https://yulapp.com/?ref=<identifier>. When someone you invited installs YUL and opens the link, the app records that you were the inviter, using only the anonymous CloudKit record name in the link, never your name, email, or any contact information. The attribution lives in the recipient's private iCloud container; our servers see no part of this flow.

Children

YUL is not directed at children under 13 (or under 16 in the EEA, where applicable) and does not knowingly collect data from them.

Data controller

The data controller for any limited processing described above is Ivan Terechin, an independent developer registered as an osek murshe in Israel (the "Developer"). Our website and supporting infrastructure are operated by Toolshare.ai LLC, a Delaware limited liability company owned by the Developer. You can reach us c/o Toolshare.ai LLC, 1007 N Orange St, 4th Floor, Suite 4749, Wilmington, DE 19801, United States, or by email at support@yulapp.com.

Legal basis (EEA / UK users)

We rely on the following lawful bases under the GDPR and UK GDPR:

Your rights

Because YUL is designed to not collect personal data, there's usually nothing for us to access or delete on our servers. Where applicable law (including the EU GDPR, UK GDPR, California CCPA/CPRA, and similar state laws) gives you the following rights, you can exercise them by emailing support@yulapp.com:

To delete your locally stored data and all iCloud-synced YUL data, uninstall the app and turn off Saved to iCloud → YUL in your device's system Settings; iCloud will purge YUL's container on the standard Apple schedule.

Complaints

If you're in the EEA or UK, you have the right to lodge a complaint with your local supervisory authority, a list is maintained by the European Data Protection Board, and UK residents can contact the Information Commissioner's Office. California residents may contact the California Privacy Protection Agency. We'd also appreciate the chance to resolve the issue directly first, email us at support@yulapp.com.

International transfers

Some processing happens outside your country. Our website runs on Cloudflare's global edge network. App analytics is processed on PostHog's EU infrastructure (Germany). The app's aggregated ad-attribution signals described under "Advertising attribution in the app" are handled by Meta Platforms, Inc. in the United States. For website visitors outside the EU/EEA/UK/Switzerland (those regions receive no website tags), the Meta Pixel and Google Analytics data is handled by Meta Platforms, Inc. and Google LLC respectively in the United States. Cloudflare, Meta, and Google are each certified under the EU-US Data Privacy Framework and offer Standard Contractual Clauses for transfers where the Framework does not apply. The Developer, as data controller, is based in Israel, which the European Commission recognizes as providing an adequate level of data protection for transfers from the EU.

Changes to this policy

If we materially change how YUL handles data, we'll update this page and bump the "last updated" date above.

Contact

Questions or concerns? The fastest way to reach us is by email at support@yulapp.com. You can also reach us by postal mail:

Ivan Terechin
c/o Toolshare.ai LLC
1007 N Orange St, 4th Floor, Suite 4749
Wilmington, DE 19801, United States