How Teardown handles data in the current beta.

1. Product usage data

Teardown may record basic extension usage events such as popup opens, analysis starts, analysis successes, and analysis failures. These events are tied to an anonymous install ID, not a required user account.

Teardown may also keep a short recent history of analyzed page URLs and timestamps in browser storage so the beta can show recent events and avoid repeating work unnecessarily.

2. Page analysis data

When you analyze a product page, the extension reads visible page information such as page URL, title, headings, pricing clues, and other public page text needed to generate the teardown.

When configured for hosted analysis, the extension may send extracted page signals and a heuristic draft to the shared backend or model provider in order to generate the teardown result.

3. Optional provider credentials

If you manually enter a shared backend token or Gemini API key in the extension settings, Teardown stores that value locally in your browser so the extension can make the requested analysis call. These values are not required for the public beta flow.

4. Payment data

If you purchase the Founding Member offer, payment is handled by the payment provider. Teardown uses the payment email only to recognize founder status and support related follow-up.

5. Storage

The extension may store local cache, settings, optional provider credentials, anonymous install ID, and recent usage events in browser storage to support the beta experience.

6. Contact

Support email: support@teardown.cc

Operator: Jiaqi Li