Cookies & device storage

DCR VEDAR LTD uses device storage to sign you in, protect and recover investigations, remember display choices and make the app work offline. The reviewed website and application do not use advertising or analytics trackers. We do not sell data or use it for advertising tracking.

Company and contact

DCR VEDAR LTD is registered in Scotland, company number SC906562, incorporated on 21 October 2026. Registered office: Clyde Offices, 48 West George Street, Glasgow, Scotland, G2 1BP. Public contact and privacy enquiries: account@dcr-vedar.com.

Public website

The separate information website uses locally hosted images, fonts and scripts. It does not set application cookies or store visitor preferences. Its hosting provider processes web requests.

Sign-in and account security

The diagnostic app uses Supabase authentication. Its browser storage holds session tokens and account information so a valid session can continue and renew. These are not advertising identifiers. Session storage can persist across browser restarts until sign-out, revocation or expiry. Signing out ends the app session; it does not delete every saved investigation or original file on the device.

Investigations, recovery and original files

Account-scoped device storage can include vehicle registrations, complaint and fault details, evidence descriptions, tests, AI answers, saved Ask VEDAR exchanges and workshop outcomes. Saved cases and temporary recovery drafts use local storage. Original evidence files use the browser's IndexedDB database and may be the only copy of those files.

After 24 hours of inactivity a temporary draft is held for a recovery decision, not silently erased. Saved cases and original files have no automatic deletion deadline in the app. Logout offers handling of unsaved work; retained data stays on the device. Short recovery markers record operation identifiers and timing, not the diagnosis content; the app discards markers older than seven days when it next reads them.

Cloud-saved case text and evidence references can be available after signing in elsewhere. This does not mean original evidence files have been backed up to the cloud. Successful Ask answers are saved as bounded text with their question, date, source links and a photo-used indicator; the Ask photo itself and unsent messages are not saved in that conversation history. New replies while viewing a completed snapshot are session-only; start a new investigation to save further work.

Preferences and offline app files

VEDAR remembers your workshop setup and chosen workspace layout on this device. In Settings, choosing Automatic removes the saved Mobile/Desktop layout preference. The web app adapts to the screen again. Android's installed prototype keeps its Mobile workspace.

The PWA service worker caches public application files, icons and guides for offline use and updates them with new releases. These caches are separate from saved investigations. Authenticated API responses are not stored in this service-worker cache. Cached files have no fixed expiry; updates, browser cleanup or uninstalling can remove them.

Moving between website addresses

Browser storage belongs to the exact website address. Evidence, drafts, local cases and sign-in sessions at dcr-vedar.com do not automatically move to vedar.app. Use the existing-device workspace on the same device and browser to review and save your records. Preserve original files independently; cloud case text is not a backup of those files. The Android prototype continues using its existing production API address. Do not clear site data or uninstall an existing PWA to change address.

Your controls and shared devices

Use Sign Out when finished, and follow the unsaved-work choices. Use a separate, locked device or browser profile for workshop work: account separation inside VEDAR does not protect readable browser files from someone with access to that profile. Clearing site data or uninstalling can permanently remove the only copy of evidence. Save or export what you need before doing so. Downloaded reports and printed copies are controlled separately by you.

Providers and privacy requests

Supabase provides authentication and cloud database services; Railway hosts the application. When you use diagnostic AI features, relevant submitted information is processed through OpenAI. Registration lookup sends the registration to the DVSA MOT history service. These operational disclosures are different from selling data or advertising tracking. Device-storage controls do not erase suppliers' records or owner-controlled backups.

Completing a case saves a private workshop outcome; it never publishes automatically. The opt-in feature lets a technician separately preview and publish an editable technical account of a confirmed repair, including deliberately entered make/model, model year, engine details and measured results. Private notes, AI answers, conversations and original files are not copied automatically. Registration, VIN, contact details and identifying stories must be omitted. The technician reviews the exact server-checked snapshot before confirming publication. Automated checks cannot guarantee anonymity; names and indirect identifying details still need human review. Historical shared records stay contained. A restricted owner/source link is retained for withdrawal and privacy review, so we do not describe our internal publication records as anonymous. Withdrawal removes future shared-history access; copies already made by others cannot be recalled. Account-deletion requests can be submitted from app Settings; they require review, and account erasure is not currently enabled. AI-answer reports send the selected answer and the information you review in the report form, not an automatic copy of the whole case.

For privacy or storage questions, contact account@dcr-vedar.com. This information describes the current functionality; it is not a promise that browser cleanup deletes all account data.