Privacy Policy

Information FootWurk collects

Depending on how you use the site, FootWurk stores:

• Your email address when you join the waitlist or free deal-alert list, request a passwordless sign-in link, or create or use a Pro account.
• Account and billing records, including subscription status, subscription dates, and Stripe customer and subscription references. When a checkout is verified, FootWurk also stores the checkout session ID, email address, Stripe references, and verification timestamps.
• For Pro members, saved sneaker requests and their active or removed status, associated with the email address used for the request.
• For Pro users who save deal filters, each filter's name and settings.
• When you use a tracked retailer link, the sneaker slug, retailer, destination URL, and click timestamp. This click record is not connected to a FootWurk account.

FootWurk uses passwordless sign-in. It creates a one-time magic-link token for sign-in; the token stops being valid after 15 minutes. Expired or used token records are not automatically erased by the sign-in process.

How the information is used

FootWurk uses this information to operate the waitlist and deal-alert signup lists, send requested sign-in links, create and verify Pro checkouts, display account and subscription status, save deal filters, and count outbound retailer clicks.

Free waitlist and deal-alert signups are stored, but email-list updates and sneaker price-alert delivery are not currently active in the app.

Services that receive information

• The FootWurk app is hosted on Render, and app records are stored in a PostgreSQL database provided by Neon.
• Polsia's email proxy receives email addresses to deliver passwordless sign-in links and register sign-in contacts.
• Polsia's payment API coordinates checkout with Stripe-hosted checkout and returns payment details that FootWurk verifies. FootWurk stores the resulting payment references and subscription status; it does not store card details.
• The site requests fonts from Google Fonts, so your browser connects to Google to load those fonts.
• When you follow a retailer link, your browser is sent to that retailer's website. The retailer then receives your visit.

This page describes the app's integrations. It does not make claims about the providers' own logs, tracking, or retention practices.

Cookies, browser storage, and analytics

FootWurk uses an authentication session cookie. It is HttpOnly, is marked Secure in production, and has a 30-day maximum age. Session data is stored in PostgreSQL.

If POLSIA_ANALYTICS_SLUG is configured, the storefront page adds a Polsia analytics beacon. It creates a persistent polsia_vid identifier in your browser's local storage and sends that identifier and the configured analytics slug to Polsia. This beacon is added on the storefront only.

The site does not currently have a consent banner or analytics preference control. You can block or clear browser cookies and storage in your browser settings. Clearing the session cookie signs you out; blocking local storage can affect the storefront analytics beacon.

Retention and available choices

The app does not currently configure an automatic deletion period for waitlist, deal-alert, account, verified-checkout, or affiliate-click records. Expiring a magic-link token makes it invalid, but does not automatically erase its database row.

You can delete saved deal filters from the deals page. Removing a saved deal alert marks its record as deleted so it is no longer active; it does not erase the row.

The app does not currently provide an account or waitlist deletion control, or publish a privacy contact or deletion-request path. The self-service controls described above are the controls presently available in the product.