1. Introduction
This page covers requests about personal data, whether you are a current or former user, an employee, a customer contact or someone who never registered. Specify whether the request concerns an individual item, your personal account, a company space or a connected source: those scopes have different consequences.
2. How to request deletion
Email support@alefos.ai or use the public support form. An active account is not required. Give the relevant company, contact details or other identifier and enough context to locate the data. If an account deletion control is available in your delivered interface, its indicated scope applies; the request channel remains available without that control.
3. What can be deleted
Requests may concern a profile, a communication, a document, an inference, a connection or other personal data. They are assessed under the relevant controller’s duties and the rights of others. Removing a member or deleting that person’s account does not automatically erase all company records or data in other companies. The company’s contractual export is a separate process.
4. Meta and WhatsApp data
AlefOS can delete data it processes in AlefOS, not data held only by Meta.
If you connected a WhatsApp Business account, Meta asset or Meta integration, you can request deletion of connection identifiers held by AlefOS, revocation of access permissions it uses, and deletion of imported or processed data, subject to applicable legal obligations.
You can also remove AlefOS access in Meta Business settings. This helps prevent new access, but does not necessarily delete data already processed by AlefOS or held exclusively by Meta.
AlefOS does not claim to delete data held only by Meta, WhatsApp or another third-party provider. Use that provider’s tools or procedures for those data.
5. What may be retained temporarily
At the end of processing services, data processed on a Customer’s behalf are returned or deleted according to its choice under the DPA, subject to legal retention requirements. Any separate retention must identify the purpose, data and applicable period. Backups awaiting their defined expiry remain protected and excluded from ordinary use, with deletion instructions reapplied following recovery. Restricted access is not equivalent to deletion, and technical constraints do not authorize indefinite retention.
6. Processing time and verification
Identity and authority checks are proportionate to the request; no identity document is required by default. MyBot handles its own processing and informs and assists the relevant Customer for processing on its behalf. Where the GDPR applies, a response is due without undue delay and within one month, subject to the permitted extension described in the Privacy Policy. Verification and backup procedures do not replace those legal deadlines.
7. Consequences of deletion
Deletion can be irreversible and may affect the functions that depend on the data concerned. Its scope and consequences must match the request. Exercising a data right is not conditional on deleting an entire account or waiving other rights. Where another person’s or the company’s rights limit erasure, the relevant reason and available remedies are explained.
8. Contact
The official contact for deletion requests is support@alefos.ai.
Email that address with a clear subject, for example AlefOS data deletion. Include only the information needed to identify the account and data concerned.
Do not send passwords, tokens, full bank details, API secrets or private exports containing sensitive information unnecessary to the request.