Rovlid Cookie Policy
Effective Date: 7 December, 2025
1) Purpose and scope 1.1 This Cookie Policy explains how Rovlid LLC (Rovlid, we, us, our) uses cookies, SDKs, pixels, local storage, and similar tracking technologies (collectively, Cookies) on our websites, web apps, and customer portals, and within our mobile applications where webviews or embedded browsers are used. 1.2 This Policy applies to all products and domains operated by Rovlid LLC and complements our Privacy Policy. If there is any conflict between this Policy and jurisdiction‑specific requirements, local law controls to the extent required.
2) What are Cookies and similar technologies 2.1 Cookies are small text files placed on your browser or device by a website. Pixels are tiny images embedded in pages or emails. Local storage and session storage are browser features for storing data. Mobile identifiers (for example, Apple’s IDFA and Google’s AAID) serve similar purposes in apps. 2.2 These technologies help us remember you, keep you signed in, understand usage, secure our services, measure performance, and, where permitted, deliver or measure marketing.
3) Categories of Cookies we use 3.1 Strictly necessary. Required for core site/app functions such as authentication, security, fraud prevention, load balancing, and user session management. These cannot be switched off in our systems. 3.2 Performance and analytics. Help us understand how visitors use our services (for example, pages viewed, time on page, crashes). Used to improve reliability, speed, and user experience. 3.3 Functionality. Remember choices you make (language, region, accessibility settings) and provide enhanced features. 3.4 Advertising and measurement. Enable delivery, measurement, and improvement of Rovlid promotions and, where allowed, partner campaigns. May rely on third‑party platforms. We do not serve targeted ads to children or where prohibited. 3.5 Security and anti‑abuse. Detect anomalous traffic, prevent automated misuse, and protect forms, APIs, and checkout flows.
4) Mobile app identifiers and SDKs 4.1 Our mobile apps may use SDKs that access device advertising IDs (IDFA/AAID) or app‑specific identifiers to provide analytics, crash reporting, or, where permitted, marketing measurement. 4.2 You can control tracking on iOS via Settings > Privacy & Security > Tracking and on Android via Settings > Privacy > Ads. Disabling these may affect personalized features but not core functionality.
5) Legal bases and consent 5.1 Where required (for example, in the EEA/UK/CH), we request your consent for non‑essential Cookies. You may accept, reject, or customize categories via our Cookie banner or preferences center at any time. 5.2 In other regions, we rely on legitimate interests for essential and strictly necessary Cookies and ask for consent where local law requires it.
6) Managing your preferences 6.1 Preferences center. You can change or withdraw consent at any time using the Cookie settings link in the site footer or app settings. Your selection is stored in a cookie so we can honor your choices. 6.2 Browser controls. Most browsers allow you to block or delete Cookies. Doing so may break certain features. 6.3 Email pixels. You can disable images in your email client to limit pixel tracking. Unsubscribe links are provided for marketing emails. 6.4 Device‑level settings. On iOS and Android, you can reset or limit ad identifiers and disable app‑level tracking where supported.
7) Global Privacy Control (GPC) and Do Not Track 7.1 Where legally required and technically feasible, we endeavor to honor Global Privacy Control signals for opt‑out preferences on our web properties. 7.2 Industry Do Not Track signals are not yet standardized. We prioritize explicit choices made in our Cookie banner or preferences center over generic DNT signals.
8) California and other US state rights 8.1 We do not sell personal information for money. If our use of advertising or analytics could be considered “sharing” for cross‑context behavioral advertising under the CPRA/US state laws, you may opt out via the preferences center or by enabling GPC on supported browsers. 8.2 You may also exercise applicable rights described in our Privacy Policy, including access, deletion, and correction.
9) International transfers 9.1 Some third‑party providers process data outside your country. Where required, we implement appropriate safeguards, such as Standard Contractual Clauses, and rely on approved transfer mechanisms.
10) Retention 10.1 Cookie lifetimes vary. Session Cookies expire when you close your browser; persistent Cookies remain until they expire or are deleted. We retain preference Cookies to remember your selections for a reasonable period (typically 6 to 12 months), after which we may re‑prompt for consent.
11) Third‑party Cookies and partners 11.1 Our services may integrate third‑party content or SDKs. These third parties may set their own Cookies subject to their privacy policies. We encourage you to review their notices. 11.2 Examples of third‑party categories we may use include: - Analytics and performance (for example, product analytics, crash reporting) - Security and anti‑abuse (for example, bot mitigation, rate limiting) - Payments and checkout (for example, payment gateway session IDs) - Marketing and measurement (for example, ad platforms and attribution)
12) Representative Cookie and identifier list 12.1 The specific Cookies deployed depend on which Rovlid site or product you use and your region. Examples include: - Essential and security: cf_clearance, __cf_bm, __Host-*, __Secure-*, sessionid, rovlid_session, rovlid_csrf - Preferences: rovlid_locale, rovlid_theme, consent_choice - Analytics and performance: _ga, _ga_*, _gid, _gcl_au, _clck, _clsk, _hjSessionUser_*, _hjSession_* - Payments: __stripe_mid, __stripe_sid, m (payment session), checkout_session - Marketing and measurement: _fbp, _tt_enable_cookie, _ttp, _uetsid, _uetvid, _twitter_sess - Mobile identifiers (apps): IDFA, AAID, app‑instance‑id (SDK specific) 12.2 The above are examples only. We will update our site‑specific Cookie table as our vendors or configurations change.
13) Email, web beacons, and local storage 13.1 We may use pixels in emails to measure opens and performance. You can opt out of marketing emails or disable images. 13.2 We may use local storage or IndexedDB for performance caching and to store non‑sensitive preferences. Clearing your browser storage may remove these.
14) Children 14.1 Our services are not directed to children under the age specified in our Privacy Policy. We do not knowingly use Cookies to profile children or deliver targeted ads to them.
15) Security 15.1 We use technical and organizational measures to help protect data collected via Cookies, including encryption in transit, access controls, and minimization of identifiers where feasible.
16) Changes to this Policy 16.1 We may update this Policy from time to time to reflect changes to our services, Cookies, or legal requirements. When we make material changes, we will provide reasonable notice and update the effective date.
17) Contact 17.1 Company: Rovlid LLC 17.2 Address: 5900 Balcones Drive, STE 100 #24657, Austin, TX 78731, USA 17.3 Email: support@rovlid.com
18) Jurisdiction and interpretation 18.1 This Policy is governed by the laws of the State of Texas, USA, without regard to conflict of law rules, while honoring mandatory consumer and e‑privacy rules of your country of residence where applicable.
19) Site‑specific Cookie details 19.1 We maintain site‑specific Cookie details to help you identify the exact Cookies used on a given domain or product. These include name, purpose, provider, category, and duration. If a Cookie is set by a third party, we identify the provider and link to its policy where available. 19.2 You can request these details or a current vendor list at any time by contacting support@rovlid.com, or consult the Cookie settings link in the site footer where we publish a live table when a consent manager is enabled.
20) Consent records and audits 20.1 Your consent choices are logged with timestamp, country/region, device/browser metadata, and categories selected, so we can demonstrate compliance. Where IAB TCF is enabled, we may store a consent string in a first‑party Cookie or local storage. These records are retained for a reasonable period consistent with legal requirements and our retention schedule.
21) Google and Apple platform specifics 21.1 Google Consent Mode (where enabled) adjusts the behavior of Google tags based on your consent status for analytics and ads. If you decline certain categories, tags operate in a limited or cookieless mode. 21.2 Apple platforms require App Tracking Transparency (ATT) permission before accessing IDFA. If you deny ATT permission, we do not use IDFA for tracking; only essential, non‑tracking functionality remains.