Only what the marketplace needs.

DeloresAI processes account email, display name, password hashes, verification and recovery records, sessions, preferences, saved apps, update subscriptions, download requests and completion receipts, community feedback and votes, publisher authorization and operational audit data.

Passwords use adaptive one-way hashes. Recoverable service credentials and pending account-code messages are protected server-side. Browser and desktop clients never connect directly to SQL.

GitHub handles authorized repositories, release metadata and artifact downloads. A transactional email provider handles account and marketplace messages when configured. Provider acceptance and confirmed delivery are recorded separately.

Download counts deduplicate signed-in accounts per app. They include full transfers observed by DeloresAI and desktop-reported downloads checked against the release hash and size. Anonymous transfers and older requests are excluded. These counts do not measure installations or product usage. Optional installation analytics remain separate and require consent. Publishers receive aggregate download metrics.

Community feedback, its author’s display name, vote totals, and publisher status are public and can be exported by signed-in users as JSON or Markdown. Individual voters and downloaders are not listed in those exports. Public GitHub star counts are cached repository statistics, separate from DeloresAI thumbs-ups. Account privacy controls include your feedback, votes, and download records.

API keys used inside individual workbenches are not collected by this marketplace. Each workbench’s separate privacy disclosures explain its external services and data egress.

Private workflow reports are uploaded only after you choose a file, review it and confirm sharing with the app’s publisher team. They are separate from public feedback, retained for 90 days, and can be deleted earlier from the app’s report page. Downloaded publisher copies cannot be recalled; backups follow existing database retention. Remove secrets and research you do not wish to share before uploading.

Theme preferences may be saved locally. Authentication does not rely on browser localStorage. Account settings manage sessions and notification preferences. A verified privacy contact, deletion/export handling, final retention periods and jurisdiction-specific terms remain launch requirements.