dkrypt

Privacy notice

Last updated: 23 July 2026

This notice explains how dkrypt handles personal data. Privacy requests may be sent to contact@dylib.dev.

Data collected

dkrypt processes identity-provider account details, billing and subscription identifiers, service requests and results, API-key metadata, preferences, support communications, session identifiers, timestamps, request records, and security audit data. Paddle processes payment details and dkrypt does not store full card details.

How data is used

Data is used to authenticate users, provide requested features, administer subscriptions and entitlements, operate queues and notifications, provide support, secure the service, prevent abuse, diagnose faults, and meet legal obligations.

Sharing and processors

Data is shared only as needed with GitHub or Discord for authentication, Paddle for payment and subscription administration, infrastructure providers, Apple services needed to fulfill authorized requests, and authorities where required by law. Personal data is not sold or used for third-party behavioral advertising.

Cookies, retention, and security

dkrypt uses an essential session cookie and browser storage for interface preferences. Data is retained only as long as needed for service, legal, accounting, dispute, security, and backup obligations. Technical and organizational safeguards include access controls, signed sessions, restricted secrets, and encrypted transport.

Your rights

Depending on location, users may have rights to access, correct, delete, restrict, object to, or obtain a portable copy of personal data, withdraw consent, and complain to a supervisory authority. Requests may be sent to contact@dylib.dev.