Privacy Policy
Who is responsible
Roman Starinskiy, an individual developer, provides YOSS. No company or sole-proprietorship entity is claimed. Contact: roman_starinskiy@icloud.com.
This policy covers the YOSS website, web app, Telegram Mini App and bot, and related account services. Apple-specific sections apply when you use a native Apple version. Telegram, browser push providers, Apple and our infrastructure providers also apply their own policies to their services.
Local use and your choices
Without signing in, your journal, profile, model estimates and settings stay in the browser's local storage. You can use the core model without an account. Clearing site data can erase these local records; installing or removing a browser shortcut is not a reliable way to erase them. Export a copy before clearing data if you want to keep it.
Signing in uses verified Telegram identity, either inside Telegram or through a browser sign-in that you approve in the bot. YOSS does not offer email or password registration. We receive the Telegram identifier and, where provided, a display name or username. Essential session cookies or tokens keep you signed in; local storage also keeps preferences and account-separated records.
Journal, cloud sync and backups
Your journal can include sleep, drinks, activity, meals, stress and wellbeing entries, body-state notes, imported health signals, profile information such as age and weight, routine rules, and model-derived history, patterns and forecasts. These may reveal sensitive information about you.
Cloud synchronization starts when you choose it. It uploads the selected account's records, profile, settings and derived history to YOSS servers and can download the account's cloud history. Cloud backup creation is also an explicit action. Enabling background reminders first synchronizes the account for delivery; saving notification preferences or message language can update the corresponding cloud settings.
Commands you send to the Telegram bot, including /water, /sleep, /stress and /steps, create records directly in your account's server-side journal. Telegram processes your messages under its own policy. Sending a bot command is a server action even if you have not pressed Sync in the web app.
Apple Health and file imports
The web app does not directly access HealthKit. If you choose an Apple Health XML export, the file is parsed locally in a worker; the complete XML file is not uploaded by that parser. You review and accept the supported recent signals. Accepted signals become part of your local YOSS data and can be uploaded later through your chosen synchronization or backup. YOSS and native-format imports can likewise contain personal journal data.
In a native Apple version, HealthKit access depends on the permissions you grant in iOS. The types and purposes must be shown by that version's permission request. You can revoke access in Apple Health or iOS settings. We do not use health data for advertising, sell it, or disclose it to data brokers. Apple's HealthKit and App Store requirements apply to that distribution; this policy does not claim that a user-selected export remains local after you import and synchronize its accepted data.
Notifications and weather
Reminders are optional. Web Push requires browser permission and registration of a delivery endpoint with YOSS, together with your account, time zone and reminder preferences. YOSS stores the endpoint and delivery state; the public application-server key is used to establish the push subscription. The current server sends a payload-free wake-up request rather than journal text or health values to the browser push provider. Your device creates the visible reminder. Browser and operating-system delivery can be delayed or unavailable.
Telegram delivery is enabled separately and uses the verified Telegram chat/account identifier and your preferences. Telegram receives the notification messages it delivers. You can disable a channel in YOSS and revoke browser permission separately.
Weather is optional and can be entered manually. If you request local weather, browser location permission is requested and coordinates rounded to two decimal places are sent to the YOSS server and its MET Norway weather proxy. The proxy caches weather responses for about 30 minutes. Approximate coordinates may still identify an area; they are not anonymous location data. Location tracking is not required for the journal.
Account usage and payment support
While a signed-in app is visible and online, it sends an account identifier and activity time about once per minute. YOSS uses account-linked presence and activity windows for usage statistics; these are not anonymous reports and do not contain journal or health values. The online window lasts two minutes. A separate server-side count of up to three activity dates determines whether a one-time trial can be offered; presence alone does not earn those days.
If purchases are available, YOSS records payment identifiers, payer/account identifiers, plan, amount, access dates and refund or renewal status for entitlement and support. Telegram Stars or the applicable store processes payment; YOSS does not receive card details. Payment support stores the message and reply you choose to send. Please do not include sign-in codes, card details or unnecessary health information. Email sent to the support address is processed to answer your request.
Providers and access
- Cloudflare hosting and D1: serve the web app and store account data, synchronized journal data, backups and service records.
- Telegram: verifies identity and processes bot messages, optional Telegram reminders and Stars transactions when available.
- Browser push providers: route optional Web Push requests to a registered device.
- MET Norway: receives rounded coordinates when you request weather.
- Supabase: runs the background scheduler that calls the YOSS delivery service. The scheduler is not the YOSS journal database and is not sent journal contents or health values by this scheduling flow.
- Apple and the support email provider: process their own platform services and support correspondence, where applicable.
Authorized staff can access the administrative data needed for support, access management and service operations. YOSS does not include advertising trackers or sell personal data. Information may also be disclosed when required by a valid legal obligation. Providers may process data outside your country, including outside the EEA; contact the developer for information about the safeguards applicable to your request.
Retention and deletion
- Local data: remains until you clear it, reset local data or your browser removes it. Downloaded exports and device backups remain wherever you save them.
- Cloud journal and profile: remain until replaced through synchronization or deleted through the cloud-data deletion control. YOSS keeps at most three application-level cloud backups and at most three local recovery copies, replacing older copies. It does not automatically erase the whole journal after 24 months.
- Usage windows: routine maintenance prunes windows older than 366 days. Cloud-data deletion also removes the account's presence and usage windows.
- Sign-in: browser account sessions expire after 24 hours; short sign-in approval flows expire after five minutes. Expired rows are cleaned during related service operations. Telegram Mini App tokens have a one-hour validity.
- Cloud-data deletion: removes the active cloud journal, profile, application backups, notification registrations and delivery jobs, account sessions, Telegram link and payment-support messages. Monthly renewal must first be cancelled successfully. Local browser data, your Telegram conversation, saved exports and provider-managed infrastructure backups are separate.
- Limited records retained after deletion: payment and refund records, minimal account/directory identifiers and associated dates, roles and access-grant audit records, deletion and anti-replay markers, and pseudonymized one-time-trial claims remain to restore access, prevent duplicate trials, handle disputes and protect the service. These ledgers do not contain the deleted journal. No automatic expiry for these retained ledgers is currently implemented; you can request a review of continued retention. Infrastructure backup retention follows the relevant provider's processes.
Legal grounds and your rights
Where GDPR applies, consent is the basis for optional health-data processing, including the additional condition of explicit consent for health data; a contract supports requested account and subscription services, and legitimate interests support proportionate service security and non-health usage statistics. Legal obligations or the establishment, exercise or defence of claims can require limited records to be retained. Agreement to general terms does not replace a separate consent where one is required.
You may request access, correction, deletion, portability or restriction, object to processing where applicable, and withdraw consent for future optional processing. Disable the relevant feature, revoke device permission or contact us. Withdrawal does not affect earlier lawful processing. Clearing local data does not delete cloud data; cloud deletion does not clear every device.
Contact roman_starinskiy@icloud.com. We may need to verify that a request belongs to you. Where GDPR applies, we normally respond within one month, subject to its permitted extensions and exceptions. You can complain to your competent data-protection authority. Other mandatory local privacy and consumer rights remain available.
Security, age and updates
YOSS uses HTTPS, authenticated account separation and restricted service access. Browser storage and exported files are accessible to people or software with access to your device. No service can promise absolute security; protect your device and Telegram account and choose export locations carefully.
YOSS is not intended for children under 13. A higher local age or parental-consent requirement still applies where required. Contact us if you believe a child's information has been provided improperly.
We publish changes here with an updated date and will provide further notice or request new consent where required. See also the Terms of Use and Support page.