Updated September 30, 2026.
Our public websites send small visit summaries to Aesthetic Computer so we can understand which projects people open, interact with, and use.
A random identifier lasts for one page visit. It is held in memory, with no tracking cookie or persistent browser identifier. We do not connect visits across websites. Each summary contains the property, a broad page category, visible-time bucket, referring website hostname when available, interaction types and a few action flags such as following a link, triggering a musical note, accepting a painting edit, starting a recording, saving media or completing a game round. Actions are yes/no flags per visit, not recordings of notes, drawings or clicks. The tracker does not send page text, full URLs, search queries, form contents, raw keys, pointer movements or account identity. Known automated browsers are counted separately.
The visit database retains records for 35 days. Network requests necessarily reach our servers; existing access logs are separate from this database. The collector uses a temporary, salted address digest in memory for rate limiting, which expires after one minute and is not written into visit records.
Do Not Track or Global Privacy Control disables this visit tracker. Embedded frames and private/admin routes are excluded. Browser blocking, offline use and unrecognized automation mean the measurements are estimates of activity, not a count of unique people.
In the Aesthetic Computer runtime and Sotce Net, we also record signed-in activity against the account verified by our authentication service. This includes public built-in piece names (other programs use a broad category), reviewed action milestones, the referring website hostname, server receipt time, and a temporary session identifier. Sotce records the site category, not diary page numbers or contents. AC actions are flags per piece load, not a log of every note or stroke. Sotce also records each displayed-page milestone after two visible seconds, thirty seconds of foreground page display, newly saved touches and successful question submissions. These are activity signals, not proof that someone read a page.
Laer Klokken's canvas and HTML clients record repeated feature-use events for signed-in accounts: opening settings, changing themes and filters, switching interfaces, and requesting message sends or edits. Controls specific to each interface also record radio, language, mail navigation, older-history and media-opening requests. These contain feature names, not messages, recipients, media identifiers or link destinations. Requests do not prove successful delivery or playback. We use these records to compare feature use by account over the retained 35-day window.
This feed lets our administrators follow account activity and resolve public handles. It is not joined to anonymous visit identifiers and does not assign earlier anonymous activity to an account. Records expire after 35 days. The same privacy controls and private-route exclusions apply, except for the successful-submission milestone in Sotce's question form. Chat text, form contents, full referring URLs and search parameters are excluded. Account activity is not proof that a unique human was present.
A missing referrer means direct or unavailable: browsers, apps and redirects can omit it. These records stay in our first-party stack; they are not exported to PostHog. Existing operational logs and their retention are separate.
Updated September 28, 2026.
Our native apps (Menu Band, MacPal, Slab, Aesel, Oskiewar, the Aesthetic Computer app and desktop app) send one small message each time they open: the app, its version, the platform, whether this is its first launch, and a random install identifier. The app makes that identifier on its first launch and keeps it only in its own settings, so deleting the app deletes it. It is not tied to an account, device, advertising identifier or address, and it is not shared with anyone. We use it to count how many installs open each day. Records are kept for 35 days, and a coarse country from our network provider is kept with them.
Aesthetic Computer for iOS 1.2 adds foreground session counts, seconds spent active, successful-load and canvas-interaction flags. It sends cumulative snapshots so retries do not count as additional opens. The random install ID is kept in app settings, survives updates and may be restored with a backup; it is not an account or hardware identifier. “First observed” can therefore include an existing installation updating to this version. Offline snapshots are kept for at most seven days on the device; server session records expire after 35 days, while daily totals contain counts only. In iOS Settings → Apps → aesthetic, turn off “Share app usage” to stop sending and discard queued snapshots. Debug builds do not send these counts.
This describes the shared visit tracker. Existing account services, product analytics, purchases and public gameplay recordings have separate purposes and are not joined into its records.
Questions: mail@aesthetic.computer.