Data Deletion Instructions

Mirylo respects your right to request deletion of personal information and data received through connected services, including Meta.

This page explains how to disconnect an integration and how to request deletion.

1Disconnecting and deleting are different

Disconnecting an integration stops future synchronization and removes or revokes the authorization used to access the connected account.

Deleting data is a separate request to remove previously stored information associated with the connection.

Disconnecting Meta does not automatically delete historical reporting records. If you want those records deleted, submit a deletion request using the instructions below.

2Option 1: Disconnect through MirylOS

If you have access to the applicable MirylOS account:

1. Sign in to MirylOS.
2. Open Settings.
3. Open Marketing.
4. Select Meta Ads.
5. Open the applicable connection.
6. Select Disconnect.
7. Confirm that you want to stop future synchronization.
8. If available, select Delete Meta Data to create a deletion request.

After disconnection, MirylOS will stop future synchronization for that connection.

3Option 2: Remove MirylOS through Meta

You may also remove the MirylOS application from your Facebook or Meta account settings.

The exact navigation may vary, but it is generally available under:

Facebook Settings → Apps and Websites → MirylOS → Remove

Removing the application revokes future access. It may also send Mirylo a deauthorization notification.

Removal from Meta does not by itself guarantee deletion of historical data already stored in MirylOS. Submit a deletion request if you want stored data removed.

4Option 3: Submit a deletion request by email

Email:

[email protected]

Use the subject:

Meta Data Deletion Request

Include:

• your name;
• your business name;
• the email associated with your MirylOS account;
• the applicable MirylOS location or account, if known;
• the Meta Business or Advertising Account ID, if known;
• whether you want only Meta data deleted or the entire MirylOS account deleted.

Do not send:

• your password;
• an access token;
• App Secret;
• payment-card information;
• government identification unless we specifically request an appropriate verification method.

5Verification

To protect customer data, we may need to verify:

• your identity;
• your authority to act for the business;
• your relationship to the applicable MirylOS account;
• the scope of the request.

Information collected for verification will be used only to process and protect the request.

If Mirylo processes the data on behalf of one of our customers, we may refer the request to that customer or obtain its instructions before deletion.

6What we delete for a verified Meta request

Depending on the scope of the request, deletion may include:

• Meta user and business identifiers associated with the connection;
• Meta advertising-account identifiers and metadata;
• campaign, ad-set, ad, form, and related identifiers and names;
• Meta advertising insights and reporting metrics;
• OAuth tokens and authorization records;
• Meta-specific mapping records;
• synchronization data associated with the Meta connection;
• Meta-derived records that can be linked to the requesting user or business.

We will also invalidate applicable caches and stop future synchronization.

7Information we may retain

We may retain limited information where reasonably necessary to:

• comply with law;
• maintain billing, tax, or accounting records;
• establish or defend legal claims;
• prevent fraud or abuse;
• document that a deletion request was completed;
• preserve security audit evidence.

Any retained information will be restricted to the permitted purpose and will not be used to continue the deleted integration.

Aggregated or de-identified information that cannot reasonably identify the requester may be retained.

8Processing timeline

We aim to:

• acknowledge a valid request within 10 business days;
• complete deletion from active systems within 30 days;
• remove remaining copies through backup rotation within 90 days.

Where applicable law permits an extension, we will notify the requester.

These timelines must be supported by actual MirylOS deletion and backup processes before publication.

9Confirmation

When a deletion request is created, we may provide:

• a confirmation code;
• a status URL;
• an email confirmation.

Keep the confirmation code for your records. A public status page will not display passwords, tokens, personal information, or private business data.

10Meta automated deletion requests

Where Meta sends MirylOS a signed data-deletion request, our system will verify the request, create a deletion case, and return a confirmation code and status URL.

Example response format:

{
  "url": "https://mirylo.com/data-deletion/status?code=CONFIRMATION_CODE",
  "confirmation_code": "CONFIRMATION_CODE"
}

11Questions

For questions about deletion or privacy: