Privacy Policy

Who we are

Crelodia is an online service and the website at crelodia.com. Both are operated by Oleksii Mykolaiovych Pyvovar, an individual entrepreneur registered in Ukraine (the operator). Crelodia is the name of the service, not a separate company.

The operator is the controller of the personal data described here: it decides why and how the data is processed and is responsible for it. The last section of this policy says how to reach us.

Where the service stands

Sign-up for Crelodia is open and free: nothing is sold, and there are no prices or payments on this site.

Until Meta approves Crelodia, signing in with Threads and connecting Threads work only with a Threads account we have added as a tester at Meta, and a keyword search returns at most posts of your own account. Signing in with Google or with a code by email, adding a business and connecting Telegram work already.

The home page describes the service as it is meant to work. Three parts of it are not switched on: finding public posts of other people, assessing posts with a language model, and sending finds to Telegram. Before any of them is switched on, this policy will describe it.

What data we process

Each category below is processed only for the purposes named in the next section.

• When you visit this website: the time of the request, the page address without its query string, the response code and size, your browser’s user-agent string and a shortened IP address — the last part of an IPv4 address is removed, and an IPv6 address keeps at most its first three groups. The public pages set no cookies and use no analytics, advertising pixels or third-party scripts.
• When you write to us: your email address, what you write and attach, and our replies.
• Your Crelodia account: an internal identifier and the ways you sign in. For each way we keep what identifies it and when it was added and last used: for Threads, the identifier Threads gives our app for your account and your Threads username; for Google, the identifier Google gives our app for your Google account and, if Google has confirmed it, your email address; for a code by email, your email address. A Threads account connected to one of your businesses is recorded as yours too; it signs you in only once you allow it.
• Your businesses: the name of each business and your role in it.
• Signing in with a code: we send the code to your address from our own mailbox for signing in. We keep a digest of the address and a keyed digest of the code — never the code itself — how many wrong codes were entered and whether the letter was sent.
• Your sessions: when you sign in, your browser gets a cookie with a random value that keeps you signed in; we keep only a digest of that value, a short label of your browser and system (for example “Chrome · Windows”, not the full browser string), and when the session started, was last used and ends. The sign-in page sets a cookie for 30 minutes that protects signing in against forged requests, and a sign-in or connection with Threads sets two cookies for 10 minutes: one ties Threads’ answer to your browser, the other keeps the page’s language. These cookies serve signing in only and nothing else.
• Your Threads connection, when you connect a Threads account through the official Threads sign-in: the identifier Threads gives our app for your account, your Threads username, the permissions you granted and when the access expires. The access token itself is stored only encrypted (AES-256-GCM); the key that encrypts it is in turn protected by Google Cloud Key Management Service and is not stored next to the data.
• Your Telegram, when you connect it in the cabinet: the link to our bot is valid for 15 minutes and only once; we keep only a digest (hash) of its code, and whom and which business it was issued for. When you open the link, the bot records the identifier of your Telegram account (which is also the identifier of your chat with the bot), your business and the language to answer in. We do not keep your Telegram name, username or phone number. So that nobody can guess a link, failed attempts are counted by a keyed digest of the Telegram identifier.
• When you set up a search in the chat with the bot, an unfinished step of the dialogue, together with the already checked text you entered, is kept for up to 30 minutes.
• The Telegram mini app: when you open it from the bot’s menu, Telegram hands it signed launch data — your Telegram identifier, the name and username of your Telegram profile, and the time of the launch. We check the signature with Telegram’s public key and open a session only for a Telegram that is already connected; we do not keep the name or the username. We keep a digest of the launch and a digest of the session, the business it is open for, and when it was opened, last used and ended. The mini app’s session lives only in the app’s tab, without cookies.
• The days of your activity: for each calendar day on which you did something in the cabinet, the mini app or the chat with the bot — the channel (website or bot), the kinds of actions from a closed list (for example signing in, viewing, changing settings, giving feedback on a find) and the first and last moment of the day. Without the text of messages, page addresses, IP address, browser or the number of actions.
• Your business settings: the description of your business, your campaigns and the words and phrases you want to search for.
• Test searches you run: the phrase, when the search ran and how it ended. If Threads returns posts of your own connected account, up to 10 of them are kept for you to see: the link, the text (at most 500 characters) and the time of publication. Posts of other people are not stored, only how many there were. For every search the service also records when it ran and how much of the Threads search limit it used.
• Technical records of the service: which function was called and how the request ended, without the content you enter, your Threads username, tokens or passwords.

Why we process it

We use each category only for its purpose:

• To show you this website and to keep it and the service secure: to notice attacks and abuse and to fix failures. Ground: our legitimate interest in a working, secure service.
• To answer your messages and to handle requests about your data. Ground: your consent, which you give by writing to us, and, for requests about your data, our obligations under the law.
• To give you the service you asked for: to create your account and keep you signed in, to connect your Threads account and your Telegram, to run the searches you start, to show you their results in the cabinet and the mini app, and to send you the bot’s messages. Ground: performing our agreement with you (the Terms of Service).
• To understand whether and how the service is used, from the days of your activity. Ground: our legitimate interest in developing the service; these records hold no content and are removed after 90 days.
• To comply with the law, where it requires us to keep or disclose something. Ground: a legal obligation.

How we use data from Threads

We use data we receive from Threads only to provide the features you use: to show which account is connected, to keep the connection working and to run the searches you ask for. We do not sell it, do not use it for advertising and do not use it to build profiles of people.

Crelodia asks Threads for two permissions: the basic one, which identifies your account, and keyword search. Until Meta approves keyword search for Crelodia, Threads answers a search with posts of your own account only.

The service publishes nothing on your behalf: it never posts, replies or comments, and never sends messages to anyone.

Before finding public posts of other people is switched on, this policy will describe what the service keeps about those posts and their authors.

Who receives data

We do not sell data and do not pass it to advertising networks. It goes only to the providers the service cannot run without, and only as far as their role requires:

• Hosting Ukraine LLC (ТОВ «Хостінг Україна»), our hosting provider. The website, the service and its database run on its servers in Ukraine; our mailboxes and the domain name service of crelodia.com are provided by it as well, and the letters with sign-in codes are sent through its mail server.
• Google, through its Cloud Key Management Service in the European Union (Warsaw, Poland). It protects the key that encrypts stored Threads access tokens and never receives the tokens or any other content.
• Google, if you choose to sign in with Google: you pick your Google account in Google’s own window, and Google tells us the identifier of that account and, if it has confirmed it, your email address. The page loads Google’s sign-in button from accounts.google.com only after you press “Sign in with Google”. Google processes this under its own terms and privacy policy.
• Meta Platforms, when you use Threads with Crelodia: you sign in to Threads on Meta’s own pages, and each search sends your search phrase to Threads through your connection. Meta processes this under its own terms and privacy policy.
• Telegram, when you connect Telegram: the bot sends you messages through Telegram, so Telegram receives their content and your Telegram identifier, and the mini app opens inside Telegram. Telegram processes this under its own terms and privacy policy.
• Public authorities, only where the law requires us to disclose data.
• No language-model provider receives your data.

Where data is kept

The website, the service database and our mailboxes are on servers in Ukraine; the operator keeps the encrypted backups of the database in Ukraine as well. The encryption key service is in the European Union, in Poland. Meta and Telegram process the data they receive under their own terms, in the countries where they operate.

The key service receives no content, Meta receives only what you send to Threads through your own connection, and Telegram receives the bot’s messages to you and what you write to the bot.

How long we keep it

Some periods are enforced by the service itself, by the database clock; the others end when you delete the data or ask us to.

• Web server records of visits — 14 days.
• The results of a test search, including your own posts in them — 24 hours.
• Your Threads access — until you disconnect Threads or your data is deleted.
• Your account, your workspace and your business settings — until you delete them or ask us to.
• Records of the searches that ran (when, and how much of the limit they used) — as long as the workspace exists.
• Our correspondence with you — as long as we need it to answer you and, for a request about your data, to be able to show that it was carried out.
• The receipt of a completed deletion — 90 days; the data deletion page explains what it holds.
• Your sessions — until you sign out or end them, and at most 30 days; a session’s record is removed 7 days after it ends.
• Sign-in codes — valid for 10 minutes; their records are removed after 24 hours.
• A started sign-in with Threads — 10 minutes to finish; its record is removed after 24 hours.
• Your sign-in methods — as long as your account exists; a method you remove is gone at once.
• A link for connecting Telegram — valid for 15 minutes and only once; its record is removed 24 hours after it expires.
• Your Telegram connection — until you disconnect it; the Telegram identifier is erased at once when you disconnect, the rest of the record after 24 hours.
• The counter of failed attempts to connect Telegram — 24 hours. An unfinished setup step in the chat with the bot — 30 minutes.
• Mini app sessions — at most 8 hours, and a session ends after an hour without activity; its record is removed 24 hours after it was opened.
• Days of activity — 90 days.
• The bot’s messages stay in your Telegram chat until you delete them; we do not keep them.
• Application logs — 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.

Disconnecting Threads and deleting your data

Disconnecting Threads removes the access to your Threads account that Crelodia stores; your workspace and your settings stay. Deleting removes your data from Crelodia for good.

Deleting your account also removes your sign-in methods and sessions, your Telegram connections and mini app sessions. In the “Account” section of the cabinet you can remove a sign-in method or end a session yourself.

Telegram is disconnected 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.

You can ask us to delete your data at any time by writing to the address at the end of this policy. We carry out a confirmed request no later than 30 calendar days after it is confirmed. The data deletion page sets out every step, and what is kept briefly afterwards and why.

Your rights

Under the Law of Ukraine “On Personal Data Protection”, and under the EU General Data Protection Regulation where it applies to you, you can ask us what data about you we process, where it came from and why; ask for a copy of it; have it corrected; have it deleted; have its processing restricted or stopped; and withdraw consent where processing rests on your consent.

To use any of these rights, write to us. If you believe we process your data unlawfully, you can complain to the Ukrainian Parliament Commissioner for Human Rights or go to court and, if you live in the European Union, to the data protection authority of your country.

Children

Crelodia is a tool for businesses and is not intended for minors (anyone under 18). We do not knowingly process data of children.

Security

Stored Threads access tokens are encrypted, and the key that protects them is held apart from the database. Each workspace is separated in the database itself rather than only in the application: every query runs in the context of one workspace. Internal access follows least privilege, and secrets are kept out of logs.

Your session cookie holds a random value that only your browser has; the database keeps only a digest of it. Every change in the cabinet must come from this site and carry a token derived from your session. Sign-in codes have six digits, are valid for 10 minutes, are spent after five wrong entries and are limited per address and in total.

The mini app opens a session only with launch data that Telegram has signed and that is at most 10 minutes old; we check the signature with Telegram’s public key, and one launch opens only one session. A link for connecting Telegram works once, and the bot connects Telegram only to the business the link was issued for.

No system is perfectly secure, so we do not promise absolute safety — this section describes what we actually do.

Changes to this policy

When this policy changes, the date at the top of the page changes too. If a change significantly affects how we use your data, we will tell the people who use the service before it takes effect.

Contact

Questions about your data and requests about it go to the address below. We answer in Ukrainian or English.

Contact for questions about your dataprivacy@crelodia.com