How WeighPay handles your data.

Effective Date

This Privacy Policy is effective as of 2026-08-12. It applies to all WeighPay Group websites, operator portals, and ScaleOS-backed services operated under the weighpay.polsia.app domain and any subdomain.

1. Information we collect

We collect the minimum information needed to operate the WeighPay platform for scrap, waste, recycling, aggregates, and bulk-materials operators. Specifically:

Operator account data. The email address and operator name you provide at sign-up are stored in the operators table.
Phone number (optional). Collected only when you opt in to SMS at-risk alerts. Stored on operators.phone; never shared with third parties.
ScaleOS sync key. A per-operator API key you store when wired to ScaleOS; persisted scoped to your account in the app_settings key-value store and used only for inbound weighments + outbound ticket sync.
Operational data. Weighments (weighments), billing tickets (tickets), and scale location names/addresses (locations) generated while you use the platform. Compliance reporting states (CA, TX, FL, AL, OH, NM, etc.) are derived from this data.
Analytics identifiers. The Meta Pixel (1523659326171082) base tag is installed on every landing page and fires a PageView on load. A subset of pages also fire Lead/Purchase events via the /meta/* event endpoints. The Polsia analytics snippet generates a polsia_vid UUID stored in your browser's localStorage.

2. How Stripe billing data is handled

Module subscriptions (Logistics, Scale Ops, Accounting) are billed through Stripe Checkout on our Stripe Connect account. We never see, store, or transmit your card number, CVV, or full payment instrument. The only Stripe data we retain is the subscription ID, plan, current period start/end, and the billing email you provided at checkout — enough to associate charges with your operator account and cancel from the Stripe Customer Portal on request.

AI engine usage is metered via our internal Stripe metered-usage endpoint (GET /api/ai-usage/stripe-meter) which returns the quantity to report to Stripe for usage-based billing. We pass per-module, per-operator usage to Stripe; we do not pass any personally identifying customer data beyond the Stripe subscription reference.

3. Data retention

We retain weighments and tickets for the period required by US state recycling, scrap-metal, CRV, and scrap-tire compliance regimes (typically 3–7 years, depending on the state and vertical). Operator account, phone, ScaleOS sync key, and analytics identifiers are retained for the lifetime of your account. On account deletion, contact data and analytics identifiers are removed within 30 days; compliance retention periods override deletion requests for tickets and weighments.

4. Cookies and analytics

We use the minimum cookie set required to operate the platform:

polsia_vid — UUID in localStorage for first-party visit tracking.
wp_operator_id — UUID in localStorage identifying you as an operator so the Subscribe buttons can attach your Stripe Checkout session to the right account.
Meta Pixel (fbq) cookies set when the Meta Pixel base tag fires on landing pages.

We do not sell, rent, or share operator data with third-party advertisers.

5. Your rights

You may request access to, correction of, deletion of, or a portable export of your personal data at any time. To exercise these rights, email sales@weighpay.com from the address on file. We respond within 30 days.

6. Changes to this policy

We will post material updates to this page along with a revised Effective Date. Continued use of the platform after a posted update constitutes acceptance of the revised policy.

7. Contact

WeighPay Group — sales@weighpay.com.