Saatja: "William Osei-Appiah" <
[email protected]>
Saaja: "info" <
[email protected]>
Teema: Request for Re-activation of Data Access Agreement No. 3.2-5/25/193-1 – Mechanico Or New contract
Kuupäev: 2026-01-28 14:11
Dear Estonia Transport Department
I am writing to formally request the reactivation of our access to the
Traffic Register (Liiklusregister) via the AVP service, as established under
the previous agreement: LIIKLUSREGISTRI ANDMETELE JUURDEPÄÄSU LEPING nr
3.2-5/25/193-1.
During the recent period, Mechanico has undergone a significant
infrastructure migration and security audit to ensure our platform meets the
highest standards of data integrity and scalability. Now that this
modernization is complete, we are ready to resume our role as a key digital
service provider in the Estonian automotive ecosystem.
Our platform, Mechanico, serves a dual purpose that aligns with the
Transport Administration's goals:
1.Public
Safety: Utilizing real-time roadworthiness data (Category 3) to alert
motorists of upcoming inspections and technical faults.
2.Economic
Transparency: Providing service providers with accurate technical data
(Category 2) to ensure fair pricing and part accuracy for Estonian citizens.
We recognize that access to verified vehicle information is the cornerstone
of consumer trust in our digital services. We are fully committed to
fulfilling all technical and reporting obligations as outlined in the
attached digitally signed request.
We look forward to your guidance on the next steps for technical
re-integration. We are available for a digital meeting via online video or
at your offices in Tallinn should you require further clarification. Demo
Video can be found here
<https://1drv.ms/v/c/e7c1025541c5bb4e/Eb5hrDbFQLdCqRik1Zy89kcBjNBRsR0rEfatLZ7cXvPo2w?e=0KdMre>
Regards
William O.A, Founder
Auto Mechanico Pty / OU
m:+372 53753269 / + 44 7960 164892 | e:
[email protected]
<mailto:
[email protected]> | w: www.mechanico.io
<http://www.mechanico.io>
Transparent, Convenient and Eco-friendly
William Osei-Appiah
Auto Mechanico OU
Staadioni tn 4-28
10132
Tallinn – Estonia
Estonia Transport Administration
Valge 4
11413
Tallinn – Estonia
Subject: Data Exchange Platform (hereinafter AVP) service for Auto Mechanico OU
Dear Sir/Madam
I am writing to you on behalf of Auto Mechanico OU, a pioneering Automotive Tech startup focused on
enhancing mobility and providing after-sales service support through a Saas platform. As an innovative
company in the automotive sector, we are dedicated to offering comprehensive post-purchase services
including toolings, integrations insight for the maintenance, repairs and technical assistance tailores for
each vehicle needs.
To achieve our objective and deliver high-quality service, we require access to data from the traffic
register. We believe that our usgae of this data aligns with legitimate interests under Section 184 of the
traffic Act, specifically for improving vehicle safety, ensuring regulatory compliance and enhancing
motorist satisfaction.
Data Requested:
• Basic Data of Vehicle Information*
• Technical Data of the Vehicle*
• Technical Inspection Data*
• Access-Restricted Data*
Need for Data:
Our operations hinge on accurate and up-to-date vehicle information to:
• Identify and verify vehicle for providing bespoke after-sale services support
• Access technical specification necessary for maintenance and repair tasks
• Track, analyse and potentially augment vehicle inspection histories to offer preventative
maintenance reminders.
• Provide motorist details to maintain and update service records.
Compliance and legitimate Interest:
We assure you that all received data will be used solely for the purposes stated, in full compliance with
the relevant legislation, and will be safeguarded appropriately. Attached to this letter is our detailed
description of the legitimate interest.
Application Submission:
We hereby submit a digital application for AVP service, specifying our data needs and choosing Package
2 to accommodate our anticipated data request volumes.
We are committed to paying the necessary state fees and adhering to the regulations set forth by the
Transport Board. Please find attached our company registry code, authorized personnel details, and the
confirmation to use the data as per the formulated goals.
IP Address: Auto Mechanico OU IP address: 35.178.229.29
We look forward to your positive decision and are ready to provide any additional information or
documentation you may require.
Yours faithfully,
William Osei-Appiah
Founder/Director
[email protected]
+37253753269 / +44 7960 164892
Attachments:
1. Detailed Legitimate Interest Description
2. Use Cases and Scenarios
Overview of Details legitimate interest:
This page refers to the type of data being requested, the use cases as well as scenarios, the control
mechanism we have in place to secure store, transmit such data and which stakeholder within the
platform this is made visible to.
1. Basic Data of the Vehicle
Use Cases: This data is used to confirm vehicle identity and provide personalized service offers.
Scenarios: Before starting service, a motorist makes a request and confirm vehicle information,
service provider verifies the vehicle’s brand, model, and trim before issuing a quotation.
Personalized offers such as a discount on a particular model’s service are created.
Control Mechanisms: Data encryption, secure access protocols, role-based access controls
(RBAC), and logged access, alerts and audit trails are implemented to protect data.
Visibility: Motorists and service providers have visibility to confirm service eligibility and
personalization.
2. Technical Data of the Vehicle
Use Cases: This data helps in maintenance and repair planning.
Scenarios: Ensuring the correct parts are ordered for a repair, providing accurate repair
specifications.
Control Mechanisms: Encrypted transmission channels (e.g., TLS), authentication and
authorization protocols protect this data.
Visibility: Service providers need access to provide accurate services.
3. Technical Inspection Data
Use Cases: This dataset is used for compliance and safety checks.
Scenarios: Service providers check last inspection reports to per request from motorist to
address any issues.
Control Mechanisms: Access is restricted based on job roles.
Visibility: Motorists and service providers need this data for compliance inspections.
4. Selectable Access-Restricted Data
Use Cases: Vital for vehicle identity verification.
Examples: Verifying VIN and registration numbers for accurate vehicle description, record
keeping, performing legitimate service applications.
Control Mechanisms: authentication, data masking for non-essential visibility, compliance with
data protection regulations.
Visibility: Service providers access this data to verify the vehicle’s identity and the legitimate
owner.
Outputs Use Cases Scenarios Control Visibility
Mechanism
Identification: Confirming Data encryption and
vehicle identity before secure access
Identification & service. protocols.
Verification, Verification: Checking the Motorists &
Basic Data of Role-based access
Personalised vehicles brand, model and Service
Vehicle controls (RBAC)
Service trim Providers
Offerings Service Offers: Offering of
Logged access, alerts
services that are tailored by
and audit trails
the request from motorist
Part Matching: Ensuring Encrypted
correct parts and transmission
Technical Maintenance &
accessories channels Service
Data of the Repairs
Repair Specifications: Authentication and Providers
Vehicle Planning
Providing correct repair authorisation
specifications. protocols
Inspection Report:
Technical
Accessing latest inspection Restricted access
Inspection Safety Checks Motorist
reports to address based on job request
Data
Any identified issues
Vehicle Identification:
Selectable Verifying VIN and
Authentication,
Access- Vehicle Identity registration number for Service
Data masking for non
Restricted verification accurate description of Providers
essential visibility.
Data vehicle, records keeping
and service application
Details of Output and their sub data
1. Basic Data of Vehicle
a. Brand
b. Commercial name
c. Modification
d. Type approval number
e. Type approval extension
f. Type
g. Variant
h. Version
i. Category
j. Color
k. Multicolor
l. First registration date
m. Date of registration in Estonia
n. Country of origin
o. Class
p. Body name
q. Body type
r. Base factory
s. Time of next inspection
2. Technical Data of the Vehicle
a. Length
b. Width
c. Height
d. Doors
e. Seats
f. Seats next to the driver
g. Standing positions
h. Tires on the axles item
i. Engine model
j. Engine type
k. Fuel type
l. Gearbox type
m. Notes
3. Technical Inspection
a. Date and time of the last inspection
b. Type of inspection
c. Decision
d. Malfunctions (detailed)
e. Third-party odometer reading (Inspection points, regular and repair shops)
4. Selectable Access-Restricted Data
a. Registration number
b. VIN code
References:
• Output refers to the categories of available data
• Use Cases refers to what the data will be used for
• Scenarios refers to a typical example of a use case
• Control Mechanism refers to how the data exchanges will be securely access, cached and
transmitted* Not all inform will be made available for viewing as some are meant for logical
processes.
• Visibility refers to the stakeholders that may view part of the data request. Motorist and
Automotive service providers such Auto repair shops, Tyre & Wheel shops, Glass fitment shops,
Parts & Accessory Shops, Paint & Body repair shops.