FlerapiiFlerapii
Home
Getting Started
Changelog
Frequently Asked Questions
  • Supported Tools
  • Supported Sites
  • Cloudflare Helper
  • Quick Export
  • Auto Refresh
  • Auto Check-in
  • Auto Detect
  • Redemption Assistant
  • WebDAV Sync
  • Data Management
  • New API Model Sync
  • New API Channel Mgmt
  • Octopus Channel Mgmt
  • CLIProxyAPI Integration
  • Model Redirect
  • Sorting Priority
  • Permissions
  • Privacy
  • Chrome Store Submission
  • Store Data Mapping
Home
Getting Started
Changelog
Frequently Asked Questions
  • Supported Tools
  • Supported Sites
  • Cloudflare Helper
  • Quick Export
  • Auto Refresh
  • Auto Check-in
  • Auto Detect
  • Redemption Assistant
  • WebDAV Sync
  • Data Management
  • New API Model Sync
  • New API Channel Mgmt
  • Octopus Channel Mgmt
  • CLIProxyAPI Integration
  • Model Redirect
  • Sorting Priority
  • Permissions
  • Privacy
  • Chrome Store Submission
  • Store Data Mapping
  • Chrome Web Store Data Usage Mapping

Chrome Web Store Data Usage Mapping

This page maps Flerapii behavior to Chrome Web Store data-usage disclosures so listing answers stay consistent with implementation.

Purpose

  • Prevent mismatches between dashboard answers and real extension behavior.
  • Keep privacy policy, in-product disclosures, and store listing aligned.
  • Provide reviewer-friendly evidence for internal audits and appeal packets.

Data Handling Summary

TopicActual behavior
Default storageLocal-first: data is stored in browser extension storage by default.
External transmissionOnly when user explicitly configures/uses related features (relay endpoint calls, WebDAV backup/sync, optional verification/protection flows).
First-party telemetryNot used.
Advertising trackersNot used.
Data saleNot used.

Disclosure Mapping (What to Confirm in Dashboard)

Disclosure areaWhat must be true in listing answers
Privacy policy URLMust exactly match: https://flerapii.riteshrana.engineer/privacy.html
Data collection/use narrativeMust state local-first default and user-configured external transmissions only.
Sharing/transfersMust not imply third-party sharing beyond user-directed endpoint interactions.
Security wordingMust avoid absolute claims like "never transmitted" or "fully offline" for all scenarios.

Permission/Behavior Evidence Pointers

  • Manifest and permission scope: wxt.config.ts
  • Privacy policy source of truth: PRIVACY.md
  • Store submission process: docs/docs/chrome-web-store-submission.md
  • Operational checklist: privacy/chrome-web-store-privacy-checklist.md

Red-Flag Claims to Avoid

  • "No network usage" (incorrect when optional integrations are used)
  • "Never uploads any data under any condition" (incorrect)
  • "Runs fully offline in all modes" (incorrect)

Use precise wording:

  • "Local-first by default"
  • "External traffic occurs only for features you configure/use"

Pre-Submit Validation

  1. Re-read current CWS questionnaire answers.
  2. Compare each answer against this mapping and wxt.config.ts.
  3. Confirm policy URL, listing text, and in-app privacy notice are consistent.
  4. Capture screenshots of final listing answers for audit trail.

Related Documentation

  • Chrome Web Store Submission Guide
  • Privacy Policy
  • Permission Management
Last Updated: 5/25/26, 5:44 PM
Contributors: ambicuity