Smart-device data access: when factories hold it
Establish who is responsible for the customer's information, arrange a targeted factory export, explain the records and review shared-device data before disclosure. If you are the controller, using the factory as a processor does not remove your responsibility. Factory coordination can be supported by Cambridge China Bridge.
Establish responsibility before requesting an export
Ask who decides how customer information is used, who operates the cloud and who can retrieve records. Do not assume that controlling the platform makes the factory your processor. If you are the controller, you are responsible for answering access requests; your processor agreement must enable retrieval and assistance.
Name a response owner in your business and a technical contact at the factory. Keep this workflow alongside the product paperwork covered in our connected-product security guide, without treating that paperwork as evidence that customer records can be exported.
Give the factory a search brief
Record the request and map the relevant account, device identifiers and any account changes. Ask the factory to search the applicable account records, device events, recordings, support records and user profiles. Include your own customer-service records. The ICO requires a reasonable and proportionate search, rather than a search confined to what the app displays.
Ask the factory to return an inventory of systems searched, the records found and any retrieval gaps. For archives or backups, ask what retrieval is possible rather than accepting a blanket technical refusal. ICO guidance says there is no technology exemption for archived or backed-up information. Keep personal-data sharing with suppliers in view when sending the search brief.
Turn the export into an intelligible copy
For an electronic request, provide a commonly used electronic format, subject to a reasonable request for another format. Ask the factory for readable files and a field dictionary explaining event codes, units, timestamps and account references. Test whether the customer can open the files and understand what each record means.
Include the required supplementary information about processing alongside the copy. Ask your privacy lead to check that it is complete and specific to this customer. An unexplained factory export is a poor response: add context where needed so the information is understandable. A downloadable account export can help, but plan an alternative for customers unable or unwilling to use the portal.
Review shared-device records before disclosure
A shared camera, lock or household hub can record information about the requester and other people together. ICO guidance says to consider whether you can respond without revealing information that identifies someone else. Work on a disclosure copy and remove identifying details where appropriate, while preserving the requester's information and useful context.
Check names, account identifiers, voices, faces and activity patterns, including details that remain identifiable after names are removed. If separating the information is not possible, consider seeking the other person's consent or whether disclosure without consent would be reasonable in the circumstances. Refer difficult cases to your privacy lead and record the reasoning.
Working out your own order? Send us the product on WhatsApp and we reply the same working day: WhatsApp us
Deliver securely and test the workflow before ordering
Check the recipient and delivery address before sending. Use a delivery method suited to the sensitivity of the records, such as an encrypted copy with its access code sent separately. Keep a record of the search, disclosure review, explanatory material and delivery. If the factory has not supplied everything requested, log the gap and escalate it rather than describing the response as complete.
Before placing an order, rehearse retrieval using test accounts and shared-device events. Agree the export format, factory contact, escalation route and continuing access if the supplier relationship ends. Include export testing in firmware and software approval. Cambridge China Bridge's own staff in China can help coordinate factory questions and demonstrations; your business should retain control of disclosure decisions.
Frequently asked questions
Can we just tell the customer to contact the factory?
If you are the controller and the factory is your processor, you remain responsible. Arrange retrieval through the factory and manage the response rather than simply redirecting the customer.
Is a raw cloud export enough for a data access request?
Only if the copy is accessible and understandable, with the required supplementary information. Explain codes and context where needed, and check that the customer can open the files.
Can a customer receive other household users' data?
Review mixed records carefully. Remove identifying information where appropriate; if it cannot be separated, consider consent or whether disclosure without consent would be reasonable.
What should we ask the factory before buying?
Ask for a test export, field explanations, a named technical contact and an escalation route. Rehearse shared-device redaction and agree continuing retrieval access if the supplier relationship ends.