embidetect – privacy policy

Last updated: 3 November 2026

embidetect is a service for capturing images, labelling them, training object-detection models and running those models on embidetect devices. It is offered as an Android app, a desktop app and a web app, all talking to the hosted service at embidetect.embinova.at. This page explains what personal data the service processes, why, and what you can do about it. The product page at the same address, and the enquiries it invites, have their own section.

Who is responsible

embinova GmbH
Raggal 77, 6741 Raggal, Austria
office@embinova.at

What we process, and why

Account: email address and password

Needed to create and sign in to your account. The password is stored only as a salted hash. Your email is also used to send you the one-time codes that confirm your address and your sign-ins, and password-reset codes when you ask for one. Legal basis: performance of the contract.

Postal address (optional)

Only if you enter one in the account dialog. Stored encrypted; you can edit or remove it there at any time. Legal basis: your consent.

Images, annotations and trained models

The images you upload to a project, the labels and outlines you draw on them, and the models trained from them are stored so you and the people you share a project with can work with them. Images may show whatever your camera pointed at; do not upload images of people unless you are entitled to. The apps send an imported image without its file name, only its type (such as .jpg), so a name that tells who or where is not stored. Since 21 October 2026 the server also removes what an image file carries besides its picture: EXIF, XMP and IPTC data such as the GPS position, the capture time, the camera's make, model and serial number, the author and comments, before it stores the image, so none of it is kept, shown to project members or exported. It keeps only the picture's orientation and what is needed to show it correctly (its colour profile). Legal basis: performance of the contract.

Camera

The Android and desktop apps ask for camera access to capture frames and to run detection live. Frames stay on your device unless you choose to upload them to a project or to send them to one of your own embidetect devices on your local network. Frames in which a running model was unsure — which signs of doubt count is set by the project's owner in the project's review settings — can be uploaded to a review folder of the model's project, at most as many per run as the project's review setting allows — 50 unless the project's owner sets another limit, never more than 200 — which the server enforces: for one run when you switch it on there, or for every run of the project's models when the project's owner turns on the project's review setting. Both are off until someone switches them on, every member of the project sees that a run is collecting and can pause it, and turning the setting on or off is recorded in the security log. A collected frame is marked as such and is kept only until it is reviewed: a frame nobody has annotated or finished labeling is deleted by the server once the project's review retention has passed, 30 days after its upload unless the project's owner sets a different period (between 1 and 365 days). A reviewed frame is a project image like any other and is deleted with the project.

Technical data

The server keeps the usual connection logs (IP address, time, requested path) for operation and abuse prevention, and counts sign-in attempts per address and per account to limit password guessing. The apps contain no advertising and no analytics or tracking libraries.

Security log

The service records security-relevant events. Every entry holds the time, the account that acted (its internal id and its email address), the IP address and the browser or app identification the request came from, whether it succeeded, and the internal id of what it acted on — a project, an image, a training job, a model, a rule or another account. Where an entry names a second person, it is said below. These are the events:

• Your account: registration and a registration the server refused (with the address that tried), confirmation of your email address, sign-ins and failed sign-ins, a wrong or expired code typed to sign in, confirm an address, reset a password or register (what the code was for, never the code; for an address without an account a fingerprint of the address in place of the address), an attempt refused because there were too many, sign-outs, password changes and resets, changing or removing your postal address (that it changed, not what it says), exports of your account's data, and deletion of your account.
• Projects: creating and deleting a project (with its name), handing a project to another owner (with the email addresses of the old and the new owner), changes to a project's settings (the section and the names of the settings changed, not their values), sharing a project with someone and changing or ending that share (with the member's email address and the areas shared), leaving a project, adding a label (with its name) and removing one, creating and renaming a folder (with its name) and deleting one, and exports of a project's dataset.
• Images: images uploaded to and deleted from a project (by their internal id, not their file name).
• Training and models: a training started (with the model family and size) or cancelled, a model registered when a training finishes (with the job it came from), and a model downloaded.
• Devices: access to a device granted for a project (claiming, using or releasing it, with the device's certificate fingerprint).
• Administration: an administrator disabling or enabling an account, signing it out everywhere, sending it a password reset, granting or revoking administrator rights, adding or removing a registration rule (with the domain or address it allows), and enabling or disabling a model family. Each names the administrator who acted and the account, rule or family it concerns.

It is what lets us and you investigate a misuse of an account, and the Cyber Resilience Act expects a product like this to keep one. Administrators of the service can read it. Legal basis: our legitimate interest in the security of the service (Art. 6(1)(f) GDPR).

Devices on your network

An embidetect device works for one project at a time. When a member takes a device into a project, the device stores the project's internal id and name, and shows that name to apps on its network that ask whom it works for, so a member of another project sees it as in use. The device keeps no account, email address or name of a person, and keeps an app's access only in memory, for an hour at most. Releasing the device, or resetting it, removes the project from it.

Product page and enquiries

The product page at embidetect.embinova.at sets no cookies, runs no script and loads nothing from another site: its styles and images come from the same server, and it shows its text in the fonts already on your device. Its own server keeps no access log. It reaches you, like the rest of the service, through the server's reverse proxy, whose connection logs (IP address, time, requested path) are kept for operation and abuse prevention as described under "How long we keep it". The service's container logs are capped at three files of 10 MB per service, so an entry is overwritten once newer output has filled them. Legal basis: our legitimate interest in running the page securely (Art. 6(1)(f) GDPR).

If you write to office@embinova.at, for example to ask for a demo or a pilot, we use your email address, your name and what you write only to answer your enquiry and, if it leads to one, to prepare an agreement with you. Legal basis: steps taken at your request before a contract (Art. 6(1)(b) GDPR). Enquiry emails are kept for [retention period for enquiry emails].

Who receives data

• Emails (verification, sign-in and reset codes) are sent through Microsoft 365 (Microsoft Ireland Operations Ltd.), which processes your email address for delivery.
• The service is hosted at [hosting provider and country].
• Members of a project you share see that project's images, annotations and models, and your email address as the owner. Nothing else is shared with other users.
• Administrators of the service can see the accounts that exist, when they last signed in, the projects they own and the security log described above. They cannot see the images in a project they are not a member of.

Data is not sold and is not used for advertising.

How long we keep it

Account data and project contents are kept until you delete them or your account. Sign-in codes expire after minutes, and a registration nobody confirms is dropped with its code — until then it is an email address and nothing else, and it is not an account. Sign-in attempt counters are kept for the limiting window only. Entries in the security log are deleted 90 days after the event. Connection logs are kept for [retention period].

When you delete your account, the security log keeps the record that each action happened, with everything that identified you removed from it: your email address, the IP address and the browser or app identification all go with the account, and what is left names nobody.

Getting a copy of your data

You can get a copy of what the service holds about your account yourself, in the app or on the web, without contacting us: open Account from the top bar and, under Your data, choose Export data and confirm with your password. The file holds your account, your address, the projects you own with their classes, the list of their images with each image's annotations, their training runs with the settings, status and figures of every epoch, and the details of their trained models, the projects shared with you, the registration rule that admits your email address if an administrator added one (with its note, without who added it), and the entries of the security log about your account. Where another user acted on your account, the entry does not name them. The image files and the model files themselves are not in the file, and a very large project lists only its newest images and says how many it holds; you download them from the project in the app, as the file explains.

Deleting your account

You can delete your account yourself, in the app or on the web, without contacting us:

1. Sign in at embidetect.embinova.at/app/ or in the app.
2. Open Account from the top bar.
3. Under Delete account, confirm with your password.

This removes your account, your address, a registration rule naming your email address, and every project you own, including all images, annotations and trained models, immediately, and strips you out of the security log as described above. Projects other people shared with you stay with their owners, and your email address is removed from the entries recording that they were shared with you. Deletion cannot be undone. If you cannot sign in, write to office@embinova.at from the address of the account.

Your rights

Under the GDPR you may ask for access to your data, correction, deletion, restriction, portability, and you may object to processing or withdraw a consent. A copy of your data and its deletion you get yourself, as described above; for anything else write to office@embinova.at. You may also complain to a supervisory authority; in Austria that is the Datenschutzbehörde.

Changes

When this policy changes, the new version is published here with a new date.