Who we are
Our website address is: https://detectingfinds.co.uk.
What personal data we collect and why we collect it
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Please see our Cookies Policy
Linkedin Share official button
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Who we share your data with
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
We use Webpushr to handle our notifications. If you have opted in to receive notifications, Webpushr will store the following information on its servers for each Subscriber:
They do not store any data related to your site visitors that have not opted to receive push notifications. Webpushr is not able to determine end-user identity with the current data it stores.
|This is the date when the subscribers opts to receive push notifications from your site.|
|The endpoint takes the form of a custom URL and associated encrypted keys pointing to a push server.|
|Subscriber’s local timezone.|
|Mobile or Desktop.|
|Mac OS, Windows, Android, etc.|
|Chrome, Firefox, Opera, Edge, etc.|
|Subscriber’s IP Address.|
|Geographic Location: City|
|Geographic Location: State|
|Geographic Location: Country|
|Date corresponding to the last session|
Webpushr – cookies
|We only store this cookie if the publisher (you) set the prompt (Custom Prompt) to show after x page visits.This cookie tracks the number of page visits on publisher’s site. If the publisher (you) decide to select native opt-in prompt then this cookie is not set.|
|This is set for non-https sites ONLY to check if the user is subscribed or not|
|This cookie is stored if the user declines to receive push notifications and dismiss the custom prompt. This helps us remember that decision.|
|This cookie stores a unique URL associated with the user’s push subscription. It is only stored if the user accepts to receive push notifications.|
|This cookie stores timestamp associated with the user’s last visit on the site. It is only stored if the user accepts to receive push notifications. This helps us successfully manage and send push notifications.|
Webpushr – Data Retention
Webpushr stores subscriber data indefinitely unless the subscriber unsubscribes from receiving push notifications. Webpushr automatically deletes all subscriber data from it’s servers when a user unsubscribes