POSTARYX

Data controls

Data Deletion Instructions

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

Last updated: [Last Updated Date]

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.

To request Account deletion, use [Account Deletion UI Path] if available. You may also contact [Privacy Email] with the subject “Account deletion request.” Include the Account email and 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.

To disconnect a social or other third-party integration, use [Integration Settings Path] and choose the applicable disconnect/remove action. Where supported and implemented, POSTARYX will stop using the connection, revoke or invalidate the upstream authorization, and delete the active OAuth token or credential from live POSTARYX systems.

You can also revoke access directly through the Connected Platform’s account-security or application-permissions settings. 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 intended to be stored only while necessary to provide the connection. After confirmed disconnection or revocation, POSTARYX should delete active tokens from live systems promptly.

Customer-supplied developer credentials, API keys, app passwords, bot tokens, or private credentials are deleted when the applicable integration or credential is removed. [VERIFY CONNECTOR-BY-CONNECTOR DELETION JOBS, UPSTREAM REVOCATION, SECRET STORAGE, AND LOG REDACTION].

1.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 have a shorter retention requirement; for example, Pinterest-derived data must follow the current Pinterest storage restrictions and [Pinterest Data Retention Period] once confirmed.

The V2 target inherited from V1 is to complete deletion or de-identification of ordinary Account 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. The final retention periods must match actual law and system configuration.

Deleted data may remain in encrypted or access-restricted backups until the applicable backup is overwritten or expires through the ordinary backup rotation, currently [Actual Backup Retention Period]. Backup data is not intended to be restored for ordinary product use.

If a disaster-recovery restoration reintroduces data that was previously deleted, POSTARYX should re-apply applicable deletion records or otherwise prevent the restored copy from returning to ordinary use. [VERIFY RESTORE / RE-DELETION PROCEDURE].

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 should be limited to the necessary purpose and protected from ordinary product use.

POSTARYX maintains a Data Deletion Request Callback mechanism for Meta integrations.

Placeholder endpoint: https://api.example.com/meta/data-deletion

Before enabling production Meta integrations, the callback must be live, publicly reachable, configured in the applicable Meta developer application, and implemented to validate Meta’s signed deletion request, identify/initiate the applicable deletion workflow, and return the confirmation URL and code or other confirmation response required by Meta.

[IMPLEMENTATION STATUS: VERIFY BEFORE PLATFORM REVIEW. Replace the placeholder endpoint before production approval.]

The callback is a technical mechanism in addition to this public data-deletion page. A page that merely instructs the user to email support does not replace a platform-required callback.

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 token. 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 [Privacy Email] 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: [Privacy Email]