Cookie Policy
How cookies and similar technologies are categorized, documented, controlled, retained, and reviewed on ryha.dev.
This policy is a draft that requires review and approval by qualified legal counsel before public launch. It is provided for general information only and does not constitute legal advice. RYHA Technologies may update it from time to time, and only a formally approved published version should be treated as binding.
Scope and Similar Technologies
Cookies are small text files stored on a device. Similar technologies can include local storage, software development kits, pixels, and identifiers. This draft explains the categories the service may use and the controls required before launch. The final inventory must be generated from the deployed website and authenticated product rather than from planned code or a vendor list.
Categories and Purposes
Potential categories are: • Strictly necessary: authentication, session continuity, security, fraud prevention, requested settings, and core service delivery. • Preference: optional choices such as language, interface, and remembered settings. • Analytics: measurement of site and feature use to understand performance and usability. • Functional: optional enhanced features or third-party content. • Marketing: campaign measurement or advertising only if specifically approved and disclosed. A category does not establish that a technology is deployed. RYHA does not intend to use cookies to sell personal information.
Consent, Withdrawal, and Browser Signals
Non-essential technologies should remain disabled until the required choice is recorded. Users should be able to revisit and withdraw optional consent as easily as they granted it, without affecting strictly necessary functions. Browser controls can block or remove storage and may affect functionality. The final implementation must determine how legally recognized opt-out preference signals apply in each offered jurisdiction and must not claim support until deployed behavior is tested.
Inventory, Retention, Changes, and Contact
The approved inventory must name each deployed technology and provider, first- or third-party status, purpose, data collected, category, host, duration, and any transfer. Expiry values must be verified in production. Material inventory or purpose changes require consent and notice review where applicable. Questions about choices or the inventory can be sent to privacy@ryha.dev.