Daedalus uses zero-footprint data handling methodologies to keep client telemetry secure. This statement outlines what data we process and how your identities are partitioned.

1. Data Collection

We restrict data collection to the absolute minimal identifiers required to protect your private slot allocation. We collect:

• Hardware ID (HWID): The system machine UUID hash generated by your operating system, used purely to bind slot architecture files to your specific test machine.
• Discord Username: Used for role verification and automated invitation delivery to our private communications channel.
• Email: Used for automated invitation delivery after being accepted.
• Crypto Payment Metadata: Order identifiers generated by our gateway integration (NOWPayments) to automatically manage and track active slot access lifespans.

2. Data Isolation & Security

Your data is shielded under secure PDO connection protocols and kept private. We do not harvest browser tracking logs, local files, real identities, or email lists. Payment routing is executed over localized decentralized systems, ensuring clear separation between your physical identity and database rows.

3. Third-Party Disclosures

Daedalus never sells, rents, handles, or reveals user metrics to external ad tracking firms, analytical agencies, or external businesses. Transaction data is safely sent only to our partner crypto processor to confirm incoming blockchain status hashes.

4. Data Deletion Protocol

If your slot reservation expires or is manually dropped by administrative action, your stored identity records can be wiped permanently from active directory servers. You can request explicit account deletion at any time by coordinating with internal support teams.

← Return to Landing Page