DeepDive Media · Legal

Data Deletion Instructions

Effective Date: May 15, 2026

This page describes how a user, a Business Manager owner, or Meta's automated systems can request deletion of data the DeepDiveTech Pilot holds about them or their connected Business Managers.

We honour every valid deletion request and complete it within thirty (30) days of receipt, often within minutes for in-product self-service deletions.

1.Self-service deletion (fastest)

If you have access to the dashboard, this is the quickest way and completes within minutes:

Sign in at https://pilot.deepdivetech.app.
Open /integrations.
Click Remove next to each Business Manager you want to disconnect. This action immediately:
- Revokes the stored System User access token
- Deletes the BM's rows from our daily store and BigQuery warehouse
- Clears any cached overview snapshots
To delete your user account itself, ask your workspace administrator to remove you from /users-management, or email us (see below).

2.Email request

If you do not have dashboard access, or you want a complete account-level deletion (including audit logs, role records, and any historical aggregates):

Send an email from the account email address to director@deepdivemedia.in
Subject line: Data Deletion Request
Include any Business Manager ID(s) or user email(s) you want deleted

We will reply with a confirmation reference within two (2) business days and complete the deletion within thirty (30) days.

3.Revoke at the source (Meta)

You can also revoke the app's access to your Business Manager directly on Meta's side. This stops any further data from flowing to us; we will detect the revocation on the next sync and delete the corresponding records.

Visit Facebook Settings → Business Integrations
Find "DeepDiveTech Pilot" and click Remove

4.Meta automated deletion callback

For Meta's App Review and the platform's automated data-deletion flow, this app implements the required callback endpoint:

Method: POST
Endpoint: https://pilot.deepdivetech.app/api/meta/data-deletion
Body: Signed request from Meta (signed_request parameter).
Response: JSON with url (the status URL on our domain where the user can verify the request) and confirmation_code (unique reference for the request).

When Meta sends a deletion callback, we verify the signed request against our App Secret, identify the user, queue deletion of every record linked to that user across the daily store, BigQuery warehouse, integration store, and overview cache. Users can confirm completion by visiting the returned status URL with their confirmation code.

5.What gets deleted

User profile record (name, email, role, profile picture URL)
Sign-in audit logs older than what we're legally required to retain
System User and OAuth access tokens for the connected BMs
Per-day insights rows in the BigQuery insights_daily table for the affected accounts
Entity-metadata rows (accounts, campaigns, ad sets, ads, creatives) for the affected BMs in BigQuery
Cached overview snapshots in the Google Cloud Storage state bucket

Aggregated, fully-anonymised metrics that cannot be re-linked to a user or BM may be retained for service-improvement purposes.

6.What we cannot delete

A deletion request from us does not affect:

Records held by Meta itself — please use Meta's own deletion process for those
Anonymised, aggregate audit metrics that cannot be tied to a user or BM
Records we are legally compelled to retain (tax, fraud, regulatory)

7.Timeline

Self-service deletion (Remove BM): Token + warehouse rows deleted within minutes.
Email request: Acknowledgement within two (2) business days. Full deletion within thirty (30) days.
Meta automated callback: Acknowledged immediately with a confirmation code. Records fully removed within thirty (30) days.

8.Contact

Operator: DeepDive Media
Email: director@deepdivemedia.in
Subject line: Data Deletion Request