Privacy

Version 2. Effective 29 September 2026.

What the registry stores about requests to this site, its API and its MCP endpoint, and how long it keeps it. This page is generated from the server's configuration when a release is built.

Who is responsible

Vayu Solutions, van Pijkerenlaan 28, 8096 VE Oldebroek, the Netherlands, Chamber of Commerce (KvK) number 67490395, is the controller of the personal data described on this page. E-mail: info@vayu-solutions.nl.

What is stored and for how long

• Usage events: one line per API or MCP operation, from a fixed list of fields: time, a random request id, route, status, timing, a client family taken from the User-Agent (a fixed list), the traffic class, how the request arrived (an installed integration, a search page from a fixed list of search hosts, or a direct call), the MCP method, the MCP client name the client sends at the start of a session, mapped onto a fixed list of client names (any other name is stored as other), a link tag from a fixed list the operator publishes, the operation and its result codes, the capability, and for searches and evaluations only the words that are in a fixed vocabulary, a count of the other words, a length class and which input fields were filled in (not their values). No IP address, task text, context value or license key is written. Kept 14 days.
• Quote, unlock, download and outcome-report events, with the same fields plus the quote, evaluation and purchase references and the list price: kept 90 days.
• Outcomes an agent reports through report_outcome: kept 90 days.
• A daily count of distinct clients, and of distinct clients per operation (an evaluation, an evaluation that found a relevant capability, a recommendation, an evaluation over MCP, an MCP initialization, a quote), per MCP client type from a fixed list and per link tag from a fixed list the operator publishes. They are counted in memory from a keyed hash of IP address and User-Agent; the key is random, changes every UTC day and is never written. Only the counts are stored: kept 90 days.
• For some capabilities, a daily count of distinct clients that received a quote, per capability and price. It is counted from a keyed hash of the IP address (for IPv6, its /64 network) and the kind of client named in the User-Agent; the key changes every UTC day. The hashes stay on the server, and are written there only so that a restart does not count a client twice, until that day's count is made shortly after the day ends. They are then deleted and only the counts are kept. Hashes whose count was not made are deleted on the second day after their own day at the latest. The counts name no client and are kept 90 days.
• Purchase records, written at the first unlock of a license key: the purchase reference, the capability version, the license and refund-policy versions it was unlocked under, the payment provider's ids for the license key and the benefit, the list price, the price of the linked quote, the quote and evaluation references and the unlock time. They hold no name, e-mail address or license key. Kept 2557 days after the first unlock (about 7 years); the retention job then deletes them.
• License keys are stored only as a SHA-256 fingerprint.
• Payment details are handled by the payment provider and never reach this server.
• The web server's access log records no IP address or network port, cookie, authorization header, query string or download token, and of a referring page only its host name. It also drops the request headers that commonly carry a client's address or e-mail address (Proxy-Authorization, Forwarded, X-Forwarded-For, X-Real-Ip, True-Client-Ip, X-Client-Ip, Cf-Connecting-Ip, X-Cluster-Client-Ip, Fastly-Client-Ip, Via, From). It keeps the time, host, method, path, protocol, status, size and duration of each request, the TLS version, the response headers and the other request headers as the client sent them, such as the User-Agent. It rotates at 5 MiB and keeps the current file and at most 3 rotated files; a rotated file is deleted at a later rotation once it is more than 14 days old, and the current file is kept until it rotates. The log never leaves the server.
• Hourly counts taken from the usage events and the access log: requests per page type, status, client family and referring host, and, for API and MCP requests, per MCP method, per MCP client from a fixed list, per link tag from a fixed list the operator publishes and per word from the fixed search vocabulary (at most the 50 most frequent words of an hour), with no identifier. Counts kept per day are kept 90 days; counts kept per month are kept until 90 days after the end of that month.

Held in memory only

• For rate limits, the IP address of each client (of an IPv6 address, its /64 prefix) with a request count. It is never written to disk. An entry goes no later than 61 minutes after the client's last request, sooner when the table holds 20,000 entries (the least recently used goes first), and at every restart.
• For license checks, a SHA-256 fingerprint of each checked key with the answer: for a valid key the payment provider's id for it and how long it may back a download, for an unknown key only that it is unknown. An entry goes within 60 seconds of the moment it can no longer be used (for a valid key, when less than 15 minutes of the time it may back remain, at most 24 hours after the check; for an unknown key, 60 seconds after the check), sooner when 4,096 entries of its kind are held (the least recently used goes first), and at every restart.

E-mail to the operator

When you e-mail the operator, for example to withdraw from a purchase, ask for a refund, report a defect or exercise a privacy right, the operator processes your e-mail address, your name if you give it, the content of your message and what you add to it, such as an order number, together with its answer. It uses them only to handle your request, and keeps them 730 days (about 2 years) after the request is handled; what belongs to its accounts, such as a refund request, it keeps as long as tax law requires (7 years, article 52 of the Dutch General Tax Act). The operator deletes them by hand. TransIP B.V., based in the Netherlands, delivers and stores the operator's e-mail on its behalf, as processor.

What the operator receives from the payment provider

For each order, Polar Software, Inc. gives the operator the e-mail address, name and billing address the buyer entered at checkout, any tax id entered there, the order number, the product, the amount and tax, and the status of the license key. The operator uses them to handle refunds, withdrawals and chargebacks (revoking the license key), to answer support questions and for its accounts. They stay with the payment provider; the operator copies them only into an e-mail answering you and, for the order number and amounts, into its accounts, which it keeps 7 years (article 52 of the Dutch General Tax Act).

Why, and on what legal basis

• Checking a license key, recording the purchase it unlocks and issuing download links: to perform the contract with the buyer (GDPR article 6(1)(b)).
• Keeping purchase records afterwards: to settle a question or dispute about a purchase against the terms it was made under, to keep to the sale limits the operator set and to report revenue (article 6(1)(f), legitimate interest).
• Quote, unlock, download and outcome-report events: to see whether quotes lead to purchases and to answer questions about a delivery (article 6(1)(f)).
• Outcomes an agent reports: to see whether capabilities work as described (article 6(1)(f)).
• Rate limits and the access log: to keep the service secure and available and to stop abuse (article 6(1)(f)).
• Usage events and counts: to keep the service secure, to see how agents find, evaluate and buy capabilities, and to improve the registry (article 6(1)(f)).
• Daily counts of distinct clients that received a quote: to set one price for every buyer of some capabilities from aggregated demand (article 6(1)(f)). No price is set for a person, and no decision about a person is made from them.
• E-mail and what the payment provider gives the operator about an order: to perform the contract, for example a refund, a withdrawal or a repair (article 6(1)(b)); to answer other questions (article 6(1)(f)); and to meet legal obligations, such as answering a privacy request and keeping the accounts (article 6(1)(c)).
• The operator's copy for reports: the same purposes as the data it copies.

Who receives it

• TransIP B.V. hosts the server in the Netherlands and processes the data above on the operator's behalf, as processor.
• Polar Software, Inc., based in the United States, runs the checkout and takes the payment as merchant of record, under its own privacy policy: https://polar.sh/legal/privacy-policy. For the order data it keeps for the operator and gives to it, it acts as the operator's processor under its data processing addendum: https://polar.sh/legal/data-processing-addendum. Payment details go to it directly and never reach this server.
• To check a license key, this server sends the payment provider only the key, the operator's organization id and the benefit id. The answer also contains the buyer's customer details; the server reads only the key's status, id, expiry, benefit and organization from it and keeps none of the rest.
• TransIP B.V. receives the e-mail you send the operator, as described above.

The operator's copy for reports

The operator copies the usage and commercial events, the purchase records and the counts, with the signed daily counts of clients that received a quote (not the access log, the hashes behind those counts, reported outcomes, secrets or keys) to its own computer for reports (ak state pull). Each completed copy ends by deleting from it what the periods above no longer allow; between copies a file can stay until the next one. When the operator stops copying, it deletes the copy.

Transfer outside the European Union

Polar Software, Inc. is based in the United States. Where no adequacy decision of the European Commission covers this transfer, the payment provider's data processing addendum, part of the terms the operator accepted with it, applies the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914) to it: https://polar.sh/legal/data-processing-addendum.

What you need to provide

Reading the site and using the API or the MCP endpoint needs no personal data. To unlock a purchase, only the license key from the checkout is needed; without it no download can be released.

Your rights

You can ask for access to your personal data, its rectification or erasure, restriction of its processing and data portability. Send it to info@vayu-solutions.nl. A purchase record holds no name or e-mail address, so name its purchase reference (from the unlock answer), your order number from the checkout or the e-mail address you used there. Do not send your license key. The operator answers within one month.

You can also lodge a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens: https://autoriteitpersoonsgegevens.nl.

Your right to object

You can object at any time, on grounds relating to your situation, to the processing above that rests on article 6(1)(f): rate limits, the access log, usage events and counts, the daily counts of clients that received a quote, the quote, unlock, download and outcome-report events, reported outcomes, and purchase records after the purchase. Send the objection to info@vayu-solutions.nl. The operator then stops, unless it shows compelling legitimate grounds that override your interests, rights and freedoms, or needs the data to establish, exercise or defend a legal claim.

Automated decisions

The registry makes no decision about a person by automated means alone that has legal or similarly significant effects. Its evaluate answers assess capabilities, not people. A price is the same for every buyer and is never set from data about a person.

Questions about this page: info@vayu-solutions.nl