Data Deletion Instructions

Last updated: August 23, 2026

This page serves as the Data Deletion Instructions URL required by the Meta Platform and supports the right to delete under the CCPA/CPRA and other applicable U.S. state privacy laws.

How to request deletion

Email midas@midasgrowth.online with the subject line Data Deletion Request
Include an identifier we can verify: the email address on file, the ad account ID, or your Meta user ID
You will receive a confirmation code within 2 business days
Deletion is completed within 30 calendar days
We send written confirmation once the deletion is complete

What we delete

Ad account data stored by us
Campaign metrics and reports tied to the identifier
Associated access tokens — revoked immediately
Contact records and request history

What we may retain, and why

Some information may be retained after a deletion request, as permitted by law:

Retained data	Reason	Period
Tax and accounting records	Federal and state recordkeeping obligations	7 years
Data subject to legal hold	Pending claim, dispute, or investigation	Until resolved
Deidentified or aggregated data	No longer identifies any individual	Indefinite
Security and fraud records	Detect and prevent malicious activity	As necessary

Any refusal to delete is communicated in writing, with a legitimate justification and the legal basis relied upon.

Checking the status of your request

Using the confirmation code we provide, email midas@midasgrowth.online at any time to check the status. We respond with a human-readable explanation of where the request stands, including a justification if any part of it was refused.

Data held by Meta

Data that Meta holds on its own servers is outside our control. To remove it, use the tools Meta provides:

Settings → Apps and Websites — remove the application
Accounts Center — manage or delete your account

Technical note: this page implements the Data Deletion Instructions URL option, which satisfies the Meta requirement. The alternative is a Data Deletion Request Callback URL that receives a signed_request via POST and returns {"url": "...", "confirmation_code": "..."}. The instructions option requires no server and is appropriate for internal-use applications.