Data Processing

1. Technical account records

Relict ID may store and process records required to identify an account, keep a user signed in, apply roles and permissions, connect applications, maintain security settings, and operate administrative tools.

2. Tokens and grants

Authorization codes, access tokens, refresh tokens, token metadata, token hashes, scopes, expiry times, revocation times, and application grants may be created, checked, revoked, expired, removed, or retained as metadata where required for security, audit, anti-abuse controls, or technical integrity. Plaintext token values are not intended to be stored after issuance.

3. Sessions and devices

Session records may include device names, user agents, timestamps, technical request metadata, and revocation status. Sessions can be terminated by the user, administrator, platform rules, security events, token lifecycle events, password changes, 2FA changes, or technical maintenance.

4. Consents and connected applications

Application consents define which scopes and profile fields a connected application may request. Relict Pro may revoke or ignore consents, remove applications, change allowed scopes, block redirect URIs, or restrict claims if this is needed for security, technical, legal, or administrative reasons.

5. Audit and logs

Audit records may be created for sign-in events, failed attempts, administrative actions, permission changes, client changes, token events, session actions, consent changes, and other security-relevant events. Logs may be retained even after account restriction or deletion where this is required for security, incident analysis, abuse prevention, legal protection, or technical diagnostics.

6. Administration

Administrative functions are controlled by roles and permissions. Authorized administrators may view, change, restrict, revoke, or delete account, application, session, token, consent, role, permission, and audit-related records where the interface or internal rules allow it.

7. Availability and integrity

Relict Pro does not guarantee uninterrupted operation, permanent storage, permanent availability of records, exact restoration of deleted records, compatibility with all clients, or error-free synchronization with connected applications. Technical data may be changed, migrated, normalized, archived, removed, or rebuilt during development, maintenance, security response, or platform changes.

8. Requests

All questions and requests about data processing must be sent to web@relict.pro. Relict Pro may process the request only where identification, technical feasibility, security, and applicable law allow it. No response time, action, restoration, deletion, or compensation is guaranteed unless mandatory law provides otherwise.