How the service engine handles your information.

This policy explains how information is collected, stored, and used across the Bgabs service engine and the website that fronts it. It applies whenever a person interacts with the product, whether that is a brand-side administrator, a service-company dispatcher, a technician on the ground, or a customer whose product is under coverage.

When a warranty or AMC contract is imported into the engine, the following information is stored against a unit: customer name, contact channel, service address, product model, serial number, install date, and the terms of the applicable contract. Every service event added to the unit - proactive visit, complaint response, repeat-issue close-out - is also stored against that record.

This information is used only for tracking coverage, predicting service needs, scheduling visits, and closing out dispatched technicians. It is not used for marketing, and it is not sold or licensed to third parties.

Technicians have their skills, home base, working hours, and vehicle load stored so the engine can assign visits and balance routes. Where the technician app is granted background location, coarse position signals are stored only for as long as they are needed for active dispatch, and are then discarded.

Technicians see only their own assignments, their own route, and the unit details required to complete a visit. They do not see other technicians\' contract data or customer information outside the scope of their own dispatched visits.

Brand administrators and service-company dispatchers have account details, role assignments, and audit trails stored so the engine can enforce role-based access and record who did what. Every override, deferral, and manual assignment change is logged with actor, timestamp, and reason.

Customer records are retained for the life of the contract plus one year, then archived and anonymised. Product and contract data is retained for the life of the unit inside the engine, with export available on demand. Location signals are retained only for the active dispatch window. Audit trails are retained for the duration required by applicable law.

Access, correction, and deletion requests are handled through a documented workflow. A customer whose product is under coverage can request a copy of the data held about them and their unit, or ask for it to be corrected or deleted. Where deletion would break an active service contract, the record is anonymised at the end of the contract instead.

Bgabs uses a small set of sub-processors for infrastructure hosting, email delivery, and error monitoring. A current list of sub-processors is available on request, with the region each one operates in.

The public website uses a minimal set of first-party cookies to remember interface preferences. It does not run behavioural advertising trackers. Aggregate, anonymous traffic analytics are used to understand which pages are read and where the site loses visitors, and nothing more.

Privacy-related requests, including data-subject requests under GDPR-style regimes, can be raised via the contact page. Requests are acknowledged within two business days and completed within the statutory window that applies to the requester\'s jurisdiction.