Privacy Policy

Effective: May 2026

CertiWatt is built around the principle that we should not need to know who you are to give you a good verdict. This page describes what actually happens with your data today — not what some bigger version of the product might collect later. If we ever start collecting more, this page will be updated first.

What our server receives

When you submit a verification (or use a feature backed by our server), the following data reaches us. Everything else stays on your device.

Power-bank model OR capacity + voltage

Used to compute the verdict. Not personal in isolation. Not associated with an account, because there is no account.

Trip route (origin / destination / airline IATA)

Used to look up the applicable rules. Not personal in isolation.

Anonymous activity trace

After a successful verification, we may store a short-lived anonymous activity record for the homepage activity panel: model ID or label, Wh value, origin, destination, airline, verdict type, and a timestamp bucket. We do not store serial numbers, IP addresses, emails, names, booking identifiers, or user-agent fingerprints in this activity record. Records expire automatically.

Language hint

Used so the verdict explanation is in the right language.

Serial number (optional, you decide)

Currently passed through the verifier and used only to compare against active recall lists. The raw value is not written to any database, log file, or analytics system. We may add hashing in a future version; today it simply is not stored.

IP address

Held in memory by an in-process rate limiter so abuse can be blocked. Not written to disk, not joined with anything else, not sold.

Subscriber email (only if you subscribe)

If — and only if — you submit the rule-update subscription form, we store the email address you typed, the language you used, and a timestamp. Used solely to send rule-change notices. You can unsubscribe at any time by emailing privacy@certiwatt.app.

Partner API request metadata (if applicable)

If a partner uses the verifier API, CertiWatt may receive the same verdict inputs above plus API authentication metadata, timestamp, request status, and limited security/debug logs. Partners should not send booking IDs, names, email addresses, loyalty numbers, or other direct identifiers unless a written agreement explicitly allows it.

Aggregated page views (analytics.clovertechnology.co)

An operator-controlled analytics instance hosted on a separate domain we run. Records the page URL, timestamp, referrer, browser family, and country (derived from CDN headers). No cookies. No device fingerprinting. No individual identifiers. The script loads from that domain and reports page views back to it; the data never reaches a third-party advertiser or analytics network and is never joined with the verifier inputs above.

What stays on your device

Several features use your browser's local storage so the experience feels faster. None of this data is transmitted to us. Clearing your browser data deletes all of it. You can audit it yourself in DevTools → Application → Storage.

Recently verified devices

localStorage key cw-recents. Lets you re-verify a previous power bank with one click.

Recent trips

localStorage key cw-trips. Pre-fills the route picker with routes you have used.

Device label photo (memory aid)

sessionStorage key cw-device-photo. Stays only in the current tab and is cleared automatically when you close the tab.

OCR text-recognition workload

Runs entirely inside your browser via WebAssembly. The photo bytes never leave your device.

Boarding-pass barcode scan

Decoded in the browser. Neither the barcode bytes nor the camera frames are transmitted.

Cookies we set

We set one cookie. That is the entire list.

certiwatt-lang

Stores your language preference (en / zh-CN / ko / ja). Not used for tracking.

What we explicitly do not do

• No user accounts, no passwords, no profile pages — there is nothing to log into.
• No advertising trackers, no third-party analytics scripts, no marketing pixels on the verdict surface.
• No device fingerprinting, browser fingerprinting, or cross-site identification.
• No selling or licensing of any data we do receive.
• No marketing email — the only email we ever send is the rule-update digest you explicitly subscribed to.
• No request logging of verify payloads with personally-tied identifiers.

B2B partner integrations

If a partner (airline, OTA, corporate-travel platform) integrates the verifier API into their own product, the partner is responsible for its own user interface, privacy notice, user identifiers, booking context, support records, and analytics. CertiWatt receives only the fields sent to our API and the operational metadata needed to run, secure, debug, and audit the API. Partners should not send personal identifiers unless a written agreement explicitly covers that use.

Your rights

Anonymous verifications have no associated personal data — there is nothing for us to delete because there is nothing tied to you. If you have subscribed to rule updates, you can request deletion of that subscription record at any time. Email privacy@certiwatt.app and we will respond within thirty days. Depending on your region you may have additional rights under GDPR, UK-GDPR, CCPA / CPRA, PIPA (Korea), APPI (Japan), PDPA (Singapore / Thailand), or PIPL — those rights apply to whatever data we actually hold for you, which today is either nothing or your subscription record.

Where data is processed

The application runs on cloud infrastructure in the regions listed in the runbook. Verification requests are processed in-region where possible. We do not transfer data across borders for any purpose other than serving the request you made.

This page describes what CertiWatt actually does today. If you spot anything here that does not match the application, please email privacy@certiwatt.app — we will treat it as a bug. When the Service changes the way it handles data, this page is updated before the change ships.