Read-only normal workflow
Guided Capture requests diagnostic values. Coding, tuning and programming operations are not part of the standard capture paths.
Read-only by design. Local by default.
OBDVeloce is coming soon for Windows. Engine Fault Scan reads supported engine fault-code evidence; Guided Diagnostic collects measurements, and SmartReport/PDF uses accepted evidence from completed runs. This diagnostic processing is local. Website submissions and files you choose to share are separate data flows.
- Read-only guided workflow
- Local session files
- User-controlled sharing
Supported diagnostic requests
On your Windows machine
- Vehicle ECU
- Diagnostic adapter
- Windows COM port
- Guided Diagnostic
- Accepted run evidence
- SmartReport + PDF
Optional manual action
You choose what to shareA recipient you have checked
Core security principles
Six principles the current workflow actually follows.
Local data control
Diagnostic captures and report processing run on the Windows computer. Website request storage is separate.
Deliberate sharing
Check file contents and the recipient before sharing. Other software or device backup settings can also affect where local files are copied.
Traceable evidence
SmartReport links accepted evidence to the completed diagnostic run and preserves its context and limitations.
Configuration-specific support
Which requests are supported depends on the exact vehicle, ECU, protocol and adapter, not on the model name alone.
Transparent limitations
Missing signals, partial captures and unsupported states stay visible instead of being quietly turned into certainty.
Vehicle interaction boundaries
The normal workflow collects evidence rather than changing configuration.
Normal Guided Capture
- Requests supported standard OBD values such as engine RPM, vehicle speed, coolant temperature and control-module voltage
- Requests supported Alfa diagnostic values for Turbo / Air, Fuel / Injection, EGR, DPF / Exhaust and Oil / Pedal
- Receives and decodes recognised ECU responses
- Records structured diagnostic-session samples locally
- Preserves the source command, identifier, raw response and timestamp where available
Manufacturer-specific capture may require diagnostic-session setup and supported read requests. That is diagnostic communication, not vehicle coding or programming.
Not part of normal Guided Capture
- ECU coding or module programming
- Proxy alignment
- Injector coding
- Adaptation writing
- Actuator control or active testing
- Forced DPF regeneration
- Fault-code clearing
- Tuning or remapping
- Immobiliser operations
- Firmware flashing
- Automatic repair commands
This describes the current normal product boundary. The excluded operations are simply not what OBDVeloce does.
Safety state workflow
Each state depends on the one before it.
Configuration first
V1 covers Giulia and Stelvio 2.2 JTD / Multijet. The documented reference is a 2020 Stelvio with Bosch EDC17C69. Other V1 configurations need review; selecting a model does not approve its ECU, adapter or diagnostic modes.
Connect adapter
Attach a supported diagnostic adapter and select the Windows COM port.
Verify ECU response
Confirm the adapter answers and that recognised diagnostic communication is established.
Select capture group
Choose Core / Standard, or Core plus one supported Alfa group.
Run read-only capture
Run the recommended condition and duration while recognised responses are recorded.
Stop and save
Finalise the session so the collected evidence becomes a local source record.
Review evidence
Examine the captured signals, the missing ones and the capture quality.
Before any driving capture
Do not operate the application when it is not safe to do so. A driving capture should only be attempted when conditions permit safe operation, with a passenger or in a controlled environment.
Local storage architecture
Sessions and reports are kept apart, and stay linked.
Guided Diagnostic saves diagnostic evidence locally. SmartReport and local PDF export use accepted evidence from completed runs. A standalone saved or imported session does not automatically become a SmartReport.
Session structure
- Live
Sessions recorded directly through Guided Capture.
- Imported
OBDVeloce JSON sessions can be reviewed locally.
- Reports
Saved structured diagnostic reports.
- Archive
Sessions intentionally excluded from the default active library.
- Simulated
Demo and test data that stays clearly identified.
- Logs
Technical and Developer Mode diagnostic logs.
What local handling provides
- Direct access to your own session and report files
- The current capture and review workflow without a required cloud account
- Local session replay and report review
- Control over where you copy files yourself
- A clear separation between sessions and reports
- Continued review without an active internet connection
What local storage does not automatically provide
Local storage alone does not establish the protections below. Check the application, Windows and any backup or sharing tools you use rather than assuming they are provided.
- Native file encryption
- Encrypted transfer
- Automatic off-device backup
- Automatic cloud synchronisation
- Protection against disk or device failure
- Malware protection
- Secure deletion
- Access control between Windows users
- Tamper resistance or immutable evidence
- Cryptographic signatures
Local storage alone does not make a file encrypted, backed up, access-controlled or resistant to modification.
User device responsibility
The computer holding the files is yours to protect.
Protect the Windows account and device holding diagnostic files. Review operating-system security, access permissions and backup settings, including any folders synchronised by other software.
- Secure the Windows user account
- Keep the operating system updated
- Use appropriate device access controls
- Consider disk protection provided by the operating system or your organisation
- Keep backups where the files matter to you
- Protect exported files
- Confirm the recipient before sharing anything
- Avoid keeping diagnostic files on untrusted shared computers
- Use reputable endpoint protection where appropriate
- Restrict physical access to the machine
Privacy and intentional sharing
Local diagnostics, website requests and voluntary sharing.
Local use
Guided Capture, supported imports, session review, replay and deterministic report generation all happen on the local Windows machine. The current workflow does not require a customer cloud account.
Deliberate sharing
The contact form accepts text only when available. Do not send diagnostic files or logs unless a suitable sharing method and the required content have been agreed. Website requests are processed separately through Vercel and Brevo.
Before you share
Review the file for vehicle identification numbers, registration details, customer information, workshop notes, email addresses or anything else not needed for the question you are asking. Share only what you are authorised to provide.
Diagnostic files can identify a vehicle
A diagnostic session may contain vehicle identification numbers, ECU identifiers, timestamps, notes and operational telemetry. Review files before sending them to support, specialists, public forums or any third party.
Data flow summary
- Desktop diagnostic processing is local; this is not a claim about all device or website traffic.
- Available forms retain requests in Brevo before attempting emails. General Contact records a privacy notice; interest registration keeps its separate versioned consent.
- Review files, recipients and your device’s backup or synchronisation settings before sharing.
Before you connect
Review compatibility before connecting to your vehicle.
Choose launch updates or interest in future validation. This is an expression of interest, not a verified Beta application. Neither choice establishes eligibility, selection, a licence or software access.