What is Oculamor? A factual guide to the UK car tracker

Oculamor is a connected tracker fitted to a vehicle. It records that car’s journeys independently of the driver’s phone, so a family can look back at where the vehicle went and review the available speed and road-limit context. That is a narrower job than “tracking a person”. It is also more than a simple arrival message.

The useful question is not whether a tracker sounds reassuring. It is what information you need, who will see it, and what you will do when the record is incomplete or surprising.

What Oculamor records

The device can provide a journey route, recorded speed and available mapped speed-limit context. Depending on the journey and account features, you can inspect driving events and feedback, then export a trip report as a PDF or available event data as CSV. These exports are useful for discussing one journey with the driver or an instructor; they are not a complete record of every vehicle input, proof of an offence or proof of who was driving.

Oculamor’s journey records are retained for ordinary family and personal use for 90 days. Save a report if you need to revisit a journey later, and treat it as sensitive: routes can reveal homes, workplaces, appointments and parked locations. Other data, such as alerts, can have different retention rules. The privacy policy explains the wider handling of personal data.

The speed view needs the same caution as any connected tracking record. It is position-derived, and a mapped limit can be missing or wrong. A marker is not an ECU reading, legal finding or witness account. Check the road and time with the driver before treating a result as a reason for action.

Does it need the driver’s phone?

No. Because the tracker is in the car, its journey recording does not depend on the driver carrying a charged phone or leaving phone-location sharing switched on. The device still needs power and network/GPS conditions, and the person viewing the dashboard needs internet access. Phone independence therefore means independence from that phone—not uninterrupted service.

This distinction matters when a parent is trying to understand a car journey rather than follow a person. A phone service may be better for seeing where somebody is after they leave the car. Oculamor follows the equipped vehicle. If a friend, sibling or parent borrows it, the record follows the car and does not establish who drove.

Alerts: power cut is not the same as ordinary disconnection

The service supports configurable notifications and can create a tamper alert when the device reports a power-cut, tamper or removal alarm. That is not the same as proving that somebody deliberately removed it.

An ordinary loss of connection is handled differently. The service allows a ten-minute grace period before a configured disconnect rule can notify you. An alert is not a default consequence of every offline state: you need the relevant notification configured, with the right recipients and an available delivery channel. Treat “alert” as a possible notification, not a promise that every loss of connection will produce an instant message.

Parked, offline and stale states can exist. A car being stationary does not make its location private, and a stale record does not prove deliberate interference. If an alert matters, check the event and the dashboard state before deciding what happened.

Who can see what?

Parents and drivers can inspect the same vehicle journeys where their permissions allow it. That does not mean they have the same dashboard, device-management controls or access to every other account detail. Roles and notification recipients are separate questions. Agree them together rather than describing Oculamor as a single shared screen.

The driver should know that a vehicle record can show destinations and where the car is parked. A family agreement can set expectations about when a parent will look, how a borrowed-car trip is handled, and what happens when a record looks wrong. It cannot turn the tracker into a technically “driving-only” system or hide a parked destination.

Vehicle compatibility

Oculamor plugs into the 16-pin OBD-II diagnostic socket that has been standard on petrol cars sold in the UK since 2001 and diesel cars since 2004. If your car has that socket, usually under the dashboard on the driver's side, the device fits and records journeys. If you are not sure, or your car is fully electric, tell us the make, model and year and we will confirm before you pay.

What does it cost?

At the time of writing, the Standard offer is £30 for the device plus £7.99 per month per vehicle, or £81.50 for an annual subscription plus the device. One device with twelve monthly payments is £125.88 in the first year; the annual illustration is £111.50. These are published display prices, so confirm the current offer and total at checkout. Pro is not currently offered at checkout.

See the current cost page, view a sample journey on the homepage, or create an account only after deciding that vehicle-linked history—not just arrival sharing—is useful to your family.

Is Oculamor right for you?

It may suit a family that wants to review a particular car journey, including when the driver’s phone was flat or left at home, and to discuss speed in road context. A free location-sharing service may be enough for an agreed arrival notification or temporary progress share. Neither choice establishes who was driving, why an event happened or that someone is safe.

Oculamor is not an emergency service, crash-prevention system or insurance product. It does not promise continuous coverage, perfect accuracy or a safety outcome. Its value is a concrete vehicle record that can support a fair conversation—provided everyone understands the limits before the device is fitted.