F Foundry / CORS Configuration LinterBack to CORS Configuration Linter

PRIVACY

CORS Configuration Linter privacy notice

Effective date: November 9, 2026. This notice applies to CORS Configuration Linter.

What this product does

Flag common syntax and configuration pitfalls. It analyzes examples you supply in your browser. It does not fetch or scan a third-party website. Your submitted text and generated results stay in the browser unless you choose to save a product backup or send a message to support.

For JWT Viewer and JWKS Format Validator, use synthetic or redacted examples. Never paste live access, refresh, ID, session, or bearer tokens, passwords, API keys, signing secrets, or private keys.

Information and service events

Browser inputs and saved local records stay on your device. A product-page view sends Foundry an anonymous event containing the product ID for aggregate traffic counts. The event does not contain an account ID, cookie, authentication token, IP address, or referring URL. Product API requests can also be counted when their product page is identifiable. Counts can include automated clients and are not unique visitor counts. AWS processes normal connection metadata to deliver requests.

Accounts, backups, and memberships

If you create a Foundry account, Amazon Cognito processes account information needed for sign-in and account management. This browser stores authentication tokens in session storage for the current tab. If you save a member backup, this product's workspace data is stored in a product-scoped Foundry account backup. Stripe processes subscription payments; Foundry receives subscription events to maintain this product's entitlement and does not receive full card numbers. Each product membership is separate. The sites display no advertising.

Retention and your choices

Local records remain in your browser until you remove them or clear browser storage. You can export supported records for your own copy. A product cloud backup remains until you delete it or complete Foundry account erasure. Account erasure requires canceling active memberships and removing public community submissions first; these security utilities do not accept public community posts. Foundry keeps a pseudonymous account-erasure suppression marker for 90 days so delayed payment events cannot recreate deleted account data. The production API log group is configured for seven-day retention. AWS processes log and storage cleanup according to its service behavior. Stripe may retain payment records under its terms and applicable law.

To ask about or request access to, correction of, or deletion of personal information, use the privacy contact below. You can cancel membership online from the product account panel using Stripe's self-service customer portal; the portal shows the effective cancellation date.

Service providers and security

Foundry uses AWS for hosting, sign-in, account backups, and service delivery, and Stripe for billing. Security-tool inputs are processed locally and are not sent to another website by these tools. Do not submit information you are not authorized to use. Keep your device and downloaded backups secure.

Operator and contact

Legal operator name: Kenneth Neaville. Mailing address: 15524 Country Club Dr, Mill Creek, WA 98012. Privacy contact: [email protected]. Applicable jurisdiction: Washington State and mandatory privacy and consumer-protection laws that apply to you. Governing-law jurisdiction: Washington State, subject to mandatory rights and laws that apply where you reside.

Return to CORS Configuration Linter · Terms of use · Technical data handling