Welcome to Critterbase

In our times of increasing human impacts on marine ecosystems, understanding, management and protection of these systems is a matter of great concern. Research on marine biotas and their interactions with each other and the environment is fundamental to address these challenges, but data and information produced are diverse and scattered over many sources. Hence, scientists, decision makers, and the public require a versatile tool to compile, synthesize and manage data on organisms in a transparent, efficient and comprehensible way and with thorough quality controls.

The wealth of data generated by AWI research on marine benthic communities in Arctic, North Sea, and Antarctic regions over the last decades called for such a modern ecological information system that allows examining data across multiple spatial and temporal scales (from local to global) and in wider contexts. We developed CRITTERBASE to fulfil this demand.

Projects at CRITTERBASE

At AWI, we currently have three regional projects, i.e., "PANABIO" (Arctic), "BENOSIS" (North Sea) and "WEECOS" (Antarctic), which are using CRITTERBASE and inputting data. The data (from 1800 onwards) were collated from primary literature, unpublished data, own research logs and online repositories.

400,000
data records
18,500
samples
14,000
stations
1,200
expeditions
3,600
marine species
53
datasets

CRITTERBASE

  • fully complies with the FAIR principles (Findable, Accessible, Interoperable, Reusable).
  • handles sample-based organism-related data from benthic and planktonic environments on a global scale.
  • is built on a data model that covers a variety of biotic data types (e.g., counts, abundances, presences/absences), sub-sample processing options and sampling methods. This model can be expanded easily.
  • is a service open to the public through a web interface.
  • is written in a source code that is freely available under an open license.

CRITTERBASE is a continuously expanding data warehouse that will enable marine ecologists across the globe to work with readily available high-quality and high-resolution data. It provides information on marine biotas and biodiversity to decision makers and the interested public. In addition, it will help to protect our data heritage for use by future generations.

The data ingestion process includes a thorough quality check of taxonomic and sampling information. CRITTERBASE updates its taxonomic information automatically via WoRMS and records / archives all modifications.

The more data marine ecologist contribute to CRITTERBASE,
the more useful it will become for all of us.

Quality Management

Data quality controls are major components within CRITTERBASE and ensure that the imported data meet a high quality standard. There are basic quality components, such as its data model itself, and several other routines that flag mistakes through a number of logical checks before, during and after data import.

The various CRITTERBASE quality control components outlined here prevent data errors that may corrupt subsequent analyses. All CRITTERBASE quality component activities are logged by a component called ActionLog and are stored in the database.

Table 1: Main components of CRITTERBASE quality control
Basis Pre-Import Import Maintenance
Data model X X X X
MyWoRMS X X X X
TaxonWizard X X(TW1) X(TW2)
ExcelTamer X
TaxaPolishing X
BioDjinn X
GeoCruncher X
BiotaControl X
Actionlog X X

Note: TW1 = create taxa list, TW2 = update taxa list

1. Basic quality components

1.1. CRITTERBASE data model

The data model (Figure 1) requires that all data are ingested in a certain format. This represents the central core of CRITTERBASE`s quality control. The model includes (1) "metadata", i.e. cruise, station, sample, subsample and subset, and (2) "sampled data", i.e. information about biota, individual measure, sediment, etc. Within the data model, the latter are attached to the metadata framework. In addition, the model also contains the category of "lookup data", i.e., inventory information (e.g., "ship", "positioning system", "gear") used multiple times across different data sets. To avoid their redundant storage and reduce the likelihood of input errors (e.g., typing errors), the lookup data are stored in "lookup tables" separate from the metadata and sampled data.

Figure 1: Schematic data model

Note: Primary and foreign keys are defined according to database structures. The primary key consists of one or more columns whose data contained within are used to uniquely identify each row in the table (e.g., primary key "Cruise" in table "Cruise"). The foreign key is a set of one or more columns in a table (e.g., foreign key "Cruise" in table "Station") that refers to the primary key (here: "Cruise") in another table (here: "Cruise").

1.2. MyWoRMS

The MyWoRMS component in CRITTERBASE synchronises taxon information with WoRMS (World Register of Marine Species; www.marinespecies.org). MyWoRMS creates a "taxon object" for each taxon imported into CRITTERBASE. For this, a new "taxon object" is created by using the entered AphiaID of the taxon, which is used to query WoRMS for the respective AphiaID. All information that WoRMS provides about this taxon are stored in "taxon object", together with the date of query and storage (see details below). If the same AphiaID is re-imported into CRITTERBASE within 30 days (via another data set with this unique AphiaID), the "taxon object" is still considered valid and WoRMS is not queried again. Otherwise, it is updated by synchronisation with WoRMS. MyWoRMS directly displays the age of all data/taxa entries; their manual update is possible at any time. All taxa are successively updated (from most recent to earliest) during a process defined as de-ageing. Taxon information of data sets that have been imported previously will still reflect changes detected by MyWoRMS (see Maintenance - BiotaControl).

The most important information stored in the "taxon object" are:

  • AphiaID used for query in WoRMS
  • valid AphiaID
  • valid scientific taxon name
  • valid taxon descriptor (= valid authority)
  • taxonomic rank (e.g., species, genus, family)
  • status (i.e., accepted or unaccepted), and
  • reason for non-acceptance (e.g., duplicate).

Only the first parameter "AphiaID" used for the query in WoRMS originates from the data import file, while all other fields are populated with information obtained from WoRMS. During a query, WoRMS itself will return an unaccepted taxon if the imported AphiaID pointed to an unaccepted taxon. The MyWoRMS algorithm in CRITTERBASE ("taxon class") was extended to always trace the unaccepted taxon to the currently accepted taxon (as registered in WoRMS). The path from the unaccepted taxon to the currently accepted one is stored in the "taxon object" together with the AphiaID of the accepted taxon (= accepted AphiaID), the corresponding scientific taxon name (= accepted scientific name) and taxon descriptor (= accepted authority).

A major advantage of MyWoRMS is that a query for a taxon already stored in MyWoRMS requires no network time, i.e., queries for about 5000 taxa run in a few seconds, whereas the same queries to WoRMS may take up half an hour. Another advantage of the local CRITTERBASE component is that MyWoRMS checks each "taxon object" for the following possible problems:

(1) Taxon status

The following parameters are used to identify the taxon status of a particular "taxon object": (i) imported AphiaID, (ii) valid AphiaID, (iii) accepted AphiaID, (iv) status and (v) unaccepted reason. In addition to "accepted" and "unaccepted" taken from WoRMS, in CRITTERBASE a status can also be "in limbo", which defines a taxon that is on its way from accepted to unaccepted but has not yet arrived (or may never arrive) there. The identification of the taxon status is realised using the following logical matrix:

Table 2: Logical matrix to identify the taxonstatus
Status AphiaID=ValidAphia=AcceptedAphiaID Status Unaccepted Reason
accepted true and ="accepted" and *
unaccepted false or ="unaccepted" and *
limbo true and !="accepted"1 and *

* = unaccepted reason is disregarded when identifying taxon status.

1 WoRMS gives here information like nomen dubium or taxon inquirendum.

(2) Status problems

MyWoRMS detects whether (i) there are multiple status associated with a "taxon object", (ii) the taxon is accepted but still no accepted scientific taxon name is recorded in WoRMS, or (iii) the taxon is accepted but WoRMS still lists an unaccepted reason entry. In addition, MyWoRMS investigates whether a change in taxon status from "accepted" to "unaccepted" or "in limbo" has an impact on any unaccepted taxa previously traced to the formerly accepted taxon (with its accepted AphiaID). For example, if taxon t1 is unaccepted, MyWoRMS follows the valid AphiaIDs until an accepted taxon tn is found (then the AphiaID of tn is the accepted AphiaID for t1). However, if tn now changes its status to unaccepted, the chain of AphiaIDs becomes invalid, because it no longer terminates with a valid AphiaID.

(3) Scientific taxon name

MyWoRMS checks whether (i) the scientific taxon name is missing, which can occur when the scientific name of a particular taxon changes in WoRMS. If a taxon status is changed from accepted to unaccepted, WoRMS deletes the corresponding (now invalid) scientific name for this taxon AphiaID leaving the record without a scientific name (i.e., blank field) but with a reference to the new accepted taxon. (ii) The taxon is accepted, but still no accepted scientific name is given, or (iii) the taxon is accepted (or in limbo), but the scientific name, the valid scientific name and accepted scientific name differ.

These checks run automatically for every single "taxon object" created in MyWoRMS when a data set is imported into CRITTERBASE. The full query log is provided, including the different types of problems that can occur in the import process. The user is then prompted to perform possible further actions on the taxa (via the import data file).

Since MyWoRMS can be backed up via snapshots and restored on other systems, otherwise cost- and time-intensive rebuilds on several computers are possible fairly easily (within the 30-day update period).

1.3. TaxonWizard

TaxonWizard builds a comprehensive taxa list across the respective target data sets stored in CRITTERBASE, which will be used for any external analytical routines (implemented in R or Python) of CRITTERBASE data, such as computation of biodiversity indices or secondary production measures. The basis for the taxa list is the TaxBase list. There are only three possibilities to input taxa to the TaxBase list: (1) Direct import of a TaxBase list, (2) import via the "biota sheet" (i.e., the sheet in the Excel template where the scientific taxa names and/or AphiaIDs are given) during data import, or (3) manual entry. Each of these three import paths is logged, ensuring that no taxon can enter TaxBase list untracked.

In addition to the TaxBase list, CRITTERBASE offers the option for independent expert knowledge lists created by the user (i.e., information does not come from MyWoRMS). For example, the user/expert can enter AphiaIDs of taxa, which are defined as colonial organisms in the TaxColony list. The user can also assign an alternate scientific taxon name to a corresponding AphiaID (from MyWoRMS) in the TaxPrivate list, i.e., an unofficial taxon name (e.g., from a historical record) that does not exist in MyWoRMS as either accepted or unaccepted taxon names.

TaxonWizard takes all AphiaIDs from the TaxBase list and any expert knowledge lists, if present. For each AphiaID, TaxonWizard queries the respective "taxon object" in MyWoRMS and creates the corresponding final entries in the taxa list (with all information stored to the "taxon object"; see details above in MyWoRMS).

TaxonWizard checks the final taxa list using the same routines as MyWoRMS. The check that MyWoRMS performs is purely "taxon object" based, i.e., each taxon is tested independently, whereas the TaxonWizard taxa list, which provides context between taxa (i.e., which taxa should be conflated), ensures that TaxonWizard can also check consistency between taxa by performing the following quality tests:

(1) Check for taxa with different AphiaIDs but the same scientific taxon name. As this is considered a legitimate case (e.g., there may be several unaccepted taxa in an AphiaID cascade that have the same scientific name), TaxonWizard only records these instances but does not create an error or warning message.

(2) Check for taxa with different AphiaIDs but the same accepted scientific taxon name. As this case should not occur, it is considered an error and a corresponding warning message is generated.

2. Pre-import quality components

CRITTERBASE features a number of components that ensure data-quality control prior to data import.

2.1. ExcelTamer

CRITTERBASE allows data input through the import of Excel files, which users create via Excel templates designed for this purpose. If an Excel import file has falsely been changed from the template, e.g., with regard to sheet and/or column names, ExcelTamer re-orders everything to the correct format to ensure an error-free data import. It does so by assigning unknown sheet and column names to the correct template names using an alias list. Missing sheet and column names (for which no alias exists) are also added if this is necessary and possible without losing any information from the original ingest file.

2.2. TaxaPolishing

TaxaPolishing checks and completes missing taxa information in the import file by searching for (a) missing AphiaIDs to the scientific taxa names or (b) vice versa by querying MyWoRMS. If the respective AphiaID or taxon name is not yet stored in MyWoRMS or the storage in MyWoRMS is outdated (older than 30 days), a new/current "taxon object" is created by the query of WoRMS and stored in MyWoRMS (see details in Basic Components - MyWoRMS). Searching for a missing AphiaID using the scientific taxon name can be done by (1) the "normal search" procedure, where only results matching the search term exactly are returned (resulting in one hit per search); or (2) the "fuzzy search", which queries WoRMS for approximate matches, meaning results will be returned even if typing errors in the search request had occurred (multiple hits returned if necessary). The normal search process is preset; a fuzzy search must be selected separately by the user.

Searching for a missing scientific name by an AphiaID (given in the input sheet) provides only one hit as only one taxon name will be found for a given AphiaID or no result at all if the given AphiaID does not exist in WoRMS.

All hits for missing taxonomic information are automatically provided in a final log, structured according to the different classes of problems encountered by TaxaPolishing.

3. Import quality components

CRITTERBASE also performs logic checks on data scenarios during data set import. Different data scenarios can be caused by different combinations of biota and sampling area inputs (Table 3). Biotic data can be provided in various units: (i) numbers (i.e., counts), (ii) abundances (i.e., densities) or (iii) presence/absence. Similarly, information on sampling area may be available in different types: (i) actually sampled area, (ii) reference area (fictional/defined area), (iii) calculated sampling area using gear information or (iv) unknown area. Depending on biotic and sample area input combinations, possible data product types are ABCD, A, B, C or D (Table 3). Data scenario of type A allows for the assessment of biomass or abundance (i.e., density). Type B only allows for the determination of the number of species per sampling unit. Type C allows the user to assess the number of species or number of individuals per sample, whereas type D only allows for the determination of the number of species per sample. The compound type ABCD supports all types of biodiversity analysis.

3.1. BioDjinn

BioDjinn checks the "data scenario" during data import (Table 3) and inspects the data to ensure entries abide by the scenario`s logic. A violation of a logic rule triggers an error message and prevents the import of data into CRITTERBASE. For example, if Scenario 1b is detected, BioDjinn checks whether a reference area is given for abundance values. If this is not the case, a warning message draws attention to the missing reference area. If no information on the reference area is available for the data set, the data have to be amended accordingly and imported under Scenario 4 (presence/absence data). BioDjinn does not convert data automatically, to give the user the opportunity to provide missing data, if available. If the imported data set contains further information (e.g., number), then Scenario 0c applies instead of Scenario 1b.

If a data set contains information that does not lead to another scenario and thus violates the logic rules (e.g., it encompasses both presence/absence and abundance data), the data cannot be imported and an error message is generated.

Furthermore, BioDjinn checks whether number and abundance values are >= 0, flagging accidentally entered false negative values. Floating-point numbers are only accepted as values for "number" if subsample information is given. For presence/absence data, only 1 or 0 are accepted values, otherwise an error message is displayed.

Table 3: Data Scenario Matrix
Scenario Number N [-] Abundance A [N/RA] Presence / Absence PA [0,1] Sampled area SA [m2] Reference area RA [m2] Area calculated by gear GSA [m2] Replicate Rep [-] Rules (R) and formulas (F)
(for definitions see below table) 		Product
0a + (+) (+) 1
  • Rules R1, R2 and R3 apply
  • Formula F1 or F2 may have to be used
 ABCD
0b + (+) (+) n
  • Rules R1, R2 and R3 apply
  • Formula F1 or F2 may have to be used
  • If necessary, consider F3 for scientific analyses
 ABCD
0c + + + (+)
  • Rules R5 may apply
  • Formula F4 applies
  • Formula F1 or F2 may have to be used
 ABCD
1a + + +
  • Formula F5 must be applied
 ABCD
1b + + A
2 + (+) (+)
  • Rules R1, R2 and R3 apply
  • Formula F1 or F2 may have to be used
 B
3 + C
4 + D
General rules:
  • (R1) SA and/or GSA must be given.
  • (R2) If SA is given, it takes precedence over GSA.
  • (R3) If SA is not given, GSA must be calculated (see Formulas F1 and F2).
  • (R4) If replicates per sample are given, SA or GSA represents the sampled area per replicate.
  • (R5) If GSA is given, calculated SA (see Formula F4) is tested against GSA to check if SA and GSA are equal. The test is performed for all gears except trawls.
General formulas:
  • (F1) GSA (for grab samples) = grab length * grab width
  • (F2) GSA (for trawl samples) = trawl gear width * sampling distance; sampling distance = towed speed * towed time or sampling distance is defined by latitude/longitude coordinates of sampling start and end (these formulas are generally valid for all towed gears)
  • (F3) Total SA/sample = n rep * SA; total GSA/sample = n rep * GSA
  • (F4) SA = (N*RA)/A
  • (F5) N = (GSA*A)/RA
Definition of products:
  • Product A: density (i.e., number of individuals of a given species that occur within a given sample unit)
  • Product B: relationship between number of species and area
  • Product C: relationship between number of species and number of individuals
  • Product D: number of species

3.2. GeoCruncher

GeoCruncher checks the geographical coordinate format used during data import (e.g., degrees° minutes′ seconds″, degrees° decimal minutes), and, if necessary, automatically converts them to the decimal degree format that is used consistently throughout CRITTERBASE. If conversion fails, the data import process is aborted.

3.3. Further quality components

Subset

The "sampled data" (i.e., biota, individual measures, sediments) are always primarily associated to their "subset" metadata ID to ensure the identification of multiple studies of the same sample (e.g., with regard to different taxonomic groups collected from the same grab or trawl sample). The uniqueness of a data set is checked using the parameter tuple of (i) taxonomic coverage (i.e., the targeted community fraction of the study, e.g., macrozoobethos) and (ii) taxonomic resolution (i.e., the taxonomic level of identification).

Expansion of existing metadata entries

Before a "cruise" stored in CRITTERBASE is to be extended by a further "station" of the (supposedly) same "cruise" from a further data ingestion, the metadata entries of the two cruises (e.g., scientific leader, ship) are checked for consistency. If metadata entries differ, CRITTERBASE generates an error message, a warning or just an information entry, depending on the default settings used.

Uniqueness of lookup data

CRITTERBASE checks the uniqueness of the following quadruple condition per subset: (i) AphiaID, (ii) life stage, (iii) sieve, and (iv) specification. One AphiaID may be named more than once in a subset only if it differs in its combination with the three other attributes. Accidental false multiple entries per subset (e.g., the same taxon of the same life stage) are thus avoided.

4. Quality components for maintenance

4.1. BiotaControl

BiotaControl checks the biotic data (i.e., taxa) on demand (i.e., user input is required) to keep them up-to-date with current "taxon objects" in MyWoRMS and detects any emerging inconsistencies, e.g., regarding the AphiaID, the scientific taxon name or the taxon status.

People & institutions

Prof. Thomas Brey
Biosciences | Functional Ecology
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
Helmholtz Institute for Functional Marine Biodiversity at the University of Oldenburg, Germany
ORCID: orcid.org/0000-0002-6345-2851
E-Mail: Thomas.Brey@awi.de

Dr. Jennifer Dannheim
Biosciences | Functional Ecology (regional project "BENOSIS", North Sea)
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
Helmholtz Institute for Functional Marine Biodiversity at the University of Oldenburg, Germany
ORCID: orcid.org/0000-0002-3737-5872
E-Mail: Jennifer.Dannheim@awi.de

Prof. Dieter Piepenburg
Biosciences | Functional Ecology (regional project "PANABIO", Arctic)
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
Helmholtz Institute for Functional Marine Biodiversity at the University of Oldenburg, Germany
ORCID: orcid.org/0000-0003-3977-2860/
E-Mail: Dieter.Piepenburg@awi.de

Dr. Katharina Teschke
Biosciences | Functional Ecology (regional project "WEECOS", Antarctic)
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
Helmholtz Institute for Functional Marine Biodiversity at the University of Oldenburg, Germany
ORCID: orcid.org/0000-0001-9595-7443
E-Mail: Katharina.Teschke@awi.de

Paul Kloss
Biosciences | Functional Ecology (developer of CRITTERBASE backend)
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
Helmholtz Institute for Functional Marine Biodiversity at the University of Oldenburg, Germany
ORCID: orcid.org/0000-0002-5587-0850
E-Mail: Paul.Kloss@awi.de

Dr. Roland Koppe
Computing and Data Centre | Head of Software Engineering
Alfred-Wegener-Institut, Helmholtz-Zentrum für Polar- und Meeresforschung Bremerhaven, Germany
ORCID: orcid.org/0000-0002-2826-3932
E-Mail: Roland.Koppe@awi.de

Partners

Alfred-Wegener-Institut Helmholtz-Zentrum für Polar- und Meeresforschung
HIFMB - Helmholtz Institut für funktionelle Marine Biodiversität an der Universität Oldenburg
BMEL - Bundesministerium für Ernährung und Landwirtschaft
BSH - Bundesamt für Seeschiffahrt und Hydrographie
DFG - Deutsche Forschungsgemeinschaft e.V.

How to cite us

Teschke, K., Kraan, C., Kloss, P., Andresen, H., Beermann, J., Fiorentino, D., Gusky, M., D. Hansen, M.L.S., Konijnenberg, R., Koppe, R., Pehlke, H., Piepenburg, Sabbagh, T., Wrede, A., Brey, T. & Dannheim, J. (in review): CRITTERBASE, a science-driven data warehouse for marine biota. Scientific Data

Kloss, P., Teschke, K., Dannheim, J., Koppe, R., Kraan, C., Piepenburg, D. & Brey, T. (2021): The Collector's App for CRITTERBASE, a science-driven data warehouse for marine biota (4.4.4). Zenodo. https://doi.org/10.5281/zenodo.5724021

Licenses

Provided data is licensed under CC-BY 4.0 unless otherwise noted.

The contents of the website are licensed under CC-BY 4.0 unless otherwise noted.

Portal software is licensed under BSD-3 unless otherwise noted.

Legal Notices

Legal form

The Alfred Wegener Institute is a foundation under public law. (Stiftung des öffentlichen Rechts) The AWI is a member of the Helmholtz Association of German Research Centres.

Representatives

The Alfred Wegener Institute is legally represented by its Directorate:
Prof. Dr. Antje Boetius (Director)
Dr. Karsten Wurr (Administrative Director)

VAT

identification number according to § 27a Umsatzsteuergesetz: DE 114707273

Data protection

The Data Protection Officer of the controller: Christoph Wagner

Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research
Am Handelshafen 12
27570 Bremerhaven
Germany

Phone: +49 (471) 4831-1637
Email: datenschutz@awi.de
Website: https://www.awi.de/nc/ueber-uns/organisation/mitarbeiter/christoph-wagner.html

Privacy Policy

By using this service you consent to our privacy policy

Liability for Content

We make every effort to keep the information on our Web site current, but accept no liability whatsoever for the content provided. Pursuant to par. 1 of TMG (German Tele-Media Act), the law limits our responsibility as a service provider to our own content on these Web pages. According to par. 8 to 10 of TMG, we are not obligated to monitor third party information provided or stored on our Web site. However, we shall promptly remove any content upon becoming aware that it violates the law. Our liability in such an instance shall commence at the time we become aware of the respective violation.

Liability for Links

Our site contains links to third-party Web sites. We have no influence whatsoever on the information on these Web sites and accept no guaranty for its correctness. The content of such third-party sites is the responsibility of the respective owners and or providers. At the time third-party Web sites were linked to ours, we found NO GROUNDS WHATSOEVER of any likely contravention of the law. We shall promptly delete a link upon becoming aware that it violates the law

Website Design and Implementation

Software development team, AWI's Computer Center

Privacy Policy

We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine. The use of the Internet pages of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.

The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.

As the controller, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone.

1. Definitions

The data protection declaration of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used.

In this data protection declaration, we use, inter alia, the following terms:

  • a) Personal data

    Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

  • b) Data subject

    Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.

  • c) Processing

    Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

  • d) Restriction of processing

    Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future.

  • e) Profiling

    Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements.

  • f) Pseudonymisation

    Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person.

  • g) Controller or controller responsible for the processing

    Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law.

  • h) Processor

    Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.

  • i) Recipient

    Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing.

  • j) Third party

    Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.

  • k) Consent

    Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her.

2. Name and Address of the controller

Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:

Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research
Am Handelshafen 12
27570 Bremerhaven
Germany

Phone: +49471 48311100
Email: o2a-support@awi.de
Website: data.awi.de

3. Name and Address of the Data Protection Officer

The Data Protection Officer of the controller is:

Christoph Wagner
Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research
Am Handelshafen 12
27570 Bremerhaven
Germany

Phone: +49 (471) 4831-1637
Email: datenschutz@awi.de
Website: https://www.awi.de/nc/ueber-uns/organisation/mitarbeiter/christoph-wagner.html

Any data subject may, at any time, contact our Data Protection Officer directly with all questions and suggestions concerning data protection.

4. Cookies

The Internet pages of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine use cookies. Cookies are text files that are stored in a computer system via an Internet browser.

Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the dats subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.

Through the use of cookies, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine can provide the users of this website with more user-friendly services that would not be possible without the cookie setting.

By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.

The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.

5. Collection of general data and information

The website of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.

When using these general data and information, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine analyzes anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our enterprise, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.

6. Registration on our website

The data subject has the possibility to register on the website of the controller with the indication of personal data. Which personal data are transmitted to the controller is determined by the respective input mask used for the registration. The personal data entered by the data subject are collected and stored exclusively for internal use by the controller, and for his own purposes. The controller may request transfer to one or more processors (e.g. a parcel service) that also uses personal data for an internal purpose which is attributable to the controller.

By registering on the website of the controller, the IP address—assigned by the Internet service provider (ISP) and used by the data subject—date, and time of the registration are also stored. The storage of this data takes place against the background that this is the only way to prevent the misuse of our services, and, if necessary, to make it possible to investigate committed offenses. Insofar, the storage of this data is necessary to secure the controller. This data is not passed on to third parties unless there is a statutory obligation to pass on the data, or if the transfer serves the aim of criminal prosecution.

The registration of the data subject, with the voluntary indication of personal data, is intended to enable the controller to offer the data subject contents or services that may only be offered to registered users due to the nature of the matter in question. Registered persons are free to change the personal data specified during the registration at any time, or to have them completely deleted from the data stock of the controller.

The data controller shall, at any time, provide information upon request to each data subject as to what personal data are stored about the data subject. In addition, the data controller shall correct or erase personal data at the request or indication of the data subject, insofar as there are no statutory storage obligations. The entirety of the controller’s employees are available to the data subject in this respect as contact persons.

7. Contact possibility via the website

The website of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine contains information that enables a quick electronic contact to our enterprise, as well as direct communication with us, which also includes a general address of the so-called electronic mail (e-mail address). If a data subject contacts the controller by e-mail or via a contact form, the personal data transmitted by the data subject are automatically stored. Such personal data transmitted on a voluntary basis by a data subject to the data controller are stored for the purpose of processing or contacting the data subject. There is no transfer of this personal data to third parties.

8. Routine erasure and blocking of personal data

The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.

If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.

9. Rights of the data subject

  • a) Right of confirmation

    Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact any employee of the controller.

  • b) Right of access

    Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information:

    • the purposes of the processing;
    • the categories of personal data concerned;
    • the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations;
    • where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;
    • the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing;
    • the existence of the right to lodge a complaint with a supervisory authority;
    • where the personal data are not collected from the data subject, any available information as to their source;
    • the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.

    Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.

    If a data subject wishes to avail himself of this right of access, he or she may, at any time, contact any employee of the controller.

  • c) Right to rectification

    Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.

    If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact any employee of the controller.

  • d) Right to erasure (Right to be forgotten)

    Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary:

    • The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.
    • The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing.
    • The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR.
    • The personal data have been unlawfully processed.
    • The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.
    • The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.

    If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine, he or she may, at any time, contact any employee of the controller. An employee of Alfred Wegener Institute, Helmholtz Centre for Polar and Marine shall promptly ensure that the erasure request is complied with immediately.

    Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. An employees of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine will arrange the necessary measures in individual cases.

  • e) Right of restriction of processing

    Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies:

    • The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data.
    • The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead.
    • The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims.
    • The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.

    If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine, he or she may at any time contact any employee of the controller. The employee of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine will arrange the restriction of the processing.

  • f) Right to data portability

    Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.

    Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.

    In order to assert the right to data portability, the data subject may at any time contact any employee of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine.

  • g) Right to object

    Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.

    The Alfred Wegener Institute, Helmholtz Centre for Polar and Marine shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.

    If the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine to the processing for direct marketing purposes, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine will no longer process the personal data for these purposes.

    In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.

    In order to exercise the right to object, the data subject may contact any employee of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.

  • h) Automated individual decision-making, including profiling

    Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.

    If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.

    If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may, at any time, contact any employee of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine.

  • i) Right to withdraw data protection consent

    Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time.

    If the data subject wishes to exercise the right to withdraw the consent, he or she may, at any time, contact any employee of the Alfred Wegener Institute, Helmholtz Centre for Polar and Marine.

10. Data protection provisions about the application and use of Google Analytics (with anonymization function)

On this website, the controller has integrated the component of Google Analytics (with the anonymizer function). Google Analytics is a web analytics service. Web analytics is the collection, gathering, and analysis of data about the behavior of visitors to websites. A web analysis service collects, inter alia, data about the website from which a person has come (the so-called referrer), which sub-pages were visited, or how often and for what duration a sub-page was viewed. Web analytics are mainly used for the optimization of a website and in order to carry out a cost-benefit analysis of Internet advertising.

The operator of the Google Analytics component is Google Ireland Limited, Gordon House, Barrow Street, Dublin, D04 E5W5, Ireland.

For the web analytics through Google Analytics the controller uses the application "_gat. _anonymizeIp". By means of this application the IP address of the Internet connection of the data subject is abridged by Google and anonymised when accessing our websites from a Member State of the European Union or another Contracting State to the Agreement on the European Economic Area.

The purpose of the Google Analytics component is to analyze the traffic on our website. Google uses the collected data and information, inter alia, to evaluate the use of our website and to provide online reports, which show the activities on our websites, and to provide other services concerning the use of our Internet site for us.

Google Analytics places a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, Google is enabled to analyze the use of our website. With each call-up to one of the individual pages of this Internet site, which is operated by the controller and into which a Google Analytics component was integrated, the Internet browser on the information technology system of the data subject will automatically submit data through the Google Analytics component for the purpose of online advertising and the settlement of commissions to Google. During the course of this technical procedure, the enterprise Google gains knowledge of personal information, such as the IP address of the data subject, which serves Google, inter alia, to understand the origin of visitors and clicks, and subsequently create commission settlements.

The cookie is used to store personal information, such as the access time, the location from which the access was made, and the frequency of visits of our website by the data subject. With each visit to our Internet site, such personal data, including the IP address of the Internet access used by the data subject, will be transmitted to Google in the United States of America. These personal data are stored by Google in the United States of America. Google may pass these personal data collected through the technical procedure to third parties.

The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the Internet browser used would also prevent Google Analytics from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Google Analytics may be deleted at any time via a web browser or other software programs.

In addition, the data subject has the possibility of objecting to a collection of data that are generated by Google Analytics, which is related to the use of this website, as well as the processing of this data by Google and the chance to preclude any such. For this purpose, the data subject must download a browser add-on under the link https://tools.google.com/dlpage/gaoptout and install it. This browser add-on tells Google Analytics through a JavaScript, that any data and information about the visits of Internet pages may not be transmitted to Google Analytics. The installation of the browser add-ons is considered an objection by Google. If the information technology system of the data subject is later deleted, formatted, or newly installed, then the data subject must reinstall the browser add-ons to disable Google Analytics. If the browser add-on was uninstalled by the data subject or any other person who is attributable to their sphere of competence, or is disabled, it is possible to execute the reinstallation or reactivation of the browser add-ons.

Further information and the applicable data protection provisions of Google may be retrieved under https://www.google.com/intl/en/policies/privacy/ and under http://www.google.com/analytics/terms/us.html. Google Analytics is further explained under the following Link https://www.google.com/analytics/.

11. Data protection provisions about the application and use of Matomo

On this website, the controller has integrated the Matomo component. Matomo is an open-source software tool for web analysis. Web analysis is the collection, gathering and evaluation of data on the behavior of visitors from Internet sites. A web analysis tool collects, inter alia, data on the website from which a data subject came to a website (so-called referrer), which pages of the website were accessed or how often and for which period of time a sub-page was viewed. A web analysis is mainly used for the optimization of a website and the cost-benefit analysis of Internet advertising.

The software is operated on the server of the controller, the data protection-sensitive log files are stored exclusively on this server.

The purpose of the Matomo component is the analysis of the visitor flows on our website. The controller uses the obtained data and information, inter alia, to evaluate the use of this website in order to compile online reports, which show the activities on our Internet pages.

Matomo sets a cookie on the information technology system of the data subject. The definition of cookies is explained above. With the setting of the cookie, an analysis of the use of our website is enabled. With each call-up to one of the individual pages of this website, the Internet browser on the information technology system of the data subject is automatically through the Matomo component prompted to submit data for the purpose of online analysis to our server. During the course of this technical procedure, we obtain knowledge about personal information, such as the IP address of the data subject, which serves to understand the origin of visitors and clicks.

The cookie is used to store personal information, such as the access time, the location from which access was made, and the frequency of visits to our website. With each visit of our Internet pages, these personal data, including the IP address of the Internet access used by the data subject, are transferred to our server. These personal data will be stored by us. We do not forward this personal data to third parties.

The data subject may, as stated above, prevent the setting of cookies through our website at any time by means of a corresponding adjustment of the web browser used and thus permanently deny the setting of cookies. Such an adjustment to the used Internet browser would also prevent Matomo from setting a cookie on the information technology system of the data subject. In addition, cookies already in use by Matomo may be deleted at any time via a web browser or other software programs.

In addition, the data subject has the possibility of objecting to a collection of data relating to a use of this Internet site that are generated by Matomo as well as the processing of these data by Matomo and the chance to preclude any such. For this, the data subject must set a "Do Not Track" option in the browser.

With each setting of the opt-out cookie, however, there is the possibility that the websites of the controller are no longer fully usable for the data subject.

Further information and the applicable data protection provisions of Matomo may be retrieved under https://matomo.org/privacy/.

12. Data protection provisions about the application and use of YouTube

On this website, the controller has integrated components of YouTube. YouTube is an Internet video portal that enables video publishers to set video clips and other users free of charge, which also provides free viewing, review and commenting on them. YouTube allows you to publish all kinds of videos, so you can access both full movies and TV broadcasts, as well as music videos, trailers, and videos made by users via the Internet portal.

The operating company of YouTube is Google Ireland Limited, Gordon House, Barrow Street, Dublin, D04 E5W5, Ireland.

With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a YouTube component (YouTube video) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding YouTube component. Further information about YouTube may be obtained under https://www.youtube.com/yt/about/en/. During the course of this technical procedure, YouTube and Google gain knowledge of what specific sub-page of our website was visited by the data subject.

If the data subject is logged in on YouTube, YouTube recognizes with each call-up to a sub-page that contains a YouTube video, which specific sub-page of our Internet site was visited by the data subject. This information is collected by YouTube and Google and assigned to the respective YouTube account of the data subject.

YouTube and Google will receive information through the YouTube component that the data subject has visited our website, if the data subject at the time of the call to our website is logged in on YouTube; this occurs regardless of whether the person clicks on a YouTube video or not. If such a transmission of this information to YouTube and Google is not desirable for the data subject, the delivery may be prevented if the data subject logs off from their own YouTube account before a call-up to our website is made.

YouTube's data protection provisions, available at https://www.google.com/intl/en/policies/privacy/, provide information about the collection, processing and use of personal data by YouTube and Google.

13. Legal basis for the processing

Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR. In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR. Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).

14. The legitimate interests pursued by the controller or by a third party

Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders.

15. Period for which the personal data will be stored

The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.

16. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data

We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner). Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded. Before personal data is provided by the data subject, the data subject must contact any employee. The employee clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.

17. Existence of automated decision-making

As a responsible company, we do not use automatic decision-making or profiling.

This Privacy Policy has been generated by the Privacy Policy Generator of the DGD - Your External DPO that was developed in cooperation with German Lawyers from WILDE BEUGER SOLMECKE, Cologne.

Regional projects that use CRITTERBASE

At AWI, we currently have three regional projects, i.e., "PANABIO" (Arctic), "BENOSIS" (North Sea) and "WEECOS" (Antarctic), which are using CRITTERBASE and inputting data. The data (from 1800 onwards) were collated from primary literature, unpublished data, own research logs and online repositories.

PANABIO: PAN-Arctic Information System of Benthic BIOta

Photo by Dieter Piepenburg

PANABIO (PAN-Arctic Information System of Benthic BIOta) is the Arctic regional subset of CRITTERBASE. Arctic seas are known to be affected profoundly and at large scales, albeit with distinct regional differences, by accelerating climate-driven environmental change, such as ocean warming and acidification, sea-ice decline and increased riverine input. Surging human activities (e.g., exploration/exploitation of natural and mineral resources, ship traffic, and tourism) add further pressures on the Arctic ecosystems. Currently, the impact of such stressors is not sufficiently understood due to the lack of pan-Arctic data that allow for estimating ecological baselines, modelling current and forecasting potential changes in benthic biodiversity and ecosystem functioning. PANABIO aims at filling this gap, by offering public access to biodiversity data collected between 1800 and 2014 by means of grabs, towed gears, or seabed imaging at point-referenced sampling stations. The samples are distributed across all major seas, i.e., the central Arctic Ocean, and Barents, White, Kara, Laptev, East Siberian, Chukchi, Bering, Beaufort Seas, Canadian Archipelago, as well as Greenland and Norwegian Seas. Currently, > 10,300 locations are included, and this will increase with the availability of new data. Data describe the composition of the marine benthic fauna at genus-level or species-level and currently comprise information about presence-absence, counts, densities or biomass of > 2,750 species/genera.

BENOSIS: BEnthic NOrth Sea Information System

Photo by Jan Beermann

The North Sea is one of the best studied marine region worldwide. Intensive utilization of the North Sea (e.g., transport, extraction and disposal of sand, laying of cables and pipes, fishery, and –for the last few years- area intensive usage by offshore wind farms) cause substantial anthropogenic environmental stress. State-of-the-art ecosystem management and modern environmental protection aim at sustainable usage of the North Sea coasts, with an emphasis on key functions of the ecosystem. A better understanding of the interaction between biodiversity and ecological functioning and the responses of the system to environmental stressors is therefore essential. Knowledge of the natural variability at ecologically relevant scales (spatial and temporal) are indispensable prerequisites for the distinction between anthropogenic and natural impacts. This large-scale/high-resolution North Sea information system combines diverse biological data with high resolution in terms of space, time and ecological structure (e.g., biodiversity and trophic relationships). Currently, our North Sea benthic information system covers the area of the German Bight from 1969 to today (< 9000 stations, > 740 species). This allows for the investigation of benthic distribution on different spatial (local/regional) and temporal (seasonal/long-term) scales and for the effects of natural and anthropogenic change on the benthic system (i.e., ecosystem shifts caused by environmental shifts). It also enables investigations of the ecological functioning of the benthos (i.e., the coupling of regulating environmental factors and ecosystem functions), relating them to essential ecosystem services.

WEECOS: WEddell Sea integrated ECOSystem model

Photo by Alfred-Wegener-Institut / Mario Hoppmann (CC-BY 4.0)

WEECOS was designed in order to enhance our understanding of the Antarctic marine ecosystem, particularly with a focus on its response to environmental change. This became especially relevant due to the need for the development of ecosystem-based management in the Weddell Sea region (Antarctica) in the light of the increasing human activities on the associated ecosystem components. The current focus and applied objective of WEECOS is the establishment of a Marine Protected Area (MPA) in the Weddell Sea. From 2013 to 2020, the AWI’s Weddell Sea MPA team compiled, tidied, and analysed a huge amount of environmental and biological data in order to obtain a representative and holistic picture of the Weddell Sea ecosystem. Several iterations of data analysis and discussions within working groups of the Commission for the Conservation of Antarctic Marine Living Resources (CCAMLR) identified an area of approx. 2 million km² that qualified for protection. The work behind WEECOS provided a sound scientific basis for political negotiations under CCAMLR on the design of the actual Weddell Sea MPA (Phase 1), including a management and a research and monitoring plan (RMP). A multidisciplinary RMP is a mandatory part of any MPA under CCAMLR, and will therefore be developed for the Weddell Sea MPA, too. Operating the Weddell Sea MPA with its RMP will continuously generate large amounts of new data. Furthermore, there is a substantial amount of historical biological data that have not yet been digitised and uploaded to any structured and accessible database. The existing WEECOS records, along with these additional components, are required to carry out the tasks under the RMP. This enormous complexity and heterogeneity of data and information calls for an efficient and tailor-made Weddell Sea MPA management system, which should be based to a large extent on automated data mining, handling and analyses. CRITTERBASE, with the incorporated WEECOS records as well as any additional data from the Weddell Sea, will be at the core of this Weddell Sea MPA management system.

Coming soon