Privacy
Cartlight keeps as little data as it can. This page lists every place that keeps or receives data, what it keeps, and when the data goes.
Who is responsible
Daniel Richter, Henggart, Switzerland, is responsible for the data on this page. Write to hello@
No tracking
Cartlight uses no cookies for tracking and no analytics service. A check sets no cookie in your browser. Cartlight counts page visits for each day and source only, with no data about you (see "Visit counts" below).
Where your data goes
Checks (Supabase)
- What
- The shop's domain, the light, the reasons with their evidence, the times and the engine version. The evidence can hold what a shop publishes about itself: the contact email address on its pages and the seller address in its imprint. For a Swiss shop, it can also hold its company's entry in the commercial register. For a sole trader, that is personal data.
- Where
- Zurich, Switzerland
- How long
- Without end, as the shop's public result
- How it ends
- A shop owner can ask for a new check through a dispute.
Requester hash (Supabase)
- What
- A code made from your IP address with a key that changes every day (a daily-salted HMAC). Cartlight never stores the IP address itself.
- Where
- Zurich, Switzerland
- How long
- 30 days
- How it ends
- Cleared by a daily job after 30 days.
Snapshots (Supabase Storage)
- What
- The shop's public pages as the check read them: the full HTML, with any names, email addresses and postal addresses that the pages show. A short list of response headers:
content-type,content-language,content-length,last-modified,strict-transport-securityandserver. No cookie header. This holds for older snapshots too. - Where
- Zurich, Switzerland
- How long
- While the check is the shop's latest, then 12 more months
- How it ends
- A daily job deletes the snapshot 12 months after a newer check of the same shop. The check's result stays.
Labelled set (Supabase Storage and Daniel's Mac)
- What
- Copies of the public pages of shops that a public warning list or another named source labelled, kept as a snapshot keeps them, with the domain, the source and the time. They hold any names and addresses that the pages show. Cartlight uses them only to test and improve its checks.
- Where
- Zurich, Switzerland, and Daniel's Mac in Switzerland. Its Documents folder syncs to Apple's iCloud Drive.
- How long
- As long as the pages help to test the checks
- How it ends
- Daniel deletes them by hand, also when a shop owner asks.
Browser on the worker (Fly.io)
- What
- Cookies, cache and storage of the shop's pages, while a check reads them in a browser, in a temporary profile. The browser keeps no download and no crash report. The snapshot of such a check keeps only the six headers above and no cookie.
- Where
- Fly.io (the machines run in Frankfurt, Germany)
- How long
- While the check runs
- How it ends
- Deleted when the check closes its browser session. After a crash, deleted at the latest when the browser starts again.
Swiss commercial register (Zefix data on LINDAS)
- What
- The UID that a shop shows on its pages, in one lookup for each check. No data about you. The check keeps the answer: the company's name, legal form, address and register number.
- Where
- The Swiss federal administration (LINDAS), Switzerland
- How long
- The federal administration's own policy
- How it ends
- See the legal notice of the federal administration.
Disputes (Supabase)
- What
- Your email address, your message, the box "I represent this shop", the language of the form, and Daniel's resolution
- Where
- Zurich, Switzerland
- How long
- While the dispute is open, then 6 months
- How it ends
- Email address, message and resolution deleted by a daily job 6 months after the dispute closes. The dispute's id, shop, check, times, status, the box and the language stay.
Hidden results (Supabase)
- What
- The shop's domain, the time, and a short reason without personal data
- Where
- Zurich, Switzerland
- How long
- While the result is hidden
- How it ends
- Deleted when Daniel shows the result again.
Visit counts (Supabase)
- What
- For each day: how many page visits came from each source, such as google, chatgpt, a social site or a direct visit, and how many came from known crawlers. Only the day, the source's name and the number. No IP address, no cookie, no page address, no browser details.
- Where
- Zurich, Switzerland
- How long
- Without end
- How it ends
- Nothing to delete: the counts hold no personal data.
Supabase backups
- What
- Daily copies of the database: checks, requester hashes, disputes and hidden results. Snapshots are not in the backups.
- Where
- Zurich, Switzerland
- How long
- 7 days
- How it ends
- The oldest copy goes each day. A value that the daily job cleared stays in a backup for at most 7 more days.
Fly.io logs
- What
- Lines of the worker and the website. For each check: the domain, the check id, the time and a fixed error code. Also the daily counts of the clean-up and of the visit sources, and alert, health and request lines with fixed codes and page patterns. Next.js, the website's framework, can add its own error text, which can name a page address. No IP address, no email address, no message.
- Where
- Fly.io (the machines run in Frankfurt, Germany)
- How long
- 7 days
- How it ends
- Fly.io deletes the lines after 7 days.
Fly.io's edge
- What
- Your IP address, to deliver the page to you
- Where
- Fly.io
- How long
- Fly.io's own policy
- How it ends
- See Fly.io's privacy statement.
Lookup limit (the website's memory)
- What
- Your requester hash (see above) and how many lookups it made in the current minute, to allow 60 lookups a minute. Only in the memory of the website's machine, never on a disk.
- Where
- Fly.io (the machines run in Frankfurt, Germany)
- How long
- At most 2 minutes
- How it ends
- A sweep each minute deletes the counts of past minutes. A restart of the website deletes all.
IndexNow (api.indexnow.org)
- What
- The addresses of Cartlight's pages that search engines may show, once a day when they are new, changed or gone. A result page's address names its shop. No data about you.
- Where
- IndexNow passes them to the search engines that take part, such as Bing.
- How long
- The search engines' own policies
- How it ends
- The addresses are public pages. When a page may no longer be shown, Cartlight reports it as gone.
Your colour choice (your browser)
- What
- Light or Dark, when you pick one under "Colours" at the foot of each page. Your browser keeps it in its local storage. It is not a cookie, and it never reaches Cartlight.
- Where
- Your browser, on your device
- How long
- Until you pick Auto or clear the site data in your browser
- How it ends
- Pick Auto under "Colours", or clear the site data in your browser.
Resend
- What
- Emails to Daniel from fixed templates: alerts, and the notice of a new dispute with the shop's domain and the dispute's id. No visitor data, no shop owner's email address, no message, no error text.
- Where
- Resend, United States
- How long
- 30 days
- How it ends
- Resend deletes the email data after 30 days.
UptimeRobot
- What
- Only its own requests to cartlight.io, which check that the site answers
- Where
- UptimeRobot, Slovakia
- How long
- UptimeRobot's own policy
- How it ends
- See UptimeRobot's privacy policy.
Microsoft 365 (hello@
cartlight. io) - What
- Emails to hello@
cartlight. io, and Daniel's replies to disputes - Where
- Microsoft
- How long
- 6 months after the dispute closes
- How it ends
- Daniel deletes a dispute's emails 6 months after the dispute closes, by hand.
Daniel's alert inbox
- What
- Alert emails and dispute notices, without personal data
- Where
- Microsoft (Outlook.com)
- How long
- Daniel's choice
- How it ends
- Daniel deletes them.
Providers and data abroad
For each provider: the company, where the data lie, and what protects data that leave Switzerland.
Supabase
Supabase Pte. Ltd., Singapore. The data lie in Zurich, Switzerland. For access from abroad, Supabase's data processing addendum uses the EU standard contractual clauses with a Swiss addendum.
Fly.io
Fly.io, United States. The machines and their logs run in Frankfurt, Germany, a country with adequate data protection under Swiss law. The edge can deliver a page from another country. Fly.io is certified under the Swiss-U.S. Data Privacy Framework.
Resend
Plus Five Five, Inc., United States. Resend's data processing addendum sends data from Switzerland under the EU standard contractual clauses. Resend is certified under the EU-U.S. Data Privacy Framework, not under the Swiss one.
UptimeRobot
UptimeRobot s. r. o., Bratislava, Slovakia, a country with adequate data protection under Swiss law. It receives only its own requests to cartlight.io.
Microsoft
Microsoft Corporation, United States, for the mailbox hello@
cartlight. io and Daniel's alert inbox. Microsoft is certified under the Swiss- U. S. Data Privacy Framework. Apple
Apple, for the iCloud Drive copy of the labelled set on Daniel's Mac.
Why, and your rights
Cartlight uses these data for four purposes: to show each shop's result page, to limit how many checks one visitor can start, to answer disputes, and to test and improve the checks.
The legal basis is a legitimate interest: to warn shoppers before they buy, and to run the site safely. Under the Swiss Data Protection Act that is an overriding interest (Art. 31). For visitors from the EU, it is Article 6(1)(f) of the GDPR.
You can ask which data Cartlight keeps about you, and have them corrected or deleted. You can also object to their use. Write to hello@
If you think Cartlight handles your data wrongly, you can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC), or to a data protection authority in your EU country.