F Foundry / Dependency RadarBack to Dependency Radar

TECHNICAL NOTICE

Dependency Radar data handling

This technical notice describes data handling in the current implementation and supplements the product privacy notice and terms. It is not a legally reviewed privacy policy; verify the described settings against the live deployment.

Browser data

Saved workspace records are stored in this browser. You can export a readable JSON backup or an optional product-bound encrypted JSON backup using PBKDF2-SHA-256 (600,000 iterations) and AES-256-GCM. Encryption and decryption run in this browser. The passphrase is never saved or sent to Foundry, and a forgotten passphrase cannot be recovered. Encrypted files can only be imported into the same product. These exports do not encrypt browser storage or product workspace backups. Clearing browser storage can remove saved records.

Anonymous product traffic

When this product page opens, the browser sends a page-load event containing this product ID to Foundry. Product API requests may also be counted when their referring product page can be identified. These traffic events do not include an account ID, cookie, token, IP address, or the referring URL; totals can include automated clients and are not unique visitor counts. AWS processes normal connection metadata to deliver the request.

Foundry account and backups

If you create an account, Amazon Cognito handles sign-in and email confirmation. The browser keeps access and refresh tokens in session storage for the current tab. After sign-in, product-use activity may be recorded for Foundry member counts, referrals, and achievement badges.

An active membership is specific to Dependency Radar. Supported product records can synchronize to a product-scoped account backup. Some standalone products require you to enable session sync or choose a backup action. The product page describes its own controls. Account backups are stored in DynamoDB; account-owned photos are stored separately in a private S3 bucket and are uploaded only through the product's member photo controls.

Payments

If membership checkout is enabled, Stripe processes the subscription and payment details. Foundry receives subscription events to maintain this product's entitlement; it does not receive or store full card numbers. A membership for Dependency Radar does not unlock other Foundry products.

Product-specific processing

Optional OSV.dev advisory lookup: the package manifest stays in this browser. CycloneDX 1.4–1.6 and SPDX 2.2–2.3 SBOM files are parsed locally and are never uploaded; only components with a recognized package URL for the selected ecosystem and an exact version are eligible. After you select the consent checkbox and request a lookup, an active Dependency Radar member may send the selected supported ecosystem and up to 200 exact package names and versions through the Foundry API to the fixed OSV.dev query service. npm lockfiles and pinned PyPI requirements are parsed locally; other ecosystems may use SBOMs or an exact-version JSON package list. Foundry applies member and global cooldowns; the result shows advisory IDs and provider modification timestamps and is not saved. A no-match result is not a safety assessment. Do not submit package names or versions if you cannot share them with OSV.dev.

Controls, retention, and launch status

You can delete browser records and use the product's available cloud-backup or photo controls. Deleting a cloud workspace backup does not remove separate photo objects. The account dialog offers Foundry account deletion, which removes account records and private uploaded photos across products before deleting the sign-in identity. Active memberships must be canceled and public community submissions removed first; deletion is refused until those conditions are met. Browser-only records on this catalog origin are cleared, while local data on separately hosted sites remains on your device and must be cleared there. For Dependency Radar support and privacy questions, email [email protected].

This product is available as a separate service. Read its privacy notice and terms for operator, contact, and service details.

Current infrastructure retention (source-level, not verified against a live deployment): API Lambda logs are configured for seven days. Objects waiting in the private moderation quarantine have a 14-day expiration. Standard product workspace records and private-media objects have no default time-based expiration in infrastructure configuration; they remain until you delete them or a successful account erasure removes them. Account-erasure markers are configured for a TTL of 90 days (90-day TTL). Some operational counters and queues have per-record TTLs; AWS TTL cleanup is asynchronous. Stripe retains payment records under its own terms and applicable legal obligations. Deleting a workspace backup alone does not necessarily delete separate media objects. These are source-level implementation facts, not a legal retention policy; live configuration and product-specific deletion behavior must be verified before launch.

Return to Dependency Radar