// legal

Privacy Policy

Last updated 17 September 2026 · Applies to all LB Development products listed below
Who this is about: LB Development is operated by Liam Burnett, an individual based in Brisbane, Queensland, Australia.

What this covers: the LB Dev homepage (lbdev.app), LB Tools (tools.lbdev.app), Pit Wall, Login Panel ("Sign in with LB Development" and any site that uses it), the shared contact-form/Discord webhook API, and future LB Development products including an in-development Scouts-focused tool (working name SFOS).

What this doesn't cover: client sites built for someone else's business (e.g. Steady Path Support) — those have their own, separate privacy policy.

// contents

  1. Our approach
  2. What we collect
  3. How we collect it
  4. Why we use it
  5. Cookies and similar technology
  6. Who we share it with
  7. Overseas disclosure
  8. AI processing
  9. Children and young people
  10. How long we keep it
  11. Security
  12. Your rights
  13. Complaints
  14. Changes to this policy
  15. Contact

01Our approach

These are personal and hobby/school-assessment projects, not a registered business — as an individual operator we may not be strictly required to comply with the Privacy Act 1988 (Cth) the way a large organisation is. We've chosen to handle your information in line with the Australian Privacy Principles (APPs) anyway, because it's the right way to run anything that touches real people's data, including students, robotics teams, and Scout troops.

The short version: we collect the minimum needed to run each feature, we don't sell your data, we don't run ads or third-party trackers, and we tell you here exactly which third parties we do share data with and why.

02What we collect

ProductWhat's collected
LB Dev site / LB ToolsNo accounts. If you use the contact form: name, email address, subject, and message.
Contact form / Discord webhook APIName, email, subject, message — from any product's contact form (LB Dev site, Pit Wall). Also handles inbound email sent to LB Development addresses.
Login PanelEmail, display name, hashed password (via Firebase Authentication — we never see or store your plaintext password), email-verification status, account role; on each login: IP address, browser/device user agent, and a coarse country/city derived from your IP (not GPS location); which other LB Development sites you've connected and what they can see; a full history of login attempts (success/fail) tied to your account.
Pit WallEmail, display name, team number/name, role on the team; robot profile (drivetrain, mechanisms, autonomous routine); scouting notes on other teams; engineering-notebook entries and any photos/documents you upload; AI chat messages; pit-checklist state.
SFOS (in development)Not yet built. This policy will be updated with specifics before it collects any real data — see Changes to this policy.

03How we collect it

04Why we use it

05Cookies and similar technology

Login Panel sets a single, essential session cookie (HttpOnly, Secure, scoped to LB Development domains) so you stay signed in — it isn't used for tracking or advertising, and it's deleted when you sign out or expires automatically. Cloudflare Turnstile may set its own cookies as part of verifying you're not a bot on login/registration/forgot-password pages. We don't run Google Analytics, ad pixels, or any other third-party tracking script on any LB Development site.

06Who we share it with

We use these third-party services to actually run the Services. Each only receives what it needs to do its job:

ServiceWhat it getsWhy
Firebase / Google CloudAccount credentials, profile data, all Firestore-stored contentAuthentication and database hosting
Cloudflare (Workers, KV, Turnstile, Email Routing)Request metadata (IP, user agent), bot-check tokens, session data, routed emailHosting, bot protection, email handling
CloudinaryUploaded photos/documents (notebook pages, final write-ups)File storage for Pit Wall's engineering notebook
GroqAI chat messages, and robot profile/scouting/notebook content used as contextGenerating AI chat responses and feedback
DiscordContact-form submissions (name, email, subject, message) and inbound-email contentPosting these as a forum thread so we see and can respond to them — visible only within our own Discord server, not publicly
FIRST FTC Events API / FTCScoutTeam/event lookups (no personal account data sent)Pulling official match schedules, results, and public team statistics

We don't share your data with anyone else, and we don't sell it. If you sign in via Login Panel's "Sign in with LB Development" to a connecting site, that site only receives what's listed on the consent screen you approve.

07Overseas disclosure

Several of the services above (Firebase/Google Cloud, Cloudflare, Cloudinary, Groq, Discord) process data on servers located outside Australia, typically in the United States. By using the Services, you understand your information may be processed overseas, subject to that provider's own security and privacy practices, which you can review on their respective sites.

08AI processing

Pit Wall's AI chat, engineering-notebook feedback, and event analysis send your input — plus relevant context from your own team's robot profile, scouting log, or notebook — to Groq's API to generate a response. This content is processed by a third party to produce that response; don't submit anything you wouldn't want handled that way. We don't use your data to train our own AI models.

09Children and young people

Pit Wall (and, in future, SFOS) are commonly used by people under 18 as part of a school robotics team or Scout troop. We collect the same limited set of information described above regardless of age, and we don't knowingly collect more from a young person than the feature actually needs. We rely on the supervising school, team, or Scout group to obtain any parental/guardian consent appropriate to their own context — this app is a coordination and record-keeping tool, not a substitute for an organisation's child-safety or working-with-children processes.

If you're a parent or guardian and want to review or ask us to delete a young person's data, contact us at help@lbdev.app and we'll work with you directly.

10How long we keep it

11Security

Passwords are handled entirely by Firebase Authentication using industry-standard hashing — we never see or store them in plain text. Firestore security rules restrict every team's/user's data to people who belong to it. All Services are served over HTTPS. Login/registration/password-reset are protected by Cloudflare Turnstile against automated abuse. That said, no online service is 100% secure, and we can't guarantee absolute security of information you transmit to us.

12Your rights

You can ask us, at any time, to:

Reach us at help@lbdev.app to exercise any of these. We'll respond within a reasonable time.

13Complaints

If you're unhappy with how we've handled your personal information, tell us first at help@lbdev.app so we can try to fix it. If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC).

14Changes to this policy

We'll update the "Last updated" date above whenever this changes, and we'll make a reasonable effort to flag material changes in-app or by email — in particular, when SFOS moves from development to a real launch, this policy will be updated with the specifics of what it actually collects before it processes any real user's data.

15Contact

Questions, requests, or complaints about your privacy: help@lbdev.app, or the contact form on lbdev.app.