BayLogicPrivacy Policy
This explains what BayLogic stores, who else can see it, and how to get it back or have it deleted. It is written to be read rather than to be technically survivable, so if something here is unclear, ask and we will fix the wording.
What we store
- Your account. Name, email address, a password stored only as a hash we cannot reverse, your role in the shop, and when you accepted these terms.
- Your work. The jobs you log — complaint, fault codes, what you tested, what you repaired, hours booked and worked, recommendations, and any fault screenshots you attach.
- Your shop’s board. Which vehicles are in, who has them, what they are waiting on.
- Operational records. Server logs, error reports, and a count of how many AI write-ups your shop has used this month.
We do not use tracking cookies and there is no advertising on BayLogic. The only cookies are the ones that keep you signed in, keep a wall display signed in, and remember whether you chose the light or dark theme.
Information about your customers
A logbook entry usually contains information about somebody who is not a BayLogic user — a vehicle owner’s name, a VIN, what they said was wrong with the car.
We hold that on your behalf and for no other purpose. We do not sell it, mine it, or use it to build anything. It is deleted when you delete the job or close your account. If one of your customers asks you what you hold about them, the export in your settings is the answer, and we will help if you need us to.
What we do with it
We use it to run the service for you: to show you your logbook, produce your write-ups, count your hours, render your shop’s board, and email you about your account. We look at individual records only to fix a fault you have told us about, or where the law requires it.
We do not use your jobs to train AI models, and we do not sell anything to anybody.
AI write-ups
When you press Polish, the notes you typed for that job are sent to Anthropic, which returns a rewritten version. Only those notes go — not your customer’s name, not the VIN, not your logbook, not anything about other jobs. Anthropic does not use it to train models.
If you never press Polish, nothing about your work is ever sent to a model. The template write-up runs entirely on our own server.
Who else necessarily sees it
Running a service means other companies handle some of the data. These are all of them:
| Company | What for | What they see |
|---|---|---|
| Railway | Hosting and database storage | Everything stored in the service, on a disk they operate |
| Anthropic | AI polish for repair-order write-ups | Only the job notes you send when you press Polish. Not sent for training. |
| Resend | Transactional email | Your email address and the contents of account emails |
| Stripe | Payment processing for paid plans | Billing details, handled by Stripe. Card numbers never reach this service. |
| Cloudflare | DNS and network for baylogic.shop | Request metadata in transit |
Card numbers never reach BayLogic. Payment details are entered on Stripe and stay with Stripe; we only ever learn that a subscription is active.
Where it lives, and for how long
Each shop’s data sits in its own database file, on a disk in the United States. We keep it for as long as you have an account. Backups are taken nightly and held for about two weeks, so for a short period after you delete something it still exists in a backup before ageing out.
Getting it out, and getting rid of it
- Export. Settings has a Backup button that gives you everything in your logbook as a single file, screenshots included. No request, no waiting.
- Deletion. Closing your account deletes your logbook, your attachments and your account record. Export first; we cannot recover it for you afterwards.
- Correction. You can edit or delete any job yourself at any time.
The exception is a case you chose to publish. Published cases are copies, they carry no customer name, VIN, repair order number or mileage, and they remain available to other technicians after you leave. The terms say so in section 6, and it is the one thing here you should read before you publish rather than after.
Security
Passwords are stored as PBKDF2 hashes and never in a form we can read. Traffic is encrypted in transit. One shop’s data is in a separate database file from every other shop’s, so a query that forgets to check cannot reach across — and there is an automated test suite whose only job is to keep proving that.
No system is perfect. If you find a way to reach something you should not be able to, email us and we will treat it seriously and thank you properly.
Children
BayLogic is a tool for working technicians and is not intended for anybody under 16.
Changes
If we change this policy in a way that matters, we will tell you before it takes effect. The version and date at the top always say which one you are reading.
Reaching us
Email [email protected] with anything at all — including a request to see or delete what we hold about you.