Version images received by dealers often have gaps. An image forwarded in a message may have a version number that is unreadable when enlarged. A clean full-page capture may contain no vehicle identifier. Before release, complete the image record: which vehicle, which page shows the version number, who captured it and when, and who forwarded it. If any item is missing, mark it pending verification, not confirmed.
A release passes through several hands, including reconditioning, export documentation, and delivery. Each person sees only the image passed on by the previous person. Adding identifying details gives later staff something to check against.
The sequence below is a recordkeeping process for imported vehicle business in Peru, connecting the image, vehicle, and responsibility in a traceable record. Dealership actions are not equivalent to local legal requirements. Official conclusions are subject to Peru's current provisions and procedural instructions.
Three identifiers for the version image
Before capturing the screen, establish three things: vehicle identity, meaning whether the image or an adjacent screen shows a VIN or configuration sheet number; version identification, meaning whether the version or firmware number can be compared character by character with the configuration sheet; and timing and source, including the person who captured it, date, transmission route, and whether it was cropped. The screen before the version number is often the vehicle information page. Capture and archive that page too.
| Check Field | Screen or Record to Review | Passing Condition | Entry if It Fails |
|---|---|---|---|
| Vehicle identity | Vehicle information or system information page | Matches the order and responsible entity | Mark pending verification; exclude from sign-off |
| Version identification | Version line on the About or system information page | Matches the configuration sheet version | Capture the corresponding page again, then recheck |
| Capture time and source | Original file properties and transmission records | Capture person and date are available | Do not use images of unknown origin |
| Personal data in the image | Account, contacts, navigation, and similar pages | Necessary for the determination or already hidden | Apply the next section's rules before retention |
Tie all four rows to this vehicle and this form. Images that do not match or have unclear sources are leads only, not conclusions.
Limit retention when images show people
Peru's basic law is the Personal Data Protection Law, Ley 29733, enacted in 2011 to implement the personal data protection right established in Article 2, paragraph 6 of the Constitution. Under the official text, personal data is information that identifies a natural person or can identify one using reasonably available means. Account names, phone numbers, home addresses, and navigation history fall within that definition. The purpose and proportionality principles require processing to stay within the explicit purpose established at collection and to be appropriate and not excessive. For images, retain only fields needed to determine the version. Hide accounts and addresses where possible, and sign out before capturing the screen if possible.
Document the processing basis and roles when deciding what to retain. Data subjects can use the public registry search page to check whether a processor is registered, the processing purpose, and the identities and locations of the holder and processor. Infotainment account systems are often controlled by the manufacturer or service provider, while the dealership can only operate the interface. If it cannot identify who processes the data, keep the item pending verification. Refer to the official Ley 29733 text and the official DS 016-2024-JUS regulation page. This regulation was published on November 30, 2024.
Mark which record replaces the old version
Keep the original image's file properties as they were when captured; do not overwrite it. Give supplemental capture notes, review comments, and sign-off their own lines, each identifying the relevant image. When an OTA update or dealership reflash changes the version, register the new image with the old entry it replaces, the operator, and the date. Keep the old image's original capture date and supporting basis. The new conclusion describes only the version observed at the new time; it does not automatically overturn earlier sign-offs. If personal data is discovered in a retained image without a valid reason for keeping it, delete it and separately record the deleted item and basis. Ley 29733's quality principle likewise requires data to be retained only as long as needed to fulfill the purpose.
Who signs off on rights requests and disputes
The sign-off covers only the vehicle and time shown in the image. Identify the applicable vehicle and version status without expanding the conclusion to an entire batch or a long-term promise. Use official channels for data matters. Under ANPD's current instructions, data subjects seeking access, rectification, cancellation, or opposition, known as ARCO, must first apply to the organization retaining the data. The response waiting period is 20 business days for access and 10 business days for rectification, cancellation, and opposition. If no response arrives by the deadline or the request is denied, appeal to ANPD. The rights procedure page lists required attachments, including a copy of the original request, the denial, and supporting evidence. If the dispute concerns a delivered vehicle that differs from the displayed version, return to the file to check the version number, capture time, and sign-off scope. Organize the order, contract, and images as one set and use the local sales dispute process. Archive data rights claims separately from sales disputes.
FAQ
Can the vehicle be released if the other party sends only a version image with no vehicle information?
It cannot be treated as confirmed. Mark it pending verification under the vehicle identity row of the decision table above and return it for a vehicle information page or order number. An image without a capture person and date is only a lead. Move to sign-off once all three elements are complete.
Can an image be retained if it shows a previous owner's or test driver's account and home address?
First narrow the scope. Account names and addresses are personal data that can identify a natural person. If unnecessary for determining the version, hide them or sign out and capture the screen again. If retaining the full image is necessary, document the basis and processor. Customers requesting deletion should first contact the retaining organization, then use ANPD's rights procedure if no response is received or the request is denied.
Is an old screenshot still valid after an OTA update changes the version?
Document the replacement relationship. Identify the earlier entry replaced by the new image, the operator, and date. Keep the old image's original capture date and basis. The new conclusion describes only the version at the new time and does not automatically overturn earlier sign-offs. Both records remain available for review.
What if the customer says the version differs?
Return to the file and check three things first: version number, capture time, and sign-off scope. If the record was wrong, correct it using the new-image replacement rules and preserve the basis. If delivery differs from what was shown, organize the order, contract, and images together and follow the local sales dispute process. Handle data retention issues separately through ANPD.
Regarding software version images and data retention boundaries in a Peruvian order, send the vehicle or order identifier, existing screenshots, and open questions to Starvia or WhatsApp. We will prepare a list of missing items and a review sequence based on this vehicle's delivery requirements.
Sources are public Peruvian government pages: the official Ley 29733 text on the congressional legal page and its provisions PDF, the official current DS 016-2024-JUS regulation page, the public personal data bank registry search page, and ANPD's rights procedure page. This article provides order review and recordkeeping methods for imported vehicle business in Peru. It does not constitute local legal, tax, customs clearance, or technical conclusions, nor does it guarantee market access, delivery times, warranty coverage, selling prices, or business results. Current official page content governs provisions and procedures. Sources checked on 2026-09-07.