How we handle your code
You are trusting us with source code that matters to you. This page lists what the service actually does with it, in plain terms. It describes how the system works today; it is not a certification.
Your uploads
- Uploaded code is never executed. Packages are only unpacked and scanned to find encoded files.
- Archives are unpacked inside a sandbox with path-traversal and symlink-escape guards, and nested ZIPs are limited to three levels.
- Uploads are deleted automatically once an order has been finished for the retention period (30 days by default). Every deletion is recorded in the order's audit trail.
- Source code is stored on disk for processing only. It is never written to the database.
Access
- Orders, invoices and downloads are scoped to the account that created them.
- Staff access to a customer's source or decoded output is logged with who, what and when.
- Passwords are stored as Argon2 hashes. API tokens are sent in the Authorization header, never in URLs.
- Payouts to external wallets need approval from a second finance operator, never the one who requested them. Support staff cannot approve payouts.
Payments
- No card data is handled. Payments are in cryptocurrency through a self-hosted gateway or from prepaid credits.
- The portal stores watch-only payment configuration, not wallet private keys.
- Payment confirmations are processed idempotently, and the deposit watcher will not credit one blockchain transaction to two invoices.
Isolation
- Decoding runs in a separate worker service. Its credentials are not available to the web-facing API.
- The service is reachable over HTTPS only.
Retention periods and your rights are set out in the privacy policy. Every order requires an attestation that you own the code or are authorized to decode it; see the terms.