Data controls

Data Deletion Instructions

How Postaryx handles account deletion, integration removal, OAuth credential revocation, and retained records.

Last updated: 12 September 2026

On this page

Postaryx is operated by Lunark Dynamics LLC. You can delete your Postaryx Account, disconnect individual Connected Platforms, remove OAuth credentials, delete stored content, or submit a privacy deletion request as described below.

Deletion from Postaryx does not necessarily delete content already published to a Connected Platform. Platform-side copies are controlled by the relevant platform and your account there unless Postaryx has a supported delete action that you use.

Postaryx processes Account deletion requests through a verified request process. To request deletion of your account, contact us directly using the instructions below.

Email with the subject “Account deletion request.” Include the Account email address and the Workspace name. We may verify identity and, for a shared Workspace, administrative authority before deleting data that affects other members.

If an Account owns a Workspace with other members, Postaryx may require transfer of Workspace ownership, confirmation from an authorized administrator, or deletion of the entire Workspace before removing records necessary to preserve other users’ access.

Before or instead of requesting full Account deletion, you can disconnect each Connected Platform yourself using the in-product control described in Section 3, and you can revoke Postaryx’s access from each platform’s own application-permissions settings.

In-product controls let you remove individual channels, posts, drafts, media, sets, signatures, webhooks, approved apps, and team members. They do not delete the Account record itself; only a request under this section does that.

You can disconnect a social or other third-party integration yourself at any time. In the Postaryx app, open the channel list on the main Launches/Calendar screen, open the menu on the channel you want to remove, choose “Delete Channel,” and confirm. If scheduled or published posts are still associated with that channel, Postaryx may require you to delete those posts before the channel can be removed.

After you disconnect, Postaryx stops using the connection, stops publishing to it, and removes the channel from your Workspace so it is no longer available in the product.

Removing a channel from your Workspace stops Postaryx from using that connection and erases the stored credentials for it, as described in Section 4. Any remaining copies in backups are subject to the retention practices described in Sections 6 and 7.

Whether the authorization is also canceled on the platform's side depends on that platform's capabilities and on whether Postaryx supports its revocation method. Not every platform offers one, so disconnecting in Postaryx does not always end the authorization held by the platform.

For that reason we recommend that you also revoke access directly through the Connected Platform’s account-security or application-permissions settings. That revocation is performed by the platform and takes effect on the platform side regardless of Postaryx. If you revoke upstream first, Postaryx may detect that the token is invalid and mark the connector disconnected or require reconnection.

Active OAuth tokens and comparable credentials are stored only for as long as necessary to provide the connection and related functionality. When you disconnect a Connected Platform, Postaryx erases the stored access token, refresh token, and expiry for that connection from its live systems as part of the same operation.

Customer-supplied developer credentials, API keys, app passwords, bot tokens, or private credentials are deleted when the applicable integration or credential is removed.

5Stored Content and Platform-Derived Data

An Account or Workspace deletion request may include deletion or de-identification of drafts, schedules, media, thumbnails, publication records, permitted analytics, platform account identifiers, platform-derived metadata, comments/replies stored by enabled features, connection data, and other customer data in active systems, subject to the exceptions below.

Users may also delete individual drafts, scheduled items, media, or records through product controls where those controls are available. Platform-specific data may be subject to shorter retention requirements according to applicable platform rules.

Postaryx aims to complete deletion or de-identification of ordinary Account and Workspace data from active systems within up to 90 days after a valid Account deletion request, unless a shorter platform rule applies, deletion can reasonably be completed sooner, or longer retention is required for a permitted exception.

Permitted exceptions may include tax/accounting records, payment and chargeback records, legal claims, fraud/abuse investigations, security incident records, regulatory requirements, or data that must be retained to establish or defend legal rights.

Postaryx may maintain backups according to infrastructure configuration and operational requirements. Backup copies may retain deleted information until they are overwritten through normal backup processes. Backup data is not intended to be restored for ordinary product use except where required for disaster recovery or security purposes.

If a disaster-recovery restoration reintroduces data that was previously deleted, Postaryx re-applies applicable deletion records or otherwise prevents the restored copy from returning to ordinary use.

Some information may be retained after Account deletion where required or permitted for billing, tax, accounting, anti-fraud, chargeback, security, audit, dispute, or legal-compliance purposes. Such retained data is limited to the necessary purpose and protected from ordinary product use.

Postaryx respects user data deletion rights and provides a process for users to request deletion of their account and associated personal data.

For accounts connected with third-party platforms, including Meta services, users may request deletion of their Postaryx account data by contacting us at:

Users may also disconnect connected platforms through available Postaryx controls or revoke Postaryx access directly through the relevant platform’s account or application permission settings.

Postaryx will implement the technical deletion mechanisms required by platforms before enabling the corresponding production integrations. For Meta integrations, this includes the Meta Data Deletion Request Callback or other deletion mechanism required by Meta for the applicable integration.

The callback or other required mechanism will allow Meta to communicate a valid user-data deletion request to Postaryx so that Postaryx can process the request in accordance with its deletion procedures, applicable Meta requirements, and applicable law.

Users may also request deletion directly from Postaryx, as described above.

A post, comment, video, Pin, Thread, Page post, business-profile update, or other material already delivered to a Connected Platform may remain there after Postaryx deletes its own copy or the authorization credentials. Use the Connected Platform’s native deletion controls or a supported Postaryx delete action to remove platform-side content.

If a platform retains logs, backups, or other records under its own policies, those records are governed by that platform’s privacy policy and terms.

Where appropriate, Postaryx will confirm completion or status of a verified deletion request using or an in-product confirmation. Requests made under privacy law may be subject to identity verification, legal exceptions, and statutory response periods.

Questions about deletion: