1. What we collect
We collect only the following. The "Where it lives" column says which system holds it.
| Data | Why we hold it | Where it lives |
|---|---|---|
| Account email and name | To create your account, sign you in and send what you asked for | Cloudflare KV (our application store) |
| Password hash | To check your password at sign-in. We store a salted PBKDF2 hash, never the password itself | Cloudflare KV |
| Saved sites: names, coordinates, working heights, your wind limits and rules | They are the point of the service: forecasts and decisions for your places | Cloudflare KV |
| Alert and briefing settings | To send alerts and morning briefs when and where you chose | Cloudflare KV |
| Agent conversation history, stated preferences and remembered facts | So the agent keeps context and your units, heights and limits | Cloudflare KV |
| Frozen evidence records | A record you chose to freeze: place, hourly values, verdict, provenance | Cloudflare KV |
| Contact-form messages | To answer you | Cloudflare KV and our inbox via SendGrid |
| API keys (stored only as hashes) and usage counters | To authenticate API calls and apply plan caps | Cloudflare KV |
| Stripe customer and subscription identifiers, plan and subscription status | To match your payment to your account | Cloudflare KV and Stripe |
| Technical logs: IP address, user agent, request path, timing, errors | Security, abuse prevention, fixing faults | Cloudflare |
What we do not collect. We never receive or store your card number, expiry or security code. Payment is taken on a page hosted by Stripe (Stripe Checkout). We do not collect precise device location: a place only enters the service when you search for it, tap the map or type coordinates.
Saved coordinates can be sensitive. A list of sites can reveal where you work, a private estate, or where your equipment sits. We treat saved sites as account data: they are not public, not shared with other users and not used for marketing.
2. How we collect it
- From you, when you register, add a site, set a rule, ask the agent something, freeze a record or write to us.
- From your device, automatically: the request your browser makes to our servers carries an IP address and user agent, which Cloudflare handles as part of delivering the site.
- From Stripe, after you subscribe: the customer and subscription identifiers and the status of the subscription (active, cancelled and so on). Stripe holds your payment details; we do not.
We do not buy data about you and we do not build profiles from other sources.
3. Why we use it, and our legal basis
Under the GDPR we must have a lawful basis for each use. Ours are:
| What we do | Legal basis |
|---|---|
| Run your account, show your sites and decisions, run the agent, take payment, send the alerts and briefs you set up | Contract: it is necessary to provide the service you asked for |
| Keep logs, rate-limit requests, block abuse, secure the service and investigate faults | Legitimate interests: keeping a safety-related service secure and available. Impact on you is small and we limit it by deleting or hashing what we do not need |
| Send optional emails that are not part of the service you ordered | Consent, which you can withdraw at any time |
| Answer your contact message | Legitimate interests, and contract if you are a customer |
| Keep records we are legally required to keep, such as proof of payment | Legal obligation |
We do not make decisions about you that have legal or similarly significant effects by automated means. The wind verdicts the service produces are about places and weather, not about people.
4. The agent and what is sent to the model
The Wind Agent includes a question-and-answer agent. When you ask it something, we send the model provider, xAI (Grok), your question, recent turns of the conversation, any facts you asked it to remember, and the data packet on screen or fetched by its tools: forecast values, the place name and coordinates, and the thresholds you set.
We do not send your account identifier, your email address or your password hash to the model. Your user ID is used only inside our own servers to look up your saved sites and memory. Be aware that if you type personal details into a question, or you name a site after a person or a private address, that text is part of what is sent. Please do not put anything into the agent that you would not want a processor to see.
You can see what the agent remembers about you, delete individual remembered facts and clear the conversation history from inside the product. Signed-out visitors keep the same kind of memory only in their own browser (localStorage), and it is sent along with each question as context but not stored on our servers.
We do not use your conversations to train our own models. We cannot speak for xAI's practices beyond the terms we have with them; see their privacy documentation for how they treat API traffic, and section 7 for transfers.
5. Who else handles your data
We use a short list of service providers. Each acts as a processor on our instructions unless noted.
| Provider | What it does | What it sees |
|---|---|---|
| Cloudflare | Hosts the site and API, stores our data (Workers and KV), delivers traffic, keeps request logs | Everything the service stores, plus request metadata such as IP address |
| Stripe | Takes payment and manages subscriptions through Stripe Checkout and the billing portal | Your email, billing details and card data. Stripe is an independent controller for its own fraud and compliance obligations |
| SendGrid | Sends email: alerts, briefings and replies to contact messages | Your email address, the message, delivery metadata |
| xAI (Grok) | Language model behind the agent | Your questions and the data packet described in section 4; no account identifiers |
| Open-Meteo | Forecast, ensemble and history data | Coordinates of the places requested and the request itself. No account or personal data. Requests go from our servers, not from your browser |
| OpenFreeMap | Map tiles | Your browser requests tiles directly, so it sees your IP address and the tiles, and therefore roughly the area you are viewing |
| Google Search Console and IndexNow | Tell search engines which public pages exist | Public page addresses only. Nothing personal |
We do not sell personal data, and we do not share it with advertisers or data brokers. We will disclose data if the law genuinely requires it, and we will tell you where we are allowed to.
If you embed a public board or share a frozen record, anyone with the link can see what is on it. That is deliberate and described in section 6.
6. Public things: frozen records and boards
A frozen record is a snapshot you create to keep evidence of what the service showed at a moment in time. It is reachable by an unguessable link. It is marked so that search engines are asked not to index it, but anyone you give the link to, or who finds it, can read it. It contains the place name and coordinates you froze, the hourly values, the verdict and the provenance, and an internal reference to the account that created it. It also carries an internal, random account reference (or the word "anonymous" if it was frozen while signed out), which can be seen in the raw record data. That reference is not your name or email address, and the record page does not show either. Frozen records are kept for 365 days and then expire automatically.
Public embed boards (an Ops plan feature) show the places you choose to publish. Anyone with the board address can see them. Do not publish a place that you want to keep private.
7. Transfers outside the EEA
Ireland is in the European Economic Area. Several of our providers are US companies or operate global networks, so your data can be processed in the United States and other countries outside the EEA.
- Cloudflare serves requests from data centres near the visitor and stores our application data on its global network. We have not pinned our data to the EU.
- Stripe, SendGrid and xAI process data in the United States.
Where personal data goes to a country without an EU adequacy decision, we rely on the safeguards our providers offer: the EU Standard Contractual Clauses incorporated into their data-processing terms, and, for providers certified under it, the EU-US Data Privacy Framework. We have accepted those providers' standard terms rather than negotiated bespoke ones. If you want a copy of the transfer mechanism that applies to a particular provider, ask us and we will point you to it. We do our best to keep transfers to what is necessary, which is why we do not send account identifiers to the model and do not send personal data to the forecast provider.
8. How long we keep it
| Data | Retention |
|---|---|
| Account, saved sites, rules, alert and briefing settings | While your account is open. Deleted on request, and in any event within 30 days of an account-closure request |
| Sign-in session (cookie token, stored hashed) | 30 days, then it expires |
| Agent conversation history | The most recent 30 turns, each shortened to 2,000 characters, kept until you clear it or your account is deleted. Older turns are overwritten as new ones arrive |
| Remembered facts and preferences | Up to 40 short facts, kept until you delete them or your account is deleted |
| Frozen evidence records | 365 days, then they expire automatically |
| Contact-form messages | 180 days in our store, then they expire automatically. The copy we received in our inbox is kept as long as the conversation needs it |
| Alert delivery log and duplicate-suppression markers | 30 days and 7 days respectively |
| API keys and usage counters | Keys until you revoke them or close the account; daily counters expire after two days |
| Rate-limit counters | About two minutes. They use a one-way hash of your IP address, not the address |
| Stripe customer and subscription identifiers | While your account is open, and afterwards as needed for tax and accounting records |
| Payment records held by Stripe | As Stripe and Irish tax law require (generally six years for accounting records) |
| Server logs at Cloudflare | Governed by Cloudflare's own retention periods, which we do not control |
When something is "deleted" we remove it from the live store. Copies inside provider backups and logs age out on those providers' schedules.
9. Cookies and local storage
We use very little.
- wind_session: an essential cookie that keeps you signed in. It is HttpOnly (scripts cannot read it), Secure (sent only over HTTPS), SameSite=Lax, and lasts 30 days. It holds a random token; we store only its hash.
- Local storage in your browser: your unit and display preferences, your saved list of evidence records, the place you last viewed, whether you have seen the intro film, and, if you are signed out, the agent's memory. These stay on your device. Clearing your browser data removes them.
We run no advertising cookies, no third-party analytics tags and no tracking pixels. We checked our code for Google Analytics, Google Tag Manager, Meta Pixel and similar scripts and found none. Because we use only strictly necessary storage, there is no cookie banner to dismiss. If that ever changes, we will update this page and ask for consent first.
Our own server logs and Cloudflare's tools may count visits in aggregate. That is operational monitoring, not behavioural advertising.
10. Children
The Wind Agent is a professional planning tool and is not directed at anyone under 16. We do not knowingly collect personal data from children. If you believe a child has given us personal data, email us and we will delete it.
11. Security, and what happens if something goes wrong
- Passwords are stored as salted PBKDF2 hashes. API keys and session tokens are stored hashed.
- All traffic uses HTTPS. Cards are handled only by Stripe.
- Access to production systems is limited to the owners and the people they authorise.
- Requests are rate-limited and the contact form is protected against automated abuse.
No system is perfectly secure and we will not claim ours is. If a personal-data breach occurs that is likely to put you at risk, we will notify the Irish Data Protection Commission within 72 hours of becoming aware, as the GDPR requires, and we will tell affected users without undue delay and say what was involved and what to do.
12. Your rights and how to use them
Under the GDPR you have the right to:
- be informed about how we use your data (this policy);
- access the personal data we hold about you and receive a copy;
- rectification: correct data that is wrong or incomplete (most of it you can edit in your account);
- erasure: ask us to delete your data;
- restriction: ask us to pause using your data while a dispute is resolved;
- portability: receive the data you gave us in a common machine-readable format;
- object to processing based on legitimate interests;
- withdraw consent at any time where we rely on it, without affecting what was lawful before;
- not to be subject to solely automated decisions with significant effects (we do not make any).
To exercise any of them, email mike@impt.io or use the contact form. Tell us the email address on your account so we can find it. We may ask you to confirm it is really you before releasing or deleting anything. We will reply within one month. If your request is complex we may extend that by up to two further months, and we will tell you why. We do not charge for requests unless they are manifestly unfounded or excessive.
Some things are faster done yourself: you can delete a site, revoke an API key, clear the agent's history and delete remembered facts in the product, and you can cancel a subscription from the billing portal.
Complaints. You may complain to us first, and you also have the right to complain to the Data Protection Commission in Ireland (dataprotection.ie) or to the supervisory authority in the country where you live or work.
13. Changes to this policy
If we change how we use personal data we will update this page and its effective date. For a material change, such as a new type of data or a new kind of third party, we will email account holders before it takes effect. Previous versions can be requested from us.
14. Contact
The Wind Agent (Hetier & English), Ireland.
- Email: mike@impt.io
- Form: thewindagent.com/contact
- [Registered business details to be added]
See also our Terms of Service.