Privacy
We collect only what we need to answer you and to do the work. No more.
We do not sell or rent your information, and we do not use it for targeted advertising or behavioural profiling.
What we collect, and why
| Where | What is collected | What for |
|---|---|---|
| Visiting the site | Browser, device and the page requested, in the host's ordinary request logs. On a form submission, a one-way hash of your IP address; the address itself is never written down. | Keeping the site up and stopping automated submissions |
| The brief and the contact form | Your name and email, and — where you fill them in — phone, organisation, role and website. The project type, budget range and timeline. Your three written answers, and any files you attach — PDF or Word, up to 20 MB each. | Reading the brief before the meeting and replying to the enquiry |
| A booked meeting | The time you pick and your time zone. | Holding the meeting and sending the calendar invitation |
| The chatbot | The text of your messages and anything you choose to type into them. On Telegram, also your chat ID and Telegram account name. | Answering, and handing you on to the human team |
| A live project | Documents, images and brand archives; contract and invoicing details. | Doing the research and the design, and invoicing |
We do not collect sensitive information — personal financial data, card numbers, identity documents — through the website or the chatbot. Please do not enter it in these channels.
The chatbot: where the data goes
The chatbot on this site and the studio's Telegram bot (@DaryaDesignStudio_bot) are one AI assistant. To produce a reply, the text of your message is sent to Mistral AI, a company based in France, and processed there — both to write the reply and to search the text of this site. Sharing data to improve the models is switched off on the studio's account, so your messages are not used to train the model. Conversations are stored, so that you can pick them up later and the studio can read them and improve the answers; for at most six months, then they are deleted automatically. If you write on Telegram, your chat ID and Telegram account name are kept too, so the reply goes back to the same chat; the message passes through Telegram's servers before it reaches us, under Telegram's own privacy policy. If you register a consultation request in the conversation, those details are kept as a brief and are not covered by that limit.
- Do not type confidential information, business documents or other people's personal data into the chatbot.
- You can talk to the human team instead at any point; how to reach us is at the end of this page.
The chatbot answers informally and does not bind the studio — the “Limits of responsibility” clause on the terms page sets this out.
Project material: where it is kept and who can open it
Project files and correspondence are kept on services with restricted access. Attachments sit in a private bucket with no public address and open only through a short-lived signed link from the studio's panel. Access reaches only team members and the collaborators on that project.
Our commitment to hold this in confidence, and how it sits with an NDA and the right to show the work, is set out under “Project confidentiality” and “Ownership and the right to display” on the terms page.
Who we share it with
Only with these, and only as far as is needed. The services the site, the email, the hosting and the chatbot run on:
- Supabase — the database and the attachment storage, on servers in Tokyo.
- Vercel — hosting for this site.
- Resend — sending the confirmation emails.
- Google Calendar — when calendar sync is switched on, a booked meeting is placed on the studio calendar with your name, email and the meeting time.
- Mistral AI, France — chat messages are sent there to write the reply and to search the site's text, not to train the model.
- Telegram — if you use the studio's Telegram bot, your messages pass through Telegram's servers.
And outside those services:
- Project collaborators and contractors, under a confidentiality commitment.
- An accountant or a legal adviser, as far as financial and contractual records go.
- Authorities, where the law requires it.
Cookies and visit statistics
This site sets only the cookies it needs to work: the language you pick, and the sign-in session for the studio panel. There are no analytics or advertising scripts on the site, and we do not follow you across other sites. You can restrict or delete cookies in your browser settings; parts of the site may then stop working correctly.
How long it is kept
| Kind of information | How long |
|---|---|
| Briefs and messages that did not lead to work | Up to 12 months |
| Chatbot conversations | Up to 6 months |
| Project documents and files | Up to 5 years after the project ends |
| Financial and contractual records | As long as the law requires |
Chatbot conversations are deleted automatically after six months. The other periods are upper limits, and the deleting is done by hand. Ask sooner and it goes sooner.
Security
No system is completely secure. If a breach touches your information, we tell you and the relevant authorities at the first opportunity.
Your rights
You can ask us to:
- Tell you what we hold about you, and give you a copy.
- Correct anything that is wrong.
- Delete it — the brief, the attachments and any booking — unless the law or a contract requires us to keep it.
A booked meeting you can also cancel yourself at any time, with the link in your confirmation email.
We answer within 30 days.
Links off this site
Our work and our profiles are also on Behance, Instagram and LinkedIn. Following those links takes you off this site, and from there those platforms' privacy policies apply, not this page.
Children
Our services are for businesses and organisations. We do not knowingly collect information from anyone under 18.
Changes and contact
Every change is announced on this page with a date and a new version number. Where a change is substantial, we tell the people whose email address we hold.
To ask for access to your information, for a correction or for its deletion, write to us from the contact page.
Version 2 — last updated: 29 September 2026