Nectarcast

Privacy policy

Last updated 1 October 2026.

Nectarcast is run by Luke Briggs in Tasmania, Australia. Apiary locations are sensitive, and the site is built so they stay with you. This page says exactly what is kept and where it goes.

What is stored

Messages you send us

The contact form sends your email address, your message and any boxes you tick to dev@nectarcast.com. They are not stored in the database; they live in that inbox, and are used to reply to you and to decide what to build next.

Who can see your sites

You, and people you invite to a particular site. Nobody else is shown a site's name, position or observations.

The shared pool

New sites contribute to a shared pool, which is what lets a brand-new site forecast before it has a season of its own. What a site contributes is limited to:

Never a site name, an exact position, an observation date, a note, or anything that identifies you. Pooled thresholds are shown to other beekeepers, and on the public front page, only as an area forecast with a count of contributors. You can turn pooling off for any site at any time in its settings; doing so, or deleting the site, removes what it contributed.

Visitors who are not signed in

The front page guesses your area from your connection, using the approximate position our host (Vercel) attaches to each request. It is rounded to a 25 km cell before use and is not stored. A town you search for is looked up through Open-Meteo and is not stored either.

Services that handle data on our behalf

Some of these services store data outside Australia.

Deleting your data

You can edit or delete your own observations and sites at any time. To close your account and remove everything attached to it, email dev@nectarcast.com from the address you sign in with. The same address takes any question about your data, or a request for a copy of it.

Changes

If this policy changes in a way that affects what is shared, signed-in users will be told before it takes effect.