Privacy notice

This notice describes what Datailo does with personal data. Each category below is something the service actually stores. If we stop storing one, this page changes.

Who we are

Kiznis Studio, the operator of datailo.com, is the controller of the personal data described here. You can reach us at hello@datailo.com.

What Datailo is, in data terms

Datailo is a hub. It connects your AI assistant to separate services (today Victano, Rekvira and Avokata) through one MCP connection. It keeps what it needs to know who you are and which services you switched on. The work you do in a service, such as searches, profiles, assessments and documents, is stored by that service, under its own privacy notice, and not by the hub.

What we collect, and why

• Your account. Your email address. Used to create and sign in to the account. Lawful basis: performance of a contract, Art 6(1)(b).
• Sign-in emails. The confirm link and the six-digit code in the sign-in email, each stored only as a hash, with the address and language the email went to. Valid for 15 minutes. Art 6(1)(b).
• Keys and sessions. Your dat_ key, stored only as a SHA-256 hash, and the binding between your AI’s connection and your account (30 days). When your client signs in with OAuth, the one-time authorisation code is stored only as a hash. Art 6(1)(b).
• Service links. For each service you enable: its name, the state of the link, the account id the service gave us, and the service’s key for that account, encrypted at rest. Art 6(1)(b).
• Plan state. Which plan you hold at each service, as the hub and the service report it. Art 6(1)(b).
• Call records. For a call through the hub: time, account, service, tool, whether it succeeded, how long it took, and whether it came from our own testing or monitoring (a label, not your address). Never the arguments you sent and never the result. Legitimate interest in running and measuring the service, Art 6(1)(f).
• Usage counts. From the call records we count, in aggregate, how many distinct accounts used the hub in the last 7 and 30 days; only those totals leave the service, and calls from our own testing and monitoring are left out. Art 6(1)(f).
• Feedback. If you send feedback from your AI assistant, only what you chose to send (the text, optional context and reply address, the tool and service it concerns) with the sending account, or a one-way hash for a caller without an account (items sent before 14 October 2026). It is emailed to our team, and feedback about a service is passed to that service. Kept 24 months, deleted with your account, or sooner on request. Art 6(1)(f).
• Messages from us. Our replies to your feedback, questions about it and service notices are kept in your hub account’s inbox, with whether you read, dismissed or answered them; your answers join your feedback item. For services you enabled, the hub asks each one only how many unread messages you have there and their titles. We email you only when we reply to your own feedback (you can turn that off), never marketing. Kept 12 months, deleted with your account; without an account (before 14 October 2026) you see service notices alone, kept 14 days. Art 6(1)(b).
• Client records. For each MCP connection: the name and version your AI client reports, how it signed in (header, key in the address, or none), and how many requests it made, stored under a hash of the connection id and a hash of the credential. No email, account or network address. Used to keep each client’s sign-in working. Art 6(1)(f).
• Access logs. The web server’s request log, with the IP address shortened before it is written and cookies and authorisation headers removed. Kept 14 days. Art 6(1)(f), for security and abuse handling.

Every call needs an account with a verified email address; registration is free on the beta plan. A request made without signing in is refused.

Linking your account to a service

Enabling a service is your instruction to Datailo to find or create your account at that service with the same email address and to keep an encrypted key for it. Disabling it revokes that key. Your account and your data at the service stay yours. For a service that has accounts, enabling it sends your email address and your hub account id to that service, which is the only personal data the hub passes on. A service without accounts (Rekvira today) receives nothing that identifies you.

What we do not do

No cookies and no analytics scripts on this site. If you press the theme switch, your light or dark choice is kept in your browser’s local storage; it never leaves your device and clearing this site’s data removes it. We do not sell personal data, use it to train models, build advertising profiles or enrich it from other sources.

How long we keep it

Account data, including call records, lives as long as the account. Sign-in links and codes expire after 15 minutes, deletion confirmations after 24 hours. Access logs are kept 14 days. Client records carry no email, account or address and are not yet deleted on a schedule; you can ask us to remove them.

Export and deletion

Your AI can fetch everything the hub holds about you from /api/account/export with your key. To delete the account, ask your AI or write to us. We email a confirmation code, because a request typed into a chat is not proof that the account holder wants it gone. Confirming removes the hub account, keys, sessions, links, call records and feedback in one step. Your accounts and data at each service stay there; delete them at the service.

Who else processes it

A short list of providers, with what each does and where, is at /legal/subprocessors. Where a provider is outside the EEA, transfers rely on the European Commission’s standard contractual clauses.

Your rights

You can ask for a copy of your data, to correct or delete it, to restrict or object to its use, and to receive it in a portable form. Write to hello@datailo.com; we answer within one month. You can complain to the Lithuanian State Data Protection Inspectorate (VDAI) or to the authority where you live.

Changes

Material changes are announced on this page with the date of the change, rather than by quietly replacing it.