Simple first-party analytics.

Minimal visitor analytics

The site records first-party pageviews using a normalized page route without query strings, the date and time, the referring hostname when available, a broad device class, and a one-way anonymous session value. A short-lived first-party analytics session lasts about 30 minutes.

RowanTree does not retain raw IP addresses as analytics identity, record form contents as analytics, use browser fingerprinting, or send this analytics data to an advertising tracker.

Game activity statistics

RowanTree records simple game activity such as launching a game from the website or actually starting an embedded game. Where an independently hosted RowanTree game sends its own first-party play event, raw player and session identifiers are one-way hashed before storage.

Public counts are aggregated. A “play” count is used only when a game-start event is available; otherwise the site labels the number as “launches.” Anonymous interaction-session records used to prevent repeated counting are retained for up to 90 days.

“I had fun”

You can give a game a simple thumbs-up without signing in. The site uses a random first-party browser token so the same browser cannot repeatedly inflate the count, and stores only a one-way hash of that identity with the game you liked. The token is not an advertising identifier, and you can press the button again to remove your thumbs-up.

Information you submit

If you use the Contact form or another RowanTree form that is deliberately made available, the site stores the details you choose to provide in a private studio inbox. Form details are not exposed publicly.

Cookies and local storage

The studio site does not add marketing cookies. It uses the short-lived analytics session described above and a longer-lived random first-party token only when a browser needs to remember a lightweight interaction such as a thumbs-up. Individual games may use their own device-local storage for settings and progress.

Dormant community tools

RowanTree has community-development tools for ideas, voting, and development signals, but they are currently hidden from the normal public website. Existing data and code are preserved so the system can be revisited later rather than silently reinterpreting old participation as the new thumbs-up signal.

Retention

Submitted messages remain in the private RowanTree inbox while useful for studio follow-up. Aggregated game counts may be retained as development history. Short-lived analytics and interaction-session records are periodically pruned.

Payments

This site does not collect payment-card details. If a verified external support or paid destination is offered, payment entry stays on that provider’s secure interface.

Choices and contact

You can use the contact form to ask about information you have submitted.

Updated 7 September 2026