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.
• afftera-commercial-session in session storage, a random UUID generated by your browser so that several actions in one tab 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

The site can measure three first-party events: a page view, opening a published program listing, and following that listing's main link to its canonical merchant or network destination. The browser sends the event to this site's own /api/events endpoint with a fresh event UUID, the anonymous session UUID, bounded page paths, device class, and the time the event occurred.

At the beginning of a tab session, the browser also keeps the landing path, the referring hostname, and only the standard source, medium, campaign, content and term UTM fields already present in the landing URL. It carries that bounded acquisition context through internal navigation. It does not send a network address, an address hash, a full referrer URL, a full user agent, a name or an email address.

Tracking remains disabled unless the deployment has an explicitly enabled server-side database configuration. When disabled, the endpoint reports that state and stores nothing. When enabled, the server supplies the environment and capture time, may add a country code supplied by the hosting platform, verifies program identifiers against the published registry, and derives the destination hostname from canonical program data. An outbound click is only evidence that Afftera observed a link being followed. It is not evidence of a conversion, lead, customer or commission.

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.

The Afftera LinkedIn application

Off this site, Afftera maintains a LinkedIn application ("Afftera Publisher") whose only job is publishing posts to the founder's own LinkedIn profile through LinkedIn's official API. With the founder's explicit OAuth consent it receives the founder's member identifier, display name and a posting permission, and nothing about anyone else: it has no access to other LinkedIn members, and it neither collects nor receives any data about visitors to this site. The access token involved is stored on equipment Afftera controls rather than on this site's hosting, is shared with no third party, and can be revoked at any time from LinkedIn's own account settings. The only piece of this flow that touches afftera.com is the OAuth return page at /linkedin/oauth/callback, which displays a status message and transmits nothing.

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. Selected affiliate links may contain tracking or referral identifiers required by a merchant or affiliate platform to attribute a visit or qualifying action to Afftera. Afftera participates in the HighLevel Affiliate Program as an independent affiliate of HighLevel, not as HighLevel itself. See the affiliate disclosure for what these relationships mean 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.