Skip to content
Tecum Portal
Sign in Tecum Help
Deutsch|Français|English

Privacy Policy

Contents

  • General information
  • How do we process your data?
    • 1. What we process data for
    • 2. Your user account
    • 3. Invitations
    • 4. Who sees which data
    • 5. Fall and health data
    • 6. The call for help
    • 7. Smartwatch and apps
    • 8. E-mails and notifications
    • 9. Operation, telemetry and cookies
    • 10. Service providers
    • 11. Storage period
  • Your rights
  • Changes to this Privacy Policy

General information

  • Version: November 15, 2026
  • This translation is provided for information only. Only the German version is legally binding.
  • This Privacy Policy applies to the Tecum Portal at app.tecumwatch.com, the interface at api.tecumwatch.com, the apps for smartphone and smartwatch, and the e-mails and notifications of Tecum.
  • The controller is CERTENTIC GmbH, Kempener Str. 42, 41334 Nettetal, Germany. You will find further details in the imprint.
  • Questions about data protection: [email protected]. We have not appointed a data protection officer, as there is no legal obligation to do so.

How do we process your data?

1. What we process data for

We process data so that Tecum can notify your contact persons when you need help, and so that Tecum works reliably. We do not use your data for advertising.

Learn more

Where the processing is necessary to provide the service you requested or to take steps prior to entering into a contract, it is based on Art. 6(1)(b) GDPR. Where we are subject to a legal obligation, the processing is based on Art. 6(1)(c) GDPR. Processing to ensure stable operation, to analyze errors and to prevent misuse is based on our legitimate interest pursuant to Art. 6(1)(f) GDPR. To prevent repeated use of the free trial offered after free use ends, we process the personal data and information about the support relationship necessary for this purpose on the basis of our legitimate interest pursuant to Art. 6(1)(f) GDPR. Where we ask for your consent, Art. 6(1)(a) GDPR is the legal basis.

We take appropriate technical and organizational measures to protect personal data. The connections to Tecum are encrypted (HTTPS). We store your e-mail address, your name, your gender, your mobile number, the address of a call for help and the addresses for notifications (push tokens) in encrypted form. Access to the data is limited to the systems of Tecum and the persons authorized for it.

2. Your user account

For your user account we store your e-mail address, name, gender, language and your confirmed mobile number and, as a person receiving support, if you wish, also an alternative number and access codes. We also store the country from which you set up your user account, as our network service provider Cloudflare derives it from the connection, in order to adapt our offer to the countries in which we offer Tecum (Art. 6(1)(f) GDPR). There is no password: you sign in with a code that we send you by e-mail.

Learn more

Sign-in with e-mail address and code

The code has six digits, is valid for ten minutes and can be entered five times. For sign-in, we store only what is necessary to complete and secure the process: a value derived from the code (not the code itself), the number and times of attempts, and a lookup value derived from your e-mail address.

Sessions in the portal and in the apps

After you sign in, we store a session. In the portal it is valid for eight hours; if you choose “Stay signed in”, for 30 days from the sign-in. In the apps the sign-in remains in place as long as the app is used: it ends 180 days after the last renewal, at the latest 365 days after the sign-in. Of the session we store only values from which the access secret cannot be derived, and the times; for the apps also the platform, the version of the app, the device model and a random identifier of the installation. You can sign out at any time; the session then ends immediately.

User account and profile

Your user account also includes your answer to the question whether you are at least 18 years old. The mobile number is confirmed with a code before it is stored. The alternative number (a second phone number, for example your landline number or the number of your smartwatch) is not confirmed and is stored in encrypted form. As a person receiving support, you can also store up to two access codes, for example for your front door or your apartment door, each with a name. Your organizers can also enter them for you. The access codes are stored in encrypted form. We also store when and in which version you agreed to the Terms of Use and took note of this Privacy Policy and, if you are a person receiving support, when and in which version you consented to the passing on of your location in the event of a call for help and to the processing of a possible fall event. We also note when you first signed in to a Tecum app. As long as you have not completed the setup of your user account, we store the information you provide in the process in encrypted form; if you do not complete the setup, we delete it after 30 hours at the latest.

The legal basis is Art. 6(1)(b) GDPR; for the proof of your agreements Art. 6(1)(f) GDPR (our interest in being able to prove the agreements).

3. Invitations

An organizer invites persons by e-mail. To do so, the organizer enters the e-mail address of the invited person and, if that person does not use Tecum yet, name, gender and language. Every invited person decides for themselves whether to accept the invitation.

Learn more

The person receiving support, contact persons and other organizers are invited. The information entered by the organizer is personal data about a third party, which the invited person can review and update once they accept the invitation.

If a user invites another person to get to know Tecum, we document the e-mail address of the invited person, the link to the inviting person, the time and the status of the invitation. We use this information to keep the invitation process traceable and to evaluate how Tecum spreads through personal recommendations. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in the proper conduct and evaluation of these invitations.

The invitation contains a personal link. The link serves as the authorization to access the pages of the invitation; we store only a value derived from it. An invitation is valid for 14 days. If nobody answers, we remind the invited person after half of the validity period and one day before it expires; the inviting organizer receives a copy of the reminder. After the expiry we inform the inviting organizer once that the invitation was not answered. None of these e-mails contains a phone number.

When accepting, the invited person agrees to the Terms of Use and takes note of this Privacy Policy; the person receiving support additionally consents to the processing of the data of a fall (see section 5). If the person declines, they go no further, and the inviting organizer learns that they declined. If an invited person has remained without a sign-in and without any further connection, we delete their data 30 days after the end of the last invitation.

The legal basis is Art. 6(1)(b) GDPR for processing the invitation. For the information about the invited person entered by the organizer, the legal basis is our legitimate interest and that of the organizer in inviting people to a support arrangement they want, pursuant to Art. 6(1)(f) GDPR.

4. Who sees which data

Your contact persons and organizers can see the information they need to help, particularly the name and mobile number of the person receiving support. The contact person who takes over a call for help can also view the stored access codes. Who sees which information depends on the role.

Learn more

Tecum has three roles. A person can have several roles.

  • Person receiving support: this person can raise calls for help manually on the smartphone or smartwatch, or following a fall detected by the smartwatch.
  • Contact person: this person is notified when the person receiving support needs help and can take over. The contact person is notified only after accepting the invitation.
  • Organizer: the organizer sets up the contact persons for the person receiving support, invites them and can manage the profile of the person receiving support.

Who sees which data: The person receiving support sees the names, e-mail addresses and confirmed mobile numbers of the contact persons who have accepted, as well as the names and e-mail addresses of their organizers. Contact persons who have accepted and organizers see the name, e-mail address and confirmed mobile number of the person receiving support and, if provided, the alternative number; an invited contact person sees the name, e-mail address, mobile number and, if provided, the alternative number; the callback for a call for help always goes to the mobile number, and a contact person calls the alternative number only by tapping it themselves. The stored access codes are seen only by the contact person who has taken over the call for help, and only on that person’s request, as long as the details of the call for help are visible (24 hours); other contact persons do not see them. The person receiving support and the organizers see and edit the access codes on the page ‘Meine Zugangscodes’ (My access codes). Organizers also see the name, e-mail address and confirmed mobile number of the contact persons who have accepted. The name, e-mail address and confirmed mobile number of the primary organizer are seen by all contact persons, even before they accept. In a call for help, contact persons see who is taking care of it and who cannot help; the mobile number of another contact person appears only when the contact person starts the call themselves. A visitor to a public page (for example the help page) sees no personal data.

We inform the persons concerned of this visibility before they agree. The legal basis is Art. 6(1)(b) GDPR.

5. Fall and health data

If you use a smartwatch with fall detection and it detects a fall, it asks whether you need help. The information processed as a result contains your answer or the absence of a reaction, the time and the location. This information is health data within the meaning of Art. 9 GDPR. We process it only with your explicit consent, to notify your contact persons and organizers and to make sure that calls for help run reliably.

Learn more

What Tecum receives in the event of a fall

Fall detection is a function of the smartwatch (on the Apple Watch of the operating system, on smartwatches with Wear OS of the Health Services on the device) and runs on the smartwatch. Possible responses are: help confirmed, “I’m fine”, “I didn’t fall” or no response. Tecum does not read any measured values of the smartwatch, in particular no heart rate, and does not use any data from HealthKit or comparable stores.

A detected fall can also trigger a call for help. The person decides on their smartwatch whether to report the fall.

Purposes

We process the information on a fall exclusively to notify the contact persons and organizers of the person receiving support and to enable them to help, and, in pseudonymous form, to make sure that calls for help run reliably (see section 9).

Consent and legal basis

The legal basis is Art. 9(2)(a) GDPR in conjunction with Art. 6(1)(b) GDPR: the person receiving support consents explicitly before using Tecum as a person receiving support. The consent also covers the passing on of their location to the contact persons in the event of a call for help (Art. 6(1)(a) GDPR), from the start of the use. The consent is also the legal basis for our processing of information on a fall in the call for help (section 6), in the apps (section 7) and in the pseudonymous technical events (section 9). We store the time and version of the consent in the user account (see section 2).

Who learns about it

The contact persons of the person receiving support are notified; if a call for help arrives late, the organizers and the person receiving support learn about it instead (see section 6). In the event of a fall, the call-for-help page also shows the answer of the person. E-mails do not state that a fall was detected.

Storage

The data are transmitted and stored in encrypted form and passed on only to service providers acting on our behalf (section 10). We store them with the call for help and in the technical events for 90 days each (section 11); on request we delete them earlier.

Withdrawal

The consent can be withdrawn at any time with effect for the future; an e-mail to [email protected] is sufficient (see “Your rights”). Fall reporting is an integral part of Tecum to the extent that the smartwatch of the person receiving support detects falls. Without the consent to the passing on of the location and the processing of the data of a fall, Tecum cannot be provided; withdrawing consent ends your use of Tecum.

6. The call for help

For a call for help, we process the trigger, the time, the location if transmitted, and the sequence of events: who was notified and who took over. Your contact persons see the location, map and address on the call-for-help page. The contact person who took over can also retrieve the stored access codes. We store calls for help for 90 days.

Learn more

A call for help is raised by the Help button in the app on the smartphone, in the portal or on the smartwatch, if you use one, or by a fall detected by the smartwatch (see section 5). Tecum does not replace Apple’s Emergency SOS or an equivalent function of your device, nor the European emergency number 112 (144 in Austria and Switzerland, 15 in France).

In doing so we process: the identifier of the call for help, the trigger, the time, for a smartwatch its platform, the location (latitude, longitude, accuracy) if the smartwatch or the smartphone transmits it, the address determined from it (stored in encrypted form), who was notified, who answered (took over or cannot help) and the times of these steps.

All contact persons of the person receiving support who have accepted are notified at the same time: by push on their smartphones and smartwatches and by e-mail with a link to the call-for-help page. The link contains a personal access secret; we store only a value derived from it, and it is valid for 24 hours. The call-for-help page shows the trigger, location, map, address, the status of the help and, only at the request of the contact person who took over, the number of the person receiving support to call and the stored access codes (each with its name; the code itself appears only after tapping and only briefly). E-mails contain neither numbers nor the location. Who takes over is shown to the other contact persons and to the person receiving support; if nobody reacts, we remind the contact persons again after a few minutes. After a set period (currently two hours), an unanswered call for help is deemed to have expired. If a call for help arrives late because the smartwatch or the smartphone had no connection, we notify the organizers and the person receiving support instead of the contact persons.

For the address and the map image we transmit the coordinates of the location to Azure Maps from Microsoft (location queries may be passed on to the map provider TomTom, without reference to your person). On request, the route opens Apple Maps or Google Maps on the device of the contact person; the distance is calculated on the device and not sent to us. The legal basis is Art. 6(1)(b) GDPR. The passing on of the location to the contact persons is also based on the consent of the person receiving support (see section 5).

7. Smartwatch and apps

Tecum can also be used without a smartwatch, with the app on the smartphone only; the smartwatch is optional. The apps store on your device only what they need for their function. They send data to Tecum and, for notifications and maps, to Apple and Google. They contain no advertising or third-party analytics.

Learn more

Pairing the smartwatch

When a smartwatch is paired with Tecum, it generates its own key pair. The private key remains on the smartwatch; we receive and store only the public key, the platform (Apple Watch or Wear OS), the device model and the version of the app. The smartwatch shows an eight-digit code that the person receiving support enters in the portal; the code is valid for ten minutes and can be used only once. Every request of the smartwatch to Tecum is signed with the private key. The smartwatch of a contact person is paired in the same way with its own key and can be disconnected by the contact person at any time.

For notifications we store the address of the smartwatch or the smartphone at Apple (APNs) or Google (Firebase Cloud Messaging), in encrypted form. If a smartphone has not opened the Tecum app for 90 days, we send it a notification once, asking to open the app so that it continues to receive notifications of a call for help; for this we note the time of the notification in the entry of the smartphone until the app is opened again.

iPhone app and Apple Watch

On the iPhone, the app stores the session in the keychain of the device (for this device only, shared with the notification extension of the app), a random identifier of the installation, a local cache of the signed-in person (identifier, name, language, roles) until sign-out, a call for help initiated by the person receiving support that has not yet been transmitted (identifier, time, trigger, location if permitted) for a maximum of six hours, and small settings. The identifier of the installation remains in the keychain even after sign-out and may be retained after the app is deleted. The local cache and the file with the call for help that has not yet been transmitted are not excluded from the backup of the device (iCloud or computer). Lists, calls for help and mobile numbers are kept in memory only; a number retrieved for a call goes to the phone function and is not stored.

The app uses notifications (including time-sensitive ones), push via Apple, and the precise location while using the app. It sends the location only with a call for help that the person receiving support raises on the iPhone themselves, if they permit it; the distance on the call-for-help screen (“n km away”) is calculated on the iPhone, and the location read for it is not sent. The map on the call-for-help screen shows Apple Maps. The app has no access to contacts, camera, microphone, photos or HealthKit.

The Apple Watch app also runs without an iPhone. It stores the private key (in the Secure Enclave, where available), the identifier of the smartwatch and the name of the person, and calls for help and fall events that have not yet been transmitted, for a maximum of six hours. It uses fall detection, the location while using the app, and notifications. It sends pairing, calls for help and fall events (trigger, answer, time, location), status queries and the address for notifications to Tecum, each signed. The complication on the watch face contains and sends no data.

Android app and Wear OS

On the Android smartphone, the app stores the session in encrypted form (AES-256-GCM, the key is held in the Android Keystore) until sign-out, a random identifier of the installation until uninstallation, a local cache of the signed-in person (name, identifier, language, roles, whether the contact person has a smartwatch) until sign-out, a call for help that has not yet been transmitted (identifier, time, trigger, location if permitted) for a maximum of six hours, and small settings. Backup and device transfer are turned off for the app. Lists, calls for help and mobile numbers are kept in memory only.

The app uses the internet, notifications and the precise and approximate location. The location is read for the distance on the call-for-help screen on the smartphone and is not sent; it is sent only with a call for help that the person receiving support raises themselves, if they permit it. Calls run through the phone app of the system; the app has no access to contacts, camera or microphone.

The Wear OS app stores two key pairs in the Android Keystore (one as the smartwatch of a person receiving support, one as the smartwatch of a contact person), the identifiers from pairing, calls for help that have not yet been transmitted (identifier, time, trigger, answer, location) for a maximum of six hours, and the open question after a fall. It uses the location (sent with a call for help), vibration, physical activity for the fall detection of the Health Services on the device, notifications and full-screen notifications for the question after a fall, a foreground service for the minute after a fall, exact alarms, and restarting after the device restarts. For calling a contact person directly after taking over, it can use the permission to make phone calls if the person grants it.

Further information on the apps

Both apps send data to api.tecumwatch.com, to Apple (push, maps on the iPhone) and to Google (push). On the device, the apps log only fixed messages without names, e-mail addresses, numbers, locations, access values or identifiers; these messages remain on the device. Outside the apps, Apple and Google (Android vitals) and Samsung may receive diagnostic data of the device if you have allowed this on the device; we have no influence on this.

With Firebase Cloud Messaging from Google, Google receives the push token of your device and the Firebase installation ID; according to Google, the library also reports whether messages were delivered. Firebase Analytics is turned off.

The legal basis for the processing by us is Art. 6(1)(b) GDPR; for storing and reading information on your device Section 25(2) No. 2 TDDDG, insofar as this is strictly necessary for the service you requested.

8. E-mails and notifications

We send e-mails and push notifications about sign-in, invitations, calls for help and your use of Tecum. They contain neither your location nor phone numbers.

Learn more

We send e-mails with sign-in codes, invitations, reminders, messages about the answers to invitations, about changes of the contact persons and about calls for help. We also use your e-mail address to inform you about everything that concerns your use of Tecum, for example about changes of Tecum, of the Terms of Use, of the Privacy Policy and of the conditions of use (for example a subscription), about planned maintenance and disruptions of the service, and about data breaches about which we are required by law to inform you. These are messages about your use, not a newsletter and not advertising. They are sent through Azure Communication Services Email from Microsoft or, alternatively, through the e-mail service of Amazon (Amazon Web Services EMEA SARL, see section 10). The e-mails contain no tracking pixels and no tracking links.

We send push notifications through the push service of Apple (APNs) and of Google (Firebase Cloud Messaging). They contain the name of the person who needs help and technical identifiers.

The legal basis is Art. 6(1)(b) GDPR; for mandatory messages Art. 6(1)(c) GDPR.

9. Operation, telemetry and cookies

For operation we process technical connection data such as the IP address and record pseudonymous technical events, which we evaluate only in aggregated form. The portal sets only technically necessary cookies.

Learn more

Provision of the portal and the interface

When the portal or the interface is accessed, technically necessary connection and access data are processed. These include in particular the IP address, the date and time of access, the requested address, and technical status and error information. Our publicly accessible services are reached through Cloudflare, and the applications run on Microsoft Azure (see section 10).

The processing serves the provision, stable operation, detection of technical disruptions and protection against misuse and attacks. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in the undisrupted and protected operation of our services.

Technical logging and telemetry

Our applications log fixed messages without personal data. To maintain and improve reliable operation, evaluate how Tecum is used, and understand how Tecum spreads, we record technical events in Azure Application Insights. These concern in particular calls for help, invitations, setup steps, the use of the portal and the apps, errors and visits to our help page and legal texts.

Depending on the event, we store pseudonymous identifiers of persons and calls for help, times, status and error information, the page visited and the language, the role of the person (person receiving support, organizer or contact person), technical information such as client, device type, operating system, device model and app version, and the approximate geographic origin of a request (country, region, city), which Cloudflare determines from the IP address. We do not store the IP address itself, names, contact data, addresses, precise locations or access values in the process.

The data are deleted after 90 days and evaluated only in aggregated form. On request, we delete events assigned to a person. The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest lies in reliable operation, in detecting and fixing errors and difficulties of use, and in being able to follow how Tecum spreads, including through personal recommendations. We do not use these data for advertising or profiling.

Cookies and local storage

The technically necessary cookies are: a cookie for your session after the sign-in (eight hours or, if you choose “Stay signed in”, 30 days), a cookie for the duration of the sign-in step (30 minutes) and a cookie that notes, only for the duration of the browser session, that we have pointed out open invitations to you. The cookies are protected against access by scripts and are sent only over an encrypted connection.

In addition, your browser stores locally that you have hidden the notice about the smartwatch of a contact person. There is no cookie for the language; the language follows your profile and, for visitors, the browser or the address of the page.

Insofar as information is stored on or read from your device in the process, this is done on the basis of Section 25(2) No. 2 TDDDG, because it is strictly necessary for the service you have expressly requested.

10. Service providers

We use service providers, in particular Microsoft Azure for hosting, storage and sending e-mails, Cloudflare for the provision and protection of our services, and Apple and Google for push notifications. The data of Tecum are stored in data centers in Western Europe.

Learn more

Insofar as our service providers process personal data on our behalf, this is done on the basis of data processing agreements pursuant to Art. 28 GDPR.

Microsoft Azure

For hosting (App Service), data storage (Storage), key management (Key Vault), operational diagnostics (Application Insights), sending e-mails (Communication Services) and maps and addresses (Maps) we use services of:

Microsoft Ireland Operations Limited
One Microsoft Place
South County Business Park
Leopardstown
Dublin 18
Ireland

The data of Tecum are stored and processed in Azure data centers in Western Europe. For Azure Maps, Microsoft processes the requests in the European Union; the map provider TomTom is involved as a subprocessor.

Amazon Web Services

As an alternative to Microsoft, the e-mail service of Amazon may be used for sending e-mails. In this case the e-mail address of the recipient and the content of the e-mail are processed:

Amazon Web Services EMEA SARL
38 Avenue John F. Kennedy
L-1855 Luxembourg
Luxembourg

The e-mails are sent from a data center in Germany.

TrafficPlex GmbH (lima-city)

We store backup files at lima-city. The service is operated by the following company:

TrafficPlex GmbH
Konsul-Smidt-Str. 90
28217 Bremen
Germany

Cloudflare

We use Cloudflare for the provision and protection of our publicly accessible services; for data and legal basis, see section 9.

Apple and Google

Push notifications to iPhone and Apple Watch run through the push service of Apple (Apple Distribution International Limited, Hollyhill Industrial Estate, Hollyhill, Cork, Ireland). Push notifications to Android devices and smartwatches with Wear OS run through Firebase Cloud Messaging from Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). The map on the call-for-help screen of the iPhone app comes from Apple. These providers process data according to their own terms insofar as they pursue their own purposes (for example the delivery of notifications).

Transfers to third countries

With the service providers named, personal data may be processed outside the European Union or the European Economic Area, in particular in the USA. Insofar as an adequacy decision of the European Commission applies to the respective recipient, in particular to companies certified under the EU-U.S. Data Privacy Framework, the transfer takes place on that basis. Otherwise it takes place only on the basis of other safeguards permitted under the GDPR, in particular the standard contractual clauses pursuant to Art. 46 GDPR and, where necessary, supplementary measures.

11. Storage period

We store data only as long as necessary, for example calls for help and technical events for 90 days. We delete a user account that has not been used for twelve months after a prior warning by e-mail.

Learn more

In detail:

DataStorage period
Calls for help with location, address and sequence of events90 days from the call for help
Links to the call-for-help pagevalid for 24 hours, deleted with the call for help
Invitationsvalid for 14 days; deleted after 90 days at the latest
Invited persons without a sign-in and without any further connection30 days after the end of the last invitation
Information from an uncompleted setup of the user account30 hours at the latest
Sessions in the portal8 hours, with “Stay signed in” 30 days; expired sessions are deleted after 30 days
Sessions of the appsup to 180 days without renewal, at most 365 days; expired sessions are deleted after 30 days
Sign-in codes and sign-in processesvalid for 10 minutes; deleted 30 days after the end
Addresses for notifications (push) of smartphones and of the smartwatches of contact personsuntil sign-out or disconnection; devices that are turned off or not connected for 100 days are removed
Addresses for notifications (push) of the smartwatch of the person receiving supportuntil sign-out or disconnection of the smartwatch; a disconnected smartwatch is deleted after 100 days, and for a smartwatch that has not been connected for 100 days the address is removed
Technical events (telemetry)90 days
Inactive user accountsdeleted after 12 months without use; you receive a warning by e-mail 30 days beforehand
Persons receiving support after their free trial ends without a subscriptionup to twelve months after the start of the trial
Access codesuntil you remove them or your user account is deleted
Time and version of your agreementsas long as your user account exists

Persons receiving support after their free trial ends without a subscription: To prevent another free trial if they use Tecum again, we retain the personal data and information about the support relationship necessary for this purpose for up to twelve months after the start of the trial. In doing so we remove the previous links to organizers and contact persons. We then delete the data stored solely for this purpose, unless there is another legal basis for keeping them longer.

If you delete your user account, we delete your data, unless legal obligations or the establishment, exercise or defense of legal claims require further storage in the individual case; then only for these purposes and only as long as necessary.

Your rights

You have in particular the right of access, rectification, erasure, restriction of processing, data portability and objection. You can withdraw a consent at any time, and you can lodge a complaint with a data protection supervisory authority. After signing in, you can delete your user account at https://app.tecumwatch.com/delete-account. For all concerns, an e-mail to [email protected] is sufficient.

Learn more

Automated decision-making and profiling

There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR. Who helps is decided by the contact persons.

Rights of the data subjects

Subject to the applicable legal requirements, you have the following rights in particular:

  • access to your personal data pursuant to Art. 15 GDPR,
  • rectification of inaccurate data pursuant to Art. 16 GDPR,
  • erasure pursuant to Art. 17 GDPR,
  • restriction of processing pursuant to Art. 18 GDPR,
  • data portability pursuant to Art. 20 GDPR, and
  • object to processing based on Art. 6(1)(e) or (f) GDPR pursuant to Art. 21 GDPR.

Where processing is based on your consent, you can withdraw it at any time with effect for the future pursuant to Art. 7(3) GDPR. The lawfulness of the processing carried out until the withdrawal remains unaffected (for information on a fall, see section 5).

You edit your data in your profile, insofar as this is provided for there.

Right to lodge a complaint

The supervisory authority responsible for us (Art. 77 GDPR) is:

Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen
Kavalleriestraße 2–4
40213 Düsseldorf
Germany
E-mail: [email protected]
Website: www.ldi.nrw.de

Changes to this Privacy Policy

We may adapt this Privacy Policy if legal requirements, our services or the processing of personal data change. The version published on this page at the time applies.

CERTENTIC © Copyright 2026 CERTENTIC GmbH

Tecum Help Terms of Use Privacy Policy Imprint

Version 0.1.1245 · Build ee0a66f · 20261116.6