Your files and account data should remain understandable.

Dislify processes uploaded video, image, and audio files to create optimized outputs. File metadata and processing state may be stored with the related job so the service can deliver progress and downloads.

Uploaded inputs and processed outputs are retained according to the configured plan and cleanup policy. Files may be removed automatically after their retention period expires.

We store the account information needed to provide authentication, verification, sessions, preferences, plan access, compression history, notifications, and support.

Usage records may include request counts, job IDs, timestamps, file metadata, processing state, and plan-limit activity.

Subscription payments are handled through Stripe. Dislify stores operational identifiers such as a Stripe customer ID, subscription ID, price reference, cancellation state, and billing period dates. Dislify does not store full payment-card details.

Developer API keys are stored as secure hashes. The original secret is displayed when created and cannot be recovered later.

Webhook signing secrets should be stored in a server environment and never exposed in browser code or public repositories.

Dislify may rely on infrastructure providers for databases, object storage, email delivery, payments, and application hosting. Access is limited to the data required to operate the service and protect it from abuse.

Users may request account deletion through the product where available. File and account records may be removed immediately or through scheduled cleanup workflows.

Some records may be retained when required for billing, security, fraud prevention, dispute handling, or legal obligations.