Privacy Policy

This explains how Vondet ("the Service") handles personal information.

Effective: August 11, 2026 · Last revised: November 5, 2026

About this document

The Service follows Japan's Act on the Protection of Personal Information, and is priced and offered in US dollars for the markets we serve today. We have not yet expanded to the European Economic Area or the United Kingdom. We do not price or communicate in EEA or UK currencies or languages, and we run no EEA- or UK-directed advertising. When we do expand there, we will first put the corresponding safeguards in place — an EU/UK representative and the applicable data-subject rights — and say so here.

Operator

Operator: Hatobash
Contact: Contact form

* Ask through the contact form and we will tell you the operator's name and address without delay.

What we collect

These are the kinds of information the Service collects (the examples are the main ones).

Account information

Your email address; your display name; your role (required) and how you heard about the Service (optional); how you signed up (email link, Google or GitHub); the identifier issued by our authentication provider (Supabase Auth); how you first arrived at the Service (the short tags carried by the link, the first page you viewed, and the referring site's domain name); and which versions of the Terms you agreed to and of the Privacy Policy you acknowledged. If you sign in with Google or GitHub, we receive from that provider your name and email address, plus basic public profile information such as your profile image URL, your username and your account ID with that provider. Of these, only your name (on GitHub, sometimes your username) and your email address are used on screen; the rest only stays in the sign-in records (we do not ask for any other information or for access to your repositories). The Service is built without passwords. If an email address with no account is entered on the sign-in screen, we send one email to that address saying that no account was found, so you can check which address you signed up with. To stop many of these arriving at the same address in a short time, we record values derived from that email address and from the IP address you connect from, in a form that cannot be turned back into them, and erase them after 90 days (we do not store the email address itself).

What you write on the board

Everything written on the board — boards, goals, tasks, decisions and so on — and the history of changes to it (including the content before and after each change). Today only you can read it; there is no way to invite anyone yet.

Records of how the Service is used

What you do on screens and with tools; calls from an AI (including calls that only read and change nothing — we do not keep the response itself); creating and using connections to an AI (including issuing a token, and the name and version of the AI application that connected with it); when you signed in; the steps passed on the way to a purchase; reaching a limit; which prompts were shown and pressed; and which notices you closed or read (so the same notice is not shown again).

Payment records

If you take a paid plan: the plan, and the state of billing and payment. Card numbers are held by the payment provider, not by the Service.

Questions and feedback

What you send from the screen or through the contact form, its kind and the screen it came from, and your answers to the satisfaction survey and to the question of why you are cancelling or leaving. What you send from the screen is recorded linked to your account — except the reason you give when deleting your account, which is recorded tied neither to your account nor to your email address, and to the day only. What you send through the contact form is not stored in the Service's database; it arrives in the operator's email inbox. We use your questions and feedback to deal with them and to reply to you (for feedback sent from the screen, acknowledgements and replies go to the email address you registered with; replies to the contact form go to the email address you entered there).

Device and connection information

The Service's own server logs (which may include the request URL); the access logs our hosting provider (Cloudflare) keeps to prevent attacks (the Service does not use these for analysis); and values derived from the IP address you connect from, in a form that cannot be turned back into it (to stop repeated sign-ups and submissions in a short time). The records the Service itself creates do not store the IP address itself. Each time you sign in, we record only the type of browser and operating system you use (for example, Chrome and macOS), linked to that sign-in, so that you can see which devices are signed in and sign out of ones you no longer use. We do not link the full browser identification string, version numbers, or any other device information to your account. Separately, the sign-in system (Supabase Auth) keeps the IP address you connect from and information about your device as a record of sign-ins, to prevent unauthorised sign-ins.

Security records

To notice and investigate unauthorized sign-ins or actions you did not take, we record the following events as "when, which account, what was done or refused": signing in; issuing and revoking connection keys and tokens; changing which boards an AI can reach; authorizing and revoking an AI app's connection; exporting data; deleting an account or board; and changing plans (on team plans, also adding and removing members and changing roles). Board content (goals, tasks, decisions and board names) is not included; boards are recorded by number. IP addresses and device information are not included either. By default, these records are deleted automatically after 180 days. We look at these records only when you ask us to, or when a security investigation requires it.

If you join the waitlist

Your email address, the language you were reading, which consent wording you agreed to and when, and a token used for unsubscribing. Once an address is unsubscribed, it stays unsubscribed even if submitted again. If you ask us to delete the record itself, the record of the stop goes with it.

How we use it

The Service uses the information it holds for the following purposes.

Providing the Service (registering and signing you in, storing and showing your board, connecting to AI, processing payments)
Dealing with your questions and feedback, and replying to you (for feedback sent from the screen, acknowledgements and replies go to the email address you registered with; replies to the contact form go to the email address you entered there)
Investigating faults and preventing abuse
Analysing how the Service is used, and improving it, considering new features and introducing them on that basis (this includes analysing, per account, how screens and features are used and which prompts led to a purchase)
Understanding how people came to hear about the Service, and deciding where to focus how we introduce it
Important notices, such as changes to the Terms or this policy

We do not serve advertising, we do not track you for advertising, and we do not follow you across other sites. What you do inside a board is not sent to any third-party analytics service (for the web analytics on our public pages, see "Information sent from your browser").

Of the purposes above, the records kept for providing the Service and preventing abuse cannot be turned off; without them the Service does not work. If you would rather your usage were not used for analysis to improve the Service, tell us through the contact form and we will leave you out of it from then on.

About AI

The Service lets an AI you connect (such as Claude) read and write the board. To connect, you either approve the connection on a permission screen, or place a connection token you issue yourself into the AI's settings. Once connected, board content is available to that AI, and how it is handled from there is governed by your agreement with that AI's provider. If you have not connected in either way, no AI can see the board, and you can remove a connection from the screen at any time. If we later add features where the Service itself sends data to an AI, we will update this policy and the list of processors first.

Requests to GitHub

If a task on your board carries a GitHub issue or pull request URL, the Service asks GitHub whether it is closed — each time an AI you connected reads the board (at most 12 per read). We send only the owner, repository name, and number taken from that URL — nothing that identifies you. The request is made under the Service's own account, so your IP address is not passed to GitHub. Note that if the URL points to a private repository, its name is part of that request. Separately, if you sign in with GitHub, we treat GitHub not as our processor but as an authentication provider you chose yourself.

Information sent from your browser

When you view our public pages (the intro, pricing, articles and help), your browser sends the following. Board screens do not send it.

Recipient: Cloudflare, Inc. (Cloudflare Web Analytics)
What is sent: the URL of the page viewed, the referring page, your browser, operating system and type of device, and your IP address (which Cloudflare uses to infer your country; it is not passed to us)
Purpose: to learn which pages are viewed and from where, so we can improve the site
No cookies are used, and it is not used for advertising.

While the contact form is shown on the contact page, your browser sends the following so that we can check you are a person. Other pages do not send it.

Recipient: Cloudflare, Inc. (Cloudflare Turnstile)
What is sent: your IP address, information about your browser and device (such as the User-Agent and characteristics of the connection), information about the site being shown, and the result of checks run in your browser to tell people from bots
Purpose: to keep automated (bot) submissions out of the contact form. Cloudflare also uses this information to improve how it tells people from bots. We do not use it for advertising.

Using content, and turning it off

Your board content is yours. We handle it only to run the service — to display and store your boards, to carry your exchanges with the AI you connect, to investigate bugs, and to respond to abuse. Unless you turn on “Help improve the product,” we do not use content to improve suggestions (it is off by default). Only when it is on do we anonymize board content and may use it to improve suggestions; you can turn it back off any time, and once off we no longer use content to improve suggestions. Usage signals — which screens are opened, how often a tool is called — are handled separately from content and are not covered by this setting (their use follows the Purposes). We never sell content to third parties. If improving suggestions ever requires handing content to an outside processor, we add that processor to the list of processors first.

Processors and overseas transfer

The Service does not sell or provide personal information to third parties. To provide the Service and deal with your questions, among other things, the Service may entrust the handling of personal information to outside providers. This may include processing such as summarising and sorting the content of questions with AI. The names of these providers and the countries they are in are listed in "Our processors".

All of our processors are located outside Japan. The names of the countries data is transferred to, and each provider's published information about the regime there, are in the list of processors (APPI Article 28). Our processors

Disclosure, correction, deletion

On your request, we will disclose the information we hold, correct it, and stop using or delete it (APPI Articles 33–35). Contact us through the contact form. As a rule, we respond within 30 days of receiving your request. To handle your request and keep a record of it, we record a reference number, the dates we received and completed it, and the email address you made the request from. This record is not linked to your account; the email address is erased 90 days after we finish handling the request (the reference number and dates remain as the record of how it was handled).

You can delete your account yourself from the screen. Deleting it removes your board, goals, tasks, decisions and connection tokens (including any connection URL containing a token that you issued earlier), and what we record linked to your account (your account information, your feedback and survey answers, records of how you used the Service, and so on) — except payment transaction records that the law requires us to keep. Once your account is deleted, your data can't be restored. When you delete it from the screen, we send one email to the address held just before deletion, so that a deletion you did not ask for does not go unnoticed; after it is sent, we no longer hold the address. Totals that do not say who you are (such as counts) remain after deletion. Records held in the sign-in system (Supabase Auth), which may include the record of any connection to an AI you approved on a permission screen (we revoke that permission when you delete your account), are erased automatically, as a rule 7 days after deletion. Your waitlist entry, if you had joined the waitlist, is not removed by anything you do on the screen. If you want it removed, tell us through the contact form; as a rule, we will remove it within 30 days of your request. If you have made a request such as a disclosure request, that record is kept separately from your account and erased on the schedule described under "Disclosure, correction, deletion" above. Even after deletion, some data remains for a time in server logs and backups; these are removed once their retention period passes — logs within 90 days, security records 180 days by default, backups up to 30 days. Messages sent through the contact form are erased from the operator's email inbox one year after we finish dealing with them. The values we keep to prevent repeated sign-ups, repeated emails to the same address, and repeated contact-form messages in a short window are erased automatically after 90 days. The value derived from an email address can be found and deleted if you tell us the address — contact us through the contact form. The value derived from your IP address cannot be deleted on request: we hold no way to link it back to you.

Safeguards

All traffic is encrypted (HTTPS).
A connection token is stored only as a fingerprint (a transformed value). After it is shown once at issue time, we cannot read it back out of our database. The token itself is the secret, however, so if it may have been seen by someone else, revoke it from the screen and issue a new one. A revoked token stops working immediately. The same applies to any connection URL containing a token that you issued earlier.
Boards are isolated per owner; you cannot read anyone else's board.
The Service is currently run by one person, with no other staff.
The Service's server logs may include the request URL. If you connect with a connection URL containing a token that you issued earlier, that URL can end up in them. If you have reason to think that happened, revoke it from the screen and issue a new token — a revoked one stops working immediately.

Cookies and other browser storage

The Service uses cookies to keep you signed in (a session cookie, plus — only during sign-in — one that remembers where to send you back and one that carries the source tag from the link you followed), to remember how you first arrived (for 30 days: only the short tags carried by the link (ref and the utm_ parameters), the path of the page you landed on and the referring site's domain name, never your name or IP address; it is deleted once you have finished signing in, and kept if we had to turn your registration away, so it is still there when you come back), and to remember your display language. It does not use them for tracking or advertising, and does not send them to any third party other than our processors. It used to store a visit timestamp in a cookie as well, to show what changed since your last visit; we stopped storing it on 27 August 2026 and clear any already stored on your next visit. Today, to show what changed since you last opened a board, we record when you last opened each board with your account rather than in a cookie (it is removed when you delete your account). The web analytics on our public pages uses no cookies.

Besides cookies, the Service holds a connection token you have just issued in your browser for a short while. The same token can never be shown again, so this keeps it from being lost if you move away from the page before you have pasted it. It is held in storage that lives only inside that browser tab (session storage), kept separately for each board. We do not send what is held there to our servers for analysis or any other purpose, except that a token left unused — for example when you close the setup partway through — is sent to our servers so that it can be revoked immediately. It is erased when you finish the connection setup by pressing “Start using it” or when you close that tab. It is not used for tracking or advertising.

Changes to this document

If we change the contents, we will post the updated content and the effective date on this page before that effective date. For changes that significantly affect users, we will give notice a reasonable time in advance, on this page or by other appropriate means.

Japanese and English versions

The Japanese version of this page is the original; the English version is a translation. If the two differ, the Japanese version governs.

← Back to the intro page Terms of Service