Keryxion Data Deletion Instructions · Keryxion
How to ask MLU Dev to delete data processed by the Keryxion application.
1. Request deletion by email
To request deletion of data processed by Keryxion, email contact@mludev.com.br with the subject “Data deletion — Keryxion”. If possible, send the message from the email registered with the service.
This is a request-based procedure, not an automatic deletion form. Do not send passwords, access tokens, authentication codes or private webhook URLs.
- Provide the email address of the account used in Keryxion and the workspace name or identifier, if known.
- Identify the relevant Instagram/Meta account or profile when the request concerns that integration.
- Describe the scope: deletion of the account, an integration, automation history or specific data about you.
- If you do not have a Keryxion account, provide the profile and information needed to locate the relevant interaction or post, without unnecessary third-party information.
2. Stop new access
If you administer the workspace, deactivate related workflows and disconnect the relevant account on the Connections page. This prevents the removed connection from continuing to be used by those workflows, but does not delete all history.
To revoke Meta authorization, open the settings of the Facebook account used to authorize the app, look for Business integrations or Apps and websites and remove Keryxion. Option names and locations may vary with Meta’s interface.
For Google, review connections to third-party apps and services in your Google Account and revoke the app’s access. For Discord, remove the webhook in server/channel settings or review authorized applications.
Revoking provider access does not automatically delete data already stored by Keryxion; also send a deletion request if you want that data removed.
3. Verification and handling
MLU Dev will review the request and may ask for proportionate information to confirm your identity, connection to the data and deletion scope, protecting other workspace users.
After verification, we will inform you of progress and completion through the contact channel. Requests are handled within the deadlines and conditions of applicable law. If there is an obstacle or a legal need to retain any data, we will explain the reason.
Deletion may cover registration, stored connections and credentials, configurations and related execution records, according to the requested scope and other people’s rights. Data subject to legal retention is limited to the necessary purpose; backups are replaced according to the infrastructure cycle.
4. Data sent to Google Sheets, Discord or other destinations
Deletion in Keryxion does not automatically remove rows already written to Google spreadsheets, messages already sent to Discord or data held directly by Meta and other platforms.
The spreadsheet owner, channel administrator or destination operator must manage removal in those services. If you need to identify the destination of data processed about you, describe this in your request so MLU Dev can assess how to help.