Privacy

We do not collect special-category data, we do not buy data about you from anybody, and we do not sell or rent what we hold to anyone.

• To give you the service. An account and the plants in it exist because you asked for them. Under the GDPR this is performance of a contract; under India’s DPDP Act it is the purpose you gave the data for.
• Legitimate interests. Keeping the service up, stopping abuse, and understanding in aggregate which material is worth writing more of. We use the least identifying option available for each — which is why model runs carry a session hash and not a user id, and why crash reports carry a stack trace and no IP address.
• A record of your own account activity. When you save, rename, duplicate, share or delete a plant, we write a line to our own database saying what happened and when. It is shown back to you in each plant’s technical panel, and it is how “last updated 13 May by you” is answered. This is part of running the account rather than measurement, so it is not behind the banner — but it only ever covers people who are signed in. If you are not signed in, nothing is written unless you have allowed measurement, and then only under a random per-tab id that is discarded when the tab closes. No IP address is recorded either way.
• Crash reporting, also a legitimate interest, and separate from measurement on purpose. When a page throws, Sentry receives the error, the stack trace and the address of the page it happened on, so it can be fixed. It is configured to attach no IP address, no cookies and no request headers, and it records no session replay — a crash report says what broke, not who was there. Because it holds no identity it is not behind the banner: a page that breaks before you have answered the banner is exactly the one worth knowing about.
• Consent for measurement. Google Analytics, Clarity and PostHog are not loaded at all until you allow them, and you can withdraw that at cookie preferences as easily as you gave it — which switches the tags off, clears their cookies and reloads the page without them.

Each of these is a processor acting on our instructions, under their own terms and security commitments. Data may be processed outside India and outside the EEA — chiefly in the United States and the EU — under the transfer terms in their agreements.

• Account and saved plants: until you delete them or ask us to close the account.
• Requests and reported corrections: kept as a record of what was said, and when.
• Model runs: kept in aggregate; they carry no identity to expire.
• Account activity: kept for as long as the account, and removed with it — the lines stop naming you the moment it is closed.
• Measurement: 14 months in Google Analytics, 30 days of Clarity recordings, and the browser lifetimes listed on the Cookies page.
• Crash reports: 90 days in Sentry, then deleted.

A copy of what we hold, a correction, deletion, a machine-readable export, or an objection to measurement. Write to hello@climatewise.today and we will answer within 30 days. If you are in the EU or UK you may also complain to your supervisory authority; in India, to the Data Protection Board once it is constituted. Deleting your account removes the account and the plants saved under it.

Access to the database is restricted by row-level policies and by owner checks in the application, connections are encrypted, and the app is served over HTTPS. But a plant you share by link is readable by anyone who has that link — that is what the link is for. Do not put anything confidential in a plant name or a note you intend to share.

cbg-sim is not directed at children and we do not knowingly collect data from anyone under 18. If you believe a child has created an account, write to us and we will remove it.

If this notice changes materially we will update the date at the top and say what changed. The current version was last reviewed on 19 August 2026.