ravencache.dev

Keeping the wires. Cutting the strings.

RAVENCACHE / SITE INFORMATION

Privacy & cookies

What this site processes, and why.

Last updated October 27, 2026.

Ravencache is independently run. You can read its public pages without an account. This notice covers ravencache.dev and its Cloudflare Pages address.

Public browsing and measurement

This site does not use behavioural advertising, advertising pixels, or sell visitor information. It does use Cloudflare to deliver and protect pages, and the live public site includes Cloudflare’s Web Analytics measurement script. That measurement is not restricted to the owner.

Cloudflare describes its beacon as collecting page-view and performance metrics using the browser’s Performance API. Read Cloudflare’s explanation of Web Analytics. The presence of this measurement is why this site does not claim to have “no analytics.”

Delivering a page also involves technical request information such as your IP address, requested address, browser information, and request time. Cloudflare may process request and security information to operate its services. Its handling and retention are described in Cloudflare’s privacy policy; this site does not promise a particular deletion period for provider records.

The software-directory filters and Bandcamp date reminder run in your browser. They do not send your searches or date checks to Ravencache. Public content has no embedded social feeds, advertising widgets, or remote fonts.

Cookies for the private editor

The editor is for the site owner only. It uses essential cookies to complete GitHub sign-in, recognise the authorised session, and prevent forged requests. These are authentication cookies, rather than advertising identifiers. Reading public articles does not require signing in.

Both cookies are restricted to secure connections and unavailable to page JavaScript. The editor checks the owner’s GitHub identity and whether two-factor authentication is enabled. Passwords and authenticator codes are entered on GitHub, not on this site. GitHub handles that interaction under its privacy statement.

The owner’s drafts are stored in a private GitHub repository. Publishing creates public content. Repository history may retain earlier versions, so deleting a file does not necessarily remove its history. The editor does not store draft text in browser local storage.

Email and external services

If you email [email protected], your address, message, and anything you attach are used to handle your enquiry. Email passes through your provider and mine. Please do not send passwords, private keys, or other sensitive records.

Correspondence may be kept while handling an enquiry and for relevant follow-up or recordkeeping. Ask if you want a message deleted; I’ll explain any practical or legal reason it cannot be removed. There is no automatic deletion schedule promised here.

GitHub, Ko-fi, Bandcamp, EFF, and other external links lead to services with their own policies. This site uses ordinary links rather than embedding their widgets. Following a link, donating, or playing externally hosted audio may send request information to that provider. Do not put confidential information in page addresses or query strings.

Your choices and questions

You can block scripts or cookies in your browser and still read the public pages. Blocking cookies prevents the owner editor from working; blocking scripts disables its editor, directory filters, and date reminders. Browser controls do not prevent the hosting provider from receiving the requests needed to deliver a page.

For privacy questions, corrections, or requests about information you have sent, contact [email protected]. Depending on where you live, you may have rights concerning access, correction, deletion, or objection; I’ll consider requests under the rules that apply.

This page will be updated when the site’s data practices change. My Promise explains the editorial commitments behind it.