Information We Collect

RTILA X is a local-first desktop application. Web automations, scraped data, browser profiles, and AI prompts stay on your machine by default. RTILA X does not send your automation content, scraped data, or credentials to RTILA servers unless you explicitly configure a supported integration.

How We Use Information

The limited account and license information we receive is used only for license validation, activation, and support. RTILA CORPORATION does not sell, rent, or share your personal information with advertisers.

Data Storage

Your automations, datasets, browser profiles, cookies, and logs are stored locally on your computer. You can delete them at any time by removing the application data directory.

Third-Party Services

Third-party services are used only when you choose to enable them. Examples include cloud AI providers through OpenRouter, database connections, messaging integrations, or CAPTCHA solving services. When you connect an integration, you are responsible for reviewing that provider's privacy practices.

Cookies and Local Storage

This website stores the following first-party entries in your browser:

• rtila-theme (localStorage) — your light/dark theme preference. It is never transmitted to any server.
• _ga and _ga_* (cookies) — written by Google Analytics 4 on this origin for every visitor. They distinguish one visitor from another across sessions for up to two years. They contain no name, email address or account identifier, because this website has no user accounts.
• rtila_ga_cid (localStorage) — written only in the uncommon case where the analytics library is prevented from loading. It holds a pseudonymous numeric identifier so the fallback measurement beacon described below can still group your visits into one session series. It is removed when you clear site data.

The RTILA X desktop application does not use advertising trackers, and no analytics SDK is bundled into it.

Google acts as a data processor for the measurements collected on this website. Google Analytics 4 does not log or store IP addresses. To produce country- and city-level reports, Google transiently processes the IP address of each hit and then discards it. The site operator sees aggregate counts only.

Analytics Measurement Scope — All Regions

This website implements Google Consent Mode v2. The following defaults are applied to every visitor, in every region, on every page load, before any measurement request is sent:

• analytics_storage: granted
• ad_storage: denied
• ad_user_data: denied
• ad_personalization: denied

In practical terms: measurement is active for all visitors worldwide, including visitors in the European Economic Area, the United Kingdom and Switzerland. No consent banner is deployed on this website and no consent signal is collected from you before the analytics cookies described above are written. RTILA CORPORATION has made this a deliberate product decision in order to obtain complete, unmodelled usage statistics rather than the inferred, modelled data that Consent Mode produces when analytics storage is denied.

Advertising features are never enabled. This website runs no advertising tags, never turns on Google signals, never turns on ad personalization, and never shares measurement data with advertisers.

Because no consent banner is deployed, there is no on-site mechanism to decline analytics measurement before it happens. Your controls are set out in the "Your Controls" section below. Visitors in the EEA, the UK and Switzerland retain all of the rights described in "Your Rights" regardless of the measurement configuration above.

How Measurement Requests Leave Your Browser

Measurement traffic is routed through a same-origin endpoint operated by RTILA CORPORATION at https://rtila.com/ga4/…, which forwards it to Google Analytics. This is done so that the site's usage statistics are not silently under-counted by tracker-blocking software. The proxy adds no fields of its own; it forwards your IP address and browser user agent, both of which Google requires to derive device and geography reports, together with the page address, referrer and the event names listed below.

If the analytics library cannot be loaded at all, your browser instead sends a single measurement beacon to https://rtila.com/ga4/mp/collect containing the page address, page title, referrer, browser language, screen resolution and the pseudonymous client identifier described above.

What We Measure

The website records a page view on every document load plus exactly these named interactions:

• demo_video_play — parameters: video_id — Fired when a visitor activates the lite YouTube player to watch the product demo video.
• mac_fix_command_copied — parameters: command, status — Fired when a visitor on the Mac download page copies a Terminal command that clears the macOS quarantine flag. `command` records which variant was copied ("applications", "downloads" or "drag-path"); `status` records whether the clipboard write succeeded ("copied" or "failed").
• pricing_toggle — parameters: mode — Fired when a visitor flips the pricing page switch between monthly and lifetime billing.
• download_clicked — parameters: os, build — Fired when a visitor clicks an operating-system-specific installer download link.
• newsletter_result — parameters: status — Fired when the footer newsletter form reports a subscription success or failure.
• contact_form_submitted — parameters: form_id — Fired when a visitor submits a contact form identified by its form id.
• search_opened — parameters: trigger — Fired when a visitor opens the site search modal via a UI trigger.
• search_performed — parameters: query_length, result_count — Fired when a visitor completes a site search query and the result count is known.
• sticky_cta_clicked — parameters: cta — Fired when a visitor clicks a call-to-action button inside the sticky CTA bar.
• checkout_link_clicked — parameters: plan_name, billing, tier_devices, price_usd — Fired when a visitor clicks a checkout link for a named plan, billing mode, device tier and price.

GA4 Enhanced Measurement additionally records scrolls, outbound link clicks, file downloads, site search queries and video engagement automatically. These are Google-defined events rather than events this website names. The "page changes based on browser history events" option is not applicable to this property because the website never rewrites the address bar.

Your Controls

You can stop all measurement from this website without losing any functionality, because no feature of this website depends on analytics. Any one of the following is sufficient:

• Use a tracker-blocking browser or extension — Brave Shields, uBlock Origin, Firefox Enhanced Tracking Protection, or a DNS-level blocker such as Pi-hole. To block the first-party path specifically, add a rule for rtila.com/ga4/*.
• Install the Google Analytics opt-out browser add-on. Note that because measurement from this website is proxied through a same-origin path, the add-on may not intercept it; a content blocker rule as described above will.
• Delete the _ga cookies and the rtila_ga_cid localStorage entry for this origin.
• Browse in a private or incognito window configured to clear site data on close.

Doing so removes no functionality. You may also email support@rtila.com to request export or deletion of any data associated with your interactions.

Your Rights

You may request access to, correction of, or deletion of any personal information RTILA CORPORATION holds about you. Because most data stays on your device, you can usually export or delete it directly from the application.

Contact

Questions about this policy can be sent to support@rtila.com .