Privacy

This site has no accounts. It stores exactly two things locally in your browser by its own code: your theme preference (under the storage key rtila-theme), and your recent search queries. Nothing else is persisted locally by the site's own code.

The site measures usage with Google Analytics 4. GA4 sets first-party cookies on this origin whose names begin with _ga; those cookies distinguish one visitor from another and persist across sessions for up to two years. They carry no name, email or account identifier, because the site has no accounts. Google processes the collected measurements as a data processor; IP addresses are not written to logs by Google in GA4, and the site operator sees only aggregate counts. The measurement records these events, and only these events, by their exact names:

• bot_download_click (parameters: bot_id, os)
• bot_json_copied (parameters: bot_id)
• bot_import_attempted (parameters: bot_id, payload_chars, degraded)
• bot_tab_viewed (parameters: bot_id, tab)
• search_performed (parameters: query_length, result_count)
• search_opened (parameters: trigger)
• sell_page_cta (parameters: destination)
• desktop_app_installed_declared (parameters: bot_id)
• import_hint_shown (parameters: bot_id, has_app_signal)
• import_fallback_json_downloaded (parameters: bot_id)
• config_digest_copied (parameters: bot_id, surface)
• config_document_downloaded (parameters: bot_id, config_encoding, config_published)
• demo_video_facade_activated (parameters: video_id)
• directory_filter_applied (parameters: facet, value, active_facets, result_count)
• directory_filter_cleared (parameters: result_count)
• manifest_problem_exposed (parameters: bot_id, problem_count)
• listing_flagged (parameters: bot_id)

The site implements Google Consent Mode v2. For visitors from the European Economic Area, the United Kingdom and Switzerland, the analytics_storage, ad_storage, ad_user_data and ad_personalization signals default to denied, so no analytics or advertising cookie is written for those visitors and GA4 instead records cookieless pings that Google models statistically. For all other visitors analytics_storage defaults to granted. The site sets no advertising tags and never enables Google signals or ad personalization. Because the site has no consent banner, a visitor in those regions cannot currently grant consent; this is a deliberate choice to prioritise compliance over measurement completeness in that geography.

No analytics request is made at all when the site is served from localhost, 127.0.0.1, 0.0.0.0 or ::1, so development and preview traffic never reaches the property. The operator additionally excludes internal traffic by IP in the GA4 property configuration.

GA4 Enhanced Measurement additionally records page views, scrolls, outbound link clicks, file downloads, site search queries and video interactions automatically. These are Google-defined events rather than events this site names. The "page changes based on browser history events" option is disabled on this property, so using the catalogue's filter controls does not register as a page view.

You can block measurement by installing the Google Analytics opt-out browser add-on, by enabling Do Not Track together with a blocking extension, or by clearing the _ga cookies for this origin. Doing so does not affect any functionality of the directory, because no feature of the site depends on analytics.

When you download a launcher, the backend writes one line to its download log per request with these columns, in order: timestamp, client IP address, bot id, platform, HTTP status, byte count, request duration. General requests are written to a separate access log with these columns, in order: timestamp, client IP address, HTTP method, request id, response status. Log lines are used for abuse prevention and rate limiting; configuration fetches at launcher start are rate limited by IP as well. Logs rotate when they exceed the configured size limit, and rotated files are retained alongside the active log.

The directory never asks for your name, email, or payment details, and launcher configuration fetches contain no user data.