Data Deletion

Disconnecting and deleting are two different things

Disconnecting Threads removes the access to your Threads account that Crelodia stores. From that moment the service can no longer call Threads on your behalf, and searching stops. Your Crelodia account, your workspace and your settings stay where they are, and you can connect again later.

Deleting removes your data from Crelodia for good. You can ask us to delete one workspace (called a “business” in the cabinet), or your whole account together with every workspace that belongs to you alone.

In Crelodia, the owner of a workspace disconnects Threads on the overview of the workspace. To withdraw the permission on the Threads side as well, remove Crelodia in the settings of your Threads account, where the apps and websites you have connected are listed. Neither step deletes anything in Threads itself.

Telegram is disconnected separately: with the “Disconnect Telegram” button in the cabinet or with the /disconnect command in the chat with the bot. The Telegram identifier is erased at once, and the bot no longer writes to you.

How to ask for deletion

Write to us at the address below. A request in your own words is enough: say what should be deleted — one workspace, which you name, or your whole account — and name the Threads account connected to it, or the email address you sign in with.

We reply to confirm the request, and only after that do we delete anything.

• Write to the address below.
• Say what to delete: one workspace, which you name, or your whole account.
• Name the Threads account connected to Crelodia, or the email address you sign in with.
• Confirm the request in the way our reply describes.

Address for deletion requestsprivacy@crelodia.com

How we make sure it is you

Deletion cannot be undone, so before deleting anything we check that the request comes from the person who controls the account. Our reply tells you how to confirm it. We never ask for a password or a code to do this.

Only the owner of a workspace can have it deleted. If other people use the workspace too, we do not delete it on the word of one of them: we get in touch to settle who decides, and nothing is removed until that is clear.

What you should never send us

We never need a secret in order to delete your data. Do not put any of the following in a message to us, even if someone asks for it in our name:

• Your Threads, Instagram or Meta password.
• A Threads access token, or any other code or key.
• A Meta App Secret or any other credential of an app.
• Codes from text messages, from a sign-in confirmation app or from password-reset emails.

What is deleted

When a confirmed request is carried out, everything listed below is removed from the service’s live database in a single step: either all of it or, if something goes wrong, none of it.

• The stored, encrypted access to your Threads account and every record of the connection, including your Threads username and identifier.
• Your business description, your campaigns and your search words and phrases.
• The results of your test searches and the records of the searches that ran for the workspace.
• Your membership of the workspace, and the workspace itself.
• Your Telegram connections together with the Telegram identifier, the links for connecting, unfinished steps of the dialogue with the bot, mini app sessions and the days of your activity.
• With a request for the whole account: the account record together with all its sign-in methods and sessions, as soon as no workspace of yours is left.
• Everything else the service stored for the workspace.

What is kept a little longer, and why

A few records outlive the deletion, each for a stated reason and for a limited time. The search limit records and the receipt contain no business description, none of your search words, no email address and no Threads post.

• Search limit records. Threads limits how many keyword searches one Threads account may run in any 24 hours, counted across all apps. So that deleting and connecting again cannot be used to get around that limit, we keep a minimal record of every search already spent: a one-way fingerprint of the identifier of your Threads account, and the time the record stops counting. It is kept only until the end of the 24-hour window it belongs to and is then removed. The fingerprint is always the same for the same account, so this record is not anonymous.
• A deletion receipt. It shows that a request was carried out, and when. It holds no name, no email address and no content, and it is removed after 90 days. The next section lists exactly what is in it.
• Web server records of visits to the website are removed after 14 days.
• Our correspondence about your request stays in our mailbox as the record that the request was received and carried out; you can ask us to delete it once the request is complete.
• Application logs and backups of the service database. Application logs (which function was called and how the request ended, without your content) are removed after 30 days. Encrypted backups of the service database — 30 days; if no new copy was made, the three latest are kept. The protected copy of the database that the server makes before each update of the service is removed after the update has been checked and no later than 7 days after it was made. Deleted data stays in the copies already made until they are removed under these rules.
• Messages the bot has already sent you in Telegram stay in your Telegram chat: we do not keep them and cannot delete them, but you can delete them yourself.

What the deletion receipt holds

When a deletion is finished we keep one small technical record of it, the receipt. It is the proof that your request was carried out, and it lets us tell you the result if you ask about that request again. The receipt is removed 90 days after the deletion.

The receipt does not hold your name, your email address, your Threads username, the identifier of your Threads account, the text of any post, or any of the data that was deleted.

One entry needs a word of explanation: the fingerprint of the person who made the request. It is a pseudonymous one-way technical fingerprint. It is calculated from the internal number of your Crelodia account and cannot be turned back into that number, so the fingerprint by itself does not say who you are. It is not anonymous, though: the same account always gives the same fingerprint, so someone who already knew that internal number could recognise it.

We use that fingerprint for one thing only. If the same request is asked about again, the result is given back to the person who made it, and to nobody else: someone who merely learns the request number receives nothing, not even a confirmation that such a request exists.

This is everything a receipt holds:

• The number of the request, and whether it asked for one workspace or for the whole account.
• The date and time the deletion was completed, and the date on which the receipt itself is due to be removed.
• How many records of each kind were removed, and how many search limit records were kept. These are totals only, with no contents.
• A one-way fingerprint of the internal number of the deleted workspace or account. It is there to stop a deleted workspace or account from being created again under the same number while the receipt exists.
• The pseudonymous one-way technical fingerprint of the person who made the request, described above.

How long it takes

We carry out a confirmed request no later than 30 calendar days after you confirm it.

When it is done we tell you in reply to your request. If the request cannot be carried out as asked, for example because other people use the workspace, we tell you so and explain why.

Questions

If anything here is unclear, or you want to know what is happening with your request, write to the same address.

Contact for questions about your dataprivacy@crelodia.com