Legal Document

Privacy Policy

Your privacy is important to us. Learn how we collect, use, and protect your information.

Last updated: September 2, 2026

Information We Collect

Account Information

16-digit account number (no email or password required)
IP address
Last login timestamp

Payment Information

Transaction IDs
Payment method type
Cryptocurrency wallet addresses (if applicable)
Purchase history

Usage Data

File metadata (size, type, timestamp)
Decoding success/failure status
Service usage statistics
Browser and device information

File Content and Processing Data

Uploaded PHP files and any companion or context file are stored privately while needed for processing and account history
Decoded source and recovered callback keys are stored in private account history so completed results remain available
When callback-key recovery runs for a charged, trusted-account, or approved trusted-partner decode, supplied context and relevant decoded fragments may be processed by our configured third-party AI/model provider
Free-preview payloads, whether anonymous or authenticated, are scheduled for deletion after the configured retention period (24 hours by default)
Paid, subscription, and lifetime-account decode payloads remain stored until an account or data-deletion request is completed

Data Security

TLS/SSL encryption for all data in transit
Private, authenticated access to account decode history
Isolated Firecracker environments for file processing
Restricted analytics dashboards exclude source files, decoded output, context, companion files, and recovered keys
Automatic expiry of free-preview payloads

Your Rights

Access your personal account data
Request deletion of your account
Export your purchase history
Correct inaccurate account information

File Processing

How we process and retain files:

Files are uploaded over encrypted connections (HTTPS/TLS)
Processing occurs in isolated Firecracker microVMs
Uploaded files, companion data, context, decoded output, and recovered keys are restricted to private processing and account-history features
Free-preview payloads, whether anonymous or authenticated, expire after the configured retention period (24 hours by default)
Paid, subscription, and lifetime-account results remain available in private history until a data-deletion request is completed

How We Use Your Information

We use the collected information to provide and improve our service, including:

Processing your file decoding requests
Managing your account and credit balance
Processing payments and preventing fraud
Sending transactional emails (purchase confirmations, account notifications)
Improving service performance and reliability
Ensuring compliance with legal obligations

Data Sharing

We do not sell, trade, or rent your personal information. We may share limited data only:

With payment processors to complete transactions
With our configured AI/model provider when callback-key recovery runs for a charged, trusted-account, or approved trusted-partner decode; this may include supplied context and relevant decoded fragments
To comply with legal obligations or valid legal requests
To protect our rights, privacy, safety, or property
With service providers under strict confidentiality agreements

AI-Assisted Callback Recovery

Some IonCube files protect functions with callback-derived keys. When that recovery path runs, the context you provide, relevant decoded fragments, candidate code, and key mappings may be sent to our configured third-party AI/model provider solely to attempt recovery.

Ordinary anonymous and no-credit public previews do not run this AI-assisted recovery path. They stop with guidance when callback-key context is required. Approved trusted-partner preview routes may run recovery and share the same limited data described above.

The provider processes that data under its own service and retention terms. Do not provide secrets or code that you are not authorized to share with that provider.

For recovery auditing and troubleshooting, the same context, generated PHP snippets, model tool output, and candidate key mappings may appear in access-restricted worker logs. Those logs are handled under our infrastructure logging controls and are not exposed in analytics dashboards.

Cookies & Tracking

We use cookies and similar technologies to:

Keep you logged into your account
Remember your preferences
Analyze website traffic and usage patterns
Prevent fraud and enhance security

You can control cookies through your browser settings, but disabling them may affect service functionality.

Data Retention

We retain different types of data for different periods:

Free-preview payloads: Scheduled for deletion after the configured retention period (24 hours by default), whether the preview is anonymous or authenticated
Paid and allowance decode payloads: Retained in private account history until a data-deletion request is completed
Account information: Retained while your account is active
Transaction records: Retained as required by law (typically 7 years)
Operational logs: Retained for security and debugging according to our current infrastructure and provider retention settings

International Users

Our service is operated internationally. By using our service, you consent to the transfer and processing of your information in jurisdictions that may have different data protection laws than your country of residence.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new policy on this page and updating the "Last updated" date. Your continued use of the service after changes constitutes acceptance of the updated policy.

Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us:

privacy@decodephp.io

Response time: 24-48 hours