This policy explains what data Cladar (the “Service”, “we”) collects, why, where it is stored, who it is shared with, and how you can control it. It covers the website cladar.app and the app at app.cladar.app. This English version is the governing text; translations are provided for convenience, and in case of any discrepancy the English text prevails.
For any question about this policy or your data, write to [email protected].
1. In short
- We store your email address, your Google account identifier, your conversations with the coach, and your plan and payment records. We do not store your name or photo from Google.
- Conversations are kept so the coach remembers context. They are private to your account: other users cannot see them, and the owner of the Service may read them only to provide support, investigate failures, or review answer quality (section 9). Any conversation can be deleted with one click, or all of them at once; your account can be deleted entirely on request.
- Conversation text is sent to language-model providers to generate answers. The Service cannot work without this.
- There are no analytics or advertising trackers on the site or in the app.
- The Service is for adults aged 18 and over. It is not intended for citizens of the Russian Federation or Ukraine, or for anyone located in the territory of either.
2. What data we process
2.1. Account
You can sign in to the app only with Google. At sign-in we receive and store:
- your email address;
- the permanent identifier of your Google account (needed to recognise you next time you sign in);
- confirmation from Google that the email address is verified.
Google also sends your name and profile photo at sign-in, but we do not store them: they are stripped before anything is written to the database. You do not create a password with us, and we never see one.
Technical details of the sign-in session (IP address, browser type, time of sign-in) are kept by our authentication provider, Supabase, as part of its own session records.
2.2. Conversations
Everything you write to the coach and every answer the coach gives is saved in your conversation history. Alongside the text we store service metadata for each answer: which relationship stage and topic the question was assigned to, which knowledge-base entries were used, which model answered, and how long it took. For long conversations we create a short summary so the coach remembers how the conversation began.
This is sensitive data. The Service is about relationships, and in your conversations you describe your private life of your own accord: relationships, intimacy, feelings, conflicts. We do not ask you to do this, but we understand that without it neither the analysis nor the Service itself can work. Such information falls under special categories of personal data, and we process it only with your explicit consent, which you give when you first sign in to the app (see section 4). You can withdraw consent at any time by deleting your conversations or your account.
What not to write: names, addresses, phone numbers, links to profiles, and other details that could identify you or other people. The coach does not need them: a situation can be analysed without them. And once the text has gone into backups and model providers’ logs, they cannot be removed later. Details that could identify another person must not be written (see the Terms of Service, section 7).
2.3. Plans and payments
We store your plan details: what you bought, how many answers are included and used, and until what date access is valid.
Payment is accepted in cryptocurrency (stablecoins) by transfer to our address. We store the network, the amount, the receiving address, and the transaction hash so that we can match the payment to your account and resolve disputes. Please note: a transaction on a public blockchain is visible to everyone and cannot be deleted by us or by anyone else. We do not deliberately collect your wallet address, but it is contained in the transaction. We never receive or store bank card or bank account details: we simply do not have them.
2.4. Support requests
Messages sent through the form on the website or to [email protected], including the reply address you provide, are kept in our mailbox and in the website database until the request is closed and for a period after that (see section 6).
2.5. Technical data
When you access the site or the app, ordinary technical data is processed: IP address, browser type, time of request. It is used to protect against overload and abuse and is kept in the logs of our infrastructure providers (Cloudflare, the site host) under their rules. Application logs contain error and failure records without conversation text.
2.6. After account deletion
After your account is deleted we keep a hash of your email address (a one-way transformation from which the address cannot be recovered), the date of your first registration, the number of free answers you used, and when you used the last one. This is needed so that free answers cannot be obtained again by deleting and re-creating an account. Nothing else about a deleted account remains.
3. Why we need this data
| Purpose | Data | Legal basis |
|---|---|---|
| Sign-in and account operation | email, Google identifier | performance of our contract with you |
| Coach answers and conversation memory | conversations, summaries, answer metadata | your explicit consent |
| Plans and answer accounting | plan details, payment records | performance of the contract |
| Support | support requests | performance of the contract, our legitimate interest |
| Protection against abuse and failures | technical data, email hash after deletion | our legitimate interest |
| Improving the Service | anonymised statistics: number of answers, refusals, errors | our legitimate interest |
We do not use your conversations to train models, do not sell your data, and do not pass it to advertising networks. We do not make automated decisions that have legal effects on you.
4. Consent
When you first sign in to the app, you tick a box confirming that you have read this policy and the Terms of Service, and press “Continue”. By doing so you give explicit consent to the processing of the content of your conversations, including any details of your private and intimate life that you choose to share, and to the transfer of conversation text to model providers in the USA (section 5). You can withdraw consent at any time by deleting individual conversations in the app or by deleting your account entirely (section 6). After withdrawal the Service will not be able to answer your questions, because an answer requires the text of the question.
5. Where data is stored and who processes it
We rely on third-party providers. Each receives only what it needs for its task and processes the data under its own terms.
| Provider | Role | What it receives | Where |
|---|---|---|---|
| Supabase | database and authentication | all account and conversation data | EU (Paris) |
| Cloudflare | network, protection, running the app code | technical request data; text passes through in transit | global network |
| DeepInfra | generating coach answers and searching the knowledge base | the text of your questions, the conversation summary, recent messages | USA |
| Together AI | conversation summaries | conversation text for summarising | USA |
| sign-in to the app; the support email address shown on the Google sign-in screen (a Google Groups address) | the fact of sign-in; Google tells us your email and identifier; emails sent to the group address | under Google’s rules | |
| Hostinger | hosting the cladar.app website | requests sent through the site form, technical visit data | EU |
Sending conversation text to generation providers in the USA is necessary for the Service to work: without a model there is no answer. These providers receive the text without your email or identifier.
Neither provider states that it is certified under the EU–US Data Privacy Framework, so we do not rely on the EU adequacy decision for the USA, and the providers act under US law. We use them under their standard terms and have no separate data processing agreement with them. The transfer therefore relies on your explicit consent (GDPR, Article 49(1)(a)), which you give at first sign-in after reading this notice and being informed of the possible risks of such a transfer (section 4). According to the providers’ own policies, DeepInfra does not store request inputs or outputs and does not log their content, keeping only technical metadata, and Together AI applies the European Commission’s standard contractual clauses when it passes data of EEA residents on to third parties. Their policies: DeepInfra, Together AI.
We may change our generation provider. If we do, we will update the table above; the principle stays the same: the provider receives only the text needed for the answer.
6. How long we keep data and how to delete it
- Conversations are kept until you delete them. You can delete any conversation, or all of them at once, in the app at any time. A deleted conversation cannot be restored.
- Account deletion is requested from the app settings. After the request there is a 30-day grace period: the chat is closed, and signing in during this period cancels the deletion. When the period ends, the account, profile, all conversations, and plan records are deleted permanently. Only the email hash remains (section 2.6).
- Email hash after account deletion is kept for 12 months.
- Payment records are kept for as long as the account exists. The transaction record on the blockchain remains forever: that is a property of blockchains, not our decision.
- Support requests are kept for 12 months after the request is closed.
- Backups of the database are made regularly and are kept by the owner of the Service in encrypted form. Deleted data disappears from backups as they are refreshed, within 60 days.
Retention periods may be extended if the data is needed to resolve a dispute or is required by law.
7. Your rights
At any time you can:
- obtain a copy of your data: conversations are visible in the app, the rest we will send on request, in a machine-readable format (JSON) if you want to transfer it elsewhere;
- correct inaccurate data (in practice this is your email address, which is refreshed from your Google account the next time you sign in);
- delete conversations or your account (section 6);
- withdraw consent to the processing of conversations (section 4);
- object to processing based on our legitimate interest;
- ask us to restrict processing while a dispute about your data is being resolved;
- lodge a complaint with the data protection authority in your country.
To do so, write to [email protected] from the address your account is registered to. We reply within 30 days. If a request comes from a different address, we may ask you to confirm that the account is yours.
8. Cookies
The website sets one cookie of its own: it remembers your chosen language (Russian or English) and is kept for a year. The app stores your sign-in session in your browser so that it does not have to ask Google every time you open it, together with your interface preferences. In addition, Cloudflare, the network in front of the site and the app, may set technical cookies for bot protection; they do not track you across websites. There are no analytics or advertising cookies. If we ever add analytics, this policy will be updated before it is switched on.
9. Security
Data is transmitted only over encrypted connections. Database access is segregated so that each user can see only their own conversations. Administrative access belongs only to the owner of the Service. In normal operation nobody reads conversations; administrative access is used only for support at your request, for investigating failures and answer quality, and for resolving disputes. We cannot guarantee absolute security, and neither can anyone on the internet, so we recommend not writing anything in conversations that could identify you or other people (section 2.2).
10. Age and territory
The Service is intended for people aged 18 and over. We do not knowingly collect data from minors; if you learn that a minor has created an account, write to us and we will delete it.
The Service is not intended for citizens of the Russian Federation or Ukraine, or for anyone located in the territory of either, and is not offered to them; by accepting the Terms of Service you confirm this. We do not collect or process data that would allow us to determine a user’s citizenship, and we do not collect personal data in the territory of the Russian Federation.
11. Changes
We may update this policy. The date of the last update is shown at the top. We will announce material changes in the app before they take effect. Continued use of the Service after that means you accept the new version.