Cookie Policy
Learn how yito uses essential and optional cookies or browser storage for security, authentication, language, product state, analytics, and support.
Last updated: 2026-07-10
- Contracting operator
- Mindepy, LLC
- Registered address
- 131 Continental Dr, Suite 305, Newark, DE 19713, New Castle County, United States
- Governing jurisdiction
- Delaware, United States
What this policy covers
This policy explains how yito uses cookies and similar browser storage when you visit the site or use the product.
Essential storage
Essential storage supports security, authentication, language selection, and the product state needed to provide a feature you request. Disabling it can prevent account and Studio functions from working.
This category can include a session identifier, request-protection values, the selected language, consent state, and short-lived checkout or sign-in continuation state. These values are used to deliver the requested service and are not switched off by the optional analytics choice. Session values normally expire when the session ends or according to the account security policy; a language or consent choice may remain longer so the site can remember it on the next visit.
Preferences and draft state
yito may store non-sensitive interface preferences and draft settings in your browser so that your workspace remains consistent between visits. Prompt text is not included in analytics events.
Draft and preference storage can include the selected creative mode, model controls, display choices, and identifiers needed to resume a local workflow. Uploaded media and generated outputs are handled through their product storage flows rather than being placed directly in an analytics cookie. Clearing browser storage can remove an unfinished local draft even when it does not delete a server-side account record.
Analytics
Optional analytics are enabled only when configured and permitted. They are used to understand product navigation and funnel performance. Analytics properties must not contain passwords, tokens, payment secrets, or prompt content.
When optional analytics are active, yito may record an anonymous browser identifier, the page or product surface viewed, a coarse referral source, consent category, locale, and registered product events. The purpose is to understand whether navigation and workflows function as intended, not to reconstruct the content a person creates. Optional analytics remain disabled where consent is required until a positive choice is stored.
Third-party services
Authentication, payment, support, or analytics providers may set their own cookies when their features are enabled. Their policies govern the data they process.
Opening an external sign-in or checkout surface can therefore create storage on that provider's domain. yito does not use a payment cookie to store full card details. Provider retention periods and cross-site controls are determined by the provider and the browser, subject to the provider terms shown during that interaction.
Retention and updates
Retention depends on the purpose of each value. Security and checkout continuation values should be short-lived; preferences and consent choices can persist until they expire, are replaced, or are cleared; optional provider storage follows the provider's documented period. We review this policy when a new storage category or provider changes the choices described here. A material change will be reflected in the policy date shown on this page.
Your choices
You can clear stored data through your browser. Where consent is required, optional categories remain disabled until you choose to enable them.
Blocking all storage can interrupt sign-in, fraud protection, language selection, checkout return handling, draft continuity, and other requested functions. You can instead decline optional analytics while keeping essential product storage available. Browser privacy controls, private browsing, and provider account settings can offer additional controls.
Contact
Contact contact@yito.ai if you have questions about this policy or want to identify the storage involved in a specific yito workflow.