SERVICE VAULT

Privacy Policy

Last updated: 14 August 2026

Who we are

Service Vault is a UK vehicle service-history product. It is operated by Lauren Dallas, trading as Service Vault. For UK GDPR purposes, Lauren Dallas / Service Vault is the data controller.

Contact: hello@servicevault.app. We are based in the United Kingdom. The product is offered in GBP for UK garages and vehicle owners.

This notice describes personal data processed through the Service Vault mobile app, the garage web portal, and the Service Vault API. The public copy of this policy is at https://api-production-95cd.up.railway.app/privacy.

What Service Vault does

Garages scan QR stickers on vehicles, record workshop visits, and stamp verified service history. Vehicle owners create accounts, link vehicles, view that history, upload older records, and transfer ownership when a vehicle is sold. Garages can order printed QR sticker sheets. Payment is taken by Stripe; print-and-ship fulfilment is handled by Diginate (or, in some cases, an internal print partner).

Personal data we collect

We only collect what the product actually uses. We do not run advertising trackers or third-party analytics SDKs.

Owner accounts

When you sign up we store your first name, last name, email address, phone number, and a hashed password. We record the time you accepted these terms and this privacy policy. We send an email-verification token so you can confirm the address.

If you request a password reset we store a hashed one-time token (the raw token is emailed). Tokens expire (verification links last 48 hours; password-reset links last 1 hour).

On the device, a login token, email, and role are stored in the operating system’s secure storage. We do not use cookies for app login.

Vehicles, QR codes, and service history

When a vehicle is linked we store the UK registration number and, if provided, the VIN, current mileage, and oil details a technician confirms. We may look up make, model, colour, fuel type, year, engine size, MOT expiry, and MOT test history by sending the registration to the DVLA Vehicle Enquiry API and the MOT History API.

Each sticker has a public QR identifier. Scanning it can open a landing page and, in the app, claim the vehicle, request temporary viewer access, or start an ownership transfer.

Service records include the date, mileage, work types (for example service, MOT, repair), job reference, summary, inspection items, parts, fluids, photos, and file attachments. Garage staff may also add internal notes. Verified records that a service manager has approved are treated as an immutable ledger for that vehicle.

If you upload past history we store the PDF or service-book photos you submit, draft entries extracted from them, and the entries you confirm. If extraction is blocked you may send a manual-review request with an explanation and optional contact name, email, and phone.

Ownership claims, transfers, and temporary viewing

To claim a vehicle you may submit documents such as a driving licence, V5C, bill of sale, or proof of purchase. Those files are stored so we can review the claim.

If you transfer ownership we store the buyer’s email and phone, a claim token, and the outcome. After a successful transfer your access to that vehicle’s history ends; the history stays with the vehicle for the new owner.

Someone who scans a claimed vehicle’s QR can ask for temporary viewer access. We email a short-lived code to the registered owner. Viewer sessions last 1 hour and do not transfer ownership. Similar short-lived email codes are used when claiming a further vehicle or requesting an ownership transfer from a previous owner.

Camera, photos, and location

The app uses the camera to scan QR stickers and, if you choose, to photograph ownership documents, service books, or workshop photos. Images are stored only when you (or garage staff) upload them as part of a record, claim, or history upload. We do not record audio. On Android the camera library may still request a microphone permission; Service Vault does not use the microphone.

Location is optional and used only while the app is in use, to sort registered garages by distance. Coordinates are sent as a one-off search (latitude, longitude, and an optional radius). We do not keep a location history or track you in the background. You can refuse location permission and still use the rest of the app.

Garage and technician accounts

Garage applications and profiles may include business name, VAT number, address, city, postcode, phone, mobile, email, website, booking URL, logo, and map coordinates if the garage is listed for owner discovery.

Staff accounts store name, email, phone, hashed password, role, and garage association. Service managers who sign up on the website also confirm their email with a verification token. Technician seats created by a service manager store a username, display name, hashed password, a bound device identifier, last login time, and last IP address (for audit and to keep a seat on one device).

Workshop activity includes who scanned a vehicle, when the visit expires, and any waiver note if a manager closes a visit without a stamped service.

Sticker orders and payments

When a garage orders QR stickers we store the quantity, optional notes, delivery address, amount in pence (GBP), and payment/fulfilment identifiers (Stripe Checkout session and payment intent; Diginate order, shipping status, and tracking code when fulfilment runs).

Stripe processes the card payment. We pass the garage contact email, garage name, order quantity, and a request identifier to Stripe Checkout. We do not store full card numbers. A Stripe customer ID field exists on garage records but is not currently populated by the live checkout flow.

For print-and-ship we send Diginate the garage name, phone, and delivery address, plus the QR artwork (public QR landing URLs). We do not send Diginate owner names, VINs, or service history.

If an internal print partner is used instead, they see batch metadata and the QR public IDs they need to print — not owner or service-history data.

Emails and notifications

We send transactional messages from hello@servicevault.app (or the configured from-address): email verification, password reset, vehicle-claim keys, viewer-access codes, ownership-transfer codes, and technician password-help notices to the garage manager. In-app notifications cover claim outcomes, transfers, and similar account events.

We do not send marketing newsletters from this product today. If that changes we will say so here and only email marketing with a lawful basis.

Cookies and similar storage

The Service Vault garage web portal stores a login token in the browser’s local storage. It does not set first-party tracking cookies. Stripe Checkout runs on Stripe’s domain and may set cookies there under Stripe’s own policy.

The public QR landing and these legal pages are ordinary HTML; they do not set analytics cookies.

What we do not collect

We do not use Google Analytics, Mixpanel, Amplitude, PostHog, or similar product-analytics SDKs.

We do not offer Sign in with Apple or Sign in with Google. Accounts use email and password (or garage-issued credentials). We do not collect Apple or Google account data for login.

We do not sell personal data.

How we use personal data

To create and secure accounts; link vehicles to owners and garages; look up vehicle and MOT details from UK government APIs; record and display service history; review ownership documents; process sticker payments and fulfilment; send the transactional emails listed above; show nearby registered garages when you allow location; and keep technician seats bound to a device.

When an OpenAI API key is configured, we may send: (1) owner-uploaded service-book images or PDFs so draft history entries can be extracted — you confirm before anything is written to the ledger; (2) vehicle make/model/year/engine/fuel to suggest oil viscosity and capacity — a technician must confirm before save; (3) garage name, city, and postcode to suggest public contact details — staff must confirm before save. If the key is not configured, those features fall back to manual entry.

Lawful bases (UK GDPR)

Contract: providing the account, vehicle history, QR linking, and sticker-order service you asked for.

Legitimate interests: securing accounts (including technician device binding and IP audit), operating the workshop scan flow, looking up DVLA/MOT data so records are accurate, and keeping a vehicle ledger after ownership changes.

Consent: optional location for nearby garages, and camera/photo-library access granted through the operating system.

Legal obligation: retaining payment and VAT-related garage records where tax or accounting rules require it.

Who we share data with

Railway — hosts the API, database, and uploaded files.

Stripe — card payments for garage sticker orders.

Diginate — print and ship physical QR sticker sheets to the garage address.

DVLA and the MOT History service — registration lookups as described above.

OpenAI — only for the optional extraction and suggestion features described above, when that integration is switched on.

Email delivery — when SMTP is configured, messages are sent through that provider. In some environments email is logged rather than sent; the product still stores the underlying tokens and codes.

We do not share owner service history with Diginate or with print partners beyond the QR identifiers needed to print stickers.

International transfers

Stripe and OpenAI are based in the United States. Railway may process data in the UK, EU, or US depending on how the service is hosted. Where data leaves the UK we rely on the provider’s appropriate safeguards (such as UK/EU standard contractual clauses or a UK adequacy decision) as applicable to that provider.

How long we keep data

Account data is kept while the account is active. Short-lived tokens and viewer sessions expire as described above (typically 1 hour to 48 hours).

Verified service history is kept as a ledger for the vehicle, including after an ownership transfer, because the next owner needs that history. Ownership-claim documents are kept to complete the review and for a reasonable period afterwards if a dispute arises.

Sticker-order and payment identifiers are kept for fulfilment, support, and accounting.

You can delete your account in the Service Vault app (and, for garage managers, in the garage web portal). Deletion removes your login and personal account data. Vehicle ledger entries that are not about you personally may remain for later owners or garage history. You can also email hello@servicevault.app to request erasure or restriction, or if you cannot use the in-app controls. We may retain data we must keep for legal claims, security, or tax.

Your rights

Under UK GDPR you can ask for access, correction, erasure, restriction, or portability, and you can object to processing based on legitimate interests. Where we rely on consent you can withdraw it (for example by turning off location in system settings).

Use in-app account deletion where available, or email hello@servicevault.app. You can also complain to the Information Commissioner’s Office (ICO) at ico.org.uk.

Security

Passwords are hashed. Production traffic uses HTTPS. App sessions use bearer tokens, not cookies. Technician logins can be bound to a single device. No security measure is perfect; please use a strong unique password.

Children

Service Vault is for vehicle owners and garage businesses. It is not directed at children. We do not knowingly create accounts for anyone under 16.

Changes

We will update this page when our practices change. The date at the top is the latest version. Continued use after an update means the new notice applies to later use of the service.

Home · Privacy · Terms