This document is a working draft. It describes how Rikoo behaves, accurately, but the entity names, addresses and jurisdictions are placeholders and it has not been reviewed by counsel. Complete it in the Studio, have it reviewed, and remove this paragraph before launch.
Last updated: [date]. Controller: [legal entity, address].
The software sends us nothing
Rikoo is self-hosted. The platform runs on servers you operate, and it contains no usage telemetry, no phone-home and no analytics beacon. Your conversations, your documents, your credentials and your metrics stay in your database, your object store and your collector.
This is a property of the architecture, not a setting: there is no code path that sends operational data to us, and a fully disconnected install is a supported deployment. Where an agent talks to a model provider, it talks to the provider you configured, under your contract with them.
What this website collects
This site is a marketing and documentation site. It collects the following.
- Server logs. Requests are logged with an IP address, a timestamp, the path and a user agent, for security and to diagnose failures. Retained [retention period].
- A language preference. A cookie remembering which language you chose. It is strictly functional and holds nothing that identifies you.
- What you send us. If you write to one of the addresses on the contact page, we hold your message and your reply address for as long as the exchange is useful and [retention period] after.
- Product analytics. Which pages are read, in what order and which links are followed, so the documentation can be improved where it is actually used. Measurement goes through our own server rather than to a third-party domain, and by default nothing is stored on your device, so a reload starts a new, unlinked visit.
There is no advertising cookie, no tracking pixel and no profile built about you across other sites. The analytics above are proxied through this server, so your browser contacts no third-party domain, and a Do Not Track signal from your browser switches them off. Fonts are loaded from Google Fonts, which sees the request; self-hosting them is on the list.
Why we may process this
- Server logs and security measures: our legitimate interest in operating a site that is not abused.
- Correspondence: our legitimate interest in answering you, or the steps taken at your request before entering a contract.
- The language cookie: strictly necessary for the service you asked for.
- Product analytics: our legitimate interest in knowing which pages are useful, weighed against a measurement that stores nothing on your device and identifies no one.
Who else sees it
Our hosting provider, [hosting provider], processes what passes through the site on our behalf under a data processing agreement. Our analytics provider, PostHog, processes the page views described above on our behalf, on servers in the European Union, under the same kind of agreement. We do not sell personal data and we do not share it for advertising.
Your rights
You can ask for access to the personal data we hold about you, its correction or its deletion, a restriction on how we use it, a copy in a portable form, and you can object to processing based on legitimate interest. Write to privacy@rikoo.example; we answer within one month.
If you believe we have handled your data badly, you may complain to your supervisory authority: in [country], [authority].
When we host Rikoo for you
A managed offering is not available yet. When it is, we will be a processor acting on your instructions, the terms will be the ones in the data processing terms, and this notice will be updated before the offering opens rather than after.
Changes
Material changes to this notice are announced on this page with a new date. The previous versions are kept and are available on request.