Privacy

Afftera has no accounts, no login and no newsletter, so there is nothing on this site that asks you for your name, your email address or any other detail that identifies you. What follows describes the data the site does handle, which is analytics and request data rather than anything you type in.

What is stored in your browser

Two values, both written by the site itself and readable only by it:

• oa-view in local storage, remembering whether you last viewed the program list as a grid or a table.
• oa-sid in session storage, a random string generated in your browser so that several actions in one visit can be counted as one visit. It is not derived from anything about you, and the browser discards it when the tab closes.

Afftera sets no cookies of its own. The only component here capable of setting one is the analytics integration described below, and it is not currently switched on.

Usage events

When you search, open a listing, apply a filter or follow a link out to a merchant, the page sends an event to this site's own /api/events endpoint. That event contains the kind of action, the program it referred to where one applies, the path you were on, the session string above, whether the browser looks like a mobile or a desktop one, and any utm_ parameters that were already in the URL you arrived on.

What happens next depends on whether a database is configured for the deployment. Without one the endpoint accepts the event and discards it, storing nothing at all. With one configured it writes a row holding the fields above plus three the server adds: the referring page, a country code supplied by the hosting platform, and a hash of the network address the request came from. That last value is a truncated one-way digest computed with a fixed secret, kept so the same visitor is not counted twice; the address itself is never written down and the digest cannot be turned back into one.

Voting

Where a program can be upvoted, the record stored is the program and the same truncated address digest, which is what lets a vote be withdrawn again by the browser that cast it. Nothing else about the voter is kept. This feature also depends on a configured database and returns an unavailable response without one.

Integrations that are wired but off

The codebase contains a product analytics integration that, when a key is supplied, would record page views and interactions, store its identifiers in local storage and a cookie, and send them to a third-party analytics provider through a path on this domain. No key is supplied to the deployment serving this page, so none of that is happening and no such cookie is being set. It is described here because the capability exists and enabling it would change what this section says.

Several other integrations, used to gather public social and ranking data about programs rather than about visitors, are similarly dormant without credentials. They never handle visitor data in either state.

Hosting and server logs

This site runs on a third-party hosting platform, which necessarily receives every request in order to answer it, including its network address and headers. That processing belongs to the platform and follows its own terms and retention rules rather than anything Afftera configures, so no retention period is claimed here.

Links to merchants

Listings link out to affiliate program pages run by the merchants themselves. Once you follow one you are on their site under their privacy practices, which Afftera neither controls nor can describe. The links carry no identifier of you or of this site; see the affiliate disclosure for what that means commercially.

Submissions

The submission page builds a program record from what you type and copies it to your clipboard. Nothing entered there is transmitted anywhere; there is no server behind that form.

Questions and requests

Write to contact@afftera.com, the same address given on the contact page. Because the site holds no account and no contact details for you, a request about your own data can only reach the analytics rows described above, and those are keyed by a one-way digest that cannot be matched back to a person from the outside.

This page describes how the current version of the site behaves and makes no claim of certification or compliance with any particular data protection regime. It is updated when the behaviour changes rather than on a schedule.