BeekeeperOS · Two Roots Homestead LLC

Privacy Notice

Version v3.18-2026-11-16 · Updated November 16, 2026

BeekeeperOS processes account email/name, membership and role information, personnel attribution, Apiary locations, operational records, photographs, preferences and relevant security/support events to provide the service and enforce access. Supabase supplies database, Auth and private Storage; Vercel hosts the app; Resend sends account/service emails; HostGator hosts the human support mailbox. GitHub stores private source and runs the bounded backup job, which briefly handles unencrypted recovery data on an ephemeral runner before AGE encryption; Cloudflare R2 holds encrypted recovery generations. The owner keeps the AGE private identity outside those services. Optional address lookup sends the address the user submits to the U.S. Census geocoder, with confirmation required before saving a suggested location. Weather integrations use the configured organization/station context. No advertising or marketing use is introduced by v2.6; marketing permission is separate from necessary service/security messages. Platform administration is restricted, scoped and audited; support is not unrestricted impersonation. Already downloaded files and issued photo links cannot be recalled instantly; current photo links expire after five minutes.

Operational records remain while an organization uses the service. Removing a membership ends that person's access but preserves shared historical attribution; it does not automatically delete the global account or other organizations' records. An authorized Organization Admin can request an export and organization closure. Support confirms the requested scope, identity, dependencies, any necessary legal/security retention and a completion date before manual deletion. No immediate or automatic erasure promise is made. Recovery archives retain seven successfully completed daily generations; a failed or paused schedule can retain older generations longer. A deletion request must be recorded outside the recovery generation and reapplied before any restored data is returned to service. Support explains remaining backup copies and their expected expiry when confirming a deletion request.

Apiary location

When you use optional Google address search, we send the text you type and a temporary search-session token to Google through our server. Google processes that information under its Privacy Policy and Maps terms. Search results stay in page memory; we may save the selected Place ID. We do not save Google-provided coordinates or address text in your permanent apiary record.

Device location is requested only when you tap Use my location. We save your confirmed GPS or manually supplied yard coordinates for weather, bloom and operational records. GPS accuracy may also be saved. Manual location entry works without Google. Existing locations and history remain unchanged unless you edit them.

To control Google usage, we keep request counts, account and organization identifiers, status and temporary search-session identifiers. We do not keep search text or returned addresses in that ledger. Network addresses, when available, are converted to a daily keyed hash. Request and network-hash records are pruned on later integration activity after 90 days; expired search sessions are pruned after a day. Owner control changes are retained for accountability. Local time-zone boundaries are provided through timezone-boundary-builder, using OpenStreetMap data.

Setup drafts

If you continue setup before verifying your email, the details you enter are kept in this browser as a draft, separate from your account records. Drafts can be resumed for 24 hours on the same browser and are removed on completion or the next time an expired draft is accessed. Passwords, verification codes and sign-in tokens are never part of this draft.

Product analytics

Effective November 16, 2026, BeekeeperOS uses routine product analytics to understand feature use, onboarding, completed workflows and usability problems, and to improve the service. Routine analytics and masked session replay are enabled by default for visits identified as being in the United States. Both remain off by default for visits outside the United States or when the country cannot be determined, unless you choose to enable them. We use country-level information supplied by our hosting provider for this default; it may be affected by a VPN or proxy. Browser privacy signals take priority. During the November 16, 2026 beta rollout, earlier in-app analytics and replay preferences were reset to these regional defaults. Choices saved after this rollout take priority.

We may use analytics and diagnostic service providers to process this information on our behalf. Providers may change over time; these purposes and your controls apply regardless of which provider we use. Routine analytics may include pages and features used, actions and timestamps, browser and device information, a pseudonymous account or browser identifier, organization identifier, and broad setup or subscription categories. These identifiers are not anonymous. Cookies or browser storage may support analytics and remember your preferences. Providers receive network information needed to deliver their services.

We do not send passwords, verification codes, names, email addresses, private notes, photos, precise apiary locations or other private record text as routine analytics event properties. We limit page information to general routes and remove record identifiers, query strings and referrers. App analytics are used for service improvement, not advertising personalization, and we do not sell this analytics data or share it for cross-context behavioral advertising.

Your analytics choice

You can turn analytics and masked replay off or on at any time in Settings → Data & privacy. Replay has its own control; turning analytics off also turns replay off. Turning it off stops future optional analytics collection by the app’s analytics providers without affecting enrollment, hive records or other core features. We honor browser Do Not Track and Global Privacy Control signals by keeping optional collection off. Necessary authentication, security, operational logs and the records you ask us to save continue to function.

Preferences apply to this browser, so set them on each browser or device you use. An opt-out from analytics or replay saved after this rollout remains in effect until you change it or clear site storage; it does not automatically expire into permission. An explicit opt-in lasts up to 180 days, after which the regional default applies. Clearing site storage also restores that default. Opting out does not automatically delete information already collected. This change applies prospectively; we do not import past hive records into analytics.

Session replay and access

Masked session replay reconstructs selected visits to help us understand clicks, scrolling, navigation and interface problems. It follows the same regional defaults and saved preferences as described above. Text, inputs and element attributes are masked before transmission. Photos, maps, embedded media and canvas content are blocked. Sign-in, registration, verification, password recovery, private profile, account security, billing, team administration and internal administration screens are excluded. Network request and response bodies, headers, console logs and automatic exception capture are disabled. Page URLs are reduced to general routes without record identifiers or query strings. Replay does not record your camera, microphone or activity outside BeekeeperOS. New recordings are retained for 30 days; not every visit will produce a recording.

Access to analytics is restricted to authorized BeekeeperOS administrators and service providers supporting these purposes. Our restricted founder dashboard connects pseudonymous analytics identifiers to account and organization details, and may link a captured completed action to its saved product record. Engagement time is estimated from visible, focused use and recent interaction; error diagnostics use bounded categories without error messages, private text or request bodies. Daily founder reports contain aggregate statistics, with individual investigations available only after administrator authentication. Daily reporting snapshots are retained for up to 90 days; underlying product records follow the retention policy above. We may retain aggregated information that no longer identifies you. Internal owner and designated test activity may be excluded from customer reports while remaining available for troubleshooting.

Communications and notification history

We keep message types, scheduling and delivery statuses, provider identifiers and relevant preferences to deliver requested service messages, respect opt-outs and investigate failures. Authorized administrators may view protected communication histories. Verification codes, recovery tokens and secret authentication links are not retained in those previews. Optional engagement, education and marketing choices are separate from essential security messages. Recipient notifications can record read and dismissal state within the app; an email delivery status does not tell us whether you read it.

Terminal message previews are removed after 90 days and provider-event metadata after 180 days through scheduled cleanup; a disabled worker can delay cleanup. Delivery identifiers, suppression and audit records may be retained for deduplication, security and accountability under the reviewed deletion procedure above.

For access or deletion requests, contact hello@beekeeperos.com. We address applicable analytics data held by our service providers as part of those requests. Marketing-site choices are managed on beekeeperos.com; the app’s controls apply to app.beekeeperos.com and do not change those marketing-site choices. Material changes to these practices will be communicated through an updated notice and, where appropriate, an in-app notice or other required choice.

Terms & Conditions

Return to registration