PixpAI Cookie Policy
Effective Date: 7 December 2025
Purpose and scope
This Cookie Policy explains how Rovlid LLC uses cookies, SDKs, pixels, local storage, and comparable identifiers (together, Cookies) on pixpai.com and within in‑app webviews used by PixpAI. It applies to all web properties we control and to embedded web content that our apps display.
Relationship to other documents
This Policy complements the PixpAI Privacy Policy and the Terms of Service. If this Policy conflicts with the Privacy Policy on a data‑processing question, the Privacy Policy controls. Nothing here limits your rights under mandatory local privacy and e‑privacy law.
Current release and advertising status
The current production release operates without targeted advertising. Advertising and related identifiers are disabled by default. If we later enable ad‑supported experiences, we will present the required notices and choices and update this Policy before any new processing begins.
Technologies covered
Cookies are small data files placed on a browser or device. Pixels are small images that can confirm a request or event. Local and session storage are browser features for saving state. SDKs embedded in apps can collect comparable signals. Mobile advertising identifiers such as Apple’s IDFA and Google’s AAID are device‑level IDs used for measurement where permitted.
Categories of Cookies and similar technologies
Strictly necessary technologies enable core functionality such as session management, fraud prevention, load balancing, and consent storage. Security and anti‑abuse technologies help detect anomalous traffic and block automated misuse. Functionality technologies remember choices such as language, region, accessibility, and display settings. Performance and analytics technologies help us understand usage and reliability so we can improve stability. Advertising and measurement technologies support delivery, frequency capping, attribution, and improvement of Rovlid promotions and, where allowed, partner campaigns. Consent‑management technologies record and honor your choices.
Legal bases and regional compliance
In the EEA, UK, and Switzerland we request consent for non‑essential technologies and provide a preferences center to accept, reject, or customize categories at any time. In the United States we do not sell personal information for money. Where our use of advertising or analytics could constitute sharing for cross‑context behavioral advertising, you may opt out via site preferences and supported browser signals. In Brazil we obtain consent where required and otherwise rely on legitimate interests for essential operations. In Canada, Australia, and other regions we rely on legitimate interests for essential technologies and seek consent where local rules require it.
Your choices and controls
Use the Cookie settings link in the site footer to change or withdraw consent at any time. Your selection is stored using a consent Cookie so we can honor your choice. Most browsers allow you to block or delete Cookies, though blocking certain categories may affect site functionality. In email you can disable images to limit pixel loading and you can unsubscribe from marketing messages. On iOS you control tracking via App Tracking Transparency in device settings. On Android you can reset or limit the advertising ID. In‑app webviews may reflect your system or app‑level consent; some consent tools render differently inside webviews.
Global Privacy Control and Do Not Track
Where legally required and technically feasible, we honor Global Privacy Control signals on pixpai.com for opt‑out preferences related to targeted advertising or sharing. Industry Do Not Track signals are not yet standardized; your explicit choices in our banner or preferences center prevail.
Retention and duration
Session Cookies expire when you close your browser. Persistent Cookies remain until they expire or are deleted. Typical durations range from a few minutes to 24 months depending on purpose and provider. We retain consent records for a reasonable period to demonstrate compliance and to diagnose consent‑related issues.
Third‑party partners and transfers
Some technologies are set by third parties providing content delivery, security, analytics, crash diagnostics, payments, and advertising. Where a partner acts for us, contracts limit use to providing services and require appropriate protection. Data may be processed in the United States and other locations; where required we implement safeguards such as Standard Contractual Clauses and assess transfer risks.
Security and tag governance
We apply encryption in transit, least‑privilege access, tag reviews, and periodic audits of third‑party scripts and SDKs. We strive to minimize third‑party surface area and to load tags asynchronously where possible. We maintain incident response procedures and monitor for unexpected tag behavior.
Children
The Services are not directed to children under 13 or a higher age where required by local law. We do not knowingly use Cookies to profile children or deliver targeted ads to them.
Changes to this Policy
We may update this Policy to reflect changes to our Services, vendors, or legal requirements. When changes are material we provide reasonable notice and update the effective date.
Governing law
This Policy is governed by the laws of the State of Texas, USA, while honoring mandatory consumer and e‑privacy rules of your country of residence where applicable.
Contact
Email support@rovlid.com. Postal: Rovlid LLC, 5900 Balcones Drive, STE 100 #24657, Austin, TX 78731, USA.
Site‑specific Cookie table
We maintain site‑specific details for each PixpAI domain and product surface. The table lists name, provider, purpose, category, duration, and whether first‑ or third‑party. You can access the live table from the Cookie settings link or by emailing support@rovlid.com.
Consent records and audits
We log consent state with timestamp, region, device or browser metadata, and category selections to demonstrate compliance and respond to audits. Records are retained in accordance with our retention schedule.
Mobile app identifiers and SDK governance
Mobile SDKs may collect diagnostics and performance metrics. Where consent is required, SDK data collection is gated until consent is obtained. Where available, we configure SDKs to disable advertising personalization or data collection unless permitted. We block or remove SDKs that do not meet our security and privacy standards.
Email measurement
Marketing emails may include pixels or tracked links to measure delivery and aggregate engagement where permitted. You can unsubscribe at any time and can disable images in your email client to limit pixel loading.
International transfers
When technologies result in cross‑border data flows, we rely on appropriate safeguards, including Standard Contractual Clauses and supplementary measures, and we evaluate partner practices.
Appendix A. Illustrative identifiers
Essential and security examples include cf*clearance, **cf_bm, *Host‑, __Secure‑, rovlid_session, rovlid_csrf, and consent_choice. Performance and analytics examples include _ga, _ga*, _gid, _gcl_au, _clck, _clsk, and similar session keys. Payments and checkout examples include **stripe_mid and **stripe_sid and other provider session IDs. Advertising and measurement examples include _fbp, _tt_enable_cookie, _ttp, _uetsid, and _uetvid where permitted by your choices. Mobile identifiers may include IDFA, AAID, or app‑specific IDs used by SDKs for analytics, crash reporting, and, where consented, marketing measurement. The examples are illustrative; actual technologies vary by region, device, and surface.
Appendix B. Partner and SDK categories
Infrastructure and hosting provide compute, storage, and content delivery. Security and anti‑abuse provide bot mitigation and threat detection. Analytics and diagnostics provide crash reporting and performance telemetry, subject to consent where required. Payments provide checkout and fraud prevention. Advertising and measurement support delivery, frequency capping, and attribution only if ad experiences are enabled and consented. Support tooling provides ticketing and communication management.
Appendix C. Consent frameworks and signals
Where applicable we support regional consent frameworks and signals, including IAB TCF in the EEA and UK, Google Consent Mode for web tags, and Apple’s App Tracking Transparency for iOS. If a framework applies, your selections in the consent interface govern downstream tag behavior.