--- title: "Data Act Vehicle Data Guidance" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/vehicle-data-guidance" source_url: "https://www.sorena.io/artifacts/eu/data-act/vehicle-data-guidance" author: "Sorena AI" description: "Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act vehicle data" - "Commission vehicle data guidance" - "connected vehicle data access" - "automotive aftermarket data" - "GDPR vehicle data" - "EU Data Act" - "Regulation (EU) 2023/2854" - "vehicle data" - "automotive" - "aftermarket" - "Chapter II" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # Data Act Vehicle Data Guidance Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries. *Artifact Guide* *EU* *Data Act* ## EU Data Act Vehicle Data Guidance Use the Commission's vehicle-data guidance to assess connected vehicles, vehicle-related services, user and third-party access, aftermarket use cases, and the safeguards that shape access under Data Act Chapter II. The guide separates binding Data Act duties from non-binding Commission guidance and keeps GDPR, trade secret, safety, cybersecurity, and sector-law questions visible. This page helps automotive teams turn the Commission vehicle-data guidance into a working assessment for connected vehicle data requests. It focuses on whether the vehicle is a connected product, whether the service is a vehicle-related service, what data is raw or pre-processed, which access route can deliver the same quality available to the data holder, and which safeguards must be documented before sharing or refusing access. ## Data Act Start with the automotive scope of the Commission guidance The Commission guidance is sector-specific. It addresses how Chapter II of the Data Act applies to vehicle data for automotive stakeholders such as OEMs, suppliers, aftermarket service providers, and insurance providers. It does not extend or modify the Data Act, and it should not be extrapolated automatically to other industries or public-sector access scenarios. A useful vehicle-data review should therefore start with a narrow scope statement: the vehicle, the user, the data holder, the requested data, the requesting third party, the intended use, and the technical route by which the data is or could be made available. - Confirm that the vehicle is a connected product that obtains, generates, or collects data about its use or environment and can communicate product data. - Record whether the request concerns product data generated by the vehicle, vehicle-related service data, or both. - Identify whether the request comes from the user directly or from a third party chosen by the user. - Keep sector-specific regimes, such as type-approval access to OBD or emissions data, separate from the Data Act analysis. Sources for this answer: - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Supports the automotive-only scope, the connected-vehicle focus, and the statement that the guidance does not modify Data Act rights or obligations. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Provides the binding Chapter II framework for user and third-party access to connected product and related service data. ## Data Act Classify the vehicle-related service before classifying the data Not every automotive service around a connected vehicle is a vehicle-related service under the Data Act. The Commission guidance treats a vehicle-related service as a digital service connected with the vehicle that involves bidirectional data exchange and affects the vehicle's operation or behaviour. This distinction matters for repair, maintenance, insurance, and mobility services. Regular offline repair or maintenance is generally not a vehicle-related service, while remote vehicle-control services, cloud preferences applied to the vehicle, dynamic route optimisation, and non-regular maintenance services that exchange data with the vehicle and adapt its functionality may be vehicle-related services. - For repair and maintenance, document whether the service is manual and offline or whether it exchanges data or commands with the vehicle. - For insurance, distinguish data analysis that creates a driver profile from a service that affects vehicle operation. - For mobility and route services, check whether vehicle data such as battery level, fuel level, tyre pressure, or location is used to affect in-vehicle behaviour or dashboard output. - For supplier services, show whether the supplier acts as a service provider, data holder, data recipient, processor, or technical operator for another party. Sources for this answer: - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Supports the distinction between vehicle-related services and aftermarket, insurance, analytics, or repair services that do not affect vehicle operation. - [European Commission - Vehicle Data Guidance page](https://digital-strategy.ec.europa.eu/en/library/guidance-vehicle-data-accompanying-data-act?ref=sorena.io) - Identifies the Commission guidance as tailored advice for applying Data Act Chapter II in the automotive sector. ## Data Act Separate raw and pre-processed vehicle data from inferred or derived information The central data-scope question is whether the requested vehicle data is raw or pre-processed data, with the metadata needed to interpret and use it, or whether it is inferred or derived information that falls outside the Data Act access obligation unless otherwise agreed. For vehicles, raw data may include sensor signals, raw image or point-cloud data, radar signals before object detection, CAN bus messages, direct user commands, and component status. Pre-processed data may include measured speed, acceleration, battery level, odometer value, fault codes, tyre pressure, liquid levels, brake-pad wear where not predictive, and other data that still describes vehicle operation or status. - Treat basic formatting, calibration, normalisation, filtering, conversion, aggregation, correction, timestamping, and similar preparation as not automatically excluding a data point. - Treat proprietary insights such as driving scores, object classification, route-planning outputs, driver analysis, crash-severity analysis, or ADAS risk assessment as likely inferred or derived unless the underlying data itself is requested. - For predictions, record whether the output is a future-looking inferred insight or whether an alternative raw or pre-processed data point is readily available. - Keep metadata with the data package, including context needed to interpret time, vehicle state, collection source, and quality. Sources for this answer: - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Provides automotive examples of raw data, pre-processed data, inferred or derived data, and the treatment of predictions and sensor-fusion outputs. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Explains the general Chapter II boundary between raw or pre-processed data and inferred or derived data. ## Data Act Choose an access route that satisfies same-quality and easy-access duties The Data Act does not mandate a single automotive technical route. The Commission guidance says access may be direct where relevant and technically feasible, or indirect through a data holder, and may use remote backend access, onboard access, or a data intermediation service. The route still has to satisfy the Data Act conditions. For vehicle data, the practical control is quality parity. Data made available to the user or user-chosen third party should not be less accurate, complete, reliable, relevant, or up to date than the data available to the data holder through another route, unless a different arrangement is justified under the Data Act or other applicable law. - If data is sent to an OEM backend under an extended-vehicle model, assess it as readily available to the OEM. - If the OEM does not retrieve or store a data point, document whether it can lawfully obtain it without disproportionate effort going beyond a simple operation. - If OBD-II or another onboard route is used, do not design access so that the user must buy specialised tools or have advanced technical skills. - Compare the quality offered to independent repair shops or other independent service providers with the quality available to the data holder, subsidiaries, authorised partners, dealers, and repairers. Sources for this answer: - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Supports backend, onboard, OBD-II, same-quality, easy-access, and independent-repairer access points for vehicle data. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines readily available data and the Chapter II access architecture for connected products and related services. *Recommended next step* *Placement: after evidence section* ## Data Act Turn vehicle-data requests into an evidence file Use this guide to structure request intake, data classification, access-route selection, GDPR and trade-secret review, and delivery or refusal records for connected vehicle data. - [Open Research Copilot](/solutions/research-copilot.md): Answer Data Act scope and vehicle-data interpretation questions with cited outputs. - [Talk through implementation](/contact.md): Review your vehicle data map, request workflow, safeguards, and evidence model. ## Data Act Build safeguards around GDPR, trade secrets, safety, and sector law Vehicle data can be personal, commercially sensitive, safety-relevant, or tied to sector-specific automotive rules. The Data Act does not displace the GDPR, privacy law, trade secret protection, type-approval rules, or other sector law. Where personal data is involved, the GDPR boundary must be assessed before a user or third-party transfer is approved. The GDPR point is not a footnote. The Commission FAQ states that GDPR rules prevail in a conflict and that a user who is not the data subject, or a data holder making personal data available, needs a valid GDPR basis for the relevant processing. The Data Act does not itself create a legal basis to collect or generate personal data. - Identify whether the requested dataset includes personal data about the driver, passengers, previous users, fleet staff, or other data subjects. - For mixed datasets, assess anonymisation, data-subject separation, minimisation, pseudonymisation, encryption, and user-specific filtering before transfer. - For trade secrets, document the protected information, proposed technical and organisational measures, and any reason why a safeguard is insufficient. - For safety, cybersecurity, OBD, emissions, and roadworthiness data, check the Data Act position against applicable automotive sector rules instead of using the vehicle guidance as the only source. Sources for this answer: - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Supports the GDPR precedence point, the need for a GDPR basis for personal-data processing, and the trade-secret boundary under Chapter II. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - States that the Data Act is without prejudice to personal-data and privacy law and does not create a legal basis to collect or generate personal data. - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Clarifies that the vehicle guidance does not affect the application of type-approval, motor-vehicle, GDPR, or other relevant legislation. ## Data Act Keep an evidence file for each vehicle-data request A defensible vehicle-data decision should be traceable from the request to the data package, role map, access route, safeguards, delivery terms, and any refusal or exclusion. This is especially important where the same company may be an OEM in one flow, a supplier in another, a data recipient for a user-directed request, and a processor or platform operator in a separate service. The evidence file should be useful to legal, product, security, engineering, customer operations, and partner teams. It should also be readable by a regulator or dispute body without relying on internal shorthand. - Request record: vehicle identifier or model context, user, requester, recipient, requested data, purpose, and user instruction. - Role record: OEM, supplier, data holder, user, data recipient, service provider, processor or controller assumptions, and reviewer names. - Data record: raw, pre-processed, inferred or derived classification; metadata; backend, onboard, or edge location; readily available analysis; and quality comparison. - Safeguard record: GDPR basis or data-minimisation analysis, trade secret measures, safety and cybersecurity review, sector-law checks, compensation position where relevant, delivery proof, and refusal rationale. Sources for this answer: - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Supports the evidence fields tied to vehicle scope, data classification, access route, same-quality access, and automotive safeguards. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Supports documenting personal-data, trade-secret, third-party-use, and role-boundary decisions in Chapter II requests. ## Primary sources - [Commission guidance on vehicle data - Official Journal](https://eur-lex.europa.eu/eli/C/2025/5026/oj/eng?ref=sorena.io) - Primary automotive grounding for connected vehicles, vehicle-related services, raw and pre-processed data, inferred or derived data, backend and onboard access, same-quality duties, aftermarket examples, and sector-law limits. - [European Commission - Vehicle Data Guidance page](https://digital-strategy.ec.europa.eu/en/library/guidance-vehicle-data-accompanying-data-act?ref=sorena.io) - Commission landing page confirming that the guidance is tailored advice for implementing Chapter II of the Data Act in the automotive sector. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for Data Act Chapter II concepts, user and third-party access rights, readily available data, GDPR non-prejudice, and connected-product design duties. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Implementation grounding for GDPR precedence, raw versus inferred data, edge processing, third-party use limits, trade secrets, and role boundaries. ## Related Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md): FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms. - [Data Act Trade Secret Technical Protection Measures FAQ](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation. - [Data Act vs GDPR: connected-product data access](/artifacts/eu/data-act/data-act-vs-gdpr.md): Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts. - [EU Data Act and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation. - [EU Data Act Applicability Test](/artifacts/eu/data-act/applicability-test.md): Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act. - [EU Data Act Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain. - [EU Data Act Article 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence. - [EU Data Act Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires. - [EU Data Act B2B Data Sharing Compensation FAQ](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards. - [EU Data Act B2G Compensation and Costs FAQ](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep. - [EU Data Act B2G Exceptional Need FAQ](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence. - [EU Data Act Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners. - [EU Data Act Cloud Switching and Exit Plans](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence. - [EU Data Act Compliance Program](/artifacts/eu/data-act/compliance.md): Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership. - [EU Data Act Connected Product Scope and Data Types](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - [EU Data Act Data Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md): FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence. - [EU Data Act deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records. - [EU Data Act Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md): FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act. - [EU Data Act Enforcement And Competent Authorities FAQ](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md): FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible. - [EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. - [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md): FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence. - [EU Data Act Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md): FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md): FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries. - [EU Data Act Product Data vs Related Service Data FAQ](/artifacts/eu/data-act/faq/product-data-and-service-data.md): FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs. - [EU Data Act Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md): FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics. - [EU Data Act Related Services FAQ](/artifacts/eu/data-act/faq/related-services.md): FAQ explaining when software is a Data Act related service, how it links to connected products, which product and service data are in scope, and what exclusions apply. - [EU Data Act requirements](/artifacts/eu/data-act/requirements.md): Source-grounded EU Data Act requirements for connected-product data access, B2B sharing terms, B2G exceptional needs, cloud switching, smart contracts, interoperability, GDPR boundaries, and records. - [EU Data Act Smart Contracts for Data Sharing FAQ](/artifacts/eu/data-act/faq/smart-contracts-for-data-sharing.md): Answers on Article 36 Data Act smart-contract requirements for data sharing: scope, robustness, access control, termination, archiving, conformity assessment, contract terms, and standards status. - [EU Data Act Third-Party Data Sharing FAQ](/artifacts/eu/data-act/faq/third-party-data-sharing.md): FAQ on user-directed third-party data sharing under the EU Data Act, covering data holder duties, recipient limits, trade secrets, security, GDPR, and gatekeepers. - [EU Data Act Trade Secret Safeguards FAQ](/artifacts/eu/data-act/faq/trade-secrets-safeguards.md): FAQ on protecting trade secrets when handling EU Data Act user and third-party data access requests, including safeguards, withholding, suspension, refusal, notices, and records. - [EU Data Act Unfair Contractual Terms FAQ](/artifacts/eu/data-act/faq/unfair-contractual-terms.md): FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence. - [EU Data Act User Access and Portability Rights](/artifacts/eu/data-act/access-rights-and-portability.md): Practical guide to EU Data Act user access, connected-product data portability, third-party sharing, trade secret safeguards, and the GDPR boundary. - [EU Data Act Users, Data Holders, and Recipients FAQ](/artifacts/eu/data-act/faq/users-data-holders-and-recipients.md): FAQ explaining Data Act users, data holders, data recipients, connected products, related services, user access, third-party limits, and GDPR boundaries. - [EU Data Act Vehicle Data Guidance FAQ](/artifacts/eu/data-act/faq/vehicle-data-guidance.md): FAQ on EU Data Act vehicle data guidance for connected vehicles, aftermarket repair, mobility services, third-party access, trade secrets, security, and GDPR boundaries. - [EU Data Act vs Data Governance Act](/artifacts/eu/data-act/data-act-vs-data-governance-act.md): Compare the EU Data Act with the Data Governance Act: connected-product access, cloud switching, B2B/B2G duties, protected public-sector reuse, intermediaries, altruism, governance, and enforcement. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/vehicle-data-guidance