AdWatch360

Privacy Policy

Last updated: February 2026 · Effective immediately

AdWatch360 is an internal tool for launching and managing Meta (Facebook) ad campaigns in bulk. This policy explains what data is handled, where it is stored, and how it is used.

1. Overview

AdWatch360 ("the Tool") enables users to connect their Meta Ad accounts via the Meta Marketing API, configure campaigns, and launch ads across multiple accounts simultaneously. The Tool is operated as a private, self-hosted web application and is not available to the general public.

2. Information We Handle

The Tool handles the following categories of data:

Meta Access Tokens — stored in your browser's localStorage to authenticate API calls. Tokens are never sent to any third-party server other than Meta's Graph API.
App credentials — your Meta App ID and App Secret, stored in localStorage on your device only.
Creative assets metadata — when you upload images or videos, Meta returns a hash/ID for the asset. This metadata (hash, URL, name, size) is stored in a local JSON file on the server (server/creatives.json) and in browser localStorage as a cache.
Campaign configuration — ad set and ad settings you configure in the UI are held in browser memory only and are not persisted between sessions.

3. How We Use Your Information

All data handled by AdWatch360 is used exclusively to:

Authenticate requests to the Meta Marketing API on your behalf.
Create campaigns, ad sets, ads, and creatives in your Meta Ad accounts.
Store and retrieve your creative library across sessions.

We do not sell, share, or transmit your data to any third party other than Meta's Graph API (graph.facebook.com) for the purpose of executing the actions you request.

4. Data Storage

Browser localStorage — access tokens, app credentials, and a cache of creative metadata are stored locally in your browser. This data never leaves your device except when making API calls to Meta.
Server-side JSON file — creative hub metadata is persisted in server/creatives.json on the machine running the AdWatch360 server. This file is not transmitted externally.
Meta's servers — uploaded images and videos are stored on Meta's ad infrastructure under your ad account. AdWatch360 only stores the resulting hash/ID references.

5. Third-Party Services

AdWatch360 communicates exclusively with the Meta Graph API (v19.0) at https://graph.facebook.com. Your use of Meta's API is governed by Meta's Terms of Service and Data Policy.

No analytics, tracking scripts, advertising SDKs, or other third-party services are loaded by this application.

6. Data Retention

Access tokens and app credentials remain in localStorage until you manually clear them via the Token Settings panel or clear your browser data. Creative hub metadata persists in server/creatives.json until you delete an asset from the Creative Library.

7. Security

AdWatch360 is designed to run as a private, self-hosted tool. You are responsible for securing access to the server and browser where the tool runs. We recommend:

Running the tool only on trusted, secured machines.
Using short-lived or appropriately scoped Meta access tokens.
Restricting network access to the server port (default: 3001).

8. Children's Privacy

AdWatch360 is a professional tool intended for use by adults managing business advertising accounts. It is not directed at children under 13 and does not knowingly collect data from minors.

9. Changes to This Policy

This privacy policy may be updated from time to time. The "Last updated" date at the top of this page will reflect any changes. Continued use of the tool after changes constitutes acceptance of the updated policy.

10. Contact

If you have questions about this privacy policy or how AdWatch360 handles data, please visit adwatch360.com or contact the tool administrator directly.