Privacy · Chrome companion

Last updated · 2026-08-22

Privacy policy — evow Chrome companion

Publisher : evow (Jean-Michel BONI · jmbonipro@gmail.com). Extension : evow — Profiled fashion navigation.

What the extension stores

The extension stores your profile bundle in chrome.storage.local on your device:

{
  display_name: string,
  gender: 'women' | 'men' | 'unisex',
  measurements: { chest_cm, waist_cm, hips_cm, height_cm },
  sizes: { top, bottom, shoe },
  source: 'evow.app' | 'demo'
}

It also stores your household profile list, mirror preference, three separate consent choices and dedicated companion access/refresh credentials. It never stores your evow website session cookie. No third-party analytics or advertising SDK is bundled.

Your three optional choices

  • Personal fit history — saves products and fit interactions in your evow account.
  • Catalogue contribution — shares public product facts such as URL, price and sizes in stock.
  • Aggregate learning — permits de-identified fit signals to improve aggregate models.

Each purpose is off by default, can be accepted separately and can be withdrawn independently.

Where the data comes from

  1. Demo personas (source: 'demo') — fictional personas hardcoded in the extension (Léa, Sofia, Mei, Marcus, Alex). Picking one stores it locally. Nothing is sent to evow servers.
  2. Your real evow profile (source: 'evow.app') — when you visit evow.app/extension/auth while signed in, the page sends your stored evow profile to the extension via window.postMessage. This only happens after you click the “Send my profile to the Chrome companion” button.

Where the data goes

When the mirror is active on a partner brand site (Sézane, Zara, COS, etc.):

  1. The extension reads the public DOM only — never cart, account, or form inputs.
  2. It sends an HTTPS POST to fit-engine-jvcpf4qg3a-ew.a.run.app/predict with brand_slug, gender, category and your measurements. Your display name and email are never sent.
  3. The fit-engine returns a per-size score (0.0–1.0). The extension uses it to badge the right products on the brand page.

The fit-engine runs on Google Cloud Run in europe-west1, operated by evow. No persistent log of measurements is kept beyond standard 30-day Cloud Run request logs (truncated to the endpoint name + status code).

What we never collect

  • Your complete browser history or data from unsupported sites
  • Brand-account contents, passwords or payment information
  • Form inputs, passwords, credit card numbers
  • Email addresses or contact information (beyond what you typed into evow yourself)
  • Any data from non-partner sites

Data deletion

  • Local storage — click the extension icon → Sign out at the bottom. This clears chrome.storage.local immediately.
  • Server-side evow profile — sign in to evow.app → Settings → Delete my account. Wipes member + household_profile + all related rows per GDPR Article 17. Confirmation by email within 30 days.

Third parties

  • No third-party fonts, scripts, analytics, or ads loaded by the extension.
  • One third-party endpoint : evow's own fit-engine on Google Cloud.
  • No Facebook Pixel, no Google Analytics, no Sentry, no similar SDK.

Legal basis (GDPR)

Profile synchronisation and local fit navigation provide the service you request. Personal history, catalogue contribution and aggregate learning are based on three separate, revocable opt-ins. Refusing them does not prevent local fit navigation.

Contact

Privacy questions, GDPR/CCPA requests, data export : jmbonipro@gmail.com · response within 5 business days.

This policy may evolve. Material changes will be announced via the extension's update changelog on the Chrome Web Store and on this page.