Privacy policy

Effective August 14, 2026 · Blacktop Labs LLC

What lotbiddr is

lotbiddr is business software for paving and pavement-maintenance companies: estimating, scheduling, timecards, and a mobile field app for crews. Your company — the organization that invited you — runs its own lotbiddr account, and you use lotbiddr as a member of that organization. This policy explains what data lotbiddr handles and how.

Account data

When your organization invites you, lotbiddr stores your name, email address, and a password (stored only as a salted hash) — or, if you sign in with Microsoft on the lotbiddr website, the name and email your Microsoft account provides. Optional profile photos and two-factor settings are stored if you add them. We use this data to run your account: signing you in, showing who did what, and sending the notifications you or your organization configure.

Your organization's data

Companies, contacts, sites, projects, estimates, proposals, schedules, timecards, and similar records belong to the organization that created them. lotbiddr (operated by Blacktop Labs LLC) stores and processes that data solely to provide the service to that organization. Organizations are isolated from each other at the database level (row-level security); no organization can see another's data. Before enabling workforce features like location tiers, each organization is responsible for satisfying any employee-notice obligations that apply where its crews work.

Location (the field app)

This is the part that matters most to field crews, so here it is plainly:

  • On the clock. Location is recorded while you're on the clock, and only when your organization uses a location tier — each organization picks its tier, or turns location off entirely, in its field settings. A checklist confirm also stamps where you tap it, on or off the clock. Recording stops when your clock-out reaches us: at once when you clock out on the clock screen with signal, otherwise when the clock-out your phone saved lands (from anywhere else in the app, as it lands and nothing is still waiting to send from your phone). When your punch is closed anywhere else — by your foreman or the office, or by you on another device — it stops the next time the app opens while you're signed in to your company with signal (once nothing is still waiting to send from your phone). A position from the background trail that reaches our servers more than fifteen minutes outside your punches is thrown away.
  • Two tiers, chosen by your organization. Punch points: your location is recorded at clock-in and clock-out, and where you tap to confirm a checklist — no trail in between. On the clock: location is recorded in the background from clock-in to clock-out, even if the app is closed — a trail position that reaches us more than fifteen minutes off the clock is thrown away. If you forget to clock out, it keeps recording until your clock-out reaches us — and if your punch is closed anywhere else (by your foreman or the office, or by you on another device), until the app next opens with signal while you're signed in and nothing is still waiting to send from your phone. You can see your own trail for the day; if you leave a site still clocked in, you get a reminder to clock out; at the end of the day you confirm your day before it goes to the office, so your hours land on the right job. The app shows a persistent indicator while this runs.
  • What is recorded: GPS coordinates, accuracy, a timestamp, and — when you cross a jobsite boundary — an entered/left marker tied to the jobsite and your open punch. On iOS, the system may ask for motion access on behalf of the location service, which can use on-device motion sensing to pause GPS while your phone is still (battery saving); lotbiddr's own code never reads motion data, and motion data never leaves your phone and is never stored by lotbiddr.
  • Consent, and the decline path. Before your first location-enabled punch, the app shows you a consent screen. If you choose "Punch without location," you can still clock in and out of every job — you're just responsible for clocking in and out of each job yourself. Declining never blocks your pay or your punches.
  • The trail is kept 90 days. The on-the-clock location trail — the recorded points and the jobsite entered/left markers — is deleted after 90 days. The single location stamps captured at clock-in and clock-out are part of the timecard itself: they stay with that business record, and are removed when you delete your account.
  • Who sees it: you first — your own trail for any of the last 30 days on the Your trail page, and the day you confirm before it goes to the office — then the office staff and crew leads of your own organization, on its timecard and crew surfaces. Nobody else's trail is ever shown to you, and yours is never shown to another crew member. Location is never sold, never used for advertising, and never shared with other organizations or third parties.

Cookies and sessions

lotbiddr uses cookies only to run the app: a session cookie that keeps you signed in, a security (CSRF) token, and small preference cookies (such as your theme and screen hints). No advertising cookies, no cross-site tracking.

Service providers

lotbiddr runs on service providers that process data on our instructions:

  • Fly.io — application hosting and managed Postgres databases.
  • Resend — transactional email (invites, sign-in codes, notifications).
  • Tigris — object storage for uploaded files: profile and project photos, organization logos, and generated documents.
  • Google Maps Platform — maps, address autocomplete, and drive-time estimates on office and estimating surfaces: jobsite addresses and coordinates are sent to Google to render maps and compute distances. The on-the-clock location trail is never sent to Google.
  • BoldSign — e-signature delivery when your organization sends a proposal for signature: the recipient's name, email address, and the document being signed.
  • Sentry — error and crash reporting, so we can fix problems. Session replay never runs on field-crew surfaces or in the mobile app.
  • Anthropic — only if your organization enables optional AI features with its own Anthropic API key; the relevant content is then sent to Anthropic under your organization's key. Off by default.

Security

All traffic is encrypted in transit (HTTPS). Passwords are stored as salted hashes. Certain sensitive fields are additionally encrypted at rest. Organizations are isolated by database row-level security. We keep a log of sign-in events on your account (time, method, outcome, IP address and device) for one year, for account security; you can see your own under Settings.

Data deletion and your choices

  • You can delete your own account data yourself, at any time — the account-deletion page walks through it, including what stays with your employer's organization as its business records and why.
  • Organization data is deleted at the organization's direction; when an organization leaves lotbiddr, its data is removed on request.
  • The on-the-clock location trail is deleted after 90 days (see Location above).
  • For any deletion or access request, email support@lotbiddr.com from the address on your account and we will respond within a reasonable time.

Children

lotbiddr is workplace software and is not directed at children under 16.

Changes to this policy

We'll post changes here with a new effective date. For material changes affecting field workers — like the location sections above — we'll notify organizations so they can inform their crews.

Contact

Blacktop Labs LLC · support@lotbiddr.com