Data Deletion Instructions
How to disconnect Meta assets immediately or request deletion of information associated with a HitOS account or creator workspace.
Effective: August 5, 2026
Disconnect a provider immediately
- Sign in to HitOS and open the relevant creator.
- Open Connections.
- Find the individual Instagram, Ad Account, Facebook Page, Pixel/Dataset, or WhatsApp connection.
- Select Disconnect and confirm.
Disconnecting ends operational access for that authorization and destroys its stored provider credential. Other independently authorized assets remain connected.
Request deletion
Email contact@byafluence.com from the address associated with your HitOS account. Use the subject “HitOS data deletion request” and include:
- your account email;
- the agency or creator workspace name;
- which provider account or asset should be deleted, if the request is limited; and
- whether you request disconnection, deletion of imported provider data, or deletion of the HitOS account.
We will verify the requester’s identity and authority, acknowledge the request, and respond within the period required by applicable law. Do not send access tokens, App Secrets, passwords, or government identification unless our privacy team requests a secure verification method.
What the process covers
Once verified, the request can remove provider credentials, creator bindings, imported channel content, messages, leads, advertising projections, and other personal information within scope. We will also instruct applicable processors where required.
Information we may retain
We may retain limited records when required for security, fraud prevention, legal obligations, dispute resolution, or evidence of consent and revocation. Retained records are restricted from normal product use and deleted when the applicable obligation ends.
Meta users
This page is the public deletion-instructions URL for Afluence’s Meta integrations. Removing Afluence from Facebook or Instagram does not always delete information already imported under a prior authorization; use the process above so we can identify and remove the applicable HitOS records.