01
Data controller
The data controller is ETHIUNI LLC (TIN 01387425), registered in Armenia and operating in Yerevan.
Contact: vahan@ethiuni.ai.
Legal
In effect from July 29, 2026. Current version: 2026-10-26.
01
The data controller is ETHIUNI LLC (TIN 01387425), registered in Armenia and operating in Yerevan.
Contact: vahan@ethiuni.ai.
02
The form states, right under the input: "By sending, you agree to the conversation being saved and passed to the AI provider (DeepSeek, China). At this construction stage the team reads the conversations. Please do not share confidential or sensitive personal information." Sending a message is the act taken under that notice, and it is your consent (§04); it holds for every message, not only the first.
Construction phase — said plainly. At this stage the Ethiuni team reads every conversation, not a sample, and it is a person reading, not only automated processing. The reason is simple: the environment is still being built, and the conversations of the first joiners are what show us what works and what does not. This is a temporary state and it is declared, not assumed: by starting a conversation you are agreeing to exactly this. If you would rather your conversation not be read, do not start one — write directly to vahan@ethiuni.ai.
A Roundtable is shared by its very form: what is put on the table is seen by those seated at it — the way what is said around a table is heard by those around it. That is a property of the format, not a separate setting. When two people sit down at one Roundtable for the first time, we sit there too — not as observers, but as the ones holding the form so that the first table actually happens.
To generate a reply, the conversation content is sent to the AI service provider (§05, §08). Every reply from Ethi carries an "AI-generated reply" label and may be inaccurate. Stored with the conversation are also the source label from the link (the “source” parameter in the address), any “utm” parameters, and the name of the referring site, where these exist. The source label, utm parameters and referring site are conversation metadata, not personal data: no IP address, no device identifier, no third-party cookie.
The name, organization, and role given at the start of the conversation (optional); the return contact method and its address (email, phone, or Telegram); the full record of the conversation; and the IP address — held only in rate-limit and security logs, never attached to an individual message.
PoC application. When you send a PoC application, we keep what you confirmed in the panel: the problem, how it is done today, what is at hand, the success criterion, the role of the person who decides (not their name) and, if you gave it, a rough build budget and timeline.
If you are signed in, the conversations started in this browser are linked to your account automatically. If a conversation is already linked to another account, the link is not changed.
Your conversations, from any device. When you sign in with your verified email, you can open and continue, from any device, the conversations linked to your account, as well as those the team has linked to your participant page. A new message, sending to the team and the Scenario are written into the same conversation; from one conversation the team receives one message, however many devices you use. No one else's conversation opens this way.
A conversation can be continued on the device where it took place, or from your account if you have linked it to your account.
The summary of the getting-acquainted conversation ("who you are, what you want to create, what opens doors for you, how you work, what does not belong in your work") is today not stored separately: it is part of the record it belongs to and follows that record's retention period (§06). A separate retention period has not been set yet, so there is no separate storage.
Scenario — only what you confirm is stored. When you close a Roundtable with a Scenario, Ethi proposes its fields from the conversation (its name, what it is for, what, why, how, its core, and in what form the result comes back to you), and you see, change and confirm them. Ethi's proposal is not stored: exactly what you confirmed is stored, and only after you press "Confirm". When the Roundtable closes, the confirmed Scenario becomes part of your Environment: it is yours, it is kept until you delete it, and you delete it by your own hand once it carries no live Roundtable. A copy of what you confirmed is kept for the same 90 days as the conversation record (§06), counted from the moment of confirmation.
03
We use the data to formulate the problem precisely, to get back to you through the channel you gave, and to prepare for a possible study.
04
The legal basis is consent: the form states, right under the input, "By sending, you agree…" (§02), and sending a message is a positive act taken under that notice, not a default assumption. That consent covers the transfer of the conversation content to the AI model provider, DeepSeek, in China (§05, §08).
05
(a) Ethiuni's internal team, for review; (b) the AI model provider, DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd., China), to generate a response; (c) an email/SMTP service, to deliver the notification. For how DeepSeek uses data, see its privacy policy: DeepSeek Privacy Policy, and its API terms: DeepSeek Open Platform Terms of Service. These documents do not separately state how long data received through the API is kept or whether it is used to train models (checked 2026-10-26).
06
Two separate classes, two separate numbers. The conversation record is kept for 90 days from the last activity, then deleted automatically, based on the file's modification date. If a conversation is linked to your account and you close the account, the link is removed at once and the conversation record enters a deletion queue: the deletion is confirmed by the responsible person and happens no later than the 90-day period above.
The inquiry record — the name, the contact detail, and the conversation record registered with it — is kept for 730 days (24 months) from the last contact.
These two periods are part of our adopted internal retention policy. If the law of the Republic of Armenia sets a longer minimum retention period for any class, that class follows the law.
A confirmed Scenario in your Environment has no retention limit: it is kept until you delete it (§02).
07
You can request access to your data, ask for it to be corrected or deleted, or object to its processing. You can also file a complaint with the Personal Data Protection Agency of the Republic of Armenia, which sits within the Ministry of Justice.
To exercise these rights, write to the address given in §01.
08
The content of the conversation is transferred to China, to the AI model provider DeepSeek (§05), to generate a response — this is an international transfer of data outside Armenia.
The transfer is carried out with your explicit consent (§04).
09
The site sets no cookies — neither its own nor third-party, advertising or analytics ones. Your browser's local storage (localStorage) keeps what is needed to continue a conversation and stay signed in on this device, and your theme choice; it is used only while you work with our site. Visit analytics, where used, come from the server's access logs. If you arrived at the conversation page through a link carrying a source label (the "source" address parameter), that label and the referring site's name are stored with the conversation as metadata.
Before daily statistics are stored, the visitor's IP address is pseudonymised (replaced by an identifier that changes daily) — the raw IP is not retained in the stored analytics summaries. The server's access log itself keeps the raw IP for a limited time, for operational and security purposes, and is rotated.
10
Administrative access has no public exposure. Outgoing email uses STARTTLS.
In the event of a security incident, we follow a written procedure covering detection through notification and recovery; no specific time figure is stated here, pending confirmation from a primary source.
11
This environment is built within the framework of two international standards — ISO/IEC 27001 (information security management) and ISO/IEC 42001 (artificial intelligence management system). For us they are a way of working, not a label.
In practice, here is what reaches this page from that framework: the provider is named (§05, §08), the retention period is written as a number (§06), administrative access has no public exposure (§10), the deletion path is open (§07), and every change carries a date (§12).
We hold no certificate, and nothing on this page claims otherwise. The formal impact assessment, and putting vendor management into written form, are still organizational work in progress — not a finished fact.
12
This notice took effect on July 29, 2026, and was last updated: 2026-10-26. Any future change updates this date.