The autopi device is a maker platform, that aims to bridge the gap between IoT and cars, and our aim is to allow people to interface with their car in a simple and straight-forward way. This is the core idea of the platform, for private consumers and businesses.
Unfortunately there are no seperate pins for writing and reading, that’s not how this works.
There are pins for the different protocols, and how it works is that the autopi device (or any OBD device), requests a specific piece of information via a (somewhat) standardized list of PIDs, by sending a request, and then listens for the response, so if you somehow blocked the ability to write to the car, you would not be able to read anything either.
We have made efforts to make sure that the device is locked down, firewalls are enabled and configured, ports are closed etc. And the way we communicate with the device, is done through an encrypted connection via a open source enterprise grade system called SaltStack, used by many huge companies to secure and control their servers.
Not to mention that we continually update the devices to make sure they are always up to date, this is one of the most important features, security-wise, as it will continually apply updates, security fixes and other critical issues.
The closest thing to what you request regarding connector heads with different pins, is that you could use this cable or a similar one, to power your device in your car, but as i mentioned, that will severely reduce the features that the device provides, including but not limited to automatic trip creation and position logging etc.
I hope this answers your questions.