The data extracted from the images (date of capture, time of capture, camera, species, and, if applicable, future location information) can only be viewed by the creator.

Only these pure text data points are stored in the database. Images or image files are never uploaded or stored. The analysis of the images takes place 100% locally on your respective device.

For technical reasons, the administrator has access to the data stored in the database.

The short answer is: No! Your private camera images are never uploaded to our servers.

To read the date and time directly from the stamps of your trail camera images (in case digital metadata is missing), Hegemonitor uses Artificial Intelligence (AI). This AI runs 100% locally in your own web browser (e.g., Chrome, Safari, or Firefox).

• Local Analysis: When you select images, they are only loaded into the RAM of your own device. Your device handles all the computing power.
• Full Privacy: Your images (and any persons or sensitive locations visible on them) never leave your device.
• What is stored: Only when you click "Save to Database" is a tiny data package sent to us, containing exclusively the text information read by you and the AI (species, camera name, date, time).

Under Demo in the navigation, you will find a live tester for your images. Simply upload an image there and our system will show you exactly if it could read the date and time!

As a rule, images in JPEG format (.jpg / .jpeg) can be uploaded for analysis on hegemonitor.de.

When saving to iPhones or sending via camera apps, digital metadata is often removed to protect privacy or save data volume.

Hegemonitor's Solution: In these cases, our integrated AI image recognition automatically reads the date and time directly from the optical stamp on the image. If an image is extremely illegible, you can easily correct or complete the data manually at any time after uploading.

Can I use a camera at a new location without overwriting the old evaluations?

Yes, that's possible! To ensure your statistics and evaluations remain clear, it is important to strictly separate the old and new locations within the application.

Here is the best way to proceed (our recommendation):

1. Mark the old location: Simply rename the camera at its previous location (you can do this in your profile, see Guide: Entering/Changing Camera). We recommend adding a minus sign or the suffix (-) before the name. For example, Camera 1 Haselberg becomes (-) Camera 1 Haselberg. This marks the dataset as "completed" while keeping all previous data under this name in your evaluation.
2. Create the camera at the new location: Set up the camera for its new location as a new device and assign the new name there (e.g., Camera 1 Schatzwiese). This way, you know it's the same camera (Camera 1), but it is active at a new location (Schatzwiese).

This message appears when you try to save an image that already exists in your database with an identical date and the exact same time.

Why does this happen? The system prevents the same event from being counted twice in your statistics, which would distort the evaluation (e.g., if an image is accidentally uploaded twice).

The Solution:

• Check if you have already saved the image.
• If it is a genuine double exposure, simply remove the affected image using the red "X" from the selection before restarting the saving process.