Developer Defence support

Start with the problem you can see.

Get help with installation, local scans, intelligence updates, findings, or privacy. Include evidence that helps us reproduce the issue, but never send credentials or private source code.

Contact:

[email protected]

Supported app version:

0.3.x

Contact support

Email [email protected]. A clear subject helps route the request, such as Install failure, Scan result, Intelligence update, or Privacy request.

Jam Data Solutions Ltd, trading as Developer Defence

Company number 14075684

102-116 Windmill Road, Croydon, England, CR0 2XQ

Install and launch
Signing, installer, or startup
Use this for Gatekeeper, SmartScreen, package-manager, launch, keychain, or secure-storage errors.
Scanner
Coverage, findings, or performance
Use this when a project is missing, a manifest is unsupported, a finding looks wrong, or a scan exceeds its budget.
Intelligence
Verification or update failures
Use this for stale intelligence, signature verification, update progress, ecosystem selection, or activation failures.
Privacy
Access, deletion, or consent
Use this to exercise a data right, withdraw an email subscription, or ask about local and cloud data.

What to include

Send the smallest amount of information that lets us reproduce the issue:

Developer Defence version and where you downloaded it;
operating system version and architecture, such as macOS 15 on Apple Silicon;
what you expected, what happened, and the approximate time;
the exact on-screen error code or a screenshot with private paths redacted;
whether retrying, restarting the app, or running a manual scan changed the result.

Do not send passwords, API keys, tokens, vault contents, private source code, unredacted home-directory paths, or live malware samples. We will ask for a specific diagnostic only when it is necessary.

Scanner help

A project is missing

Confirm that its directory is inside an active scan root, is not excluded or paused, and contains a supported lockfile or imported SBOM. Discovery intentionally skips symlinks, other filesystems, caches, build outputs, dependency vendor directories, and unsupported manifests by default.

A scan reports limited coverage

Open the Scanner coverage details. They show which roots completed, which budgets were reached, and which inputs were unsupported. Limited coverage does not mean a threat was found; it means some requested discovery work could not be completed.

A finding looks incorrect

Open the finding and include its advisory ID, package ecosystem, package name, resolved version, and the affected range shown by the app. Do not send the full project or lockfile unless support asks for a minimal redacted reproduction.

Intelligence update help

Developer Defence verifies signed metadata and the downloaded PersonalDB before activating an intelligence release. It will not activate an update that fails signature, hash, compatibility, or database checks.

Check that the system clock is correct and HTTPS access to developerdefence.com is available.
Open Settings, review the selected ecosystems, and use Sync now.
Keep the existing verified intelligence active while an update is retried.
Do not delete trust metadata or bypass a failed signature check.

If the failure persists, include the update stage, release identifier, timestamp, and public error code shown in Settings.

Platform coverage

macOS scanner
Local package scanning and signed intelligence are available in the current scanner. Apple has approved the entitlement required for a future direct-protection edition; protected-path enforcement appears only when that native component is installed.
macOS scanner
Local package scanning and signed intelligence are available in the current scanner. Apple has approved the entitlement required for a future direct-protection edition; protected-path enforcement appears only when that native component is installed.
Windows and Linux
Scanner behaviour is shared across platforms. Native protected-path capability depends on the installed edition, operating-system support, and successful native component setup.
Windows and Linux
Scanner behaviour is shared across platforms. Native protected-path capability depends on the installed edition, operating-system support, and successful native component setup.
Unsupported inputs
An unsupported manifest is reported as a coverage limitation. Developer Defence does not silently treat it as scanned or clear.
Unsupported inputs
An unsupported manifest is reported as a coverage limitation. Developer Defence does not silently treat it as scanned or clear.

Privacy requests

For access, correction, deletion, objection, portability, or email-subscription requests, contact [email protected]. Include the device, account, or subscribed email you control. We may ask for a signed device challenge or email verification before acting.

Read the Developer Defence privacy policy for the distinction between local scanner state and limited cloud-held device or subscription data.

Security reports

Email [email protected] with the subject Security report. Explain the affected version, impact, and safe reproduction steps.

Do not test against another person's device or account, degrade the service, publish a live exploit before coordination, or include real credentials. We will acknowledge the report and arrange a safer channel if sensitive material is required.