Trace which services receive parking images, plate text and support copies, including their access locations and permitted uses.
The supplier register should cover every service handling plate text, images, backups or support records. Identify each recipient's role, access location and disposal responsibility, then compare that register with the actual deployment diagram.
A diagram showing only the parking application can miss diagnostics, messaging and troubleshooting copies. The recognition service is one part of the supplier chain, rather than the only part worth examining.
A standalone recogniser could keep processing close to the camera. Connected operations add hosting, communications and support providers, so the organisations handling deployment information can extend beyond the company named on the proposal.
Those providers do not all need the same material. A messaging service may only need a reference, while a recognition service may need an image. The register should explain the difference rather than treating all data as one package.
Supplier disclosure matters whenever another party handles deployment information, including occasional troubleshooting. Local recognition, limited diagnostic samples or reference-only messages may reduce what leaves the operational system without assuming outside support is unnecessary.
Assess those alternatives against the task and permitted purposes. An in-house recognition model does not establish that no third party can access images, plate records or copies attached to support requests.
An image attached to a support ticket creates a copy outside the normal event queue. Its retention and disposal need attention even if the operational record expires. Separate raw video, event images, plate text, device telemetry and account details in the register.
Document retention, countries, access and change-notification arrangements for each recipient. Recognition evaluation and model training also need explicit review: establish whether customer records are used and under which terms, then resolve any recipient unexplained by the deployment diagram.
RackLink processes supported RTSP locally before structured events join CORE. Aero Ranger's policy also identifies service-provider categories and overseas access. The actual recipients and countries therefore need confirmation beyond the local recognition boundary.
Aero Ranger's agreement permits licensed model work and other improvement uses, with de-identification where practicable. Customer ownership does not remove that licence, and local recognition does not exclude outside access to the resulting records.
Aero Ranger: RackLink; Aero Ranger: privacy policy; Aero Ranger: master services agreement; Aero Ranger: data processing and security schedule
Sources were reviewed on the publication date. Check the linked material for current details.
