As well as the core business of eCommerce, security and consultancy, we also work as part of a small group of companies on product development. At the moment we’re collaborating on two pieces of development, one of this is a delivery tracking service for important documents.

One of the most important aspects of physical post is the recorded / signed-for use case, where the recipient has to sign for the delivery. This proves that the delivery was completed and shows the lifetime from the delivery tracking pespective.

When delivering important legal documents this can be absolutely essentual in order to comply with regulations. In business we tend to veer towards electronic communications and so have to find other ways to solve this problem.

Email – by virtue – generally means that you will know if you got the wrong address or domain fairly quickly: you’ll get a bounceback. However if the recipient domain has a catch-all rule which allows sending to any address, or if it’s configuration not to respond to messages to invalid mailboxes, you may never be aware that the email hasn’t arrived.

More and more organisations are applying this latter configuration to prevent malicious actors (including spammers) collating valid email addresses from your server without permission.

So how do we ensure that our message has been delivered and – more importantly – has been read?

Cue the LSP Tracking Pixel project which focuses on message and document responsiveness. It means the recipients can still take advantage of all the privacy tools they’d normally have available (like the ones that stop ads and trackers), whilst providing you with the appropriate proof-of-delivery.