Privacy Policy

1. Core Privacy Principle: Zero Server File Uploads

ToolRipple is engineered from the ground up as a client-side utility suite. When you select, drag, or drop a supported file into our available tools:

• Your file content is never transmitted to our servers.
• Your filenames and file paths are never logged or stored.
• OCR text extraction and image conversions execute strictly in your browser's local memory.
• QR code input strings remain entirely on your device.

Because we never receive your files, we cannot view, inspect, copy, sell, or retain any of your documents or images.

2. Data We Do Not Collect

We purposefully do not collect:

• Account credentials or user passwords (no user accounts are required).
• Payment information or credit card numbers (MVP utilities are free).
• Personal identifying information (PII) from your uploaded documents.
• Biometric or photo analysis data.

3. Local Storage & Cookie Preferences

We use browser local storage (localStorage) exclusively for client-side user experience conveniences:

• Appearance Theme (toolripple_theme): Remembers whether you prefer light mode or dark mode on your device.
• Consent Record (toolripple_consent): Remembers whether you chose to allow or decline performance analytics so you are not repeatedly prompted on each page visit.

These preferences are stored solely on your personal computer or mobile phone and are never synchronized to any remote database.

4. Hosting & Infrastructure

ToolRipple static web assets (HTML, CSS, JavaScript, and WebAssembly binaries) are served via global static edge hosting (Cloudflare Pages). Standard HTTP server access logs generated at the edge network (such as anonymized IP address, user-agent string, and requested static asset URL) are maintained by Cloudflare solely for DDoS mitigation, caching, and infrastructure security.

5. Performance Analytics & Google Analytics 4 (Basic Consent Mode v2)

To understand website traffic and ensure file conversion tools perform reliably across different browser versions, ToolRipple includes an optional, privacy-conscious integration with Google Analytics 4 (gtag.js) operating under Google Basic Consent Mode v2.

Our analytics integration is governed by non-negotiable architectural privacy boundaries:

• Strict Blocking Before Consent: No Google Analytics scripts or network requests are emitted until you explicitly click "Accept" on our consent banner. If you choose "Decline" or ignore the banner, zero tracking requests or analytical cookies are set.
• Advertising Permanently Denied: Advertising cookies, remarketing audiences, personalized ads, and Google Signals are permanently disabled (ad_storage, ad_user_data, and ad_personalization set to 'denied').
• Tool Events: The application’s custom analytics events contain predefined tool identifiers (e.g., merge-pdf), rather than document content or filenames.
• Google Analytics Data: If enabled and you consent, Google Analytics may also collect automatic events and identifiers. Its configuration must be reviewed to prevent collection of sensitive URLs, filenames, search terms, or other user document data.
• Right to Withdraw at Any Time: When analytics is configured, you can change your choice or withdraw consent at any time by clicking Cookie & Privacy Settings in the footer of any page. When analytics is not configured, that control is not shown.

6. Regional Privacy Compliance & Regulatory Notes

ToolRipple is committed to international data protection and privacy standards:

• European Union (GDPR) & United Kingdom (UK GDPR): Under Article 6 and the ePrivacy Directive, analytical cookies and device tracking require prior, freely given, specific, and informed consent. By blocking analytics prior to opt-in and offering equal "Accept" and "Decline" controls, ToolRipple aligns with core consent requirements. Deployments with commercial advertising or programmatic monetisation should evaluate a TCF v2.2 certified Consent Management Platform (CMP).
• California Consumer Privacy Act (CCPA / CPRA): ToolRipple does not sell, rent, or share personal information or user files with third parties for monetary or valuable consideration.

7. Contact Regarding Privacy

If you have questions, feedback, or security inquiries regarding our privacy-first architecture, please reach out via our contact page.