Privacy notice
Public reading and browser preferences
Reading and RSS subscription do not require an account. Saved articles, read status, theme preference and unsent feedback drafts are kept in your current browser, without synchronization across devices. Clearing browser data removes them. The language is included in the requested URL. Requests still reach the server and may appear in access logs.
This deployment has no advertising, third-party visitor analytics or tracking pixels. An RSS reader is a separate service: its own privacy notice applies.
Optional reader accounts
You may create a reader account to save a display name, reading language and fuel-category preferences across devices. Public articles and RSS remain available without signing in. Bookmarks and read status still stay in your current browser; creating an account does not move those records to the server or activate email, SMS or messaging-app delivery.
For password accounts, we store your username, display name, a salted password hash and a hash of your recovery code. We do not store your readable password or recovery code. A recovery code is displayed when issued and replaces the previous code when account access is recovered. Keep it privately: it can be used to regain access to your account.
If you add a passkey, we store its public key, credential identifier and limited device/usage metadata needed to check later sign-ins. Your fingerprint, face scan and device-unlock secret stay with your device or passkey provider; renofaro does not receive them. Your device or password manager may offer to synchronize a passkey under its own terms.
When Google sign-in is available and you choose it, Google authenticates you and returns an account identifier and profile information. The site uses Google's stable account identifier for sign-in and does not merge accounts merely because an email address matches. Google sign-in is displayed as available only after the site's Google application has been configured. Password and passkey login do not require a Google account.
Reader sessions use a secure, HTTP-only cookie scoped to renofaro, with a maximum lifetime of 30 days. Temporary sign-in challenges expire after five minutes. Authentication attempts are limited to reduce abuse. We do not send passwords, passkeys or reader preferences to article-processing or translation models. You can sign out or delete your account in Account settings; deletion removes the live account, credentials, sessions and preferences. Restricted database backups may retain earlier copies for up to 14 days.
Feedback and administration
Submitted feedback stores your message, optional email, page URL and optional screenshot on our server so we can investigate it. A keyed identifier derived from network address and browser family helps control abuse. It is pseudonymous data. Include only information needed to explain the issue.
Feedback is accessible to the site's administrator. It is not forwarded to Feishu or sent to article-processing models. Messages, email, page URL and screenshot content are deleted after 90 days, or sooner when a removal request is handled. A handling record without that content may remain. Daily database backups are retained for 14 days, so removed content can remain in a restricted backup for that period.
Administrator login uses a secure, HTTP-only session cookie restricted to this site's path. It expires after 30 days. Public reading does not use that login cookie.
Hosting and public-source processing
The application, database, feedback and backups are hosted on our server in Amsterdam, Netherlands. Server and reverse-proxy logs may include IP address, request time, URL, user agent and errors. Web access logs rotate daily and retain 14 days. Application logs are size limited and contain operational records.
Article processing uses public source material. Summary translation first uses the open-source OPUS-MT models on our server. When necessary, editorial processing and translation use our privately connected Windows model. That processing is separate from reader feedback. Paid external model APIs and external feedback forwarding are disabled in this deployment. Model names and licenses are documented with the installation.
External links and requests
Original-source links take you to publishers' services, whose own privacy notices apply. To request access, correction or deletion of submitted feedback, use Feedback with Privacy at the start of your message and supply enough information to identify the submission. We may need to verify a request before disclosing or removing another person's data. Changes to this notice will carry a new date and version here.