Your data. A clear process.

Version 1.0 — effective 18 September 2026.

Disconnecting a social account

In the beta product, an organization owner can disconnect a social account from Social accounts. This stops future queued work for that connection, clears its active credentials, and marks it as disconnected. A request already sent to a platform may still complete. For platforms other than Google and Bluesky, remove the permission in the provider’s connected-app settings as well; local disconnection does not confirm provider revocation.

Disconnecting does not delete the organization, its drafts or media, or copies already published on a social platform. Review connected-app permissions on the provider itself where appropriate.

Disconnecting also deletes the account and post statistics collected for that account. The same statistics are deleted when the organization is deleted and when the platform sends Moklex a deletion or deauthorization request for the account.

Removing a YouTube connection

The implementation also removes the stored channel profile and associated provider post IDs, links, upload checkpoints, and publishing attempt records, cached command responses, and linked notifications and email records. Completed delivery records are marked archived after their provider information is removed. It immediately attempts to revoke the Google grant. If Google cannot confirm revocation, an encrypted credential is held in a separate retry job, with a seven-day retry cutoff and an owner notice. It is cleared when revocation succeeds or the cutoff is processed.

Social accounts shows whether Google revocation is pending or needs attention. You can remove access directly through your Google account permissions. Your independently supplied drafts and media remain in the organization. The implementation checks connected accounts daily and expires stored Google delivery metadata at 29 days. External revocation and expired-data removal are covered by automated tests.

Removing a Bluesky authorization

The OAuth implementation disables the connection and queues remote authorization removal. An encrypted session is retained for retries until removal is confirmed or the seven-day retry cutoff is processed. Pending or failed removal is visible in the product. If removal cannot be confirmed, remove Moklex in your account provider’s authorization settings.

Organization deletion

The product has an owner-authorized backend deletion command with an explicit confirmation. It clears organization social credentials, queues deletion, and excludes the organization from subsequent authentication. A background worker removes the organization’s stored media and organization records, including related records covered by database deletion rules. It waits for issued upload links to expire before sweeping stored files, including untracked uploads. Failed file removal is retried. Restored database copies are quarantined: provider credentials, active sessions, queued work, and Google API data are removed before recovery review.

This website does not offer a self-service deletion interface and does not submit deletion commands. An organization owner starts deletion in the product, or sends the request to the privacy address below.

Timing and retained copies

The background worker starts once issued upload links have expired, about fifteen minutes after confirmation, and normally finishes the same day. Moklex aims to complete every deletion within 30 days.

Some copies outlive the live records for a defined period. Encrypted backup snapshots can still contain deleted content until they expire, currently within seven days, and are never used to bring it back: the deletion is replayed against any restored copy before that copy is used. Technical logs are kept 90 days and accounting records 10 years, as Swiss law requires. A short deletion record — an opaque identifier, a request identifier and the time, with no content, name or email address — is kept outside the databases and backups so that a deleted workspace stays deleted if a backup is ever restored. The privacy notice lists every retention period.

Content already posted to a social platform must be managed on that platform. Where a supplier holds a copy on Moklex’s behalf, the deletion is passed on to that supplier under its processing terms.

Making a request

Responsible business

Daimyo International GmbH (CHE-295.167.208)

Privacy contact

info@moklex.com

Request submission channel

Email

Identity and authority verification

Confirmed by reply to the email registered on the account

Response and completion times

Answered within 30 days; deletion normally the same day

Backup, log, and processor retention

Backups 7 days, logs 90 days, accounting records 10 years

Use the email on the contact page for deletion requests. The privacy notice explains what is held, who receives it and for how long.