Avenpa

Privacy

What we keep, and for how long

Nine short sections, written to be read once rather than skimmed. The short version: browsing this site tells us nothing about you, and the contact form holds one message until you ask us to drop it.

Last updated 11 October 2026

01 / Scope

What this covers

This page is the policy for www.avenpa.com, the studio site: a handful of pages, and one form.

Avenpa Tool is a separate service, with accounts, saved tools and its own database. Whatever happens there is covered by its own policy, not this one.

Avenpa Tool privacy policy

02 / Collection

Nothing, until you write to us

The pages are prerendered HTML served from Cloudflare's edge. There is no account system, no analytics script, no advertising tag, no tracking pixel and no cookie of our own.

We do not read a device identifier, we do not fingerprint a browser, and we do not ask a third party to do either. A visit that does not use the form leaves nothing behind that identifies you.

03 / The form

Name, email, topic, message

Sending the contact form stores the name, email address, topic and message you typed, together with the time it arrived, the browser's user-agent string, the two-letter country Cloudflare reports for the request, and an eight-byte salted hash of the connecting IP address.

The message is kept so that we can answer it. The hash exists so a repeat sender can be recognised without storing the address itself: it is stripped down to the first eight bytes of a SHA-256 digest, salted with a fixed studio string, and it cannot be turned back into an IP address.

04 / Storage

Cloudflare, and only Cloudflare

Messages are written to a Cloudflare D1 database bound to the worker that serves this site, and are read by the studio through Cloudflare's own tooling. Nobody else is given access.

Cloudflare also keeps ordinary network request logs for operating its edge, on its own terms. We do not put your message into a mailing list, a CRM, or any other system.

05 / Retention

Until the thread is done

A message is kept while the conversation is live and for a short while afterwards, so that a follow-up still has the earlier context.

There is no automatic expiry and no archive of old contacts. Ask for a message to be deleted and the row goes, along with anything derived from it.

06 / Your choices

Copy, correction, deletion

Write through the contact form and say what you want: a copy of what we hold for your address, a correction, or deletion. We answer to the same address, which is how we know the request is yours.

Contact details are never sold, rented, or shared with anybody else, and they are never used to send you something you did not ask for.

07 / Children

Not aimed at children

This site is written for people building and using software at work. It is not directed at children, and we do not knowingly keep a child's personal data.

If a child sent us a message, ask us to remove it and we will.

08 / Changes

Dated, not silent

If the practice changes — a new field on the form, a different database, a tool added to the studio — this page changes and the date at the top moves with it.

We do not rewrite an old policy quietly and leave the old date on it.

09 / Contact

Ask the studio

A question about this policy is a question we answer like any other: through the contact page, in writing, by a person.