No analytics or advertising profile
The site does not need an advertising profile to explain the product. It does not need cross-site tracking to show a live simulation, publish documentation, host examples or provide SDK information. That makes the public privacy message easier to understand.
Visitors can read about the product without accepting a tracking banner. Developers can inspect documentation without being placed into an advertising audience. This is consistent with RTO’s broader position: reduce hidden behavior and prefer visible, explicit interactions.
If statistics are ever needed for server maintenance, they should be aggregate, anonymous and documented. They should not become a marketing tracker hidden behind vague language.
Why this fits local-first automation
RTO is presented as local-first browser automation. The extension runs in the user’s browser. The public model emphasizes visible tabs, explicit allow-listing and human review. Adding unnecessary tracking to the website would weaken that message.
A cookie-free public site also helps explain the extension’s own boundary. The product does not ask users to trust a hidden data collection pipeline while claiming to be privacy-conscious. The website and the extension should tell the same story.
The story is simple: no tracking cookies on the public site, no cookie reading as an extension feature, and no attempt to use cookies as a browser automation shortcut.
What would happen if this changed
If a future feature ever required a strictly necessary technical cookie, it should be documented clearly. If a future feature ever required non-essential cookies, consent should be requested where required before those cookies are used.
This is the safest public promise: do not claim that no technical nuance can ever exist, but state clearly what the site and extension are designed not to do today.
For now, the practical result is easy to understand: there is no cookie banner because there are no non-essential tracking cookies to consent to.
What users should remember
Users should remember three things. First, the public site does not use advertising, analytics or profiling cookies. Second, the extension is not designed to read website cookies. Third, RTO’s automation model relies on visible tabs and explicit boundaries, not hidden session extraction.
That combination is important for trust. It keeps the product easier to explain to users, developers and reviewers. It also avoids a common contradiction: asking people to trust a privacy-focused tool while tracking them unnecessarily on the product website.
No cookie banner is not an omission here. It is the visible result of a simpler privacy choice.