Legal documents
Data deletion
How to request erasure of Instagram data retained by Disskero AutoChat.
Requests are handled manually by email, with proportionate identity verification and a private administrative operation. There is no public erasure form or automated deletion callback.
1. Where to send a request
The controller is Manuel Jesús Ramos Jiménez, the individual operating Disskero AutoChat. The Disskero brand is not a separate legal entity.
Privacy and deletion requests should be sent to audio@disskero.com.
2. What AutoChat may retain
For accepted comments received, data may include text, identifiers, media, official author identifier when available, date and validation and campaign-association references. Technical records and campaign configurations and history also exist.
The owner’s connection holds profile data and an encrypted token. Instagram passwords are not stored. Automated DMs, automated public replies and real click measurement are not enabled.
Not all such data necessarily relates to the requester. The review must locate the requester’s data without deleting other people’s information.
3. Minimum information to locate data
- State that you request erasure of data processed by Disskero AutoChat.
- Provide your Instagram username and, if possible, the post or comment link and an approximate date. You do not need to know the technical identifier.
- Provide a reply channel and the scope of your request. Do not send passwords, access codes, tokens or an identity-document copy by default.
The controller should request additional information only where necessary and proportionate to clarify scope or address reasonable doubts about identity.
4. Verification and manual handling
The operator will proportionately verify control of the account or the connection with the comment. A display name alone is insufficient. Dashboard access is not provided and passwords or tokens are not requested.
After verifying the request, the operator uses a private administrative operation to erase the located active records and retain a minimal pseudonymous marker preventing reingestion.
Configurations or their history containing manually entered personal information require selective review. A follower’s request does not erase unrelated campaigns or the operator’s connection. Justified residual records and recovery copies follow the retention criteria.
Rights handling is manual. There is no public erasure form or automatic deletion callback. A Meta request already in flight cannot be recalled by local erasure; its result must be checked and, where appropriate, addressed separately through official mechanisms.
5. Scope, retention and copies
Erasure would cover the requester’s data that should be removed. Information would be retained only as necessary for an applicable legal obligation or the establishment, exercise or defence of legal claims, with restricted access and use. Any refusal or limitation must be explained.
Backups or recovery mechanisms may temporarily retain information until expiry under their rules. Immediate disappearance from every copy is not promised. If recovery reintroduced erased data, erasure would need to be reapplied and ordinary use prevented.
A hash does not guarantee anonymity. Link validity periods or token expiry do not automatically erase related records.
6. Response and rights
The usual legal response period is one month from receipt. It may be extended by two months for complexity or the number of requests, with reasons given within the first month. The outcome must be communicated, or the grounds for not fulfilling all or part of the request explained.
You may complain to the Spanish Data Protection Agency and exercise the other rights described in the privacy policy.
7. Difference from Instagram
Deleting a comment, withdrawing authorization or using Instagram controls affects Meta’s service and does not establish that AutoChat erased earlier records. Conversely, this AutoChat process cannot delete an Instagram account or all data retained by Meta.
Disconnecting removes the operator’s local connection and OAuth states, but not all history. Data retained by AutoChat is handled through the manual procedure described on this page.