What LineRight Regbot keeps, and what it does not
LineRight Regbot is split in two on purpose. This site keeps the line: who holds which place and with how many credits. The desktop app keeps you: the details a booking form asks for, on your own computer. Nothing below changes that split.
What this site keeps
- Your account. A nickname other bidders see beside your bids, an email address if you give one, and how you sign in — a password hash, or the id Google gives this site for you.
- Your places in line. Each bid: the line, the credits staked, the dates and times you would take, and your choice of office or distance — never your name, licence number or date of birth.
- Your credits. Every movement: given, earned, bought, staked, returned, spent — and how long your apps have spent checking lines for everyone, which is what earns them.
- Your purchases. The pack, the price, a Stripe session and payment id, and whether it was paid, refunded or disputed. Stripe hosts the payment page; this site never sees a card number.
- Your paired apps. Each one's name, operating system and version, when it was last heard from, and how fast its round trips to this site are — measured by the site, and used to offer slots to apps that can take them.
- What the apps see. The openings apps report while looking for everyone in line, and which app reported each.
- How the site is doing. Counts of requests, errors and response times per page — never what was in a request.
- What your apps did, with you taken out of it — the trace below — for 14 days.
What stays on your computer
- Your profile: name, date of birth, licence number, address and anything else a booking form asks for. The app types it into the booking site's own form when your turn comes. It is never sent to LineRight Regbot.
- Your sign-ins to booking sites, and whatever those sites store in the app's browser tabs.
- The app's own telemetry — see below — unless you share it.
- Everything personal in what the app does: it is taken out of the trace below before anything is written into it.
The app's telemetry, and sharing it
The app keeps numbers about itself for its Advanced screen: how often it synced with this site and how long that took, the round trips the site timed, what its robots did and how long it took them, and how much memory and CPU it used. They stay on your computer for a day.
They are sent to this site only if you press Share now in the Advanced screen, or turn on
sharing every six hours. The app shows exactly what would be sent first. What goes is numbers, a short
fixed list of words (kinds of event and how they ended — read, done,
blocked), and the app's version and operating system. No profile detail, no line, office,
date or booking reference, no page you visited. This site refuses anything else in an upload, keeps
what it takes for 90 days, and uses it only to see how the apps are doing. That is the
numbers; the trace below is the other thing the app keeps for this site.
The trace the app keeps for this site
The app also writes down what it does, so that the people running LineRight Regbot can see why a booking did or did not work: when your turn reached it and what it did with it; the booking pages it opened — their addresses, how long each page and each request took, and what came back; what its robots saw and how each run ended; the errors it met; and what it told you. A page it opens on any other site is written down as that site's name alone.
Before anything is written into it, the app takes you out of it, by what it knows of you: your name, date of birth, licence, passport and Social Security numbers, address, phone and email — in every way a page or an address could spell them — any booking confirmation number, and the name of your computer's account. What you type into a form is kept only as how long it was. A value in an address is kept only when it is plainly not personal: a number, a date, a single word. This site checks every upload again — for your account's email, for any email address, Social Security or card number — and strikes out whatever it finds.
The app sends its trace only when this site asks for it: now and then, one app at a time. This site keeps it for 14 days. The app's Advanced screen shows the latest of it as it would be sent, and turns it off; off, nothing more is written down, and what was kept on your computer is deleted.
AI booking oversight
When the app's robot gets stuck while booking your slot — the booking site changed a page under it — and you have
bought credits and left AI booking oversight on, the app lets an AI finish it: a language model, DeepSeek's, asked
through this site. What goes to it is the page the robot was on as text, with you taken out of it the way the
trace takes you out (your name becomes [first_name], your phone [phone], and so on), the
office, day and time being booked, and what the robot did before it stopped. When the AI types one of your
details, it writes that placeholder and the app puts the real value into the form on your computer: your details
themselves never reach the model, nor this site. This site checks each call again, as it checks the trace, and
strikes out what it finds.
This site keeps, for each time the AI stepped in: which booking, where the robot was stuck and why, each step the AI took (with your details only as their placeholders), how it ended, and what each call to the model cost — so that a booking site that changed is seen and the robot fixed. Each call is charged to your bought credits; the app's Settings → AI booking oversight says how much, and turns it off.
When the apps' robots cannot read a line's calendar at all, this site may ask an app that has AI booking oversight on to have its AI look at the booking site and say why. That is no booking and has nothing of yours in it: the AI is given the booking site's start page, the offices and what the robots said, goes through the pages up to a list of times, and books, holds and types nothing. This site pays for it; your credits are not touched. It keeps what the AI found and suggests, to fix the robots. Turning AI booking oversight off turns this off too.
Asking for a line
When you ask for a line on a booking site LineRight Regbot does not cover, the site keeps the site's address
(without anything after a ?), what it is called, the appointments, where, and — for the
people running LineRight Regbot only — your role, your note and the email you gave, if any. Everybody can see
which sites have been asked for and how many people asked; nobody else sees who. Signed out, you are
counted once per request by a keyed fingerprint of the email you gave or of where you asked from; the
address itself is not stored.
Payments
Credits are bought on Stripe's own checkout page. Stripe handles the card; this site learns that a payment succeeded, for how much, and — if it is refunded or disputed — that too, and takes the credits back accordingly.
Leaving
Withdraw from a line and its credits come back at once. Unpair an app from your account page, and its next request is refused. The app's Settings → Start over deletes everything it keeps on your computer.