Privacy Notice

Beta · Version 2.0 · effective 5 October 2026 · version 1.0

AgentoNest runs on your machine. We do not host your household’s data, cannot read it, and could not hand it over if we were asked to. This notice describes the few things that do reach us — all of them because you chose to send them.

1. Who is responsible

Oleksii Kulinich, Coswig, Germany — reachable at support@agentonest.com. He is the controller for this website and for anything you deliberately send to support.

For the data inside your own installation, you are the controller. It sits on hardware you control, and we have no access path to it.

2. The website

Visits are measured with Umami, an analytics tool we host ourselves on our own server. It is cookie-free: nothing is written to your device and nothing is read from it, so there is no consent banner to click away — under § 25 TDDDG (formerly TTDSG) consent is required only for storing or reading information on a device, and Umami does neither.

What it records for each page view: the page address including any parameters in it (for example a campaign tag), the page title, the page that linked here, the browser, operating system and device type, the screen size, the browser’s language, the time, and an approximate location — country, region and city — looked up from your IP address at the moment of the request. The IP address itself is not stored.

Returning visits. To count visitors rather than page views, Umami turns your IP address and browser into a one-way hash, using a secret that changes at the start of every calendar month. Within a month, a second visit from the same device counts as the same visitor; from the next month on it cannot be linked to the earlier one. There is no cross-site tracking, no advertising network and no profile.

Events. A few actions are counted: pressing a download button (with the platform and where on the page it was), whether the download that followed worked, and sending the form for asking to take part (whether it went through). Nothing you type into a form is part of an event.

Your account pages are not measured at all. The pages for signing in, joining, resetting a password and managing your account (/login, /join, /verify, /forgot, /reset, /account, /authorize) load no analytics script, are kept out of search engines and send no referrer to anybody.

People and programs. A browser that reports itself as remote-controlled — automation tools set a flag for this — is labelled as automated, so such visits can be told apart from people’s.

Do Not Track and Global Privacy Control. If your browser sends either signal, Umami’s script records nothing about your visit: no page view, no event, nothing that describes you. The only trace is the one described next — our server counts that a page was opened with the signal, and when.

The web server’s own log. Like any web server, ours notes each request to this site: the time, the page, the response code, and the headers your browser sends to describe itself — the browser name, whether a language preference was given (not which one), and the privacy signals above. It contains no IP address and no cookies. It is kept for 35 days and used for one thing: counting, per day, how many page views came from people’s browsers and how many from programs such as search engines, AI assistants, link previews and scripts, and how many asked not to be tracked. These counts are shown in our self-hosted Umami as anonymous entries, one per page view: the page, the time and the kind of client (for a program, the name it publishes) — never an address, a browser description or anything else about a person. The legal basis is our legitimate interest in running the site and understanding how it is read (Art. 6(1)(f) GDPR). The same holds for every service on our server: its logs contain no IP addresses.

Because this measures the website, location figures describe visitors. They say nothing about who installed anything.

3. The application

The installed application sends us nothing about your family. No analytics and no usage beacons. Apart from the services you connect yourself, it talks to us for one purpose: keeping itself current. It asks our server whether a newer release exists and downloads updates and the parts of AgentoNest it runs, presenting the key of that computer (see section 7). With each such request we record when that key was last used and the version the application reported — nothing else, and no IP address.

One optional exception: the install ping. During setup you are asked — in a separate, unticked box, apart from accepting the Beta Terms — whether the installation may announce itself. If you say yes, and only then, it sends five things: a random identifier generated on your machine, the application version, the operating system family (windows / macos / linux), the release channel, and the edition number of the terms you accepted (a figure such as the one printed at the top of the Beta Terms, so we can see whether a changed edition has actually reached people). Nothing else is accepted — the receiving service rejects any field it was not expecting.

What it deliberately does not contain: no name, no hostname, no language or locale, no country, no household data, and nothing derived from any of it. Your IP address is not stored — it is needed to deliver the request and is discarded, not written down. The identifier is random and cannot be traced back to you by us.

Why we ask. To know how many installations exist and which versions are still in use, so an old release is not dropped while people are still running it. The figures stay internal — they are aggregate counts we read ourselves, not something published on this site or anywhere else.

Saying no costs you nothing. Refusal is the default, blocks no feature, and is not asked again. You can turn it on or off later in the settings. Legally this is consent under Art. 6(1)(a) GDPR and § 25(1) TDDDG, and consent can be withdrawn at any time with effect for the future. Ping records are kept for 400 days and then deleted.

4. Fix requests and feature ideas

You can ask, from inside AgentoNest, for a bug to be fixed or a feature to be built. This is a service we offer, not an obligation we owe — see section 6 of the Beta Terms for what sending grants us and what it does not.

What is sent. The text you write and the diagnostic context you attach, plus a random identifier for your installation so that several requests from the same household can be read together. That identifier is a random value; it contains no name, no address and nothing derived from your data.

You see it before it goes. Nothing is transmitted silently. The request is written down locally first, you are shown the exact text that would leave the machine, and it goes only when you confirm. If you never confirm, it stays on your disk and reaches no one.

Keep sensitive material out of it. Do not paste passwords, tokens, account numbers, medical details or documents into a request. A description of what went wrong is enough; the underlying records are not needed and we would rather not receive them.

What it is used for. To improve AgentoNest for everyone who runs it — a fix you report ships to every installation, a feature you suggest becomes part of the product. Requests are not used for advertising, not profiled, and not sold or passed to anyone else.

Who sees it and for how long. Requests land in the vendor support inbox and are read by the maintainer. They are kept while the request is open and for up to twelve months after it is closed, then deleted. You can ask us to delete one sooner at any time, without giving a reason.

5. Services you connect yourself

A bank, a calendar, a mailbox, a cloud AI model — each is off until you switch it on, and each then runs under that provider’s own terms and privacy policy, not ours. The connection is between your installation and that provider; it does not pass through us. Local models send nothing outward at all.

6. Asking to take part

There are two ways to ask. If you write to us through the form on the home page — the way that needs no account at all — we keep what you typed: your first and last name, your email address and your message. We keep it to answer you and to send you an invitation, and for nothing else — it is not used for advertising, it is not passed to anybody, and it does not become an account until you register.

Or you can create an account first and ask from it, which is described in section 7. Then what we hold is the account, plus the fact that you asked, when, and the one line you chose to write.

The legal basis is our legitimate interest in answering somebody who asked us a question and in running the closed beta (Art. 6(1)(f) GDPR). We keep an application until we have invited you or until it is clear the beta is not going ahead for you, and at most twelve months. You can ask us to delete it sooner at any time, without giving a reason, and we will.

7. Your beta account

Anybody can create an account; using AgentoNest is a separate answer, because the beta is closed. So two different things are recorded about you here. We store the email address you give us, which edition of the terms you accepted and when, the invitation it was created from if there was one (and who sent it, if it came from another family), and — if you ticked the separate box — that you agreed to receive product news, together with the exact wording you were shown. That last part is kept as evidence: without it we could not show, later, that a message we sent you was one you had asked for.

Whether you are taking part is recorded separately: that you asked, the date you asked, the one optional line you wrote about why, and our answer. We keep the answer even when it is no, so that you are not asked the same question twice and so it can be checked later that you were in fact answered. An account that was created and never asked for anything holds nothing — no installer, no connected computer, no invitations — and is deleted after 90 days.

Your password is never stored. We keep a one-way scrypt hash of it, from which the password cannot be recovered — by us or by anybody holding a copy of our database. A link to set a new password works once and for 30 minutes.

Staying signed in. When you sign in, the website sets one cookie, __Host-agn_session. It holds a random value and nothing else, is sent only to agentonest.com over an encrypted connection, and cannot be read by scripts. It is strictly necessary for the account you asked for, so it needs no consent (§ 25(2) No. 2 TDDDG). With each signed-in browser we keep: when you signed in, when it was last active, and a coarse description such as “Firefox · Windows” so you can recognise it in your list — no IP address and no full browser string. A session ends after 14 days without use and in any case after 30 days; you can end any of them on your account page. Ended sessions are deleted 30 days later.

Signing in with Google — optional. Beside your email address and password you may choose “Continue with Google”. It is entirely optional: every account can be used with a password alone, and nothing on these pages contacts Google until you press that button.

If you do, two things follow. Google learns that you sign in to AgentoNest, and when — that is unavoidable, because it is Google that asks you to confirm; what happens on their side is covered by Google’s own privacy policy, not by this notice. And we receive three things from Google about you: a stable identifier for your Google account, your email address, and whether Google reports that address as verified. We store the identifier and the address, so that the next sign-in finds your account and so your account page can show which Google account is connected. We ask Google for nothing else — not your name, not your picture, not your contacts, no access to anything in your Google account — and we receive no standing permission: the exchange happens once, at sign-in, and leaves us nothing we could use afterwards.

The second cookie. Starting a Google sign-in sets one more cookie, __Host-agn_oidc. It holds a random value, nothing else, and lives at most ten minutes — it is deleted the moment the sign-in finishes, successfully or not. Its only purpose is to ensure that the sign-in coming back from Google is the one that left from your browser. Like the session cookie it is strictly necessary for the function you asked for (§ 25(2) No. 2 TDDDG).

You can connect Google to an existing account, or disconnect it again, on your account page at any time. Disconnecting removes the identifier and the address from our side; it tells Google nothing, and if Google is the only way into your account we ask you to set a password first.

Your computers. When you sign in the AgentoNest application through your browser, that computer receives its own key. We store, for each one: the name the application reports (your computer’s name, shortened to 60 characters — you see it on the page before you allow it), its operating system family, when it was connected, when it last fetched an update and which version it reported, and whether and when it was disconnected. Only a one-way hash of the key is stored. Keys from the beta’s first months and any hand-entered keys issued before that route was retired are listed the same way.

Security records. To protect accounts from password guessing we count failed sign-ins per address — under a one-way hash of the address, not the address itself — and delete the count a day after the last attempt. We also keep a log of security events on your account: sign-ins, failed sign-ins, password changes and resets, computers connected and disconnected, sessions ended. It contains no IP address, no password and no key, and is kept for 12 months. You will also get an email whenever your password changes or a new computer is connected.

Legal basis. The account itself, signing in — with a password or with Google, whichever you choose — your computers, the emails about your account (confirmation, password, new computer) and messages about your own support requests are the performance of the beta agreement (Art. 6(1)(b) GDPR). The failed-sign-in counter and the security log rest on our legitimate interest in keeping accounts secure (Art. 6(1)(f) and Art. 32 GDPR). Product news is sent only on your consent (Art. 6(1)(a)), which you may withdraw at any time on your account page or in one click from any such message; withdrawing it does not affect anything else.

Email is delivered through a service provider inside the EU, engaged as a processor under Art. 28 GDPR.

We keep the account for as long as you take part in the beta, and for a period afterwards only where record-keeping obligations require it.

8. Inviting another family, and downloads

Invitations. You can create a few invitation links on your account page and pass them on yourself. We do not ask who a link is for and send nothing to that person: we store only that you created an invitation, when, and whether it has been used. The person you invite tells us their email address themselves if and when they register, and that becomes their own account. An invitation we send by email comes only from us, to somebody who asked to take part (section 6) or whom we invite ourselves.

Downloads. Installers are served from our own server to your signed-in account, and each download is recorded against it: which file, which version, and when. Updates for the installed application, and the parts of AgentoNest it runs, come from our own server too, against the key of the computer asking (section 3).

9. Your rights

Where we do hold something about you — your beta account, your computers and sessions, your download history, an invitation, a support request you sent us — you may ask for access to it, correction, deletion, restriction of processing, portability, and you may object to the processing. Much of it you can see and change yourself on your account page: your computers, where you are signed in, your invitations and whether you receive news. Write to support@agentonest.com; we answer within one month.

You may also complain to a supervisory authority. For us that is the Saxon Data Protection Commissioner (Sächsischer Datenschutzbeauftragter).

For the data inside your own installation there is nothing to request from us: delete the installation and it is gone.

10. Changes

This notice carries a version number and an effective date, numbered independently of the software release. A major change to what we do gets a new major version and is announced; wording repairs get a minor bump. Superseded versions remain online at their own address: version 1.0 applied from 1 September 2026. Version 2.0 adds accounts with passwords, the sign-in cookie, connected computers, invitation links and the security log, and corrects two statements of 1.0: the application does contact us — to fetch its own updates — and those updates come from our own server rather than from GitHub Releases. The section on signing in with Google, and the short-lived second cookie it needs, were added to 2.0 on 6 October 2026 without a new version number: they describe a way in offered alongside the password, and change nothing about anybody who does not use it. On the same day it was extended again to say that an account can now be created without an invitation, and that whether you are taking part in the beta is recorded and answered separately from the account itself.

Questions

Write to support@agentonest.com.