A vehicle arriving at a Lima dealership from a Chinese port may have an infotainment interface in Chinese, or perhaps only English. Switching it to Spanish completes just the first task. For the form to make sense to customers and everyone who handles the vehicle afterward, it must answer three questions: Do the language pack and firmware version match this vehicle's VIN? Have previous accounts and navigation history been completely cleared? Who handles the data removed? If any answer is missing, mark it pending verification and sign off only after the gaps are filled.
A walkthrough of dealership operations explains why a record matters. Reconditioning, quality inspection, and delivery each involve a different person. Rental and used vehicles also have another user afterward. Each person cannot see what the previous person did; the record gives them something to check before taking the next step.
This article covers recordkeeping only and does not present internal dealership procedures as local mandatory requirements. Conclusions involving the authority of ANPD or Indecopi are subject to official pages and the views of the responsible local entity.
Three columns to sort the infotainment check
Going straight to the language settings makes it easy to miss other tasks. First, separate the work into three columns. Put the displayed result in the interface language column, the language pack's origin in the version and source column, and cleanup actions in the accounts and data column. Support every column with screenshots, document numbers, or dates, and identify the operator in the record. Keep the three columns separate because a language switch can be completed in one session, while account data may have to wait for customer information to be confirmed. Their completion times may differ.
| Check Column | Evidence to Keep | Passing Criteria | Action if It Fails |
|---|---|---|---|
| Interface language | Settings page screenshot and date | Spanish interface remains after a restart | Mark pending recheck, not confirmed |
| Version and source | Factory document, OTA receipt, or dealership reference number | Version number matches the configuration sheet and VIN | Do not install or accept a version of unknown origin |
| Accounts and pairing | Comparison of accounts and devices before and after cleanup | No previous accounts or devices remain | Keep a pending cleanup item and specify what is missing |
| Data destination | Handling entity and basis | The handler and basis can be identified | Mark pending verification if the handler cannot be identified |
Tie every row to this vehicle. Close failed rows individually once supporting documents arrive.
Is the data column compliant?
Accounts, contacts, navigation history, and driving preferences are all personal data. Peru's basic law is Ley 29733, enacted in 2011, and ANPD is responsible for rulemaking, supervision, and penalties. Use current guidance for the data column, keeping two points in mind.
The first is registration. The current regulation, Decreto Supremo 016-2024-JUS, took effect on March 31, 2025. Personal data bank holders must register through a free automatic approval procedure, subject to subsequent supervision, with the entire process handled in SIPDP. If owner profiles have been created for connected services, use the registration instructions on the data bank registration page to assess whether the obligation applies and who acts as the processor, then record the determination.
The other point is data subject rights, known in Peru as ARCO: access, rectification, cancellation, and opposition. The entry point is ANPD's ARCO rights page. When customers ask whether they can access or delete their data, follow this process and keep a record.
Account cleanup raises a question about the responsible entity. Vehicle account systems are often controlled by the manufacturer or its operator. The dealership may have permission to perform actions without authorization to decide how data is handled. The distinction between the operator performing the action and the data processor directly affects the registration assessment. The official report personal data misuse channel addresses such issues. If the roles are unclear, mark the item pending verification. Refer to the Ley 29733 text page for the legal provisions.
Use the official channel for disputes
Discrepancies between interface language, manuals, advertising, and the actual vehicle concern consumer information and go through Indecopi. According to the Indecopi complaint instructions, first file with the seller through the Libro de Reclamaciones. If unsatisfied, take the matter to Indecopi through Reclama Virtual online or the toll-free number 0-800-44040. Data requests such as account deletion follow ANPD's ARCO procedure. Keep the two sets of materials separate.
The complaint page requires supporting documents such as invoices and contracts. A delivery form is one such document, so recording the conclusion on it prepares the evidence in advance.
Consolidate the Record into One Infotainment Handover Form
At the top, enter the VIN, configuration sheet number, and dealership arrival date. Organize the main section into the three columns, identifying the evidence location and operator. Leave two lines at the bottom: one for the conclusion and one for unresolved items. Use only two conclusion statuses: confirmed after review or pending verification.
Follow a clear update rule. After an OTA update or dealership reflash, change only the affected columns and specify which earlier entry is replaced. Keep the original date on the old form. If the update changes the interface language or account status, recheck each of those two columns once.
The completed process ties the vehicle, version, and data to one form that can be retrieved at any time. If something cannot be verified, pending verification is more defensible under questioning than completed.
FAQ
Does switching the interface to Spanish complete the language pack check?
It completes only the first column. You must also check whether the version's source matches this vehicle's VIN, whether accounts and paired devices have been cleared, and whether the data handler can be identified. If evidence for any column is missing, mark it pending verification under the table's rules.
What procedure applies to deleting account data?
This is a data request and belongs on the ANPD side. Peru groups access, rectification, cancellation, and opposition under ARCO, with an entry point on the official ARCO page. After signing out and clearing the data, enter the time, operator, and screenshots on the handover form.
How should the dealership close out a language pack check if the version's source cannot be traced?
Follow the table's action column. Do not install or accept a version of unknown origin. Specify whether the missing evidence is a factory document, OTA receipt, or dealership record. Keep this vehicle pending verification and close the item when the missing documents arrive.
Is the old record still useful after an OTA update?
Yes. Keep the original basis and review date on the old form. For the new update, replace only the version and source column and add a new screenshot and date. If the update changes the interface language or account status, recheck each of those two columns once before signing off.
Regarding the language pack configuration and the account data behind it for a Peruvian order, submit the vehicle or order identifier, existing materials, and open questions through the Starvia contact page or WhatsApp.
Sources are public Peruvian government pages, including the official texts of Ley 29733 and Decreto Supremo 016-2024-JUS, ANPD's data bank registration page and ARCO page, ANPD's reporting channel, and Indecopi's complaint instructions. Sources checked on 2026-09-07; current page content governs. This article provides a recordkeeping method and does not constitute legal, tax, customs clearance, or technical conclusions, nor does it guarantee market access, delivery times, warranty coverage, selling prices, or business results.