Cookie Notice
Last updated 18 October 2026
In short
- riwer sets no advertising cookies, and in ordinary use no cookies at all: it uses your browser’s own storage.
- Your sign-in and small preferences are kept there because riwer needs them to work.
- With your OK, riwer also counts what people do in it — a file made, a person invited — never what anybody writes. In the EU, the UK, Switzerland and Türkiye nothing in your browser is counted until you say yes.
- Paddle, when you pay, and Google or Apple, when you sign in with them, use their own on their own sites.
Cookies riwer sets
None in ordinary use. If riwer ever has to close the site behind a password for a while, one strictly necessary cookie, riwer_gate, remembers for 30 days that you have entered it. It holds no information about you.
What riwer keeps in your browser
riwer uses your browser’s local storage — which stays on your device — for what it needs to work and to remember how you like it:
- Your sign-in session, so you stay signed in. Without it you would sign in on every visit.
- Preferences, such as your theme, the layout of your panels, the documents you opened recently and how your board was zoomed.
None of it is used to follow you across sites, and none of it is sent to us. Your answer to the cookie message is kept there too (riwer.consent.v1), so riwer does not ask again.
Analytics, with your OK
To see what works in riwer and what does not, riwer counts what people do in it, in Mixpanel, with its data kept in the European Union. It counts actions and their plain facts — a project started, a file made and of what kind, a theme changed, a person invited, a file exported and in what format, which screen was open — with the browser and operating system, the screen’s size, and the site you came from. Never what anybody writes, never a page’s address, never your email or name, and nothing is recorded of the screen.
A random id, kept in your browser’s storage (riwer.analytics.device), tells one visit from the next. Once you sign in, your riwer account’s id is used instead — a number, not your name. Mixpanel works out a rough location (country and city) from your connection and does not keep the address itself.
- In the EU and EEA, the UK, Switzerland and Türkiye, riwer asks first, and counts nothing until you say yes. If riwer cannot tell where you are, it asks.
- Elsewhere, riwer counts unless you say no in Cookie settings.
- Anywhere, a browser that sends the Global Privacy Control signal is taken as a no, and a no stops it at once and forgets the id.
Apart from your browser, riwer’s server sends Mixpanel a few moments its own database records — an account or a project made, a document edited, an invite taken, Team started or ended — by account id, with nothing kept in your browser for it. The Privacy Policy says more.
Cookies others set
- Paddle — when you pay, Paddle’s checkout opens inside riwer from Paddle’s own site, and uses what it needs to take the payment safely. See Paddle’s privacy notice.
- Google and Apple — when you sign in with them, their own sign-in windows use their own cookies, under their own policies.
- Cloudflare Turnstile — when you ask for a sign-in email, a check from Cloudflare’s own site makes sure the request comes from a person, and uses only what it needs for that, under Cloudflare’s Turnstile privacy addendum. It is not loaded anywhere else in riwer.
Your choices
Open to say yes or no to analytics at any time; the link is also at the foot of riwer’s home page. You can clear or block cookies and local storage in your browser’s settings. riwer works without cookies; without local storage it cannot keep you signed in or remember your preferences.
Questions: support@riwer.io. The Privacy Policy says more about what riwer keeps.
Questions? support@riwer.io · Privacy · Terms · Refunds · Acceptable use · Sub-processors · Security · DPA · KVKK · Back to riwer