How Bee Community handles your data

Bee Community ("we," "us," "the app") is operated at mybeecommunity.com. This policy explains what we collect from you as a beekeeper using the app, why, and what control you have over it. It's written to describe what the app actually does — not a generic template — so if a section doesn't apply to a feature you use, it's because that feature doesn't do that. Version 1.9 adds three kinds of notification our database may send you, each of which you can switch off, with a 30-day pause for them — getting-started tips, overdue check reminders and, on the free plan, a Sunday look-ahead — together with the notification timing record they use (the hour you last opened the app, whether a check was overdue then, and the days your phone holds a reminder of its own), a count of which notifications are opened, kept with the send log for up to 14 days, and a count of how often the plans and paywall screens are seen, which carries no account identifier (see Reminders & notifications). If you last accepted version 1.7: version 1.8 describes five new tools and what each one records. The bring-a-friend referral programme creates a referral code for you and a record for each referral, and that record stays after an account is deleted with the deleted member's identifier removed (see Information we collect and Retention); a verified club's vouch for your mentor listing is new community data shown to other members as a badge, with the organizer's note visible only to you and the club's organizers (see Community network); NFC hive tags and QR codes carry only a hive's id, and the season recap card is built on your phone from your own logbook and shared where you choose (see What's public vs. private); in-app announcement banners are chosen from your plan and your account's age and create no new personal data; and three notifications are added to the list, with their switches — the referral reward, the season opener and the club vouch (see Reminders & notifications); and Community network now lists the further actions a muted or banned member cannot take. If you last accepted version 1.6: version 1.7 added sections for members in Canada, Québec, the European Economic Area, the United Kingdom and Switzerland (sections 19 to 22), described how community moderation works and the records kept after an account is deleted, and named the services that send our emails and screen community photos. These notes summarise the changes back to version 1.7 only; if you last accepted something earlier, the sections below are what applies, and the app will ask you to read and accept this version once.

Information we collect

We collect only what the app's features need to function. Nothing here is collected passively in the background.

Account information

When you sign up: your email address, the display name you choose, and the region you select (used to tailor seasonal content like colony-phase timing, swarm windows and winter-stores targets — not your precise location). Optionally, your US state (and in California your county), and whether you sell honey or bees — see Your state & registrations. You can change all of these later from the Account screen (the account icon on Home).

Your password is handled by our backend provider's sign-in service, and the app keeps a sign-in session on your phone so you stay signed in.

Hive & logbook data

Hive names, types, yard groupings, hive configuration you enter (supers on, screened bottom board, number of brood boxes, frames of bees), a colony-phase override, your current queen's record (mark colour, year reared, source, installed date), and — only if you choose to drop a pin — a location for that hive. Logbook entries (inspections, treatments, harvests, feedings, queen events and heft checks) and whatever details you enter for each, including the product, dates and dose text of a treatment and the acknowledgement that you read its protective-equipment list. Mite-wash results (mites counted, bees sampled, method, colony phase, context) are kept as their own records so the app can chart them. If a colony dies, the date and reason you choose. On Premium, the apiary books you keep: expenses (category, title, amount, date, an optional hive or yard and note) and bee sales (kind, count, price, an optional buyer name, the hive a nuc came from or the hive that was sold, line name and note) — private to your account like the rest of the logbook.

Each hive can also carry a state, province or territory (US states, the District of Columbia and the Canadian provinces and territories). For a pin in the United States it is filled in by a separate state lookup: the app sends the hive pin, rounded to two decimal places (about 1.1 km), to the U.S. National Weather Service, which answers with the state the point is in. The app makes this request when you place or move a pin on the hive form, and — without you doing anything — once per app session from the Community tab for each active pinned hive that has no state yet. Pins outside the United States are sent too; the service returns no state for them, and you choose it yourself. You can change the state at any time. An older logbook entry may still hold a suggestion saved by the photo-diagnosis tool that was withdrawn; it is shown as a note only, and nothing new is created.

Voice quick-log

If you use the voice quick-log, the app asks for microphone access and uses your phone's own speech recognition, set to run on the device; the microphone button appears only on phones that can do that. The app does not upload the audio.

Reminders

Reminders you write yourself — a title, an optional hive, a due date, an optional repeat interval and note — and when you marked each one done. The alerts the app derives from your logbook (treatment removal dates, mite-check cadences, seasonal tasks) are computed on your phone and are not stored on our servers; only your snooze and done choices are kept, on the device.

Push token & nearby-alert preferences

If you allow notifications, the app registers a push token with your account: an identifier issued by Expo, Inc.'s push service for this app on this phone (it looks like "ExponentPushToken[…]" and is not your phone's advertising or hardware ID), which is the only way a notification can be addressed to the phone. We store the token, which platform the phone runs (Android today), when it was registered and when it last checked in — at most five phones per account. We also store your nearby-alert preferences with your account — your alert radius in miles and which categories you want — because our database reads them when it decides whom a new alert reaches, and, in the same record, the Referral rewards and Season opener switches from Settings → Reminders (both on unless you turn them off); the "Mentor requests, messages and club vouches" switch also decides whether a club-vouch notification reaches you. The settings, snooze and done choices for the reminders built on your phone stay on the phone. See Reminders & notifications.

Location data

We request location access only when you tap "Use my location" — to drop a pin marking where a hive is, to fetch a one-off local forecast when you have no pinned hive, or to mark the rough spot of a swarm alert, bloom report or area alert you are posting (you can place that spot by tapping a map instead). The app does not track your location in the background, does not record your device's location automatically, and does not share hive locations with other users — they're private to your account, enforced at the database level. A hive pin you place is stored with your account on our servers at the precision you placed it, and stays private to you (see below). Apart from that, the locations that leave the phone are all rounded to two decimal places (about 1.1 km, roughly two-thirds of a mile) before they go: the weather request described in Weather and the state lookup described under Hive & logbook data above, both sent to the National Weather Service and never stored by us (only the state it returns is saved on the hive); the rough spot on an alert you post (optional on swarm alerts and bloom reports, required on area alerts), which is stored with the alert and shown to other members as a circle about a mile across — see Community network; and, if you set one, a rough home point — captured only when you tap "Use my location" or type a place on the "Where are you?" card, rounded to two decimal places, stored in your profile where only you can read it, used inside our database to measure how far a swarm, area alert or bloom report is from you when you have no pinned hive, and never shown to other members. You can change or clear it from Settings at any time. Your hive pins are also used, inside our database only, to work out whether a new alert is within the radius you chose; the pins never leave the database to do that — see Reminders & notifications.

A hive pin itself is stored with your account at the precision you placed it (an address or coordinate lookup is rounded to six decimal places, about 10 cm; a pin from "Use my location" keeps the precision your phone reports); only the weather and state lookups, alert spots and the home point are rounded to two decimal places. Your active hive pins are also used inside our database to decide which posts appear in the community feed's "near" view — see Community network.

Photos

Photos you choose from your photo library or take with the camera to attach to a community post, a swarm alert, an area alert or a logbook entry. The camera and your library are opened only when you tap a photo button. Community, swarm-alert and area-alert photos are shared (see What's public vs. private); a community or club post photo is safety-screened before it uploads (see How we share it); logbook photos are private (see Logbook photos).

Before any photo is uploaded, the app downsizes it and removes its embedded metadata, including any GPS location stored in the file.

Community content

Posts, comments, and likes you create in the community feed and in any club you join, plus the community-network records described in Community network: bloom reports, swarm alerts and replies, area alerts, your mentor listing and mentor requests and messages, and club memberships. If an organizer of a verified club you belong to vouches for your mentor listing, we store the club vouch: which club, which organizer, an optional note of up to 140 characters, and when it was made; if you decline it or the club withdraws it, the record is kept with that date but is no longer shown to any member. If you are a club organizer, the vouches you give are stored the same way. If you report a post, comment or any other member content, we store the report — what you reported, the reason you gave, and that it came from you — so a person can review it. If you block another member, we store that so their content stays out of your feed and they can't message you.

You can also report a member rather than a single item; the report stores the reason you chose (spam, harassment, unsafe, underage, impersonation, location privacy or other) and any detail you add. When you accept the Community Guidelines, we record which version you accepted and when.

Moderation records

To keep the community safe we keep records of moderation: any warning, mute or ban applied to your account (its kind, reason, expiry, whether it was lifted, whether it was applied automatically or by a moderator, and whether a ban applies to the community only or to your whole account — you can see your own); a moderation log of automatic and moderator actions — such as content being hidden, member reports and account deletions — which records the member concerned, a copy of their display name at the time, and for hidden content or a member report the first 160 characters of the text; and a copy of each moderation notice we send you by push or email, including any message sent to you by our moderators or support team (subject, text, the address it went to and whether it was delivered). How moderation works is described in Community network.

Honey, club and apiary-book records (Premium tools)

If you use them: honey harvest batches (yard, extraction date, frames pulled, yield, jar size and count, notes) and honey sales (date, jars, total price, an optional buyer name or description of up to 80 characters, notes), which are private to you; and a club's shared expenses and treasury (a title or kind such as dues or deposit, amount, date, notes, which member paid or is concerned, and who the cost is split among and has settled), which every member of that club can read. A buyer's name, or another member's name on a club record, is information about someone else — enter only what you need. Your apiary books (above) are the same kind of record: private to you, and a buyer's name you enter is information about someone else.

Subscription records

If you buy or are given a plan: the plan and product, the store, its status and renewal setting, the current period, the price and currency, and the latest billing event; a copy of each billing event message RevenueCat sends us; and any promotional code you redeem and how long it grants access. We also record that your account took the swarm-season trial (the region it was judged in and the day it ends) and, for a club seat pack, which club it belongs to, how it was paid and who bought it. If you open the Invite a beekeeper screen, we create your referral code (BEE-XXXX-XXXX) and keep it with your account; and for each referral — one when a friend uses your code, one when you use a friend's — we keep a record of the two accounts, the code, its status (pending, charged, rewarded or void), the dates of each step, the fact that the referred member's first payment went through — its date, the plan and the store's transaction reference for it, never the amount, read from the billing record we already hold — the two one-use grant codes behind the months, and, if it was voided, the reason and who voided it (a person on our team, or our nightly check when that first payment is refunded). See Premium & billing.

Consent records

When you accept our Terms and this policy, we log an audit record — your account and its email address, a timestamp, and which version of the document and app you accepted — so there's a permanent record of consent. Once created, that record isn't edited or deleted, by you or by us, and it's kept after your account is deleted (see Retention below). The record also holds a fingerprint (a SHA-256 hash) of the exact document you were shown.

Technical data and our website

The app contains no advertising, analytics or crash-reporting software, and no third-party measurement. We do keep some counts of our own, such as how many of the notifications we send are opened and how often the plans and paywall screens are seen, as described in Reminders & notifications. The device details it sends itself are limited to the phone's platform (with a push token), the app version (with a consent record), and a line naming the app and our support address on weather and address-search requests. When something goes wrong, our server functions may write your account identifier or a file's storage path to their error logs. Like any internet service, the services your phone contacts directly — our backend provider, the weather and address-search services, the photo-screening function and the push, billing and map software built into the app — receive your device's IP address with each request. The billing, push and map software (RevenueCat's SDK, Firebase Cloud Messaging and the Google Maps SDK) also sends those providers technical details of the device and app under their own designs — for example the app version, the Android version and a device or installation identifier — as described in RevenueCat's and Google's privacy policies; we do not add your name, email or beekeeping data to any of it.

Our website, mybeecommunity.com, is hosted by Expo Application Services (Expo, Inc.). Its pages load fonts from Google Fonts, and the password-reset page loads a software library from jsDelivr and talks to our backend provider to finish your reset or sign-up confirmation; those services receive your browser's request details, such as its IP address. The website pages contain no analytics code. The page an NFC hive tag points to, mybeecommunity.com/hive/hive id, loads no fonts and runs no script that sends data; it reads the hive id from the address only to offer an Open-in-the-app link. Like any web page, the address — which carries the hive id and nothing else — and your browser's request details reach our website host when the page opens.

Information about you from other people

Some information about you comes from other members rather than from you: reports another member files about you or your content; your name on a club's shared expenses or treasury record, entered by a club organiser or member; a name entered as the buyer on another beekeeper's honey sale or bee sale (apiary books); a club organizer's vouch for your mentor listing and the note they wrote with it; if a friend used your referral code, or you used theirs, the status and dates of that referral (never the other member's name); and the moderation records that result from reports. We also receive the status of your purchase from Google Play through RevenueCat.

How we use it

• To create and maintain your account, and let you sign back in.
• To run the features you use — your logbook, your hives' computed stats and mite trend, the alerts and reminders derived from your entries, the troubleshooting tree's saved progress, the field guide, the community feed and network.
• To show your region-relevant content (seasonal tasks, swarm windows, bloom calendar) and, if you add a state, your state's apiary-registration and honey-labelling rules.
• To fetch a forecast for your yard from a weather service, using only an approximate location.
• To send you the nearby and community notifications you opt into — working out, inside our database, whether a new alert's rough spot is within your chosen radius of your hive pins, and telling you about replies, comments and messages addressed to you.
• To let other members recognise your posts, reports, alerts and mentor listing by your display name.
• To keep the community safe: refusing community text that contains links, phone numbers, cryptocurrency wallet addresses, off-platform payment or contact handles, or abusive or threatening language; hiding reported content; applying warnings, mutes, community or account bans and suspensions; telling you about them by push notification and email; and keeping a moderation log.
• To manage subscriptions and promotional access, and keep a record of the billing events the store reports.
• To run the bring-a-friend programme: mint your referral code, check each night against the billing records we already hold whether a friend who used it has made a first payment that stood for 7 days, grant and count the months, hold your month while a store plan is live, and void a referral that was refunded or abused.
• To show a verified club's vouch on your mentor card and profile, list vouched mentors first in the directory, and tell you when a club vouches for you.
• To pick which announcement banners to show you inside the app, from your plan and how long ago your account was created — never from what you do in the app.
• To send you the referral-reward and season-opener notifications while you leave them on.
• To keep the honey, club-finance and apiary-book records you choose to enter.
• To screen a photo you attach to a community or club post before it uploads, so obviously sexual or violent images never get a first showing.
• If you opt in, to count your routine mite washes into anonymous state statistics that every member can see as an index and Premium members as a band on their own chart.
• To keep a consent audit trail for legal accountability.
• To respond when you contact support.

We do not use your data to serve ads — there are none — and we do not sell your information to anyone. We do not build profiles for marketing: the announcement banners in the app are chosen by two facts only — your plan and how old your account is — and nothing you do in the app is used to choose them. We do not use your logbook, your washes or your photos to train any AI model. No photo of yours is sent to an AI provider: the photo-diagnosis tool that earlier versions of this policy described has been withdrawn, and the only automated look at any photo is the safety screen on community and club post photos described in How we share it, which answers allow or refuse and keeps nothing else.

If you are in the European Economic Area or the United Kingdom, the legal basis for each of these uses is set out in section 21; Switzerland is covered in section 22.

How we share it

We use Supabase as our backend provider — it hosts our database, handles authentication, and stores uploaded photos. Supabase processes data on our behalf under its own security commitments. Its contracting company is Supabase Pte. Ltd. (Singapore); our database is hosted in Amazon Web Services' Oregon region in the United States.

We use the U.S. National Weather Service (NOAA, api.weather.gov) for weather forecasts. The only thing it receives is an approximate location — a hive pin rounded to two decimal places (about 1.1 km, roughly two-thirds of a mile) — and it may log your device's IP address for technical reasons. It does not receive your name, account, hive names or exact coordinates. Weather is available in the United States only. See Weather.

The app also sends the National Weather Service a separate state lookup — again a hive pin rounded to two decimal places, and nothing else about you — to fill in a hive's state: when you place or move a pin on the hive form, and once per app session from the Community tab for each active pinned hive with no state. See Hive & logbook data.

If you look up an address or place name while placing a hive pin or setting your rough home point on the "Where are you?" card, the text you type is sent to OpenStreetMap's Nominatim search service (OpenStreetMap Foundation, servers in the United Kingdom and the Netherlands; its privacy policy) to turn it into map coordinates. It receives that text and may log your device's IP address; it never receives your name, account, hive names or existing pins, and nothing is sent unless you type in that field. Search results © OpenStreetMap contributors.

To deliver nearby and community notifications while the app is closed, we use Expo, Inc. (Expo Application Services, United States), whose push service relays each notification to Google (Firebase Cloud Messaging) for delivery to your Android phone. Our database sends Expo the push token for your phone and the notification itself — a title, one line of text such as "Swarm alert nearby · Bucks County · about 8 miles from your hive", and a small data block used to open the right screen in the app and to count opens, which can include identifiers such as a hive's, a post's or your own account's identifier — and later asks Expo whether it was delivered. Those two services receive the token, that text and that block. We do not include your name, email, hive locations, logbook, or the content of a reply or message in what we send them. The referral-reward and season-opener notifications are fixed text; a club-vouch notification's title carries the club's name. If you never allow notifications, no token exists and nothing is sent. See Reminders & notifications.

Moderation notices (see Community network) are also sent by push notification through the same services, and their text can state the reason for a warning, mute, ban or suspension. A message to you from our moderators or support team can be sent the same way.

When you attach a photo to a community or club post, the app sends it — through our own server function, before it uploads — to Google Cloud Vision's SafeSearch detection (Google LLC, United States) for an automated safety screen. Google receives the image bytes only, as the downsized copy the app would upload (1,280 pixels on the longest side, camera metadata removed): not your name, account, region, caption or any location. The screen answers allow or refuse with a category (sexual, violence or gore); a refused photo is never uploaded, the post can still go out as text, and the app tells you in one sentence why. We keep only the category in our server log — never the image. If the screen cannot be reached, photos cannot be attached until it can (the screen fails closed rather than letting an unscreened photo through). Logbook photos, swarm-alert photos and area-alert photos are never screened and never sent to Google. See the Terms, Automated photo screening.

We send moderation emails through Resend, an email delivery service. When a warning, mute, ban, lift, suspension or unsuspension concerns you and your email address is confirmed, Resend receives your email address and the notice — its subject and text, which states the reason and can quote up to the first 80 characters of your own hidden post or comment. When one of our moderators or support team sends you a message through our administration tools (a subject of up to 80 characters and a message of up to 2,000), Resend receives your email address and that message if email was chosen for it. Resend also delivers alerts to our own moderators when an item needs review; those alerts can name the member concerned. Sign-up confirmation and password-reset emails are sent by our backend provider's sign-in service through Resend as well.

If you buy Premium, Commercial or a club seat pack, the purchase is processed by Google Play (the store you bought through — for buyers in the European Economic Area, the United Kingdom and Switzerland the seller is Google Commerce Limited, Ireland) under Google's own terms and privacy policy, and by RevenueCat, which we use to keep track of whether a subscription is active. We never receive or store your card number — the store handles payment. RevenueCat receives your account's internal identifier — a random code that is not your name or email (a pseudonymous identifier) — together with the fact and status of your purchase, and the store receives what it needs to process the purchase, so we can unlock the plan you bought and show it as active. Bee Community is currently available for Android on Google Play only. See Premium & billing.

On Android, maps in the app are drawn with the Google Maps SDK, which loads map images from Google for the area you are viewing and operates under Google's own terms and privacy policy; we do not send it your hive pins as data, but the map you look at shows them.

Our website is hosted by Expo Application Services, and its pages use Google Fonts and jsDelivr as described in Information we collect; the hive-tag page at /hive uses neither. Support emails you send us are received and stored by our email provider.

When you share your referral code, a season recap card or its text summary, it goes through your phone's share sheet to whatever app and recipients you choose — a message, an email, a social app, a file — and we do not see where it went. The share text carries a link to the app on Google Play; the card carries counts and totals from your logbook and, only if you switch it on, your hive names. The QR tag sheet you print is handed to the share sheet the same way; the printed sheet shows each hive's name and yard name beside its code — the code itself carries only the id — so share the PDF as you would any list of your hives.

Within our company, only people we authorise as operators or moderators can use our administration tools. To handle reports, support and billing questions, they can see a member's account details including email address and account status, their posts, comments and other community content, reports made by and about them, sanctions, notices and moderation history, subscription status, their hive names and whether each hive is active (but not hive locations), the number of honey batches they have recorded, and how much photo storage they use; referral records with both members' identifiers, their status and the date and plan of the friend's first payment; club vouches with their notes and history, including declined and withdrawn ones; the announcements that have been published; and, for the notifications we send, a member's notification timing record together with their recent notifications and the hour each was opened, and the recent delivery log across members (the member, the kind, whether it was sent and when). They can message a member, apply or lift sanctions, suspend or delete an account, grant a plan, void a referral, take a club's vouch off a mentor's listing, and publish, change or take down an announcement. They act under the responsibility of the Owner of UnGrounded Innovations LLC.

Apart from the services named in this section and other members as described in What's public vs. private, we don't share your data with any other third party for their own purposes. Supabase, Resend, RevenueCat, Expo and Google (for Cloud Vision and Firebase Cloud Messaging) act for us, on our instructions; Google acts for itself when it draws maps and when Google Play sells you a plan; the weather and address-search services receive requests your phone sends directly. We may disclose information if required by law, to protect the rights and safety of our users, or in connection with a merger or acquisition of the company — in which case you'd be notified.

What's public vs. private

Your display name (not your email) appears on anything you post publicly. Your region appears on your mentor listing and community-network records; your state does not. Club posts are visible only to members of that club. A phone number you add to a swarm alert is visible only to you and to the one member who claims the alert. Your hive pins, your rough home point, your alert radius and your notification settings are never shown to anyone; a member who is notified of your alert learns only how far its rough spot is from their own nearest hive or home point. Your referral code is shown only to you and to whoever you send it to; a member whose code you used sees that someone joined with it and when, and later that the member's first payment went through, never your name or what you paid, and you see the same about the members who used yours. A printed QR code or a written NFC tag carries only the hive's id — no name, yard, pin, note or account — and the hive opens only on a phone signed in to the account that owns it; on a phone signed in to another account the app says the hive is not one of yours. A printed QR code opens nothing on a phone without the app; an NFC tag tapped on a phone without the app opens a web page saying the tag belongs to a Bee Community hive, with a Google Play link. The season recap card and its text summary carry counts and totals from your logbook — never a hive location, pin or yard — and your hive names only if you switch them on for that card; where they go is your choice in the share sheet.

"Never visible to anyone else" refers to other members: the authorised operators and moderators described in How we share it can see the account and community information listed there. Honey harvest and sales records and your apiary books are private to you; a club's shared expenses and treasury are visible to every member of that club.

Reminders & notifications

Reminders — built on your phone

If you turn reminders on, the app schedules local notifications on your phone from your own logbook — treatment removal dates read from the product label, mite-check cadences, queen follow-ups, seasonal tasks for your region, apiary-registration renewals and the reminders you write yourself. Everything about a reminder is computed and stored on the device: no server knows what you were reminded of, and nothing about your hives leaves the phone to make one fire. The app schedules at most two reminders a day and none between 8 pm and 7 am; you can turn each category off in Settings or change the hour. Your snooze and done choices are stored on the device only. A check that is already overdue can be reminded again in the weeks after it was due, a limited number of times. On a phone that holds a push token, where your profile or a hive carries a US state or Canadian province, the app generally leaves that repeat out and the overdue check reminder described below takes its place.

Nearby & community notifications — sent to your phone

Some things happen while the app is closed and come from other members, so they cannot be built on your phone. If you allow notifications, the app registers a push token for this phone with your account (see Information we collect), and our database sends you a short notification when:

• a member posts a swarm alert, area alert or bloom report with a rough spot that falls inside the alert radius you chose — Off, 5, 10, 25, 50 or 100 miles (25 miles unless you change it), measured from your own hive pins;
• someone replies to or claims your swarm alert, comments on your post, sends you a mentor request, accepts yours, or messages you in a mentor thread — or, if you switch it on, posts in a club you belong to;
• on Premium, and only while the switch is on (it is on unless you turn it off), once on Sunday evening — the Sunday week plan: one push in the 6 pm hour of the time zone of the US state or Canadian province in your profile or on your hives, saying the week's plan is ready; if neither carries one — for example outside North America — it is sent at 6 pm UTC. Its text is the same for everyone and never contains a hive name, a location or a count; the switch is the "Sunday week push" card in Settings; on the free plan that switch covers the Sunday look-ahead described below instead.
• on every plan, and only while the switch is on (it is on unless you turn it off), once per rewarded referral — the referral reward: one push saying "A beekeeper you invited is now subscribed" and "Their first payment went through and 7 days have passed. A month of Premium is on your account now. Nothing you already held is shortened or lowered.", sent between 9 am and 8 pm in the time zone of the US state or Canadian province in your profile or on your hives (if neither carries one, a zone matched to your region — Pacific or Central), opening the Invite screen. It is the same text for everyone and never names the member who used your code. The switch is "Referral rewards" under Settings → Reminders.
• on every plan, and only while the switch is on (it is on unless you turn it off), once per season change — the season opener: one push in the 9 am hour of that same time zone, during the first seven days of the month a new colony-phase season starts in your region, saying that the season has begun. Its text is the fixed line for your region and never contains a hive name, a count, a pin or a location; a member with no region set gets none. The switch is "Season opener" under Settings → Reminders.
• a verified club vouches for your mentor listing — the club vouch: one push per vouch, within seven days of it, between 8 am and 8 pm in that time zone, whose title names the club ("Club vouched for you as a mentor") and whose text is fixed — never the organizer's note or name — opening your listing, where you can decline the vouch. It goes out only while the "Mentor requests, messages and club vouches" switch is on and not between members who have blocked each other.

Announcements from us are banners at the top of the app, not notifications: nothing is pushed to your phone for them.

The distance check runs inside our database: it compares the alert's rough spot with your hive pins and keeps only the result — your pins are never sent anywhere, not to the alert's author and not to the push service. You get one notification per alert, however many of your hives or yards fall inside the circle, and its text says how far the spot is from your nearest hive, rounded to whole miles ("about 8 miles from your hive"). You are never notified of your own posts, nor of anything from a member you have blocked or who has blocked you; a member with no pinned hive gets no nearby alerts at all (the Settings card says so), and swarm alerts and bloom reports posted without a rough spot notify nobody. Notifications about replies, claims, comments and messages name the member (their display name) but never contain the text itself. Nearby and community notifications arrive as things are posted, at any hour — a bear or a spray truck does not wait for morning — so your phone's Do Not Disturb and, on Android, the per-channel settings ("Nearby alerts", "Community activity") are the quiet control; the two-a-day, none-overnight rule applies to reminders, and we aim to keep the tips, check reminders and look-ahead below to your daytime as well; it does not apply to nearby and community notifications.

Each notification travels from our database to Expo, Inc.'s push service and on through Google Firebase Cloud Messaging (Android) to your phone. Those services receive the push token, the notification text and a small data block that travels with it: what the app needs to open the right screen and to count opens, which can include identifiers such as a hive's, a post's or your own account's identifier (see How we share it). We keep a log of what we sent — recipient, title, text, time, the delivery result the push service reported and, for a notification you tapped on a current version of the app, the hour you opened it — for up to 14 days, so we can spot phones that can no longer be reached and stop sending to them, and count how many notifications of each kind are opened (the totals we keep after that are per kind and per day, with no member attached); a token the push service reports as gone is deleted straight away. No member account can read that log; only the database's own sending routine, and we as the operator when checking delivery, can.

The app asks for notification permission only after you tap a "Turn on" button, never at launch, and it never registers a push token before you have allowed notifications. You choose the radius and switch each category on or off in Settings → Nearby alerts & community (swarm alerts nearby, area alerts nearby, replies and claims, comments and mentor activity are on unless you turn them off; bloom reports nearby and club posts are off unless you turn them on). Setting the radius to Off stops the three nearby categories (swarm alerts nearby, area alerts nearby and bloom reports nearby) and nothing else; replies and claims, comments, mentor activity and club posts each stop only when you turn its own switch off. The referral-reward, season-opener, getting-started-tips and overdue-check-reminder notifications are on unless you turn them off, each with its own switch under Settings → Reminders; the club-vouch notification follows the mentor switch. Turn every category off and we stop sending; disable notifications for Bee Community in your phone's settings and the phone discards anything that arrives, and the app generally releases this phone's push token the next time it runs and can reach us. Either way the feeds and the alert list in the app keep working. When you sign out, the app tells our server to forget this phone's token (if the phone is online at that moment); a token is also deleted when the push service reports the phone unreachable, when the phone has not checked in for 180 days, and with your account. Push delivery is best effort: the operating system, a battery saver or a dropped connection can delay or drop a notification, so never treat one as your only warning of anything.

Getting-started tips, overdue check reminders and the Sunday look-ahead

If you allow notifications, and once you have accepted these documents, our database may also send you these, on every plan and while the matching switch is on (each is on unless you turn it off):

• Getting-started tips — generally up to two while you are setting up, each of which we aim to send only once: "Add your first hive" (a new account with no hive) and "Log your first visit" (a hive you have not logged yet; with one hive it opens that hive's quick log, so its link carries the hive's identifier). The switch is "Getting-started tips" under Settings → Reminders.
• Overdue check reminders — "A check is overdue in your yard", generally when the app itself last found an overdue check, your account is a couple of weeks old, the app has been closed for some days and nothing has been logged since; and a note after about two weeks away while you have an active hive. These repeat only occasionally, and generally stop once you have opened the app again and it has been able to reach us. The switch is "Overdue check reminders" under Settings → Reminders.
• The Sunday look-ahead — on the free plan, a Sunday-evening push saying this week's core checks are ready, while you have an active hive and have opened the app recently. It is covered by the same "Sunday week push" switch as the Premium week plan.

We aim to send these sparingly: in the daytime of the time zone of the US state or Canadian province in your profile or on your hives (we do not send them when neither carries one), generally at most one a day and a few in any week — counting the Premium week plan and the days your phone tells us it holds a reminder of its own — and not just after you have used the app. "Pause tips for 30 days" in Settings holds these kinds. Their texts are the same for everyone, and we do not put a hive name, a location or a count in them; on Android, a current version of the app gives each kind its own notification channel ("Getting-started tips", "Overdue check reminders", "Sunday look-ahead"), so you can generally silence one kind without the others on that phone; an older install of the app may show them together with its other notifications. Like any notification, one of these can be delayed or dropped by your phone or by the push services, and one sent late in the day may be discarded rather than delivered.

To keep to that, while notifications are on and this phone holds a push token, the app tells our server, when you open it and after it plans your reminders: the hour you last opened it, whether a check was overdue at that plan (yes or no, not which check or how many), and which of today and the next 30 days your phone holds a reminder of its own, with that date (one yes or no per day, not what the reminder is). Our server keeps that, together with what an earlier report said about the days just before, which one-time tips and notes it has already sent you and when it last sent an overdue check reminder. It also records the hour you tapped one of our notifications, so we can count how many are opened. We do not record any of this before you have accepted these documents. When you turn notifications off for Bee Community or sign out, the app releases this phone's push token the next time it runs and can reach us. Once none of your phones holds a token, our server clears the last-open, plan, reminder-day and overdue-reminder details, generally within a day, and keeps which one-time tips and notes were already sent. Whatever happens with a token, that record is kept for at most 180 days after your last app open, and is deleted with your account. Views of the plans and paywall screens are counted per day, without an account identifier.

Weather

To show inspection and treatment weather for your hives, the app sends an approximate location — your hive pin rounded to two decimal places (about 1.1 km, roughly two-thirds of a mile) — to the U.S. National Weather Service (NOAA, api.weather.gov), a government weather service that needs no account or key. If you have no pinned hive you can tap "Use my location once"; the app rounds your device's location the same way, keeps the rounded value only on the phone, and never writes it to our servers. The service may log your device's IP address for operational reasons; we do not send your name, account, hive names or exact coordinates, and we do not receive anything back except the forecast. Because it is a U.S. service, weather is available in the United States only; outside its coverage the app shows that the forecast is unavailable and everything else keeps working.

Members outside the United States — in Canada, the European Economic Area, the United Kingdom or Switzerland, for example — therefore do not receive forecasts in the app. The request is still made for a pin outside the United States; the service answers that the point is outside its coverage and the app shows the forecast as unavailable.

Forecasts are cached on your phone for up to 24 hours so a screen does not re-request them every time it opens. National Weather Service data is a U.S. Government work in the public domain, and is credited ("Weather data by the U.S. National Weather Service (NOAA)") on every weather card and on the Credits screen. The inspection grades and treatment-window checks shown next to a forecast are computed by Bee Community from that data using published extension guidance and product-label temperature ranges; they are a weather check, not a treatment recommendation.

If the weather provider ever changes, this section and the consent version will change with it and you will be asked to accept the new policy.

Offline storage on your device

The logbook is built to work in a bee yard with no signal. Your hives, logbook entries, mite washes, apiary registrations and reminders are cached on your phone in the app's private storage, and anything you add or change while offline is queued there and sent to our servers when you're back online. Each change carries a timestamp; if the same record was edited on two devices, the later edit wins and the app tells you when one of yours was replaced.

The cache also holds your last forecast, your reminder preferences, your snooze and done choices, the push token registered for this phone, an unsaved quick-log draft, your place in the troubleshooting tree, your referral code and referral progress, your "Not now" on the Home invite card, the announcement banners you were last offered and which ones you have seen or dismissed, your "Got it" on the new-season card, what the app last told our server about your reminders (the hour, whether a check was overdue, and the reminder days), your "Not now" on the Home set-up steps, the plan you last picked in the plan picker and your "Not now" on its comparison, and enough of your profile to open the app offline. It is stored only on that device, is never shared, and is cleared when you sign out or delete your account (the app warns you first if changes haven't synced yet). Your nearby-alert radius and category switches — the Sunday week-plan switch, and the Referral rewards, Season opener, Getting-started tips and Overdue check reminders switches with the 30-day pause — are the notification settings stored with your account rather than on the phone, because the database needs them to decide whom an alert or one of those pushes reaches. Community content, photos and your profile are online-only and are not cached.

Logbook photos

Photos you attach to a logbook entry (up to four per entry, from the camera or your library, downsized on the phone before upload) go to a private storage bucket. Only your signed-in account can read them: the app fetches each one through a short-lived signed link, there is no public address, and they are never shown to other members or used anywhere else in the app. They are removed when you delete the entry, the hive it belongs to, or your account. If an upload fails while you're offline, the photo waits on your phone and is retried when you reconnect. Logbook photos count toward your plan's photo storage allowance — 100 MB on the free plan, 2 GB with Premium, 10 GB with Commercial — together with the photos on your community posts, swarm alerts and area alerts. When the allowance is full, new photos are not uploaded until you delete some; nothing you already stored is ever deleted for being over it.

Community network

The Community tab adds five shared tools. Swarm alerts, area alerts and bloom reports are shown to members within their alert radius of their hive pins or home point (a swarm alert or bloom report posted without a rough spot is shown within its region instead); the other tools are visible to other signed-in members in your region unless stated otherwise. Because nearby lists and notifications are measured in miles rather than by region, a member in a neighbouring region whose hive pins or home point fall inside their radius can see, be notified of, and open a swarm or area alert that carries a rough spot. The distance is worked out inside our database from the other member's own pins or home point, which are never shown to you. All of it is covered by the reporting and blocking tools described below.

The community feed. By default the feed's "near" view shows posts whose author has an active hive pin within a distance of your own hive pins; the distance is worked out inside our database in broad 10, 25, 50 or 100-mile bands, to make it harder to work out where anyone's hive is. The "states" view uses the states, provinces or territories of authors' hives. This means your active hive pins and your hives' states decide in whose "near" or "states" view your posts appear, although neither is ever shown to anyone. Your own "states" view shows posts from authors with a hive in the same states as your hives; if none of your hives has a state, the state in your profile is used instead. It is still not shown to anyone. You switch views with the chips above the feed (near, states, region, all); near is the default and the app remembers your choice on this phone.

• What's blooming — bloom reports: the plant, its status, an optional note, an optional coarse area label, your region and display name, and — only if you add one — a rough one-mile spot (see below) so that members within their radius who have switched bloom notifications on hear about it. No other location.
• Swarm alerts — a description, an optional photo, a coarse area label (a town or county; the database rejects anything that looks like a street address, coordinates or a map link), an optional rough one-mile spot (see below) so nearby members can be notified, your region and display name, and an optional phone number that is stored separately and shown only to you and to the one member who claims the alert. Alerts expire after 72 hours. Replies carry your display name.
• Area alerts — a warning to nearby beekeepers about something in the area: bear activity, pesticide or mosquito spraying, robbing or yellowjacket pressure, hive theft or vandalism, disease confirmed nearby, wildfire smoke, flooding, or something else. Each carries the kind, a coarse area label (same rules as swarm alerts), a required rough one-mile spot, an optional note of up to 500 characters, up to three photos, your region and display name, and — if you turned one of your own community posts into the alert — a link back to that post. An area alert stays open for 3 to 30 days depending on its kind (spraying and smoke 3, robbing 5, bears, flooding and other 7, theft 14, confirmed disease 30) or until you close it; you can edit its label and note (photos cannot be changed after posting), close, re-open or delete it, and post up to five a day.
• Mentors — if you choose to list yourself: years kept, hive count, topics, an introduction, an optional coarse area label (a town or county — the database refuses street addresses and coordinates), your region and display name. Mentor requests and the messages exchanged in an accepted request are stored so both people can read them; nobody else can, and a blocked member cannot message you. An organizer of a verified club you belong to can vouch for your listing: members with a confirmed email who are not muted or banned then see "Vouched by club" on your card and profile (up to two clubs, then "+N more"), and vouched mentors are listed first. The organizer's optional note is readable by you and by that club's organizers only, and the app does not tell you which organizer vouched. You can decline a vouch from your own listing at any time; the club can withdraw it; a vouch is not shown while the club is not verified and comes back if the club is verified again; and a person on our team can take it off, with the reason kept in our moderation log. A declined or withdrawn vouch is kept but hidden from every member.
• Clubs — a club's name, description, state, city, website and meeting note are visible to members in that region; the member roster and club posts are visible only to members. The clubs you found or join are recorded with your account. A club's "This season" card shows how many of its members share wash statistics (below) and, once five or more do, counts of washes and treatments across the club in the last month — never a figure for one member. Once a club is verified, its organizers can vouch for a listed, willing mentor who is a member of the club (never for themselves and never across a block); the vouch is stored under the organizer's account, the note they add must carry no address, phone number or link, and the organizers of that club can read the notes on the club's current vouches (a declined or withdrawn note is no longer shown to them).
• Mite benchmark near you (opt-in) — if you switch on "Share my wash counts" in Settings → Privacy (it is off unless you do), your routine mite washes join anonymous statistics for your hive's state (or your region when no hive carries a state): the median, the middle half and the share at or over the Honey Bee Health Coalition threshold, per state, 14-day period and colony phase. A figure is published only when ten or more members' washes stand behind it; the table holds no hive, name, pin, note or account, and the app reads it only through two database functions that return numbers. Every member sees the free state index; Premium members also see the band drawn on their own mite chart. Switch sharing off and your washes drop out at the next nightly recount; they leave the same way when your account is deleted. It is a comparison of numbers, not a verdict — the HBHC threshold stays the rule.

Bee Community is for adults (18+); the mentor and swarm screens carry a reminder never to arrange to meet a minor through the app, and a report reason exists for suspected underage use. Reports on any of these records go to a person; content reported by several members is hidden automatically until reviewed.

How moderation works, including automatic steps

Some moderation happens automatically, without a person deciding each case:

• Text that is refused. Posts, comments and other community text are refused when saved if they contain a link, a phone number, a cryptocurrency wallet address, an off-platform payment or contact handle, or a word or pattern on our list of slurs, threats and self-harm phrases.
• Photos that are refused. Photos on community feed posts and club posts are screened before upload, as described in How we share it.
• Hiding. A post, comment, bloom report, swarm alert or area alert reported by three or more members is hidden from other members until a person looks at it.
• Strikes and automatic sanctions. Each of your own posts or comments that is hidden this way counts once as a strike, within a rolling 90-day window. With the standard settings, a first strike brings an automatic warning, a second an automatic 7-day mute, a third an automatic 30-day mute, and a fourth is sent to a person for review instead of adding a sanction. An automatic mute needs reports from at least five different members whose accounts are at least seven days old — otherwise the case goes to a person — and no automatic sanction is applied within 24 hours of another one, while a moderator's mute or any ban is running, or while the account is suspended. Automatic bans are switched off; if they are ever switched on, an automatic ban only stops community posting, never signing in, and is also sent to a person.
• Member reports. When three different members report the same member within 30 days, a person is asked to review; no sanction is applied automatically.

A mute or ban stops you posting, commenting, liking, editing posts or comments, editing, closing or re-opening your own swarm or area alerts, changing your mentor listing, replying to swarm alerts, filing swarm, area or bloom reports, messaging or requesting mentors, and starting or joining clubs; while muted or banned you also cannot attach a contact number to a swarm alert or change it, claim another member's swarm alert, accept a new mentee, upload a community photo, or — as a club organizer — edit the club's page or its members' roles, add or edit the club's ledger or treasury entries, or vouch for a mentor, and club-vouch badges are not shown to you except on your own listing. You can still read the community and use your hives, logbook and photos. Moderators can also warn, mute, ban, suspend or delete an account themselves. A moderator can ban you from the community only — you keep signing in and using your hives and logbook — or, in serious cases, suspend or ban the account itself, which stops sign-in until it is lifted.

Every sanction, lift, suspension and unsuspension is sent to you by push notification and, if your email address is confirmed, by email, with the reason; the app shows the same reason on a banner. An automatic notice says it was applied automatically, gives the number of strikes, the window and how long it lasts, and may quote up to the first 80 characters of your own hidden post or comment. A suspension can be issued without a detailed notice; you then see only a general message when you try to sign in, and you can ask us the reason by email.

To ask for a second look at anything moderation did, write to support@mybeecommunity.com and a person will review it. There is no in-app appeal button. The Terms describe the reporting route, the notices and how to object in Content moderation.

Location on community content is deliberately coarse. Besides your region and a coarse area label, a swarm alert or bloom report may carry — and an area alert always carries — a rough spot: a latitude and longitude rounded to two decimal places (about 1.1 km, roughly two-thirds of a mile) on your phone before it is uploaded, taken from your device's location when you tap "Use my location" or from a tap on the map. The database refuses anything finer, so nothing more precise than that can ever be stored, and the app draws the spot as a circle about a mile across, never a pin. It exists so that members within their alert radius can be told; it is not your hive location and need not be your home — place it where the swarm, the bloom or the bear is. Swarm alerts and bloom reports posted before this feature existed have no spot and never trigger a nearby notification. Your hive pins stay private and are read only inside the database, to measure distance.

Your state & registrations

Adding your US state is optional (you can skip it during onboarding and add it later in Settings). It is used to show your state's apiary-registration rule, honey-labelling requirements, pesticide-notification registry and inspector contact, and to time registration-renewal reminders; if none of your hives has a state, it also decides which posts your community feed's "states" view shows (see Community network). It is never inferred from your region, and it is not shown to other members. In California you can add your county, because cottage-food labelling there names the issuing county. The two "I sell honey" / "I sell bees" switches only decide whether the labelling and sale checklists appear.

Separately, each hive can carry its own state, province or territory, as described in Information we collect; it is not shown to other members, but it is used inside our database for the feed's "states" view. The profile field itself lists US states only; a hive can carry a US state, the District of Columbia or a Canadian province or territory.

Registration records you keep in the app — yard, state, registration and expiry dates, certificate number, colony count, reminder lead times and notes — are private to your account, synced offline like the rest of the logbook, and deleted with it. The app links to official state and inspector directories rather than copying their contact tables, so those links open in your browser.

Retention

We keep your data for as long as your account is active. When you delete your account (from the Account screen in the app, or by asking us), we remove your account, profile, hives, logbook entries and their private photos, mite washes, apiary books, registrations, reminders, posts, comments, likes, bloom reports, swarm alerts (with any phone number) and replies, area alerts, mentor listing, requests and messages, club memberships, the reports you filed, blocks, the shared photos you uploaded, your nearby-alert preferences and the week-plan, referral-rewards, season-opener, getting-started-tips, overdue-check-reminder and wash-sharing switches, your notification timing record, your referral code, the club vouches on your mentor listing, your swarm-trial record, your honey harvest and sales records, the club shared-expense and treasury entries you recorded (which also removes them from that club's books), your subscription status and redeemed codes, your warnings, mutes and bans, your Community Guidelines acceptance, the moderation notices addressed to you, the push tokens for your phones and any notification still queued or logged for you, right away; the anonymous wash statistics are recounted every night from members who currently share, so your washes drop out of them at the next recount. Deleting a single entry, post or alert removes its photos too. A club you founded stays for its remaining members, with no founder attribution; a club seat pack you bought stays for the club, no longer naming you as the buyer; a vouch you gave as a club organizer stays on the mentor's listing, no longer naming you; a referral record you were part of stays with your identifier removed (below); a swarm alert you had claimed is released.

Notifications: the log of what we sent (recipient, text, time, delivery result, the hour it was opened) is kept for up to 14 days; the totals we keep after that are per kind and per day and carry no member. The notification timing record is kept for at most 180 days after your last app open, and is deleted with your account. Before that, it is generally cleared within a day once the last of your phones has released its push token — which the app generally does the next time it runs after you turn notifications off, or on sign-out while it can reach us — keeping only which one-time tips and notes were sent. A push token is deleted when you sign out on that phone (if it is online at the time), when the push service reports the phone can no longer be reached, after 180 days without that phone checking in, or with your account. An area alert expires 3 to 30 days after posting depending on its kind. The area-alerts list shows the last 30 days: while yours is listed you can delete it from the alert itself; after 30 days it leaves the list and the app no longer offers a way to delete it, but the record is not purged on its own — it stays until it is removed with your account, or you ask us to remove it.

The same is true of other community records: a swarm alert stops being shown after 72 hours, but swarm alerts, bloom reports, posts, comments and reports stay until you or a moderator delete them, or your account is deleted.

What is kept after your account is deleted

• Consent records — the email address the account used, the timestamp, the document and app version and the document fingerprint — no longer linked to a live account, kept for as long as we may need to prove what you accepted.
• The moderation log. Entries about you are no longer linked to your account but keep the copy of your display name taken at the time, your former member identifier, the moderator's reason and any excerpt they hold (up to the first 160 characters of a hidden post or comment, or of the detail in a report). If you reported a member, the entry keeps your former member identifier, the reason and up to the first 160 characters of your detail. If a moderator deletes an account, the log records the deletion with the display name first. A referral voided or a club vouch removed by a person on our team is logged the same way, with the reason. Kept for as long as needed to prevent someone banned from coming back and to defend claims.
• Review alerts sent to our moderators that named you (display name and former identifier) — kept for the same period.
• Reports other members filed about your content — up to the first 160 characters of the reported text and the reporter's detail — until a moderator dismisses them.
• Billing event messages RevenueCat sent us about your plan, with your former account identifier and the full message, for as long as tax and accounting records must be kept and disputes can arise.
• Club finance records other members entered: the rows stay for the club with your identifier removed from "paid by" and "member", although the lists of who a cost was split among or settled by may still contain your former identifier.
• Codes: the club-only code of a seat pack you bought stays for the club without your name, and the single-use code rows behind a swarm-season trial or a referral month stay with no identifier.
• Referral records. If a friend used your code, or you used a friend's, the record of that referral stays with your identifier removed: the other member's identifier, the code, the status, the dates, the date and plan of the friend's first payment and the store's transaction reference for it, and the grant codes remain, because the twelve-a-year cap and the one-code-per-account rule are worked out from these records and deleting an account must not reset them. If the referral was voided, the reason and the operator who voided it stay on it. Nothing about your own account stays on the record. When both accounts are gone, the record holds no member identifier at all.
• A vouch you gave as a club organizer stays on the mentor's listing for the club, no longer naming you; if you had withdrawn it, that mark stays too. The vouches you received go with your mentor listing.
• Anonymous wash statistics keep your numbers inside the stored averages until the next nightly recount; they never held an identifier.
• Copies we do not control: delivery logs at the push and email services (Expo, Resend), RevenueCat's customer record and Google Play's purchase records, Google Cloud Vision's request logs for community photos you posted (the image bytes only), our backend provider's backups and logs, and any copy another person saved of a shared photo.

Deleting your account does not cancel a subscription. Cancel it in your Google Play account settings first, or it will keep renewing; see the Terms of Service.

Forecasts requested from the National Weather Service are cached on your phone for at most 24 hours; we never store them. Files you export (CSV or PDF), the QR tag sheet (PDF) and the season recap picture (PNG) are written to a temporary folder on your phone that the app sweeps after 24 hours, and the copy you shared lives wherever you sent it.

Your rights & choices

You can review and correct your information directly in the app: your display name, region, state, rough home point (set, change or clear it), reminder settings, your nearby-alert radius and categories, the Sunday week-plan, Referral rewards and Season opener switches (Settings → Reminders) and the wash-statistics switch (Settings → Privacy) on the Account and Settings screens; your hives, entries, washes, registrations and reminders in the logbook and Alerts; a club vouch on your mentor listing (decline it from the listing); the "Include hive names" switch on the season recap card, which is off every time you open it; and an area alert you posted from the alert itself while it is listed (edit its label and note, close, re-open or delete it). You can export everything — every entry, every hive, every wash — as CSV, and any hive as a PDF report, from Settings → Export my data or from a hive's share button; hive coordinates are included only if you switch that on for that file. You can delete your account, and everything in it, from the Account screen → Delete account — you'll be asked to confirm twice, and it takes effect immediately. If you'd rather we handle a deletion or any other request, email support@mybeecommunity.com from the address you signed up with.

The in-app export covers your logbook entries, hives and mite washes. For a copy of anything else we hold about you — your profile, community content, notification and moderation records, or subscription records — email us.

Depending on where you live, you may have additional rights — to access a copy of your data, to correct it, or to object to certain uses. Contact us and we'll do our best to accommodate the request even where it isn't strictly required by local law.

The rights that apply in Canada, in Québec, in the European Economic Area and the United Kingdom, and in Switzerland, and how to complain to a regulator, are set out in sections 19, 20, 21 and 22. We handle these requests free of charge.

Children's privacy

Bee Community is intended for beekeepers 18 and older; account creation requires accepting our Terms, which state that you must be 18 or older, and the community-network screens repeat it. The app is not directed at children, and we do not knowingly collect information from anyone under 18 (and never from a child under 13). If we learn that someone under 18 has an account — including through a report from another member — we'll suspend the account and delete it.

Security

Your data is protected by industry-standard access controls at the database level — including row-level security rules, enforced by the database itself, that prevent one account from reading another's private hive, logbook, wash, registration or reminder data, regardless of any bug in the app's own interface. Logbook photos sit in a private bucket readable only through short-lived signed links. The routines that measure distance from your hive pins or home point run inside the database and return nothing but a member and a whole number of miles, or the alerts within your radius; the notification queue and delivery log can be read by no member account at all, and your push tokens only by you. The offline cache on your phone lives in the app's private storage. No system is perfectly secure, but private data here isn't just hidden by the UI; it's blocked by the database itself.

The key that can bypass those rules is kept only inside our server functions, never in the app; the server functions that act for you check your sign-in first, and the billing-event receiver refuses any request without a shared secret; photos lose their embedded location before upload; shared coordinates are refused by the database if finer than two decimal places; author names are set by the server; and the email-service key is kept in a secrets vault, never in tables or logs.

Where data lives

Your data is stored on infrastructure operated by our backend provider, Supabase, in a data center located in the western United States. If you're using the app from outside the United States, your information will be transferred to and processed there. Weather requests and state lookups go to the U.S. National Weather Service's servers (operated by NOAA in the United States) and carry only the approximate location described above. Address searches go to OpenStreetMap's servers in the United Kingdom and the Netherlands and carry only the text you typed. A photo you attach to a community or club post goes to Google Cloud Vision's servers (United States) for the safety screen and carries only the image bytes. Nearby and community notifications leave that infrastructure only as the short messages described in Reminders & notifications, addressed to a push token: they pass through Expo, Inc.'s push service (United States) and then Google's notification relay to your phone. A copy of your logbook data is cached on your own phone.

Community and club post photos are screened by Google Cloud Vision (Google LLC, United States); our moderation and sign-in emails are sent by Resend (United States); subscription status is kept by RevenueCat (United States); push notifications pass through Expo, Inc. (United States) and Google's Firebase Cloud Messaging, a global Google service; maps are drawn by the Google Maps SDK and plans are sold through Google Play (Google LLC, United States — for buyers in the European Economic Area, the United Kingdom and Switzerland, Google Commerce Limited in Ireland); our website is hosted by Expo Application Services (Expo, Inc., United States). Our backend provider's contracting company, Supabase Pte. Ltd., is in Singapore, while the database itself is in Amazon Web Services' Oregon region in the United States. Information about transfers from Canada and Québec is in sections 19 and 20; about transfers from the EEA and the UK, with their safeguards, in section 21; and from Switzerland in section 22. Organisations in another country are subject to that country's laws, and courts, law-enforcement and national-security authorities there may be able to obtain information held there.

Premium & billing

The core of Bee Community is free for everyone and carries no advertising — we never collect data for ad targeting, and the weather and Varroa tools in particular stay free because their sources are licensed for non-commercial use. An optional Premium subscription (US$3.99 per month or US$24.99 per year — Premium yearly carries a 7-day free trial for members new to Premium, applied by Google Play at purchase) raises the limit to 30 active hives (the free plan includes two) and photo storage to 2 GB (the free plan includes 100 MB), and adds the newer tools listed in the Terms; an optional Commercial subscription (US$14.99 per month or US$119.99 per year) allows up to 1,000 active hives and 10 GB of photo storage on top of everything in Premium. When you finish setting up the app you pick a plan: Start free is always offered, nothing is pre-selected, and nothing is bought inside the setup wizard — a paid choice only opens the store purchase screen. Once per account, a free member who reaches the two-hive limit during their region's swarm season can start a 30-day Premium trial with no card: we record that the account took it, the region it was judged in and the day it ends; it ends on its own, nothing renews, and every hive you added stays yours. A verified beekeeping club can buy, through one of its organizers, a club seat pack — a one-time purchase that becomes a club-only code giving up to 25 of its members one year of Premium, counted from the day each redeems it or, if they already hold a plan period, from the end of that period; it unlocks nothing on the buyer's own account, and we record which club it belongs to, how it was paid and who bought it, so that members can redeem it from the club page. Every member has a bring-a-friend referral code: a new member who enters it within 30 days of creating their account gets 30 days of Premium at once, and you get 30 days once that member's first payment for a Premium or Commercial plan goes through (after any free trial) and 7 days have passed without a refund — checked each night, up to 12 rewards in a rolling 365 days. We record your code and, for each referral, the two accounts, the code, the status and dates, the date and plan of that first payment and the store's transaction reference for it (never the amount, and nothing beyond what our billing records already hold), and the one-use grant codes behind the months. The friend's month starts at once; yours is added to the end of a promotional period you hold, or, while a store plan is live, waits and lands the night after that plan has lapsed — a renewing plan keeps it waiting — so nothing you hold is shortened or lowered. A referral is voided automatically if that first payment is refunded, and can be voided by a person on our team for abuse — either way no further reward is paid for it, and a month already granted stays.

Premium, Commercial and club seat packs are billed by Google Play through its in-app purchase system — never by us directly. We never see, receive or store your card or payment details; the store handles the money, under Google's own terms and privacy policy (for buyers in the European Economic Area, the United Kingdom and Switzerland the seller is Google Commerce Limited, Ireland). To recognize that your subscription is active we use RevenueCat, which receives your account's internal identifier (a random code, not your name or email — a pseudonymous identifier) and the status of your purchase — not your beekeeping data. That status — including which of the two plans you hold — is mirrored to your account so the app can unlock the right plan and show it, and we keep each billing event message as RevenueCat sent it: the event type, product, store, price and currency, dates, your account identifier and whatever else RevenueCat includes. A plan can also be given to you by a promotional code, a club seat-pack code, the swarm-season trial, a bring-a-friend referral month, or by us directly, without a purchase. If you cancel or your plan lapses, none of your data is deleted; see the Terms for what stays available. Deleting your account does not cancel a store subscription. Full billing terms are in the Terms of Service.

Image & source credits

The photographs in the field guide, equipment guide and bloom calendar are bundled with the app (never fetched from the web while you use it) and are used under public-domain, CC0, Creative Commons Attribution or — only where no other photo exists — Creative Commons Attribution-ShareAlike licences. Every photo's author, licence and source page is listed on the Credits screen (Settings → Credits & sources, and the Learn tab); no photo without a named author is shipped. Diagrams are drawn in-house and credit the extension publications they are based on.

Varroa thresholds, sampling cadence and colony-phase names in the app are stated in our own words and cited to the Honey Bee Health Coalition, Tools for Varroa Management, 9th edition (June 11, 2026), available at honeybeehealthcoalition.org under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 licence. Bee Community reproduces no sentence, table, figure, logo or tagline from that guide in the app or in any exported file; the Varroa tools that paraphrase it are part of the free plan and are never placed behind Premium, which keeps attributed paraphrase plus a link within that non-commercial licence. Treatment facts come from EPA-stamped product labels, cited by registration number and label date, and from USDA and university extension publications. Weather data is credited to the U.S. National Weather Service (NOAA) and is a U.S. Government work in the public domain. The app's typefaces, Fraunces and Figtree, are used under the SIL Open Font License.

Changes to this policy

If we make a material change to this policy, we'll update the effective date and version at the top of this page and let you know in the app before the change takes effect — we don't change the terms of a relationship you already agreed to without telling you. The app records which version you accepted; a material change means you'll be asked once to read and accept the new one.

If you are in Canada

This section applies in addition to the rest of this policy if you live in Canada. If you live in Québec, section 20 applies as well. If you live in Alberta or British Columbia, the provincial Personal Information Protection Acts apply as well, and you may complain to the Office of the Information and Privacy Commissioner of Alberta or of British Columbia.

Who is accountable

UnGrounded Innovations LLC is responsible for the personal information described in this policy. The person accountable for our compliance with Canadian privacy law is the Owner of UnGrounded Innovations LLC, who can be reached at support@mybeecommunity.com; our postal address is shown on our Google Play developer page and is available on request at the same email address.

Consent

We explain what we collect and why before you create an account, and you accept this policy in the app. The optional features — hive pins, the home point, device location, photos, the voice quick-log, push notifications, the community network, the referral code, hive tags, the season recap card, apiary books and the other Premium tools — are used only if you choose to use them, and you can stop using each one as described in this policy. You can withdraw consent at any time by turning off a feature or deleting your account; some features cannot work without the information they need.

Access and correction

You can see and correct most of your information in the app (see Your rights & choices). You can also ask us, by email from the address you signed up with, for access to the personal information we hold about you, how it has been used and to whom it has been disclosed, and ask us to correct it. We will answer within 30 days, or tell you within that time if we need longer and why, as the law allows. If we refuse a request, we will explain why and how you can challenge that.

Information stored outside Canada

Your information is stored in the United States and processed by the service providers named in How we share it, most of them in the United States (address searches go to the OpenStreetMap Foundation in the United Kingdom and the Netherlands; our backend provider's contracting company is in Singapore). While it is there, it is subject to the laws of those countries and may be accessible to their courts, law-enforcement and national-security authorities. Each provider that acts for us is bound by a written agreement to protect it — the standard contractual clauses in Supabase's, Resend's and RevenueCat's data processing terms, Google's data processing terms, and Expo's terms — and Google, Expo and Resend are also certified under the EU-US Data Privacy Framework. You can ask us for copies.

Breaches of security safeguards

If a breach of security safeguards involving your personal information creates a real risk of significant harm to you, we will report it to the Office of the Privacy Commissioner of Canada, notify you as soon as feasible, and keep a record of every breach as the law requires.

Questions and complaints

If you have a concern about how we handle your information, please write to us first at support@mybeecommunity.com; we will look into it and reply. You can also complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) and, after the Commissioner's report, apply to the Federal Court.

If you are in Québec

This section applies in addition to the rest of this policy if you live in Québec, under the Act respecting the protection of personal information in the private sector.

Person in charge of the protection of personal information

The person in charge of the protection of personal information at UnGrounded Innovations LLC is the Owner of UnGrounded Innovations LLC. You can reach that person at support@mybeecommunity.com (please write "Privacy — Québec" in the subject line); our postal address is shown on our Google Play developer page and is available on request at the same email address.

Why we collect your information, and how

We collect personal information for the purposes listed in How we use it and only by the means described in Information we collect: what you enter in the app, what the app obtains from your phone when you tap a button (location, camera, photo library, microphone), what the app and our services generate as you use it (for example notification and moderation records), and what other members report about you. We use it only for those purposes, or for another purpose with your consent or where the law allows. The policies and practices that govern personal information at UnGrounded Innovations LLC — who can see it, how long we keep it, how a complaint is handled — are the ones described in this policy.

Who in our company can see it

Only people we authorise as operators or moderators can see member information, limited to what is described in How we share it and only as needed to run the service, handle reports and answer support and billing requests.

Your rights

• Access. You can ask whether we hold personal information about you and receive a copy of it.
• Rectification. You can have information that is inaccurate, incomplete or ambiguous corrected, and have information deleted if we are no longer authorised to keep it. Most of it you can correct yourself in the app.
• Portability. You can receive the computerised personal information you gave us in a structured, commonly used technological format, or have it sent to someone you name. The in-app CSV export covers your logbook entries, hives and mite washes; for the rest, email us.
• Stopping dissemination and de-indexing. Where the law allows — for example if something about you is being disseminated in breach of the law or a court order, or causes you serious harm — you can ask us to stop disseminating it, or to de-index a link that gives access to it. Your own posts, alerts, reports and their photos you can delete yourself (an area alert older than 30 days, by asking us); content about you posted by someone else can be reported in the app or by email.
• Withdrawing consent. You can withdraw consent to an optional use at any time by turning the feature off or deleting your account, as described in this policy.
• Automated decisions. If a decision about you is made solely by automated processing — the automatic warnings and mutes described in Community network are — you are told so in the notice. Automatic text and photo refusals, hiding after reports and nearby matching are automated processing of content rather than decisions about you, but we offer the same steps for them. On request, you can find out what personal information was used, the reasons and main factors that led to the decision, and have that information corrected; and you can present your observations to a person who can review the decision, by writing to support@mybeecommunity.com — see also Automated measures and human review in section 21 for how each automatic step works.

Send requests in writing to the person in charge, from the email address you signed up with so we can confirm it is you. We will answer within 30 days of receiving the request. If we refuse, we will give the reasons and tell you how to ask the Commission d'accès à l'information to review that decision (a request for review must reach the Commission within 30 days of our answer).

Communication of your information outside Québec

Your information leaves Québec as soon as you use the app, because our servers and providers are in the United States (and, for address search and our backend provider's contracting company, in the United Kingdom, the Netherlands and Singapore — see Where data lives). We assess, as section 17 of the Act requires, how sensitive the information is, what we use it for, the contractual and technical protections that apply, and the legal framework in the United States, so that it receives adequate protection in light of generally recognised privacy principles. Our written agreements with our providers reflect that assessment: Supabase's data processing addendum, Resend's and RevenueCat's data processing addenda, Google's data processing terms for Cloud Vision and Firebase and its controller terms for Maps and Google Play, and Expo's terms; you can ask us for copies.

Confidentiality incidents

If a confidentiality incident involving your personal information presents a risk of serious injury, we will promptly notify the Commission d'accès à l'information and you. We take reasonable steps to reduce the risk of harm and prevent new incidents, and we keep a register of all confidentiality incidents.

Technology that can locate you, and how to turn it off

Bee Community uses location in the following ways. None of it runs in the background.

• Your device's location is read only when you tap "Use my location", and is rounded to two decimal places for the weather request, the home point and alert spots; a hive pin placed this way keeps the precision your phone reports and stays private to you. You can refuse or revoke the location permission for Bee Community in your phone's settings; you can then place hive pins, alert spots and the home point by typing a place or tapping a map instead.
• Hive pins are optional and private. Inside our database they are used to decide which nearby alerts reach you and which posts appear in your feed's "near" view, and your pins decide in whose "near" view your posts appear. A pin is removed with the "Clear pin" button on the hive form.
• The home point is optional and private; clear it from Settings at any time.
• Nearby alerts. Once you allow notifications and have a pinned hive, swarm-alert and area-alert notifications within 25 miles are on unless you turn them off. Set the radius to Off, or switch those categories off, in Settings → Nearby alerts & community.
• The community feed opens on the "near" view by default. You switch views with the chips above the feed (near, states, region, all); near is the default and the app remembers your choice on this phone.

We do not use location or any other information to build a profile of you for marketing. Nearby notifications need two steps of your own — allowing notifications and placing a hive pin — and the radius and each category can be set to Off in Settings; the feed's "near" view is worked out from your hive pins, never from your phone's position, and you can switch it to states, region or all.

Complaints

If you are not satisfied with how we handled your information or a request, write to the person in charge at support@mybeecommunity.com. You can also file a complaint with, or ask for a review of our decision by, the Commission d'accès à l'information du Québec (cai.gouv.qc.ca; complaints and requests for review are filed at formulaire.cai.gouv.qc.ca).

If you are in the European Economic Area or the United Kingdom

This section applies in addition to the rest of this policy if you are in the European Economic Area (EEA) or the United Kingdom, under the General Data Protection Regulation (GDPR) and the UK GDPR.

Who is responsible for your data

The controller of your personal data is UnGrounded Innovations LLC, a Wyoming limited liability company, United States; our postal address is shown on our Google Play developer page and is available on request at support@mybeecommunity.com. Contact: the same address, attention of the Owner of UnGrounded Innovations LLC. We have not appointed a data protection officer; write to the Owner at that address.

Representatives in the EU and the UK

We are appointing a representative in the European Union and a representative in the United Kingdom under Article 27 of the GDPR and of the UK GDPR. Their names, postal addresses and email addresses, and the current status of each appointment, are published at mybeecommunity.com/representatives and kept up to date there; until a representative is in place, write to support@mybeecommunity.com. You can contact a representative instead of us about anything in this policy.

What we use your data for, and our legal basis

The table below lists each purpose, the data used, and the legal basis we rely on. "Contract" means the processing is necessary to provide the app under our Terms of Service (Article 6(1)(b)); "legitimate interests" means it is necessary for interests of ours or of other members that are not overridden by your rights (Article 6(1)(f)); "consent" means you agreed (Article 6(1)(a)) and can withdraw; "legal obligation" means the law requires it (Article 6(1)(c)).

What you must provide

To create an account you must give an email address, a password and a display name, choose a region, and accept the Terms and this policy; without them we cannot provide the app. Everything else — state and county, seller switches, hive pins, the home point, photos, notifications, the voice quick-log, weather, address search, the community network, the referral code, hive tags, the season recap card and the Premium tools — is optional. Some Premium features need the data they work on — for example the week plan needs an active hive. No law requires you to give us any of it. We handle rights requests free of charge unless a request is clearly unfounded or excessive, where the law allows a reasonable fee or a refusal.

Legitimate interests: moderation and safety

We have weighed our interest, and other members', against your rights for the community-safety processing. In summary:

• Our interest. Keeping a community for adults free of spam, scams, harassment, abusive or threatening language, unsafe images, and the sharing of people's contact details or precise locations, and being able to show what action was taken and why.
• Necessity. Text and photo checks look only at what you are about to post. Photo screening sends Google the photo alone, without your name, account or location. Sanctions are counted from your own content that several members reported, and the log keeps only a display-name copy and excerpts of up to 160 characters rather than whole items.
• Impact on you. A refusal stops one post or photo; a warning is a notice; a mute or ban stops community posting for its length, but you can still read the community and use your hives, logbook and photos. A moderator's ban is normally limited to the community; only an account ban or a suspension stops sign-in.
• Safeguards. With the standard settings the automatic steps stop at warnings and mutes of 7 or 30 days; automatic bans are off. A mute needs reports from at least five different members with accounts at least seven days old, and no automatic sanction follows another within 24 hours. A fourth strike, three reports about the same member, and any automatic ban go to a person. Every sanction is notified to you with its reason, and a person reviews it if you ask. A sanction record you can see names the moderator only as "moderator", never by email address (a record made before the current moderation tools were introduced may still carry one).
• Retention. The moderation log and review alerts are kept after account deletion, unlinked, for as long as needed to prevent someone banned from coming back and to defend claims (see Retention).
• Your right to object. You can object to this processing (see Your right to object below). Because it protects other members, we may continue where our grounds override your interests, and we will explain why.

Who receives your data

International transfers

Our servers are in the United States, so using Bee Community from the EEA or the UK means your data is processed there and in the other countries shown above. Where a provider acts for us, we rely on the following safeguards, and you can ask us for a copy of them at support@mybeecommunity.com:

• Supabase: the standard contractual clauses in its data processing addendum, with the UK International Data Transfer Addendum and its Swiss terms (contracting company Supabase Pte. Ltd., Singapore; our database is hosted in the United States).
• Expo, Inc.: certified under the EU-US Data Privacy Framework, its UK Extension and the Swiss-US Data Privacy Framework.
• Google (Cloud Vision, Firebase Cloud Messaging): certified under the EU-US Data Privacy Framework, its UK Extension and the Swiss-US Data Privacy Framework; its data processing terms also contain standard contractual clauses. For the Maps SDK and Google Play, Google acts as a controller under the same certifications and its own terms.
• Resend: certified under the EU-US Data Privacy Framework and its UK Extension; standard contractual clauses with the UK Addendum and Swiss terms in its data processing addendum.
• RevenueCat: standard contractual clauses with the UK Addendum and Swiss provisions in its data processing addendum.
• jsDelivr is a United Kingdom company; the U.S. National Weather Service and the OpenStreetMap Foundation receive requests your phone sends directly when you use weather or address search, so we transfer nothing to them: the Weather Service is a US federal agency that logs the request, and the OpenStreetMap Foundation is an independent controller in the United Kingdom and the Netherlands (its policy).

As at the effective date of this policy, the EU-US Data Privacy Framework adequacy decision (Decision (EU) 2023/1795) is in force: the EU General Court upheld it on 3 September 2025 (case T-553/23), an appeal (C-703/25 P) is pending before the Court of Justice, and in July 2026 the European Data Protection Board asked the European Commission to assess the effect of a US Supreme Court judgment on the independence of the US Federal Trade Commission. The UK Extension has been in force since 12 October 2023 and stands on its own. Because the Framework may change, every provider above also holds standard contractual clauses or equivalent contractual commitments, and we check their certifications regularly.

UnGrounded Innovations LLC itself is not certified under the Framework. Your own use of the app sends your data directly to us in the United States; where the law treats that as a transfer, it rests on the explicit consent you give when you accept this policy at sign-up, knowing that the United States has not been found to give the same protection as EEA or UK law (except for certified companies) and that US authorities may be able to access data under US law with fewer ways for you to challenge that. You can withdraw that consent at any time by deleting your account, which ends the service; it does not affect what was done before.

How long we keep your data

Your rights

You have the right to:

• access your personal data and receive a copy;
• rectify data that is inaccurate or incomplete;
• erase your data — you can delete your account in the app at any time, subject to the records kept after deletion described in Retention;
• restrict our use of your data while a dispute about its accuracy or our grounds is resolved, or where you need it kept for a legal claim;
• data portability — receive the data you gave us, used under contract or consent, in a structured, commonly used, machine-readable format, or have it sent to another controller where technically feasible (the in-app CSV export covers entries, hives and washes; ask us for the rest);
• object at any time, on grounds relating to your situation, to processing based on legitimate interests, including the moderation processing described above — see Your right to object below;
• withdraw consent where we rely on it, at any time, without affecting what was done before — turn off notifications in Settings or your phone's settings, switch off "Share my wash counts" in Settings, revoke location or microphone permission in your phone's settings, or delete your account (which withdraws the transfer consent above). The Sunday week plan is a Premium feature you can switch off in Settings at any time; the Referral rewards and Season opener switches are under Settings → Reminders, the club-vouch notification follows the mentor switch, and a club vouch itself can be declined from your own mentor listing.

To use these rights, email support@mybeecommunity.com from the address you signed up with (or, if you cannot, tell us how we can confirm your identity). We will answer within one month of receiving your request; for complex or numerous requests we may extend that by up to two further months and will tell you why within the first month. If you are in the United Kingdom, you can also complain to us first: we acknowledge a complaint within 30 days and tell you the outcome.

Your right to object

Automated measures and human review

Some community measures are applied automatically, as described in Community network: a post, comment or alert is hidden once three members report it; text that matches our abuse rules, and photos that Google Cloud Vision's SafeSearch rates as sexual, violent or gory, are refused before they are published; repeated hidden items can lead, with the standard settings, to an automatic warning or a 7-day or 30-day mute on posting (the system counts your strikes in the last 90 days, the number of different reporters and the age of their accounts, and whether another sanction is running or was applied in the last 24 hours); nearby matching decides which alerts and posts you are shown or notified of, from distances worked out inside our database; and whether one of the notifications described in Reminders & notifications is sent to you is decided automatically from the limited signals listed there. None of these decides anything about your legal rights or has a comparable effect on you: you can still read the community and use your hives, logbook and photos, and only a person can ban or suspend an account. Every automatic sanction notice says it was automatic and why. You can ask a person to look at any automatic measure again, give your side, and contest it by emailing support@mybeecommunity.com; a person will review and reply. We do not make decisions about you based solely on automated processing that produce legal effects or similarly significant effects.

Complaints to a supervisory authority

We would like the chance to resolve a concern first, so please write to us. You also have the right to lodge a complaint with a data protection supervisory authority — in particular in the EEA country where you live, work, or where you think the problem happened. The European Data Protection Board lists every national authority at edpb.europa.eu. In the United Kingdom, the authority is the Information Commissioner's Office (ico.org.uk/make-a-complaint; the ICO also handles complaints about the UK Extension to the Data Privacy Framework).

If you are in Switzerland

This section applies in addition to the rest of this policy if you are in Switzerland, under the Federal Act on Data Protection (FADP).

Who is responsible

The controller is UnGrounded Innovations LLC, a Wyoming limited liability company, United States; our postal address is shown on our Google Play developer page and is available on request at support@mybeecommunity.com, attention of the Owner of UnGrounded Innovations LLC. We have assessed article 14 FADP and do not currently appoint a representative in Switzerland: on our assessment the processing does not pose a high risk to your personality — there is no sensitive data, and no tracking across other services or sites. The measurement we do is our own: a count of how many of the notifications we send are opened and how often the plans and paywall screens are seen, and, to decide whether one of the notifications described in Reminders & notifications is worth sending, the limited signals listed there (whether the app has been opened recently, whether a check was overdue, how old the account is, your plan). We keep that assessment under review. Our EU and UK representatives, once appointed, are listed at mybeecommunity.com/representatives.

What we process and why

The purposes are those in How we use it and the recipients those in How we share it and in section 21.

Where your data goes

Your data is stored in the United States (Supabase on Amazon Web Services in Oregon; Resend; RevenueCat; Expo; Google). Google LLC and Expo, Inc. are certified under the Swiss-US Data Privacy Framework. For Supabase (contracting company in Singapore), Resend and RevenueCat we rely on standard data protection clauses recognised by the Federal Data Protection and Information Commissioner, in their data processing terms. Address search goes from your phone to the OpenStreetMap Foundation in the United Kingdom and the Netherlands, and weather requests to the U.S. National Weather Service in the United States. Because we are a US company and not ourselves certified, the transfer of your data to us rests on the explicit consent you give at sign-up (article 17(1)(a)) and on the contract you have with us (article 17(1)(b)); you can withdraw the consent by deleting your account.

Automated decisions

The automatic measures in section 21 apply to you in the same way; you can ask a person to review any automatic sanction and give your point of view (article 21).

Your rights

You can ask for access to your data (article 25), have it corrected and use the civil-law remedies (article 32), receive the data you gave us in a conventional electronic format (article 28 — the in-app CSV export plus copies on request), withdraw consent, delete your account in the app, and object to processing you do not want (article 30(2)). Send requests to support@mybeecommunity.com from the address you signed up with; we answer within 30 days as a rule.

Complaints

Write to us first. You can also report a concern to the Federal Data Protection and Information Commissioner (edoeb.admin.ch) and bring civil claims under article 32.

Contact us

Questions about this policy, or a request regarding your data: support@mybeecommunity.com.

UnGrounded Innovations LLC, a Wyoming limited liability company; our postal address is shown on our Google Play developer page and is available on request at the same email address. The person responsible for privacy — including as the person in charge of the protection of personal information for Québec and as our contact for the EEA, the UK and Switzerland — is the Owner of UnGrounded Innovations LLC, at the same email address. Our EU and UK representatives, once appointed, are listed at mybeecommunity.com/representatives.