SIMLAB · TRAFFIC PRIVACY
Aggregate arrivals and page views
Back to the landingActive sessions and product activity
When audience measurement is enabled, a visible landing, pricing or app tab sends a first-party signal about once a minute. A random in-memory handle distinguishes that tab temporarily; it rotates daily and is not stored in cookies or browser storage. The server hashes it and retains the last coarse destination and signal time for a five-minute active window. Expired handles are deleted on the next signal or owner statistics read. Only aggregate minute peaks remain for up to 95 days, pruned on subsequent measurements. DNT/GPC and known bots are excluded. Multiple tabs, reloads and devices may count separately; this is not a count of unique people or authenticated accounts.
Owner-only product reports also keep hourly aggregate counts of confirmed project creation, saved versions, completed uploads and saved videos for up to 95 days, with cleanup on later actions. They include owner actions, contain no project names or account identifiers, and do not build individual activity histories. These operational aggregates are derived from committed service operations, separately from browser audience signals. Neither report exposes identities to other users or sends analytics to a third party.
Link arrivals
The traffic panel defaults to successful HTML arrivals recorded on the server, without requiring JavaScript. Same-origin navigation, prefetches, known bots and DNT/GPC requests are excluded. Profile-link redirects count only when their final destination returns an eligible HTML document. Navigating onward through pricing or the app does not add an arrival. Reopening a link can count again; these are not unique people or clicks measured inside another platform. Missing referrers or reloads may be indistinguishable from direct arrivals. No new visitor identifier or session cookie is created. This separate counter starts at activation and never converts older page views into arrivals. The same owner classification, source reduction, capacity limits and retention periods below apply.
What our audience counters record
When enabled, the historical server counter counts successful HTML visits to the landing and pricing pages by broad source. A separate browser counter records rendered landing, pricing and application page views by source: a fixed public profile-link label, a search provider, a reduced external domain, or an unknown/direct category. It requires JavaScript. Reloads count; editor control changes do not. Browser and server totals can differ. Daily totals are kept for up to 95 days and minute totals for up to 26 hours, then pruned on subsequent measurements. There are no individual event records. Earlier totals cannot be reconstructed into the new source breakdown.
Cookieless daily visitor estimate
For an eligible page request, SimLab transiently combines the network address observed by its gateway with a coarse browser, platform and device category. A keyed HMAC that includes the Argentina calendar date converts those inputs into an opaque day-scoped value before database storage. The raw address and full user-agent are not written to the analytics database or logs by this counter. The opaque values are reduced to daily totals and deleted when the following measured day begins.
This provides an approximate daily count, not a count of people. A shared network may combine several people; a network change may count one person again. The day-scoped values cannot deduplicate a visitor across different days, so a multi-day result is reported as visitor-days and a daily average.
Browser storage and owner test visits
The browser counter keeps only a source category and a 30-minute expiry in session storage for the current tab, to retain the origin while moving from the landing into the app. This is not a unique browser or visitor identifier. A fixed owner-browser marker can persist for one year, including after sign-out. New page-view totals are separated into owner-recognized and other observations, so the owner can include or exclude their visits when reading reports without deleting them or changing collection. The previous include/exclude cookie, if present, also identifies an owner browser. A first anonymous visit in another browser or private window may not be recognized. Older aggregate totals lack this classification, remain explicitly unclassified and cannot be retroactively separated. Previously discarded observations cannot be recovered. The independent daily visitor estimate and landing design comparisons continue to omit new owner-recognized observations.
What it does not record
The counters do not save raw network addresses, full user-agents, full URLs, full referrers, search terms, arbitrary campaign values or unique cross-day browser identifiers. Fixed labels identify our public profile links, not individual visitors. External sites are reduced to a domain grouping and bounded in number. Authentication is checked transiently to classify owner visits; only the two-value owner/other group enters the aggregate counters, never an account ID, email, project, checkout or payment. No individual event history or third-party analytics are created.
Your privacy signals
Do Not Track or Global Privacy Control prevents page-view counts and the daily visitor estimate. Known bots and prefetch requests are skipped, but counts are not guaranteed to represent human visits. Referrers can be missing or reduced by the originating app or browser. A tagged link can be copied and shared, so its label is not proof of the page where it was clicked. Requests above the counters' capacity may be dropped; requests without a gateway-verified address do not enter the daily visitor estimate.
Separate services and voluntary forms
Account authentication, essential security and server operations are separate from this audience counter. When Paddle Checkout loads, SimLab records the first load time on the existing checkout receipt and uses it in aggregate reports. The signal contains only the transaction ID. Do Not Track and Global Privacy Control exclude this measurement.
If you choose Get notified, the email form explains the launch-notification opt-in. An email is never added merely because you visit.
Privacy questions: privacy@theyeprofessor.com.