Fyncta Meta Data Deletion Instructions

1. What this page is for

This page explains how a Fyncta member can request deletion of Fyncta Cloud account metadata and Meta-related setup metadata. It is provided for Meta app settings and Meta data deletion instructions.

2. What Fyncta Cloud may hold

Fyncta Cloud may hold account and control-plane metadata such as your name, email address, sign-in provider, workspace metadata, device registration metadata, session metadata, admin audit metadata, and provider configuration posture.

Fyncta Cloud is not designed to be the default storage location for your local documents, prompts, model outputs, local vector indexes, connector refresh tokens, or private business records.

3. Meta-connected data

If you connect a Meta-backed provider such as WhatsApp Business or Instagram DM in Fyncta Desktop, member-owned provider tokens and business-account credentials are intended to stay in the Fyncta Local Engine connector vault by default. Disconnecting or deleting local connector data should be handled from Fyncta Desktop when the matching connector package supports that provider.

4. How to request deletion

To request deletion, contact Fyncta through the support or account channels provided with your Fyncta membership and include the email address used for your Fyncta account plus the Meta product involved, such as WhatsApp Business or Instagram.

Fyncta will review the request, verify account ownership when needed, and delete or de-identify eligible Fyncta Cloud metadata unless retention is required for security, fraud prevention, legal obligations, audit integrity, or legitimate operational records.

5. Local data

Data stored on your Fyncta Desktop computer, including local connector vault entries, local documents, local indexes, prompts, model outputs, and private business records, is controlled from that device. Fyncta Cloud cannot delete local-only data unless the Desktop app or Local Engine provides a reviewed local deletion workflow for that data.

6. Timing

Fyncta aims to handle deletion requests in a reasonable time after verifying the request. Some metadata may remain in backups, security logs, or audit records for a limited period where required to protect the service and comply with applicable obligations.