Privacy
Policy.

1. What this Policy covers

This Policy explains how We Make Stupid collects, uses, stores, and shares information when you visit our site, contact us, use free resources, or use WMS products including Capsize, Permit, AI Pilot Pack, Paper Trail, and Stupid Parts.

2. Information you provide

• Name, email address, and other contact information you send to us.
• Billing and transaction information needed to connect your purchase or subscription to Stripe. WMS does not store full payment-card numbers.
• Support messages and the product, purchase, entitlement, or project references needed to investigate them.
• Product inputs you deliberately submit, subject to the product-specific sections below.

3. Capsize

Capsize is paid-only. Running it requires an active subscription.

When you run Capsize, the idea and context you submit are sent from WMS servers to a configured zero-cost inference provider so the text can be structured. Groq is the primary route. If the configured Groq route is unavailable, WMS may use the configured OpenRouter zero-cost fallback. The provider that serves a request therefore can receive the submitted Capsize text under that provider's applicable terms and privacy practices.

WMS persists paid Capsize account and product state needed to provide the service. This can include account identifiers, saved project inputs, generated run results, provider/model identifiers, run history, evidence entries and provenance fields, evidence classifications, Reality Gate state, usage counters, and timestamps.

When WMS's internal Paper Trail evidence capture is configured, validated Capsize model output may also be sent to that WMS-controlled evidence path to record bounded egress evidence. Failure of that internal evidence capture does not change the Capsize result returned to you.

4. Permit

Permit processes the PDF you submit in memory to extract searchable text and run the requested preflight. The current Permit telemetry records bounded run information such as page count, readiness, finding counts, evidence-strength counts, scope answers, and engine/ruleset versions. It does not intentionally store the uploaded PDF or extracted document text in the Permit telemetry record.

Permit also stores the transaction and time-bounded entitlement state needed to verify the paid access window and support payment or access recovery.

5. AI Pilot Pack

The current AI Pilot Pack workbench is deterministic, and the workbench answers you enter in that browser's local storage stay in that browser. Those workbench answers are not sent to an AI model by the current product.

WMS does store the purchase, entitlement, and associated transaction identifiers needed to verify ownership, handle support, and revoke access after a qualifying refund. If you clear browser storage or move devices, the local workbench answers do not automatically follow you.

6. Paper Trail

Paper Trail stores the account, subscription, project, provisioning, credential-reference, and bounded evidence data needed to provide the product. Evidence records can include content deliberately submitted to a supported attestation path, timestamps, trace references, and evidence-state information.

Paper Trail is designed so a useful evidence record does not require silently warehousing every raw AI output. The specific evidence you submit or configure remains part of the product data needed to provide that service.

7. Stupid Parts

For published Stupid Parts, WMS stores the purchase, product, price, email, entitlement, delivery, and download/access records needed to fulfill the purchase and let an owner regain access where supported.

8. First-party revenue and reliability measurement

WMS records a bounded first-party product funnel so we can tell whether a product is actually working. This can include a random WMS session identifier, attribution source such as an UTM source or external referrer host, product views, purchase-button intent, checkout creation, checkout completion, access grant, first product use, fulfillment failure, and refund events.

This operational funnel is designed not to contain the contents of your Capsize idea, Permit PDF, Pilot Pack workbench answers, payment-card number, password, or secret keys. The WMS session identifier and source are stored in first-party cookies so checkout and fulfillment can be connected to the same product journey across the WMS domain.

Separate advertising or analytics tools such as Google or Meta are subject to the site's applicable consent controls. The first-party transaction/reliability record exists so WMS can fulfill paid products, prevent duplicate processing, diagnose failures, and measure whether a customer journey completes.

9. Other automatically collected information

Hosting and security systems can process information such as network address, browser/device information, requested pages, timestamps, and diagnostic logs. WMS uses this information for availability, security, fraud/abuse prevention, debugging, and service operation.

10. Service providers

• Stripe: checkout, payment processing, subscriptions, taxes, invoices, and billing-management services.
• Supabase: authentication and database infrastructure.
• Vercel: website and application hosting.
• Groq: primary cloud model processing for Capsize requests when configured.
• OpenRouter: zero-cost Capsize model fallback when configured and used.
• Resend: transactional or support email where configured.
• Google and Meta: analytics or advertising where enabled and consented.

11. How we use information

• Provide, authenticate, and fulfill WMS products.
• Process purchases, subscriptions, refunds, and access recovery.
• Preserve product state and evidence where the product requires it.
• Measure first-party product reliability and conversion.
• Respond to support and customer communications.
• Protect the service, prevent fraud/abuse, and debug failures.
• Comply with legal, accounting, tax, and regulatory obligations.

12. Retention and security

We retain information for as long as reasonably needed to provide the service, preserve transaction and entitlement history, investigate failures, handle disputes/refunds, meet accounting or legal obligations, and exercise or defend legal rights. Product data may have different retention needs depending on the product.

WMS uses access controls and server-authoritative payment/entitlement checks, but no Internet service can promise absolute security.

13. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, and rights relating to marketing or certain sharing. Some transaction, security, accounting, or legal records may need to be retained where law permits or requires it.

To make a privacy request, contact us using the email below.

14. Children

WMS products are not directed to children under 18, and we do not knowingly collect personal information from children for these products.

15. Changes and contact

We may update this Policy when products or data flows change. The page shows the current update date.

We Make Stupid
hello@wemakestupid.com