Privacy Policy

Last updated: October 13, 2026

1. What we collect

Account info: your email, name (if provided), preferred language, and experience level.

For official records (if you give them): your postal address, your beekeeper number with the national register, your national ID or tax number (RUT in Chile, NIF in Spain), your phone (Chile's field notebook asks for it) and your apiaries' register numbers. They are printed only on the official records you download (such as the medicine record), shown nowhere else and shared with no one.

If you record visitors in the apiary log (Chile's field notebook asks for it; the EU animal health record asks for the vet's visits), the name, ID number and phone you enter are kept only in your records and in the book you download; telling the visitor you are writing it down is up to you.

Spray notices: a farmer who gives one shares their name, phone and e-mail with the beekeepers whose apiaries lie in the zone; your apiary's location is used only to find whether it is in the zone, and the farmer sees only how many beekeepers were told, never who or where. A notice is kept three years after the application, then deleted; an unconfirmed one after a week.

Deliveries to a cooperative: when you deliver a batch to a cooperative, it sees your name, e-mail, postal address, phone and how many hives the batch came from (what buyers ask it for); your name appears on the cooperative lot's public page only if you say yes. If the cooperative inspects you internally, it records the report (date, hours, inspector, scope, findings, result); only you and the cooperative's admin see it, and your signature is kept with its time.

Beekeeping data: apiaries, hives, and inspection records you create (location, date, hive condition, notes).

Media: inspection photos and voice notes you upload.

Where a visit happened: during a visit your phone's location is used to show the visit was made at the apiary. No coordinates are kept, only the distance to the apiary (metres) and whether the hive's QR code was scanned. The date and place a phone writes into a photo are read too; again only the date and the distance to the apiary are kept. You can turn location off in your phone's settings; the visit is still saved, and the honey batch check says "unknown".

Medicine and feeding records, honey batches: the treatments you record (product, quantity, supplier, vet), the feeding you record (feed, amount, hives, reason, whether organic), each apiary's organic status and certifier, and the honey batches you seal. The earlier versions of corrections you make to harvests, visits, medicine and feeding records are kept too: traceability requires that no correction erase what was there.

Reminders and the calendar link: the reminders you write (what, which day, which apiary or hive). If you turn the calendar link on, its secret is kept only as a fingerprint (SHA-256); anyone with the link can see your reminders, treatment end dates and hive names — no location. You can renew or turn off the link at any time (Calendar screen).

Technical data: login tokens (JWT), basic usage logs and when you last used the app (to the hour; only to count whether people come back).

Visit counters: when someone opens the map without an account we store only the day, one word for where they came from ("reddit", "direct"), the country (as the network reports it, two letters) and a count. No cookie is set, no IP address is stored, no session is kept; these numbers cannot lead back to a person.

2. How we use it

Your apiary/hive/inspection data is used solely to run the service for you — health scoring, map display, reminders.

Voice notes are sent to OpenAI to transcribe your speech, then to Anthropic to extract structured inspection fields. Only the resulting transcript and extracted fields are retained afterward.

Photos are stored on Cloudflare R2 (cloud storage), accessible only to you and any delegates you authorize. They are sent to Anthropic for the AI comment.

Model training only with your permission: if you turn on "Help train the varroa model" in your Profile, photos you upload from then on, with their type (frame, board, bees), may be used to train ARIA's varroa-counting model; your name, email and apiary location are not used. A photo taken by a delegate needs both the hive owner's and the delegate's permission. It is off by default. Before any photo is sent to a service provider for training, that provider will be named on this page.

Your apiary's coordinates are sent to OpenWeatherMap for weather and place names, to GBIF for nearby flowering observations, and to OpenStreetMap and Esri (ArcGIS) servers for map imagery. For the flying hours of a place you tap on the map, its approximate position (rounded to 0.1 degree, roughly 11 km, and not linked to your account) is sent from our server to MET Norway (the Norwegian Meteorological Institute). Its location (country, region) is sent to Anthropic for the flowering and regulation explanations. When you seal a honey batch, your apiary's coordinates are sent to NASA POWER (NASA's climate data service) for the past weather on your visit days, not linked to your account. For fire alerts, NASA FIRMS's world file of fire hotspots is downloaded to our server and the distance to your apiary is worked out there; your location is not sent to NASA. When a hotspot is near, your apiary's coordinates are sent to OpenWeatherMap for the direction of the smoke.

3. Who we share it with

We do not sell your data. It is shared only with the sub-processors needed to run the service: hosting (Render, Vercel), database (Neon), file storage and domain services (Cloudflare), email delivery (Resend), AI processing (OpenAI, Anthropic), weather and place names (OpenWeatherMap), weather forecasts (MET Norway), past weather (NASA POWER), maps (OpenStreetMap, Esri ArcGIS), flowering data (GBIF). Payments are taken by our reseller Paddle.com; we never see card details, only whether your subscription is active.

If you add a "delegate," that person can see the apiaries you choose and add inspections, medicine and feeding records for you; managing hives and apiaries, recording harvests and sealing honey batches stay with you.

If you ask for a beekeeping association's members' price, that association's admin in ARIA sees your name and e-mail and approves or refuses the request; they never see your apiaries or records. Your membership is in your data export; you can withdraw the request from your Profile.

When you seal a honey batch, anyone who scans its QR code can see its page: the region and country (never your apiary's exact location), the producer name if you gave one, harvest dates and amounts, that season's medicine record, the number of visits and the results of the consistency checks. Opens of the page are counted only by day and country; nothing else is kept about the reader. Of sealed batches and cooperative lots, only the seal's fingerprint (a 64-character SHA-256 that the record cannot be rebuilt from, no personal data) is sent to the public OpenTimestamps calendar servers for the Bitcoin timestamp and is written into a Bitcoin block; that cannot be erased. If you attach a lab report to a batch or lot, the file and what you write about it are public on that page, and the file's fingerprint is timestamped in Bitcoin the same way. You can withdraw a report (it stays, marked as withdrawn); erasing your account deletes the file.

4. Your rights

You can view and update your information from your profile page.

You can download a copy of all your data as one file: Profile → Download my data. Photos and voice files come as download links valid for a week.

You have the right to permanently delete your account and all associated data, photos and voice files included: Profile → Delete Account.

You can withdraw your model-training permission at any time in your Profile; your earlier photos are then taken out of training too.

5. Contact

ARIA is operated by Yekta Sevim. For questions: hello@ariabuzz.com