Data Deletion

In short

Disconnecting a social account is self-service and takes effect immediately. When a connection is revoked, the stored access and refresh tokens are destroyed, the connection record and every publishing destination under it are deleted, and only a small record that the connection existed and was revoked — containing no credentials — is kept for accountability. If you would rather we did it, email us and we will.

1. Disconnect the account yourself (recommended)

An administrator with the social administration permission can do this at any time, without contacting us:

• Sign in to ZIJ.
• Go to Admin → Social.
• Find the platform card for the connection you want to remove (LinkedIn, Meta, or X).
• Choose Revoke on that connection, and confirm.

Revoke is the permanent verb and takes effect at once. If you only want to pause publishing while keeping the connection, use Disable instead — that is the reversible option and it leaves the stored authorisation in place.

Note that Facebook and Instagram are held under a single Meta connection. Revoking that connection removes both the Facebook Page and the linked Instagram account as publishing destinations.

2. What happens when you revoke

Immediately, and without any further action by you:

• The stored access token, refresh token, expiry and granted scopes for that connection are destroyed in the encrypted secret store. They are not archived, and they are not recoverable.
• The connection record is hard-deleted, along with every publishing destination beneath it and the per-destination grants and policy attached to them.
• A bounded revocation record is kept: the connection's identifier, the platform, the label, the names of the destinations that were removed, who authorised the connection, and who revoked it and when. It contains no tokens, no credentials and no content. These records are capped in number, oldest dropped first.
• An entry is written to the audit trail recording that the connection was revoked and by whom.

The revocation record and the audit entry exist so that an organisation can show who authorised publishing under its name and when that authority ended. They hold no credentials and cannot be used to access your social account.

3. Remove access from the platform as well

Revoking inside our platform destroys our copy of the authorisation. You can also withdraw the authorisation at the platform end, which we recommend if you want a record of removal on the platform itself. The exact menu wording changes as the platforms update their settings, but the location is:

• LinkedIn — Settings & Privacy → Data privacy → Other applications → Permitted services.
• Facebook — Settings & privacy → Settings → Apps and websites (or Business integrations).
• Instagram — managed through the linked Facebook Page and its business settings, in the same Apps and websites area.
• X — Settings and privacy → Security and account access → Apps and sessions → Connected apps.

4. Ask us to delete it for you

If you cannot reach the administration screen — for example you no longer have access to the workspace — email us at the address in the contact block below and we will carry out the deletion.

So we can identify the right records without asking for anything unnecessary, please include:

• the platform concerned (LinkedIn, Facebook, Instagram or X);
• the name of the page or account that was connected;
• the name of the organisation or workspace it was connected to; and
• whether you want only the social connection removed, or the user account as well.

We may need to verify that you are entitled to make the request before we act. We will respond to a verified request without undue delay and in any event within 30 days, and we will confirm in writing once the deletion is done.

5. Posts that were already published

Deleting a connection does not delete anything already published. A post that has gone out to LinkedIn, Facebook, Instagram or X is held by that platform under its own terms, and our platform has no ability to remove it. To take a published post down, delete it on the platform itself.

The record that the post was created, approved and published remains in the audit trail, as described above.

6. Deleting a user account or an entire workspace

An administrator can remove an individual user from the workspace, which ends that person's access and their permissions. Audit entries recording actions that person took remain, because removing them would defeat the purpose of an audit trail.

To delete an entire workspace and the data in it, contact us using the details below. Where Pro Max Gulf holds the data as a processor on behalf of a customer organisation, we act on that organisation's instruction, and we will refer a request that comes from an individual to them.

7. Related

Our Privacy Policy sets out the full picture: what we process, on whose behalf, the legal bases, retention, and your rights under the Saudi Personal Data Protection Law. Read the Privacy Policy.