For our purposes here, "digital assets" refers to image, video, and audio files, as well as text documents used in our Named Entity Recognition tool. For these types of task, the Alegion platform does not need to read your digital assets. Since it is a web application, the user's browser must be able to load the asset, but there are a variety of ways to limit access, as described below.

Note that in any case, the platform will retain the asset's URL as well as the annotations. For instance, a simple image annotation record with one bounding box might look like this:

{
    url: 'https://someurl/someimage.jpg',
    coords: ...,
    classification: 'Basset Hound'
 }

Finally, the input record for form-based tasks will contain whatever data you need to display to the labeler to perform the task. In these cases, Alegion will work with you to maximize security of sensitive data, but even in these tasks, digital assets are handled by the same techniques explained here.

By default, Alegion hosts digital assets in our secure S3 buckets (AWS) in a US availability zone. Signed URLs allow access within a limited time-to-live (TTL) window. Once the TTL automatically expires, attempts to load the asset will fail.

In this option, we manage copies of your files and generate the signed URLs. Assets can be transferred into our S3 buckets through secure cloud-to-cloud pipelines, or manual methods such as SFTP, Filecloud, Dropbox, Google Drive, etc.

In this option, Alegion never has a copy of your digital assets, and you manage access restrictions. In either case, the Alegion platform only knows the asset's URL. You host the asset on the cloud or datacenter of your choice.