BMHub

Privacy Notice

BMHub — Privacy Notice Operator: BMHUB LLC Contact for access, correction, withdrawal, account closure and deletion: bmhub01@gmail.com 1. Scope and purposes BMHub's commercial offering is directed to the United States. Data is processed to deliver requested functions, manage accounts/access, process payments, maintain contributions/files, handle requests and protect the service. These functions involve storage and processing by the relevant providers. 2. Accounts, authentication and requests Username, email, preferred language, status, roles/licenses and account/security records are used. Passwords and verification/recovery tokens are protected by hashes; links sent to users contain temporary credentials that must be kept private. Verification/recovery processes do not erase an account or history. The email delivery service also participates in processing those messages. BMHUB LLC receives access, correction, account-closure/deletion requests and legitimate content/data claims at bmhub01@gmail.com. Account-deletion requests are handled manually. Identify the account/content and requested action without sending passwords, tokens or complete bank details. Proportionate information may be requested to verify authorization. The request's scope, existing capabilities and applicable obligations determine what is deleted or retained; total-erasure self-service is not offered. 3. Cookies, identifiers and preferences Sessions use first-party cookies with security controls. The device feature uses a random installation identifier and protected server representation, along with general device/activity information. Browser storage holds preferences and identifiers used for community functions. These data can relate to sessions, contributions or an account; they do not guarantee anonymity or unlinkability. A pending action and files selected to resume an operation may remain in page memory. External resources/providers may also process technical data when their services are used. Cookie/session duration is not the retention period of all account data. 4. Location and POSSIBLE_FOUND Geolocation is requested through a user action. Address searches use Esri ArcGIS. Visit cycles store an HMAC-protected address context or rounded center, radius, candidate benchmark and timestamps. Opening the map may select the candidate; changing context, signing out or inactivity closure can generate POSSIBLE_FOUND without another confirmation. It is not proof of physical presence or verified FOUND. The resulting status and contribution history may be shown to other users. A registered session retains an account link; functions without a session use the relevant collaborator identifier. Administration can relate records to an account to manage the service. Such an event is therefore not necessarily anonymous or exclusively private. The cycle does not record continuous GPS routes, ETA or speed. Other functions, including contributions/jobs, may contain coordinates. External maps/navigation or OpenStreetMap tiles communicate with their operators. 5. Photographs and community content Photos/contributions identified as community content may be displayed to other users with the benchmark/history. The author retains their rights. The corresponding limited authorization permits retention/display of those photographs within BMHub after account closure; it does not make them BMHUB LLC's property or authorize external advertising or unlimited sublicensing. Photo flows use Cloudflare R2/Google Drive processing/storage, references, states and timestamps, and may adapt formats for receipt/display. Retroactive consent for earlier photographs is not presumed. Legitimate privacy/copyright claims may be submitted at bmhub01@gmail.com; applicable removal is handled separately from the benchmark's FOUND, NOT FOUND or POSSIBLE_FOUND status. Recovery of copies others have lawfully downloaded is not guaranteed. 6. Daily RTK files and packages File/package download endpoints check the owning account and do not offer them to other user accounts. This does not exclude technical processing by BMHub, personnel with authorized access or providers hosting, processing or storing the data. Files may contain job names, observations, locations, snapshots, results and versions. PostgreSQL holds data/metadata and private R2/Google Drive storage supports processing/archive phases. Some packages have no automatic expiration; this is not an unlimited availability guarantee. Confirmed deletion of an archived Daily RTK ZIP does not erase other versions, observations, metadata, audit or the whole account. 7. Billing, support and progress Stripe hosts Checkout and the financial portal. BMHub retains customer/subscription relationships/states, events, invoices, payments and refund reviews. Card entry occurs at Stripe, but BMHub processes other account/billing data needed for the service. Feedback includes messages and optional screenshots accessible to the relevant user and administration; screenshots in that flow are reencoded without EXIF. Help/tutorials retain progress, version, language and timestamps. Support/security records may identify an account or activity. Do not send secrets through support. 8. Providers and technical access Services used include Render/PostgreSQL for hosting/data; Cloudflare Turnstile/R2 for protection/storage; Google Drive for files; Stripe for payments; the relevant SMTP/Resend email integration; OpenStreetMap/Esri ArcGIS for maps/geocoding; official data sources; and OpenAI for particular AI functions. Providers receive/process information needed for their functions. No absence of third parties or exclusive storage geography is asserted. Product controls separate accounts/permissions. Operational/administrative access and provider processes differ from other users' access to your packages. A protected download must not be interpreted as an absence of technical access or external processing. 9. OpenAI functions Legal Locator may send a question and retrieved official excerpts to OpenAI. Administrative tools may send aggregates or other context allowed by their functions. Use depends on technical configuration/provider availability; 'optional' does not mean there is an individual user consent/switch for each transmission. A feature not storing prompts in BMHub does not determine provider retention/processing. Daily RTK files are not described as automatic OpenAI input, nor is it claimed that no service content is sent to AI. Avoid unnecessary sensitive third-party information in questions/support or information you are not authorized to provide. 10. Retention and deletion Sessions, devices, photos, observations, packages, feedback, billing, logs and backups have different retention mechanisms. Cleanup processes cover particular records/temporary files, not every category. ZIP deletion does not erase its history/observations or every backup. Files without automatic expiration are not guaranteed unlimited retention. Account-deletion/closure requests may be sent to bmhub01@gmail.com and are handled manually. Closure does not automatically remove community photos where the corresponding authorization permits retention/display. This does not prevent legitimate claims or legally required removal. Scope must distinguish content, account records, history and copies requiring separate treatment. Anonymization, instant deletion, erasure of every copy or an unestablished fixed deadline is not promised. Applicable mandatory rights/obligations remain unaffected. 11. Security and contact Authentication, permissions, request protections and private-storage controls are used in the described flows. No system guarantees absolute security. Send data requests/questions to bmhub01@gmail.com with only information necessary to identify them.