F Foundry / TankJournalBack to TankJournal

TECHNICAL NOTICE

TankJournal 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 TankJournal. 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 TankJournal does not unlock other Foundry products.

Product-specific processing

Aquarium records: dated water readings, owner-entered reference ranges, and separate maintenance/observation notes are stored in this browser. Activity notes may include the tank label, activity type, time, optional water-change volume in litres or U.S. gallons, and your notes. These records may be included in the product-scoped account backup when membership is active and you save a backup. Foundry does not provide care, diagnosis, or treatment recommendations.

External services: TankJournal does not connect to an aquarium database. Source names you enter for reference ranges are stored with those ranges; the product does not fetch them automatically.

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 TankJournal 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 TankJournal