Submitted inspection data is used to run DAEDALUS.
DAEDALUS may store the submitted URL, client name, organization, inspection claims, authority proof status, evidence artifacts, report records, verification activity, and commercial inquiry records.
Privacy version
DAEDALUS is designed to inspect submitted software artifacts and produce evidence-bearing records. Routine public URL inspection should not require private credentials, live payment secrets, or unnecessary personal data.
DAEDALUS may store the submitted URL, client name, organization, inspection claims, authority proof status, evidence artifacts, report records, verification activity, and commercial inquiry records.
Owner dashboards, confidential exports, operational error ledgers, and proof-bundle controls are restricted to owner access. Client report access is limited to the matching proof-room or intentional share path.
DAEDALUS expects sandbox evidence or controlled proof artifacts for payment and restricted workflows. Live API keys, passwords, and payment credentials should not be placed in ordinary intake fields.