Deletion of Userdata Instructions

1. Disconnect a social-media channel in Postiz

1. Sign in to Postiz with your authorized company account.
2. Open the area used to manage connected channels, integrations, or social accounts.
3. Select the account or channel concerned.
4. Use the available disconnect, remove, or delete-connection action and confirm it. The wording may differ between Postiz versions and platforms.
5. Confirm that the channel is no longer connected and that no posts remain scheduled for it.

Disconnecting prevents normal future use of that connection. For complete revocation, also remove the authorization directly at the third-party platform. If you cannot sign in or locate the controls, email hermine@the-corona.net.

2. Revoke Postiz access at the third-party platform

Platform labels change over time. Look for connected apps, authorized applications, business integrations, or account permissions.

Meta, Facebook, and Instagram

• In Facebook, review Business Integrations and Apps and Websites, locate the integration used for Postiz, and remove it.
• In Instagram or Meta Accounts Center, review apps, websites, permissions, and business integrations and remove the applicable authorization.
• For a Facebook Page or Instagram professional account connected through Meta Business, an authorized business administrator may also need to remove assigned app or asset permissions in Meta Business settings.

Starting points: Facebook Business Integrations and Facebook Apps and Websites.

Google and YouTube

1. Open Google Account third-party access.
2. Find the application or connection used by Postiz.
3. Remove its access to the Google or YouTube account.

LinkedIn

Review LinkedIn permitted services, locate the connection used by Postiz, and revoke it.

X

Open X connected apps, locate the application used by Postiz, and revoke access.

Revoking access at a platform does not necessarily delete data already held in Postiz. Continue with the request procedure below when Postiz-held data must also be deleted.

3. Request deletion of Postiz user or workspace data

Email hermine@the-corona.net with the subject Postiz user data deletion request.

Include:

• your full name and company email address;
• the email address used for the Postiz account, if different;
• the relevant Postiz workspace or team;
• the relevant social channels, identified by platform and account or page name;
• whether the request covers particular channel data, your user account, or an entire workspace; and
• enough non-secret information to identify the records.

Requests affecting a shared workspace, company-owned channel, or another person’s records must be approved by an authorized workspace owner or company administrator.

Identity and authority verification

To prevent unauthorized deletion, xFHEngineering may verify identity and authority using the requester’s company email address, existing internal records, or confirmation by an authorized administrator. Only information reasonably necessary for verification will be requested.

Never send a password, social-media password, access token, recovery code, or multi-factor authentication code by email.

4. What a confirmed deletion request covers

Depending on the verified request and the data present, deletion from the live Postiz environment may include:

• the user’s profile, local account, memberships, roles, and preferences;
• OAuth access and refresh tokens and connected-channel records;
• drafts, queues, schedules, and unpublished content;
• media uploaded to Postiz;
• Postiz-held publishing results, analytics, comments, messages, or platform data where present;
• application caches and operational records linked to the request; and
• other identifiable personal data in the relevant live workspace.

Company-owned material may need to be reassigned or retained after the user’s personal account, credentials, and personal associations are removed.

5. Deletion from Postiz does not delete data held by platforms

Deleting data from Postiz does not automatically delete posts, comments, messages, media, analytics, account information, or other records held independently by Meta, Google, YouTube, LinkedIn, X, or another platform. Previously published material may remain visible until it is deleted using the destination platform’s own controls.

Conversely, deleting material at a platform does not necessarily delete its corresponding draft, schedule, media file, or publication record from Postiz. Where both copies must be removed, complete both procedures.

6. Deletion timelines

• After verification and confirmation of scope, applicable data in the live Postiz environment will normally be deleted within 30 days.
• Residual copies may remain temporarily in protected backups and will age out through the normal backup lifecycle within 90 days.
• If a backup is restored for disaster recovery during that period, the deletion will be reapplied where reasonably practicable.

xFHEngineering will confirm completion by email or explain if additional information, authorization, or time is required.

7. Legal, security, and operational exceptions

Limited information may be retained where necessary to comply with law or a binding order; establish, exercise, or defend legal claims; investigate fraud, abuse, unauthorized access, or security incidents; preserve essential audit integrity; protect rights and systems; or document the deletion request and its completion.

Any retained information will be limited to what is necessary, restricted from ordinary use, and deleted or anonymized when the reason for retention ends.

8. Contact

See also the Postiz Privacy Policy and Postiz Terms of Service.