GadgetGaugeiPhone Deal CheckBeta

GadgetGauge · Beta

Privacy

GadgetGauge is built around not needing your — or the seller's — personal information in the first place.

No accounts, no seller identity

There is no login and no user account. GadgetGauge does not need the seller's identity to help you evaluate a listing, and it does not intentionally request, store, log, analyze, or place in a URL: IMEI, serial number, seller name, phone number, exact meeting address, marketplace login, payment credentials, or unnecessary location information.

Listing text and URLs stay on your device, briefly

An optional listing URL or pasted listing text is a convenience input handled entirely in your browser. It is never sent to the /api/check request, never stored, and never included in results, analytics, server logs, result URLs, shared summaries, or outcome submissions. If a client-side suggestion is drawn from it (asking price, model, or storage), only that structured, editable suggestion is kept — the raw text is discarded from application state as soon as practical after you confirm the fields.

If pasted text appears to contain an email address, phone number, street address, or other long identifier, GadgetGauge warns you and asks you to remove it before continuing.

Results are stored locally, not on a server

A result and its checklist completion state are saved only in your browser's local storage, tied to that specific browser and device. GadgetGauge does not operate a server-side account database of your results. A copied result link works only on the browser that created it — if a result cannot be found locally, GadgetGauge tells you so and offers to start a new check.

The personalized Deal Check beta

The only place GadgetGauge ever asks for an email address is the optional, explicitly-consented personalized Deal Check request. That email is never placed in local storage, analytics, result URLs, logs, or outcome records. When no delivery endpoint is configured, the request is validated but not transmitted or retained anywhere, and the interface says so plainly.

The outcome form

The anonymous outcome form (did you buy it, pass, or are still deciding, plus a few structured questions) never accepts a name, email, phone number, listing URL, seller information, IMEI, serial number, or meeting address — those fields are rejected outright. Your response is saved on this device only after you explicitly consent; this is a local beta simulation, not server-side storage.

Analytics

Analytics events use a fixed allow-list of non-personal properties only — things like the exact supported model, storage, verdict, confidence, counts of unknown answers or triggered risk rules, data snapshot ID, and rule-set version. Analytics never contains raw listing text, a listing URL, an email, a name, a phone number, a street address, an IMEI, a serial number, seller identity, meeting location, marketplace account information, or any free-text input you typed.

What GadgetGauge cannot verify

GadgetGauge cannot authenticate a phone, verify ownership, verify stolen status, confirm that a screenshot is current or belongs to the listed phone, guarantee part authenticity, diagnose hidden damage, validate the seller, or guarantee meeting safety. Treat every result as decision support, not a safety guarantee.