Policy draft — not effective

Privacy Policy

This document is not ready for public reliance or purchase decisions.

Is the privacy policy final, and what data boundaries matter?

This is an unapproved policy draft. Local Instagram task data, product account records, payment processing, support submissions and optional analytics are different flows. Final operator identity, retention commitments and legal approval are still required before public reliance.

Who operates the product

Draft only: the operating legal entity and formal privacy contact have not been approved. This page is not an effective privacy policy or a compliance certification.

Data categories and purposes

The implementation separates local Instagram task data from product identity, billing, and support messages. A user-created local backup is not uploaded as automatic cloud storage.

Recipients retention and rights

Support delivery and authentication/payment providers process different data. The operator must approve named recipients, retention, transfers, and rights-handling before publication.

Contact and policy updates

Use the support entry for a privacy question without sending credentials or target data. An effective date and policy-change procedure must be approved before the draft becomes public policy.

Official sources & scopeChrome: storage and cookies — Local extension storage and service workersChrome: extension service worker lifecycle — Worker termination and persistent state

These sources explain platform behavior. Product-specific scope and limits come from our implementation registry; they are not an endorsement by Instagram, Google, or Stripe.

Current Instagram settings and live source behavior are not yet verified. These links support only the topics named beside them.

Your next step

Contact support