ChipChip ChipChip

Legal

Privacy Policy for ChipChip

Effective date: 2026-05-28 Last updated: 2026-07-23

ChipChip is a Chrome extension that helps you schedule and send messages through WhatsApp Web. This policy describes what data the extension accesses, what stays on your device, and what is sent to our servers or third-party services when you use optional features.

Related: Terms of Service / User Agreement

Summary

Data Where it stays Sent externally?
Scheduled messages, attachments, tags, saved prompts, recipient lists (phones/names) Your browser (IndexedDB) No — local only; not uploaded as a backup
Chat notes, quick replies, composer history, UI prefs, redacted send logs Your browser (chrome.storage.local) No (unless you use a separate export/download)
License key + purchase / billing email Cached locally, encrypted with a per-profile device DEK (AES-GCM) Yes — sent to Cloud Function getSubscription to verify your purchase; not sold to third parties
Chrome Identity email (optional) Cached locally if Chrome provides it Used for subscription identity / UI; not required for basic scheduling
Premium entitlement (JWT) Encrypted locally; short-lived on the server (~2 hours default) Yes — issued and verified via our backend
Device id (ccd_…) Local storage Yes — device-binding header on subscription requests
AliExpress / Shopee API keys (optional) Local storage, DEK-encrypted Yes — only to our Cloud Functions for affiliate APIs; not logged in full
Gemini API key (BYOK) Local storage, DEK-encrypted Yes — directly from your browser to Google; not stored on our servers
AI product-copy prompts (optional) Built in the extension Yes — to our Cloud Functions (e.g. generateProductDescription), which may call OpenAI
Public Google Sheets (optional import) Sheet ids → Cloud Functions; cells returned to client; phones/names may be saved locally if you import Yes — sheet id to CF; cells may contain PII if your sheet does
B2B credential / task payloads (optional) Transient server task docs Yes — to our Cloud Functions; task docs expire after about 48 hours
PayPal subscription events PayPal → our webhook Processed on Google Cloud; updates subscription status
Firebase App Check token Memory / offscreen helper; not persisted in storage Yes — with Cloud Function requests that require App Check
Ops / Monitor diagnostics Local queue on device Owner build only — numeric metrics (no message text, phones, or chat ids) may be sent to reportExtensionOpsTelemetry. The standard Chrome Web Store (PROD) build does not upload this telemetry

We do not sell your personal data. We do not use advertising or analytics SDKs inside the extension.

Bring Your Own Key (BYOK)

  • You may optionally provide your own Google Gemini API key for certain free-tier AI flows.
  • The key is saved only in your browser, encrypted on disk with a per-profile device encryption key (DEK) (AES-GCM).
  • BYOK requests go directly from your browser to Google (API key in the HTTP header, never in the URL).
  • ChipChip does not upload, store, or log your BYOK key on our servers.
  • You can delete the key from the Integrations panel or by clearing extension data.

Premium product-copy generation through our Cloud Functions uses our OpenAI integration and does not require your Gemini key.

Data we access locally

Stored on your device (not as a cloud backup of your scheduler):

  • IndexedDB: message text, schedules, attachments, tags, tag↔group assignments, saved prompts, and recipient lists (including display phone numbers and names you save).
  • chrome.storage.local: license/entitlement material (encrypted), optional Chrome Identity email, chat notes and quick replies keyed by WhatsApp chat/group id, composer history, UI preferences, and send logs with contact phones redacted (last digits only).
  • Group and contact identifiers visible on WhatsApp Web while the extension runs (to pick recipients and send scheduled messages).

Clearing the Chrome profile or extension storage removes local data, including the device DEK (encrypted secrets become unreadable).

Encryption at rest (device DEK)

Sensitive values in extension storage are protected with a per-Chrome-profile AES-GCM data encryption key (DEK) managed by the extension (wrapped for that profile / extension id).

Typically encrypted this way: license key, billing email, entitlement JWT, and optional integration secrets you choose to persist (for example affiliate keys, Gemini BYOK, or Telegram/Facebook tokens when persistence is enabled).

Data sent to ChipChip servers (Google Cloud / Firebase)

When you use subscription, Sheets import, B2B, or optional premium / commerce / AI features, the extension communicates with Firebase and Cloud Functions on Google Cloud (chipchip-a3d33), including:

  • Subscription (getSubscription): license key you paste, billing email, device id, and App Check; returns an entitlement JWT when active.
  • Entitlement token: a signed JWT proving access for gated endpoints (default short TTL).
  • Public Google Sheets: spreadsheet / sheet identifiers; the server returns a cell grid that may contain phones or names if your sheet contains them. Values you import may then be stored in local IndexedDB recipient lists.
  • B2B tasks (optional): task type and credentials for a short-lived server job; related task documents expire after about 48 hours.
  • Product description / affiliate / hot-image features (where enabled): product context, URLs, or credentials as needed; secrets are redacted in server logs where applicable.
  • Ops telemetry (reportExtensionOpsTelemetry): owner build only (see below).

We use HTTPS for these requests. Server operational logs are limited to metadata where designed (status codes, lengths, redacted identifiers)—not full API keys or full message bodies in those paths.

Owner Monitor build (optional internal distribution): When compose / in-chat UI health checks cross configured thresholds, the owner build may upload a small batch of numeric counters only to reportExtensionOpsTelemetry (Cloud Logging). This payload does not include message text, contact names, phone numbers, or chat identifiers. The standard Chrome Web Store (PROD) build does not enqueue or flush this telemetry.

Third-party services you may enable

  • Google Gemini (BYOK): key stays on your device and talks to Google directly.
  • Telegram / Facebook mirroring (optional): tokens and message text you choose to mirror may be sent to those APIs. Tokens are DEK-encrypted when persisted, or kept in tab session storage when not persisted.
  • PayPal: subscription payments and webhooks; we do not receive your full card details.
  • OpenAI (server-side): only when you use product-copy generation through our Cloud Functions.

What we do not do

  • We do not sell or rent your data to data brokers.
  • We do not inject third-party advertising or tracking pixels in the extension UI.
  • We do not upload your IndexedDB scheduler archive (messages, attachments, recipient lists) as a cloud backup.
  • The standard store build does not request host permissions beyond WhatsApp Web (https://web.whatsapp.com/*) for core messaging. Optional owner / integration builds may add hosts required for those features.

Chrome extension permission: offscreen

ChipChip requests the Chrome offscreen permission to run a hidden extension page that is never shown to you.

  • Why: To obtain a short-lived Firebase App Check token via https://chipchip-a3d33.web.app. Google reCAPTCHA Enterprise may run as part of this process.
  • When: Only when the extension calls ChipChip cloud services (subscription, premium AI, hot-products APIs, etc.).
  • What is sent: A technical App Check token in the X-Firebase-AppCheck header to our Cloud Functions.
  • What is not collected: The offscreen page does not read WhatsApp messages, browsing history on other websites, or screen content.

App Check tokens are kept in memory for use and are not intended to be persisted in extension storage.

Security practices

  • Production builds limit verbose console output; sensitive fields are redacted in client and server logs.
  • PayPal webhooks are verified with PayPal’s signature API when verification is enabled in production.
  • AI-generated HTML is sanitized before DOM insertion.
  • Optional integration secrets remain in your browser profile under the device DEK.

Limitation: Data in the browser Network tab or DevTools may still show request bodies while you debug—that is expected browser behavior, not server logging.

Data retention

On your device

  • Failed / missed / cancelled scheduled messages are automatically pruned from IndexedDB after about 48 hours.
  • Pending / sending / sent schedules, tags, prompts, recipient lists, chat notes, and similar local data remain until you delete them or uninstall / clear the extension.
  • Exports you download (CSV/XLSX) stay where you save them; export helpers do not upload those files to our servers.

On our servers

  • Subscription / license records are retained as needed for billing, support, and abuse prevention.
  • Short-lived B2B task documents expire after about 48 hours.
  • Entitlement JWTs are short-lived (about 2 hours by default).
  • Other operational collections (rate limits, webhook deduplication, caches) expire on backend schedules.
  • Owner ops telemetry batches are handled as log metrics; they are not designed as a durable archive of chat content.

There is no single in-extension “delete all my cloud data” API. Revoking a license affects server-side seats/devices; it does not by itself wipe your local notes, schedules, or IndexedDB.

Your choices

  • You can use core scheduling without enabling AliExpress, Shopee, Gemini BYOK, Sheets import, B2B tasks, or social mirroring.
  • You can remove integration keys and clear extension storage by uninstalling or clearing extension data in Chrome.
  • Premium / gated cloud features require an active license / entitlement as applicable.

Children

ChipChip is not directed at children under 13. We do not knowingly collect children’s data.

Changes

We may update this policy. The “Last updated” date at the top will change when we do. Continued use after an update means you accept the revised policy.

Contact

Questions or privacy requests: support@romsyn.com

Disclaimer

ChipChip is an independent product and is not affiliated with, endorsed by, or sponsored by WhatsApp, Meta, AliExpress, Google, OpenAI, PayPal, Telegram, or Facebook.

Terms of Service

Use of ChipChip is also subject to our Terms of Service / User Agreement.