Something went wrong. Try again.
Monorepo for Aesthetic.Computer aesthetic.computer
Something went wrong. Try again.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283<!doctype html><html lang="en"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Aesthetic network visit measurements</title><style>body{max-width:42rem;margin:3rem auto;padding:0 1rem;font:18px/1.6 system-ui;color:#222;background:#fff}a{color:#174ca0}</style><h1>Website visit measurements</h1><p>Updated September 30, 2026.</p><p>Our public websites send small visit summaries to Aesthetic Computer so wecan understand which projects people open, interact with, and use.</p><p>A random identifier lasts for one page visit. It is held in memory, with notracking cookie or persistent browser identifier. We do not connect visitsacross 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 followinga link, triggering a musical note, accepting a painting edit, starting arecording, saving media or completing a game round. Actions are yes/no flagsper visit, not recordings of notes, drawings or clicks. The tracker does not send page text, fullURLs, search queries, form contents, raw keys, pointer movements or accountidentity. Known automated browsers are counted separately.</p><p>The visit database retains records for 35 days. Network requests necessarilyreach our servers; existing access logs are separate from this database. Thecollector uses a temporary, salted address digest in memory for rate limiting,which expires after one minute and is not written into visit records.</p><p>Do Not Track or Global Privacy Control disables this visit tracker. Embeddedframes and private/admin routes are excluded. Browser blocking, offline useand unrecognized automation mean the measurements are estimates of activity,not a count of unique people.</p><h2>Signed-in activity</h2><p>In the Aesthetic Computer runtime and Sotce Net, we also record signed-inactivity against the account verified by our authentication service. Thisincludes public built-in piece names (other programs use a broad category),reviewed action milestones, the referring website hostname, server receipttime, 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-pagemilestone after two visible seconds, thirty seconds of foreground page display,newly saved touches and successful question submissions. These are activitysignals, not proof that someone read a page.</p><p>Laer Klokken's canvas and HTML clients record repeated feature-use eventsfor signed-in accounts: opening settings, changing themes and filters,switching interfaces, and requesting message sends or edits. Controls specificto each interface also record radio, language, mail navigation, older-historyand media-opening requests. These contain feature names, not messages,recipients, media identifiers or link destinations. Requests do not provesuccessful delivery or playback. We use these records to compare feature useby account over the retained 35-day window.</p><p>This feed lets our administrators follow account activity and resolve publichandles. It is not joined to anonymous visit identifiers and does not assignearlier anonymous activity to an account. Records expire after 35 days. Thesame privacy controls and private-route exclusions apply, except for thesuccessful-submission milestone in Sotce's question form. Chat text, form contents,full referring URLs and search parameters are excluded. Account activity isnot proof that a unique human was present.</p><p>A missing referrer means direct or unavailable: browsers, apps and redirectscan omit it. These records stay in our first-party stack; they are not exportedto PostHog. Existing operational logs and their retention are separate.</p><h2>App launches</h2><p>Updated September 28, 2026.</p><p>Our native apps (Menu Band, MacPal, Slab, Aesel, Oskiewar, the AestheticComputer app and desktop app) send one small message each time they open: theapp, its version, the platform, whether this is its first launch, and a randominstall identifier. The app makes that identifier on its first launch and keepsit only in its own settings, so deleting the app deletes it. It is not tied toan account, device, advertising identifier or address, and it is not sharedwith anyone. We use it to count how many installs open each day. Records arekept for 35 days, and a coarse country from our network provider is kept withthem.</p><p>Aesthetic Computer for iOS 1.2 adds foreground session counts, seconds spentactive, successful-load and canvas-interaction flags. It sends cumulativesnapshots so retries do not count as additional opens. The random install IDis kept in app settings, survives updates and may be restored with a backup;it is not an account or hardware identifier. “First observed” can thereforeinclude an existing installation updating to this version. Offline snapshotsare kept for at most seven days on the device; server session records expireafter 35 days, while daily totals contain counts only. In iOS Settings → Apps→ aesthetic, turn off “Share app usage” to stop sending and discard queuedsnapshots. Debug builds do not send these counts.</p><p>This describes the shared visit tracker. Existing account services, productanalytics, purchases and public gameplay recordings have separate purposesand are not joined into its records.</p><p>Questions: <a href="mailto:mail@aesthetic.computer">mail@aesthetic.computer</a>.</p></html>