Contents
3. Necessary cookies #
The Service uses necessary cookies required to authenticate you, protect against cross-site request forgery, and optionally remember a trusted device.
Because these cookies are necessary for the Service to function securely, they are used on the basis of providing the Service you request rather than as optional marketing tools.
5. Local storage (not cookies) #
Locale and theme preferences are stored in localStorage on your device (internal keys associated with the flowtask product codebase). These preferences are not analytics cookies and are not used to track you across unrelated sites.
Clearing site data in your browser removes these preferences and may also clear cookies, requiring you to sign in again.
6. Analytics (Yandex.Metrika) #
The Service uses Yandex.Metrika (counter ID 112759090) to measure visits, traffic sources, click maps, and session replay (Webvisor). The counter script loads from Yandex domains (including mc.yandex.ru) and may set Yandex cookies or similar identifiers in your browser.
For guests, Metrika loads only after explicit consent via the on-site banner (stored in localStorage as flowtask.analytics_consent). Until consent is given—or if it is declined—the counter does not run. For signed-in users, Metrika is enabled as part of using the Service.
Yandex LLC processes Metrika data under Yandex’s Metrika terms and privacy policy. The Operator uses aggregated statistics to improve the Service.
You may limit analytics collection via browser settings, tracker-blocking extensions, or opt-out mechanisms provided by Yandex where available. Guests who declined can change their choice by clearing site data / localStorage.
7. Error monitoring (Sentry) #
The Service uses Sentry (Functional Software, Inc. / Sentry) for error monitoring, performance tracing, and diagnostics in the browser and on the server. Data is sent to the Operator’s project in the EU region (ingest.de.sentry.io).
In the browser, the SDK may send JavaScript errors, stack traces, page URLs, browser/device metadata, and related technical details. Session Replay (UI interaction recording) runs for guests only after consent via the same banner (flowtask.analytics_consent) or for signed-in users; text and media in Replay are masked by default.
On the server, the SDK may send API/worker exceptions, request traces, profiles, and technical logs needed to fix outages, under Sentry’s privacy policy.
8. Duration #
Session and CSRF cookies follow the Service’s session lifetime rules (including sliding and absolute limits). They are not limited to “until the browser tab closes” when a max-age is set. The remember-device cookie follows the trusted-device lifetime configured in the Service.
Lifetimes of Yandex.Metrika and Sentry browser storage are determined by those vendors’ SDKs. Exact lifetimes of Service cookies may change for security reasons; the functional purpose of each cookie remains as described above.
9. Third parties #
Payment flows may take you to YooKassa, which may set its own cookies under its policies. Telegram, MCP client applications, and Sentry are outside tydy.dev and may use their own storage.
The Operator does not control cookies set solely by those third parties.
10. Managing cookies #
You can delete or block cookies in your browser settings. Blocking flowtask_session or flowtask_csrf will prevent normal authenticated use of the Service. Disabling tydy_remember_device only affects remember-me behaviour.
Blocking Yandex or Sentry domains may disable Metrika / Session Replay without preventing sign-in. You can change locale and theme in the product UI, which updates localStorage accordingly.
12. Relation to other documents #
This Policy supplements the Privacy Policy and Personal Data Processing Policy. Capitalized concepts have the meanings given in those documents and the Terms of Service where applicable.