JAN DIGITRUST
Privacy Notice
This notice explains how personal data is handled in the temporary JAN DIGITRUST Krini test.
1. Scope
This notice applies only to the invited, temporary Krini test used to develop and evaluate the ELIXIR On-Cloud Krini integration. The test is not a public research-data service and this notice is not a general privacy policy for every JAN DIGITRUST activity.
2. Who is responsible
The data controller for this test is JAN DIGITRUST, 6 Yekmalyan Street, Yerevan 0022, Armenia.
For privacy questions or to exercise your rights, contact pavel@jandigitrust.org.
3. Why we process personal data
We process personal data only to:
- authenticate invited testers through LS Login;
- verify access to the test interface and apply the appropriate test access tier;
- operate, secure and troubleshoot the test; and
- evaluate the Krini integration.
Where the EU General Data Protection Regulation applies, the legal basis is our legitimate interest in developing, securing and evaluating the limited test (Article 6(1)(f) GDPR). We balance that interest against the rights and expectations of invited testers and limit the test to the data needed for these purposes.
Providing the login attributes required by the test is optional, but without them we cannot authenticate you or provide access. We do not use the data for advertising, marketing, profiling or automated decisions with legal or similarly significant effects.
4. Data we process
- Identity and access data from LS Login: LS identifier, name, email address and group or access entitlements released according to the scopes and choices presented by LS Login.
- Session data: login tokens and information needed to maintain and end your authenticated session. Krini does not create a separate user-profile database.
- Technical data: IP address, request time, requested path, browser information and error information contained in web-server and security logs.
- Preferences: colour theme stored in your browser and sidebar state if you change it.
5. Cookies and local storage
Krini uses strictly necessary cookies for login and session management. It also stores interface preferences when you choose them. The identity provider determines whether a refresh token is issued.
| Item | Purpose | Maximum lifetime |
|---|---|---|
authState-… | Protects a login in progress | 10 minutes or until login ends |
access_token | Authenticates requests to enabled services | Until token expiry, normally up to 1 hour |
id_token | Confirms the login | 1 hour |
refresh_token | Renews the session, if issued | Up to 30 days; deleted on logout |
oidc_provider | Records the session's login provider | Up to 30 days; deleted on logout |
token_expires_at | Records when the access token expires | Up to 30 days; deleted on logout |
logout_marker | Prevents an open page from renewing a logged-out session | 15 minutes after logout or until the next login |
sidebar_state | Remembers the sidebar setting you choose | 7 days |
| Browser local storage | Remembers the colour theme you choose | Until you clear it or change the setting |
The test does not use advertising cookies or analytics.
6. Who receives data
- LS Login processes authentication separately under its privacy notice.
- Microsoft Azure hosts JAN's test infrastructure in the Switzerland North region and may process traffic and operational logs on our behalf.
- Authorised JAN technical personnel may access limited logs when necessary to operate, secure or troubleshoot the test.
- Enabled workflow services: if you deliberately select a WES service, your browser sends that service your access token and the service operator's terms and privacy notice apply. The test uses an empty local service registry unless service testing is separately approved.
- jsDelivr: if the Krini workflow editor is enabled and opened, its helper script may be served by
cdn.jsdelivr.net, which receives your IP address and browser request.
We do not sell personal data. Infrastructure is hosted in Switzerland, while JAN DIGITRUST operates from Armenia. This means authorised access may involve data being available in both locations. Where applicable law requires safeguards for an international transfer, we apply the safeguards required for that transfer.
7. How long we keep data
- Krini session data remains in cookies for the periods shown above and is removed on logout where indicated.
- Krini obtains identity information while you are signed in and does not store a separate server-side user-profile database.
- JAN web-server access and error logs are retained for up to 14 days, unless a security incident requires relevant records to be preserved for longer.
- Information shared with LS Login or a deliberately selected external service is retained under that operator's own notice.
8. Your choices and rights
Participation is limited to invited testers. You may stop using the test and log out at any time.
Subject to applicable law, you may ask us for access to your personal data, correction, deletion, restriction of processing, data portability, or object to processing based on legitimate interests. To make a request, email pavel@jandigitrust.org. We may ask for information needed to verify your identity.
You may also lodge a complaint with the Personal Data Protection Agency of the Republic of Armenia. Where the GDPR applies, you may also complain to the supervisory authority in the EU or EEA country where you live, work, or believe an infringement occurred.
9. Security
We use access controls, encrypted HTTPS connections, limited test participation and operational logging to protect the test. No system can be guaranteed completely secure, and testers should not submit research data, sensitive personal data or production credentials to this temporary test.
10. Changes to this notice
We will update this notice if the test begins processing additional data, enables external services, changes providers or becomes publicly available. The effective date and version at the top identify the current notice.