Roogle
LegalBack to Roogle

Cookie Policy

Last updated: July 11, 2026

Roogle – a platform published by TNJ Alpine Technologies Sàrl

Version dated 07.07.2026

Document prepared for publication on Roogle. It should be reviewed and approved by your legal counsel before final publication.

This Cookie Policy explains how the website https://roogle.app/ uses cookies, pixels, scripts, local storage and similar technologies. It supplements Roogle’s Privacy Policy.

A cookie or tracker may be used to operate the website, remember a choice, maintain a session, measure website traffic, understand how the interface is used, provide online support or measure the performance of advertising campaigns.

1. Who places cookies?

The website is published by TNJ Alpine Technologies Sàrl, Rue de la Tour-de-l'Ile 4, 1204 Geneva, Switzerland, which can be contacted at contact@roogle.app.

Some cookies are placed directly by Roogle or its technical service providers. Other cookies may be placed or accessed by third-party service providers when the user gives consent, including Google Analytics, Meta Pixel, Microsoft Clarity and Crisp.

Cookies that are strictly necessary for the operation of the website or for the provision of a service requested by the user may be used without prior consent where permitted by applicable law.

This includes, in particular, cookies used for authentication, security, storing cookie preferences, maintaining the user session or recording certain essential preferences.

Non-essential cookies and trackers, including advanced audience measurement, session replay, heatmap or advertising tools, must not be activated before the user has given consent where such consent is required.

3. Trackers used or planned on Roogle

Category Service provider Purpose Data concerned Consent Indicative retention period
Necessary / security Roogle, Supabase, Hetzner Authentication, session management, security, abuse prevention, storage of cookie preferences and operation of the account and user area. Session identifier, technical token, IP address, technical logs and essential preferences. No, where they are strictly necessary. For the duration of the session or for the limited period necessary to provide the service. Cookie preferences may be stored for approximately 6 months.
Preferences Roogle Remember the language, certain filters, interface choices or browsing preferences where this facilitates use of the service. Language, country, city, interface or filter preferences, depending on the settings selected. No, where necessary for the requested service; yes, where the preference is not essential. For a limited period, generally until the preference is changed, the account is deleted or the tracker expires.
Audience measurement Google Analytics Measure visits, viewed pages, events and performance in order to improve Roogle. Cookies, online identifiers, page views, events, device, browser, approximate location and IP address processed according to the applicable configuration. Yes, where required for non-essential audience measurement trackers. According to the Google Analytics settings and the user’s consent choice; retention must be limited to what is necessary.
Product analytics Microsoft Clarity Understand how the interface is used, identify friction points and provide heatmaps and session replay where activated. Interactions, clicks, scrolling, pages viewed, device, browser and technical data. Sensitive fields should be masked. Yes, where required. According to the Microsoft Clarity settings and the user’s consent choice; retention must be limited to what is necessary.
Marketing / advertising Meta Pixel Measure conversions, optimise advertising campaigns and create or measure audiences where the user has given consent. Pixel data, online identifiers, page views, events, device, browser, IP address and data transmitted according to the applicable configuration. Yes, prior consent is generally required. According to Meta’s settings and the user’s consent choice. It may be disabled through the cookie management tool and Meta or browser settings.
Online support Crisp Display the support chat, respond to requests, retain conversation history and diagnose technical issues. Conversation identifier, e-mail address where provided, messages, technical metadata, viewed page and conversation status. Yes, where the widget or its trackers are not strictly necessary. Activation following user interaction is recommended. For the period necessary to provide support, followed by limited archiving in accordance with the support policy.
Payments Stripe Secure payments, prevent fraud and enable the purchase of a Premium subscription or Pass when a purchase is initiated. Payment identifiers, checkout session, anti-fraud data and billing data. Roogle does not store full bank card details. Cookies necessary for payment or fraud prevention may be used depending on the Stripe payment process. Other trackers may require consent where applicable. According to Stripe’s rules and applicable accounting and tax obligations.
Notifications Telegram Send instant notifications to paying Premium users who voluntarily activate this communication channel. Telegram identifier or other information necessary to send notifications, alert preferences and subscription status. In principle, this is not a Roogle website cookie. Activation is voluntary. Until Telegram notifications are disabled, the alert is deleted or the account is deleted.
Transactional e-mails Resend Send necessary e-mails, including verification messages, password reset messages, e-mail alerts and service-related notifications. E-mail address, sending metadata, delivery logs, bounced messages and errors. In principle, this is not a Roogle website cookie. For the period necessary for sending, support and proof of delivery.

During the first visit, the user may be invited to accept, refuse or customise non-essential cookies.

Refusing non-essential cookies must not prevent access to Roogle’s essential features, except for features that technically depend on a voluntarily activated third-party tracker or service.

The user must be able to change their choice at any time through the cookie management tool, a “Manage my cookies” link or any equivalent mechanism made available on the website.

The user’s cookie preferences may be stored for a limited period, generally approximately 6 months, so that the user is not asked to make the same choice during every visit.

For improved compliance, Roogle’s cookie banner should provide:

  • An “Accept” button and a “Refuse” button displayed with comparable visibility;
  • Easy access to a “Customise my choices” option;
  • Activation according to purpose: necessary, preferences, analytics, marketing and support;
  • No placement of non-essential Google Analytics, Meta Pixel, Microsoft Clarity or Crisp cookies before consent where consent is required;
  • Technical evidence of the user’s consent and any subsequent withdrawal;
  • The ability to withdraw consent as easily as it was given.

6. How can cookies be refused or deleted through the browser?

Users may also configure their browser to block or delete cookies.

The available settings vary depending on the browser used. However, blocking certain necessary cookies may affect the operation of the website, including account access, security features and the storage of user preferences.

Third-party tools may also provide their own privacy settings or opt-out mechanisms, including Google, Meta, Microsoft, Crisp, Stripe and Telegram.

Users are encouraged to review the privacy policies of these service providers to understand how they independently process personal data.

TNJ Alpine Technologies Sàrl may amend this Cookie Policy to reflect changes to Roogle, its service providers, the analytics, support or marketing tools used, or the applicable legal requirements.

The applicable version is the version published on https://roogle.app/ on the date it is consulted.

9. Contact

For any questions concerning the cookies and trackers used on Roogle, users may contact:

Back to Roogle