Privacy Policy
This Privacy Policy describes how HortiHub (operated by Get2Grow) collects, uses, and protects information about users of our professional horticulture platform. We are committed to your privacy and comply with the EU General Data Protection Regulation (GDPR).
1. Who We Are
Data Controller: Get2Grow — except for the labour records a nursery's people keep (hours, numbers of people and notes), for which the nursery is the controller (section 8)
Contact: info@get2grow.nl
Platform: HortiHub — professional horticulture calculation tools and learning platform
2. Data We Collect
We collect only the data necessary to provide our service:
- Email address — required for account creation and authentication
- A message through the contact form — on the website, the name, email address, company (optional) and message you write. It is sent to us as an email and is not stored on the platform
- Name and company — optional, provided when requesting access. The company account we set up for your nursery keeps its name, and who belongs to it, with each member's role
- Learning progress — which courses you have completed and quiz scores. Visible to you and, in summary, to the owner of your company account (see section 8)
- Tool activity — which tools you visited and when (used for your dashboard activity feed)
- Your dashboard checklist — the items you add to your own dashboard checklist. They are yours alone: your colleagues do not see them
- Session data — authentication tokens stored in your browser's local storage to keep you signed in, and, on our servers, which of your companies you last worked in, so you return to it
- Company and greenhouse data — the greenhouses (their size, rows and compartments), crops, cultivation dates and growth phases or crop stages you enter, the climate exports you upload from your climate computer or have it mail to your company's import address (below) — each export file you upload is kept as you sent it, so the days read from it can be read again once a column's link is corrected — how your export's columns map to our measurements, any measurements of your own you add to them, and the day values you enter or correct by hand, with who entered them and when. The readings our cleaning of an export leaves out of a day as sensor faults (a spike, or a value no sensor of that kind can read) are kept with that day, with what they read, so the day window can show them
- Mailed climate exports, only if your company switches them on — your climate computer can mail its daily export to an address we give your company, which names that company and nothing else. We read that mailbox every half hour, without ever writing to, moving or replying from it. Per message we keep the sender address, the subject, the attachment's name and size, a fingerprint of the file, the message identifier, the times it arrived and was read, and what happened to it — that log is what you see on the Climate page. The export itself is stored as climate data of the greenhouse it belongs to, exactly as an upload you make yourself. We also keep the sender addresses your company sets up, each with the greenhouse its exports belong to. Mail addressed to no company, or from a sender your company has not set up, is not imported; the message text is never stored
- Your locations and where your greenhouses are — the locations of your nursery: the name you give each site under Setup, which of your greenhouses stand on it, and the place or coordinates you enter for it. This is company data, stored with that location, and used to pick the nearest KNMI weather station and to fetch the forecast for its greenhouses. The coordinates are sent to Open-Meteo for the forecast (see section 4). They are kept to about a kilometre, and every member of your company — owner, growers and assistants alike — can see a greenhouse's location, because their browser fetches that greenhouse's forecast
- Water analyses — the water sources you name (a bore, a rain basin, a drain line) and the laboratory analyses of them that you type in or import from a lab report, with the sample date, the laboratory and the report number. A lab report PDF carries your company name and address. Neither is stored. The address is read past; from the name a short code is made and kept with the analysis — enough to notice a report addressed to someone other than your company's usual name, or to tell two of your sites apart. The code is not the name, but anyone holding a list of names could find which one gives it, so we treat it as personal data: only the members of your company, and Get2grow as administrator, can see it. What is kept with an analysis you confirm: the values, and the report's own type-of-water, location, cultivation and crop lines — your own naming from the lab's order form — so the tool can tell which source, greenhouse and cultivation a report belongs to. When you confirm that reading, a rule "a report titled X belongs to source S" is kept for your company, and which of your greenhouses the source serves, so the next report with that title is recognised
- Your fertilisers — the products you keep for the nutrient calculator: the name you give them, solid or liquid with its density, the analysis as printed on the label, the tank you choose and the data sheet's solubility. Nothing else about your supplier is stored
- Nutrient recipes — the setups you save in the nutrient calculator for a greenhouse, under a name you choose: the water it is fed, the target recipe, the pH set-point, and the fertilisers, acids and micronutrients chosen, so a setup can be reopened and recalculated. A saved setup keeps its own copy of the products it used
- Fertilisers and tanks per greenhouse — for each greenhouse, which fertilisers, acids and micronutrient products the nutrient calculator doses with, each acid's strength, and the stock tanks' concentration, volume and temperature, so colleagues and other computers start from the same settings
- Own heating settings per greenhouse — for a greenhouse you give settings of its own on the CHP tab: its setpoints, the energy screen, the minimum pipe and the humidity targets the CHP plan heats it by. A greenhouse without them follows your shared settings
- Targets for the climate advice per greenhouse — what you enter on the Climate page's Targets tab for a greenhouse, for a period or a single day: the light the glass and each screen let through, the light sum you aim for, your RTR line, your CO₂ target and your humidity and temperature limits. The advice judges each day against the targets in force on it, and a change re-judges the days already stored
- Labour planning and hours — the activities your company plans, with their working norms (how much area, how many plants or what weight per hour, and the length of a shift), and a greenhouse's own labour norms where they differ; the weeks and activities planned per greenhouse, over what share of it and on which days; and the hours worked and the number of people recorded against them, per greenhouse, week and activity, each with an optional short note of at most 300 characters. Hours are recorded per activity, not per person: the record says how many people worked, not who. Each record keeps which account entered it. Section 8 says what a note should and should not hold
- Saved calculation plans — the plans the tools save for a day, each with its inputs and its result, and the greenhouse it is for when one is chosen: an RTR plan (the day's light sum and the temperature it leads to), a light plan (the lamps' settings and the day's light balance) and a CHP plan (your units and their settings, the hour-by-hour energy prices, and the schedule with its expected result). Saving again for the same greenhouse and day replaces the earlier plan. We also keep the CHP presets, the named unit settings your company shares. Each keeps which account saved it
- What your CHP actually ran — per location and month, the figures you enter from your meters on the CHP tab: the hours your CHPs ran, the electricity they made and the gas they burned, and, if you enter them, the heat put to use, the CO2 dosed, the boilers' gas, the gas meter's readings at the start and end of the month and a short note of at most 300 characters. The CHP cost price card on Growing can price from them. Each month keeps which account entered it, and every member of your company can see it
- Climate advice and what came of it — the advice cards the platform produces for each greenhouse day, the advice rules your company writes or tunes (with each version of a rule as it read when it changed, and who changed it when that was someone signed in, and each change to a rule's threshold and the evidence it rested on), the rapid swings in temperature, humidity, VPD, dew point or CO2 it detects in your climate data, whether the control an advice card named moved afterwards, whether the condition a card flagged stopped holding on the days after it, and whether — and by whom and when — a card was accepted as a task on the dashboard, and the score a model gave each card, with how much of what the model reads the card had measured and how many of those values lay outside the range the model learned from. The Dagrapport written for you is kept with your account in that company, so the next one can follow on from it
- Your notes on the advice — your rating of each advice card, which trains the models behind the advice (below) — pressed on the card, or counted from a comment of yours that Claude checked against the readings and you confirmed, which is recorded with it, as is whether the models' estimate could have been shown on that card when you rated it; the comments and preferences you write on a Dagrapport, which the platform keeps so later advice follows on from earlier advice; the questions you ask Claude about a day under its Dagrapport, with its answers, kept so you can return to the conversation — they are yours alone, and later advice reads none of it unless you turn a point into a rule or a remark yourself; the comments you write on an advice card, or on a day to say that advice should have been given there, which Claude reads into a fixed form (what kind of point, the measurement, which way) and checks against that greenhouse's readings, saying whether the data bears the point out, and which everyone in your company sees with your address beside them, so the rules can be improved from them, and a change to a rule proposed from those comments, with who applied or declined it; a change to the advice of one greenhouse learned from them or from your company's ratings — a limit, a "not when", the days running, the order of the levers, a rule switched off there, its words, or the whole rule rewritten — with the comments or ratings it came from, who applied it and when, how many days rated "Klopt" the editor accepted it would no longer flag, and whether it was undone or, kept in the greenhouses that use the rule, became the company's rule; and when an editor applies a change to the whole company at once, the reason they give, kept with it, while each greenhouse that uses the rule is still watched; when Claude's check says the readings show otherwise and you choose to hold to your comment and send it to Get2grow ("Ik blijf erbij"), that dispute and Get2grow's answer to it: Get2grow then sees your comment and anything you add to it, the advice card, Claude's check with the numbers it verified, and the company, greenhouse and day it is about — not your email address — and the answer is shown under your comment, named once in the greenhouse's next Dagrapport, and kept as an example to test Claude's checks against; and which days you have already opened, so it can show you what is new
- Advice models — a record of each model trained on your company's ratings: when it was trained, on how many ratings, how accurate it was, and the range of your company's climate readings it learned from (the middle 90 % of its ten main inputs, and how much of them was measured). Whether your company's ratings also help train the shared per-crop models, which every company's advice can fall back on, is your company's choice: it is off until the owner of your company account switches it on. The same choice decides whether what the advice learned from your company's comments goes, anonymised, into the register Get2grow uses to improve the standard rules: which standard rule was changed and how, for which crop, in how many greenhouses, and what the change did to the stored days and how they were rated — never the comments' words, names, or which company or greenhouse it was. That choice is recorded with the email address of the owner who made it and when, and this record is kept after that account is deleted, because it shows who agreed to the sharing and when
- A record of what we do as administrators — when Get2Grow approves or refuses a request for access, adds someone to a company or takes them off it, removes an account, or creates, renames, merges or deletes a company account, or reviews one of a company's days without advice (section 3), we record which of us did it, when, and the email address or company name it concerned. It is how we can show what was done to an account or a company, also after it is gone
- Your browser's own position, only if you ask for it — if you use "use my location" on the weather or energy card, your browser's position is rounded to about one kilometre and stored in this browser so the forecast is for your area. We never ask for it on our own, that browser position is not sent to or stored on our servers, and you can remove it by choosing a location by name instead. The rounded coordinates are sent to Open-Meteo to fetch the forecast (see section 4)
We do not collect payment information or any sensitive personal data.
3. How We Use Your Data
- Authentication — to verify your identity and keep your session active
- Service delivery — to show your learning progress and recent tool usage on your dashboard
- Password recovery — to send you a reset link when requested
- Product improvement — aggregate, anonymised usage data helps us understand which tools are most used, and the date of each company's latest tool activity tells us which companies are using HortiHub — per company, never per person
- The CHP figure on our public website — the expected results of saved CHP plans feed one average shown on the public site. It is published only when it combines at least five companies, demonstration accounts are left out, and it names no company and does not say how many took part
- Climate advice — to analyse your uploaded climate data and generate the Dagrapport, and to answer the questions you ask about a day. This involves sending the relevant context to an AI provider; see section 4
- Finding advice that was missed — each week Get2grow reviews a small sample of your company's days on which the climate advice gave no card, to find advice that was missed. When it was, Get2grow records what was missed as a report on that day, which is checked against the day's readings by the AI provider as your own reports are (section 4). It never changes your advice by itself: where the check finds a change worth making, it is proposed to your company's editors and shown under that day on your Dagrapport as Get2grow's
- Fertiliser calculation — to read the lab report you import, blend your water sources and calculate the doses. Reading the report is done by our own file-processing service (section 4); no AI provider is involved
- Automatic climate import — to read the export your climate computer mails to your company's address, match it to the right greenhouse and store it as climate data, and to keep the log of what arrived. The file is processed exactly as one you upload yourself
We never sell your personal data. We do not use your data for advertising.
4. Data Processors (Sub-processors)
We use the following third-party services to operate the platform:
- Supabase — database and authentication provider, and storage for the trained model files behind the advice. Servers located in the EU (Frankfurt). Supabase is GDPR-compliant and acts as a data processor under our agreement with them. Supabase Privacy Policy
- Vercel — web hosting, CDN and (with your consent) cookieless web analytics. Vercel Privacy Policy
- Anthropic — the AI model behind the Climate Advisor's Dagrapport, its rule suggestions and the conversation about a day. When you generate a brief we send the greenhouse name, the crop and growth stage, that day's measured climate values, the advice cards produced for that day, and any comments or standing preferences you have written. When you ask about a day under its Dagrapport we send that day's report, advice cards, incidents and figures, its readings per quarter hour, the seven days before, and your conversation about it so far. When you comment on an advice card we send your comment, the card and its rule, and the readings and day figures of that greenhouse that Claude looks up to check it (at most the two weeks up to the card's day). When you, or Get2grow in its weekly review, report that advice should have been given on a day, we send the report, that day's readings and figures, the names of the rules that gave or nearly gave a card that day and of the catalogue rules the day would have set off, and the readings and day figures Claude looks up to check it, as for a comment. Anthropic processes this only to return the brief or the answer; under their commercial terms, inputs and outputs are not used to train their models. Anthropic processes it in the United States; the transfer is covered by our data processing agreement with them, which incorporates the EU Standard Contractual Clauses. Anthropic Privacy Policy
- Railway — hosting for our file-processing service. A climate export you upload is sent there to be read and matched to the right measurements, and the models behind the advice are trained and run there; the trained model files are stored with Supabase (above). A water-analysis lab report you import is sent there to be read; the file is processed temporarily and discarded after parsing. Analysis values and sample metadata (location, cultivation and crop, when present) come back. The grower's name is read only to make the short code described in section 2; neither the name nor the address comes back or is stored. It is also this service that reads the import mailbox, over IMAP, read-only. Servers located in the EU (Amsterdam). Railway Privacy Policy
- Mail provider — the mailbox your climate computer mails its export to, if your company uses the automatic import. The provider holds those messages: the sender, the recipient, the subject, the date and the attached export. Our file-processing service reads the mailbox and never writes to it. We are selecting the provider; it is named here, with its servers' location, before the automatic import is switched on for any company — as section 4 promises for every processor we add
- Microsoft — our own email (Microsoft 365). A message you send with the contact form on the website is delivered to our mailbox there as an email, and we answer it from there. Microsoft Privacy Statement
- Open-Meteo — the weather forecast shown on the dashboard and used by the energy planner. Your browser requests the forecast directly, so Open-Meteo receives the approximate coordinates of the location you chose (rounded to about one kilometre) or the place name you typed, and your IP address. Nothing identifying you or your company is sent, and no account data passes through them. Open-Meteo Terms and Privacy
Each of these acts as a data processor under Article 28 GDPR. If we add or replace one, this section is updated before the change goes live.
Typography and icon fonts are served by this website. Loading them does not contact Google Fonts or Cloudflare cdnjs.
5. Cookies and Local Storage
We use essential cookies and browser local storage only:
- Authentication session — a session token stored in local storage to keep you signed in
- Preferences — your dashboard layout, language preference (EN/NL), and — only if you asked for it — the approximate coordinates of your weather location, stored in local storage
- Tool settings — the calculator inputs and saved CHP presets you last used, so a tool opens where you left it. Cleared when you sign out or switch company. This is a copy in your browser: the presets themselves are kept with your company (section 2)
- Cookie consent — a record of your consent choice, stored in local storage
These are strictly necessary for the platform to function and are used whatever you choose in the consent banner.
Optional — analytics. If you choose "Accept all", our public website also loads Vercel Web Analytics, which counts page views and referrers. It sets no cookie and does not identify you. Choosing "Essential only" means it is never loaded, and you can change your mind by clearing site data in your browser. We do not use tracking cookies or third-party advertising cookies.
6. Data Retention
- Account data is retained while your account is active
- Learning progress is retained for the lifetime of your account and deleted with it
- Tool activity belongs to your company account as well as to you: when your account is deleted, it stays with the company without the link to you, and it is deleted with the company account. Only you see your own; Get2Grow sees it per company, never per person — how many actions were recorded and the date of the latest
- Water sources, their analyses and the report-recognition rules belong to your company account and are retained until someone in the company deletes them or the company account is deleted (deleting a source deletes its analyses and rules)
- Your fertilisers belong to your company account and are retained until someone in the company removes them or the company account is deleted; a saved setup keeps its own copy of the products it used
- A greenhouse's fertiliser and tank settings are retained until they are changed, the greenhouse is deleted, or the company account is deleted
- Nutrient recipes belong to your company account and are retained until someone in the company deletes them, the greenhouse they are for is deleted, or the company account is deleted
- Labour plans, the hours recorded with their notes, the activities and the labour norms belong to your company account and are retained until someone in the company deletes them or the company account is deleted (deleting a greenhouse deletes its plans, hours and norms; deleting an activity deletes them for that activity)
- Saved RTR, light and CHP plans and the CHP presets belong to your company account and are retained until someone in the company deletes them or the company account is deleted; a plan for a greenhouse that is later deleted is kept without it
- What your CHP actually ran belongs to your company account and is retained until someone in the company empties the month on the CHP tab or the company account is deleted. A location with months entered cannot be deleted until they are emptied
- Climate data, the advice made from it and what came of that advice belong to your company account, and are deleted with the greenhouse they belong to or with the company account. The export files you uploaded are kept as long as that greenhouse's climate data; someone in the company can delete one on the Upload tab, and its stored days stay
- Your ratings of advice, your Dagrapport comments and preferences, the Dagrapporten written for you, your conversations about a day (until you start one over, which deletes it), which days you have opened, and your dashboard checklist are yours: they are deleted with your account
- The log of mailed imports (sender, subject, filename, file fingerprint, times and outcome) belongs to your company account and is kept with your climate data until the company account is deleted. The messages themselves stay in the import mailbox until we clear it, and are used for nothing else
- When an account is deleted, the greenhouses, climate data, labour records, recipes and plans that person entered stay with the company, and the link to the account that entered them is removed
- The record of what we do as administrators, and the record of who switched on sharing for the advice models and when, are kept, also after the account or company they concern is gone: one is a security record, the other a record of consent, and each keeps the email address it names
- Upon account deletion, your personal data is removed within 30 days — except the two records in the line above, and what stays with your company without the link to you
- A message sent with the contact form is kept as our correspondence with you, in our mailbox, for as long as it is needed to answer you and follow up
- Anonymised aggregate data (e.g., total tool usage counts) may be retained indefinitely
7. Your Rights Under GDPR
As an EU resident you have the following rights regarding your personal data:
- Right of access — request a copy of the data we hold about you
- Right to rectification — correct inaccurate data
- Right to erasure — request deletion of your account and data
- Right to data portability — receive your data in a machine-readable format
- Right to restrict processing — limit how we use your data
- Right to object — object to processing based on legitimate interest
To exercise any of these rights, contact us at info@get2grow.nl. We will respond within 30 days.
You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
8. Data Security
We take reasonable technical and organisational measures to protect your data, including:
- HTTPS encryption for all data in transit
- Row-level security on all database tables, scoped to your company
- Authentication managed by Supabase with industry-standard password hashing
What your colleagues can see. Your data is walled off from other companies, not from your own. Everyone who belongs to your company account can see the greenhouses, climate uploads, the advice cards behind each Dagrapport and their history, labour plans and hours, recipes and saved plans belonging to that company, whoever entered them. The Dagrapport text written for you, your ratings of the advice, the comments and preferences you write on a Dagrapport about the report itself and the days you have opened are yours: colleagues do not see them, although your ratings help train your company's advice models and count in its totals. The comments you write on an individual advice card, and a report on a day that advice should have been given there, are not: everyone in your company sees those, with your email address beside them, because that is how the rules are improved from them. That is deliberate — growing is a team activity and a colleague covering a weekend needs the same picture you have — but it means work you do here is visible to your company, not private to you.
Your training, and what an owner sees of it. Learning progress is personal: nobody sees which slides you read, how long you took or what you answered. The owner of your company account has a Team view showing, per colleague, how many courses are completed or started and when the last activity was — so a nursery can see its team's training. Growers and assistants do not see each other's.
Notes about work, and who decides what goes in them. The hours, numbers of people and notes your nursery records under Labour are the nursery's own record of its work. The nursery decides what its people record there, and for that record it is the controller; Get2Grow stores and processes it on the nursery's behalf, to provide HortiHub to the nursery, and uses it for nothing else. A note should hold what the work needs — what was done, what held it up — and not personal details about colleagues, such as their health, why they were absent or how well they work.
9. Changes to This Policy
We may update this policy from time to time. The "Last updated" date at the top of this page will reflect any changes. For significant changes we will notify active users by email.
10. Contact
Get2Grow
Email: info@get2grow.nl