Legal

Data Practices

Technical details on how cleange collects, processes, and stores data.

Last updated:

1. Data We Collect

cleange collects only non-personally identifiable information through server-side processes. We do not collect, store, or process any personally identifiable information (PII) during normal site usage. No user accounts, registration forms, or login systems exist on this site.

As a clean living & ingredients resource, cleange.com serves articles, guides, and interactive tools. The analytics data collected helps us understand which clean living & ingredients topics are most useful to readers and improve our coverage accordingly.

The data points collected server-side on each page request are:

  • Page path — the URL path of the page visited
  • Referrer — the referring URL, if provided by the browser
  • Country code — a two-letter country code derived from the request IP at the network edge
  • Device classification — mobile, desktop, or tablet, derived from the User-Agent header
  • Bot flag — a boolean indicating whether the request appears to originate from an automated crawler
  • Timestamp — the date and time of the request in UTC

IP addresses are used solely at the network edge to derive the country code. The IP address itself is never written to storage, logs, or any persistent data store.

2. Data Processing

All data processing occurs at the network edge, close to the user. No data is routed to a centralised origin server for processing. The processing pipeline is as follows:

  • Edge extraction — country code and device type are derived from request headers at the network edge
  • Aggregation — individual request data is aggregated into daily summary statistics
  • Storage — only aggregated, non-identifiable data is persisted to the database

No machine learning models, profiling systems, or automated decision-making processes operate on the collected data. The data is used solely for understanding aggregate traffic patterns.

3. Data Storage

Data is processed and stored at the edge using distributed infrastructure. The following retention policies apply:

  • Raw request data — processed in memory at the edge and not persisted. Discarded immediately after aggregation.
  • Aggregated analytics — stored for a maximum of 90 days before automatic deletion
  • Summary statistics — non-identifiable trend data (e.g., monthly page view counts) may be retained indefinitely

All stored data resides within Cloudflare's global network. No data is transferred to or stored on privately operated servers. Data is encrypted at rest and in transit.

4. Data Deletion

Because cleange does not collect personally identifiable information, there is typically no personal data to delete. However:

  • Aggregated analytics data is automatically purged after 90 days
  • If you believe any data associated with your visit should be removed, you may submit a request through the contact form at /contact/
  • We will respond to legitimate deletion requests within 30 days

Third-party services (Google Analytics, Google AdSense, Cloudflare) maintain their own data deletion procedures and timelines as described in their respective policies.

5. Third-Party Data Sharing

cleange does not sell, rent, trade, or otherwise share any collected data with third parties. No data is transmitted to external parties for marketing, advertising targeting, or any other commercial purpose.

The only third-party services that independently collect data through their own mechanisms are:

These services operate under their own data collection and sharing policies, independent of cleange.

6. Data Portability

Under regulations such as the GDPR, you have the right to receive personal data concerning you in a structured, commonly used, and machine-readable format.

Because cleange does not collect or store personal data, there is typically no data to export. All interactive tools on the site run entirely in your browser, and any inputs or outputs remain on your device.

This includes all tools currently on cleange.com: Ingredient Safety Checker. These tools process data in-browser using JavaScript and do not communicate with any backend service.

If you have previously submitted information through the contact form and wish to receive a copy of that data, you may submit a portability request through the contact form at /contact/. We will respond within 30 days.

7. Changes to These Practices

We may update this Data Practices page to reflect changes in our technical infrastructure or data handling procedures. When we make changes, we will update the "Last updated" date at the top of this page.

This page complements the Privacy Policy with additional technical detail. In the event of any conflict, the Privacy Policy shall take precedence.