TECHNICAL NOTICE
BrewBench 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
Where a tool supports saved records, they are stored in this browser; unsaved work may be kept only in memory until you leave. Free-use records remain on this device unless exported. Clearing browser storage can remove saved records. Selected images are generally resized and re-encoded in the browser to remove embedded metadata before they are saved.
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 BrewBench. When you are signed in with an active BrewBench membership, the app schedules an automatic product-workspace backup after a saved change and attempts a final save when the page is hidden or closed. A network, authentication, or size error can prevent the cloud save; your browser copy remains available and the app reports the failure. Check the status and keep a local export if the data matters. Bag, brew, recipe, and equipment records are stored in a product-scoped DynamoDB backup protected by AWS-managed encryption at rest, not end-to-end encryption; authorized service operators can access it. Optional local encrypted JSON backups use PBKDF2-SHA-256 (600,000 iterations) and AES-256-GCM; the passphrase is never stored or transmitted and cannot be recovered if lost. Readable JSON/CSV exports remain unencrypted. BrewBench does not upload photos.
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 BrewBench does not unlock other Foundry products.
Product-specific processing
External services: the current product build has no user-selected remote scanning service. Where a feature offers a source link, the link is opened only when you choose it.
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 BrewBench 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.