Early access
Privacy
This page describes how HiveJot handles information today, based on how the application is actually built. HiveJot is in early access and is not yet a production service; the open decisions at the end must be settled by the owner before a public launch.
Who uses this information
HiveJot is a beekeeping record-keeping application. Businesses record their own hives, inspections, harvests, expenses, sales and team. Information you or your business enter is used to provide those features to you and to the other people in your business.
This website
The public pages use no cookies, no analytics, no advertising and no third-party scripts, fonts or images. They are served from Cloudflare, which, like any host, can see ordinary request information such as the address of the visitor's connection.
Signing in
- Sign-in uses Firebase Authentication from Google, with Google Sign-In or an email and password. A verified email address is required. Google and Firebase handle the sign-in itself under their own policies.
- HiveJot keeps a record that links your verified sign-in (the provider's account identifier and your email address) to your person in your businesses. Signing in does not create a business and does not give access to any business.
- After sign-in the application creates a session that lasts eight hours. It is held in a secure, HTTP-only cookie; the server stores only a one-way digest of it. A second short-lived cookie protects against cross-site requests. Both are strictly necessary and are used for nothing else. Sign-in tokens are not kept in browser storage.
- The browser keeps a pending invitation code in tab storage until it is used or expires (48 hours). A record that you finished or skipped the welcome tour may be held briefly in local browser storage if it could not be saved to your account.
Businesses, people and access
- Applications. To ask for a business workspace you provide a business name, your name, your verified email, an operating region, a short description and a time zone. A platform administrator reviews it; nothing is created until it is approved.
- Invitations. A business owner or administrator can invite an email address. The invitation code is stored only as a one-way digest, expires after 48 hours and is shown to the inviter once. Invitation emails, when switched on, are sent through the Gmail service and contain the business name, the invited email address and the role offered.
- Roles. Access inside a business depends on its roles (Owner, Admin, Member), farm assignments and, for financial information, a separate partner designation. These rules are enforced by the server, and information from one business is not available to another.
- Business records. Farms, hives, inspections, harvests, packaging and stock, inventory, expenses, sales, payments, capital and reports, and the names and roles of team members. Changes are recorded in an audit history that is not edited after the fact.
- Security records. Sign-in and onboarding events and short-lived counters that limit repeated attempts. Counters are keyed by hashed identifiers and expire automatically.
Receipts and attachments
An expense can carry up to ten receipt files (PDF, JPEG, PNG or WebP, up to 5 MB each). The file is stored by the HiveJot server and its details in the database. Nothing is uploaded until you save the expense. In the current early-access setup these files are kept on the storage of the machine running the service, which is not durable hosting.
Services involved
- Google and Firebase: sign-in, email verification and password-reset messages.
- MongoDB Atlas: hosts the database of business records.
- Cloudflare: serves this website and carries traffic to the application through a secure tunnel.
- Gmail: sends invitation emails only when that feature is switched on, one message per invitation.
HiveJot does not sell information, show advertising or use analytics services.
Early-access status
The early-access application currently runs against a development database that is shared with development work, and is available only to approved testers while the owner's computer and services are running. Records entered by testers are real records in that database. Do not enter information that you would not want held in a development environment.