Website privacy

Information you send us

When you request a demo, we collect your first and last name, organization, work email address, and any optional role/category, phone, organization type and website, organization description, demo interests, approximate membership size, discovery source, or message you provide. Please do not submit confidential member information, grievance details, passwords, or other sensitive case records through this form.

How your request is handled

If you request demo access, an owner-approved policy may send one email-verification link and, after verification and eligibility checks, provision a synthetic demo and send one invitation. If you choose the disclosed demo service-email sequence, it may send one activation reminder after 24 hours and up to two resends after 48 and 96 hours while you remain unactivated. Resends replace the earlier link and never extend the original activation deadline. Requests using personal email, uncertain organization or role information, repeat demos, and identity collisions receive operator review. A demo request does not create a customer subscription. Email verification links expire after 24 hours; invitations are single-use with a separate activation deadline.

The optional, unchecked demo email agreement on the request form covers synthetic demo access, activation emails, sales follow-ups and feedback together. Leave it unchecked to request an operator conversation without these automated emails. Older requests with individual email choices retain those choices.

We use these details to respond to your inquiry and arrange a demonstration. The website sends your request to the LaborNexa application hosted on Render. The application stores your request in a prospect record and request history accessible to authorized LaborNexa platform staff. This is separate from customer organization data. When configured, our email delivery provider, Resend, also processes a company notification for delivery to hello@labornexa.com. Your request remains recorded if that notification is unavailable. We use the information for the demo conversation and follow-up, including any preferences you share with us.

The application also keeps temporary counters, including a hashed email identifier, to limit repeated submissions. These counters are separate from customer accounts. Submitting this form does not create an account or subscribe you to a mailing list.

Demo email agreement

By selecting the optional demo email agreement, you request an isolated synthetic demo and agree to email verification and an invitation after eligibility checks. You also request one activation reminder after 24 hours and up to two invitation resends after 48 and 96 hours if you have not activated. Resends replace earlier links and retain the original activation deadline; activation stops these reminders and resends.

You also agree to up to two sales follow-up emails on days 5 and 12 after activation while your demo is active, plus one optional feedback request three days after activation. Each sales email includes an unsubscribe link that stops sales follow-ups without changing demo access. We retain a hashed email identifier to honor that preference. You may decline feedback using its link. Contact hello@labornexa.com for help or to withdraw permission for all contact.

Eligible requests may be processed automatically under an owner-approved policy; other requests receive operator review. Existing requests are not enrolled retroactively. A demo request does not create a customer subscription. We record your email choices and feedback for product review, without automatically changing your sales stage.

Questions about your information

Email hello@labornexa.com with questions or requests concerning information you have submitted through this website.

Customer application data

This website notice covers public website inquiries. Member, case, and other records held within a customer's LaborNexa account are governed separately by the applicable customer arrangements and account policies.

Optional first-party source attribution

With a separate opt-in, we remember the source and campaign that brought you here in this browser for up to 90 days. Your first attributable visit is kept separately from the source of your current demo request. Internal navigation can carry the current source within this browser tab. Without permission, we do not persist or send this optional attribution; the demo form remains usable. The consent preference itself is stored until you change it.

When you submit a demo request, permitted attribution accompanies it into platform prospect history. We retain only supported UTM source, medium, campaign, content and term values, a capture time, and a referring hostname where available. We do not retain full referral URLs, query strings from external referrers, IP addresses or browser fingerprints for attribution. Values can be missing or inaccurate; Direct / Unknown is used when evidence is unavailable. Your answer to “How did you hear about LaborNexa?” stays separate.

Source attribution does not load advertising trackers or share identifiers with them, and is separate from the website analytics choice. Source attribution preferences in the footer let you decline or withdraw permission, which clears the attribution stored by this site in the browser. Browser Global Privacy Control or Do Not Track disables this optional attribution. Previously submitted request history is not erased by clearing browser storage; contact hello@labornexa.com about submitted information.

Optional website analytics

Updated October 25, 2026. This public website asks before enabling HeyCatch and, where configured, Google Analytics. An earlier Google-only approval does not enable HeyCatch. You can decline or change your choice using Analytics preferences in the footer; the site and its forms remain usable. The choice is stored in this browser. Global Privacy Control and Do Not Track keep optional capture off.

After you allow analytics, HeyCatch measures public page visits, navigation and clicks, supported marketing campaign parameters, and referring website origins. It uses pseudonymous browser identifiers and receives browser/device information and the technical connection information needed to process permitted requests. The SDK loads from this website with capture and identifier persistence disabled until consent. Demo forms are excluded from automatic interaction capture. URL fragments, including purchase-receipt tokens, and unsupported query parameters are removed from outgoing event properties. We do not identify visitors by name or email, send form entries or case details, or record browsing sessions.

Where configured, Google Analytics uses cookies and similar browser identifiers for page paths and limited actions such as demo requests and product-link clicks. Its events exclude form entries, names, email addresses, case details, query strings and account information. See how Google uses information from sites that use its services. Google Analytics remains off on the separate Get started and purchase-measurement pages; the shared choice also applies when you visit other public pages. LinkedIn choices and first-party source-attribution choices remain separate.

This integration covers the public website, not the customer application. Use the footer controls to withdraw permission. This stops further analytics capture and clears accessible Google Analytics cookies. Withdrawing does not erase information already processed by an analytics provider. Contact us about privacy questions at hello@labornexa.com.

Optional LinkedIn landing-page measurement

Updated October 23, 2026. The public Get started page offers a separate choice before loading the LinkedIn Insight Tag. This choice is independent of Google Analytics and first-party attribution. Declining leaves signup available. LinkedIn measurement is not installed on our demo forms, signup forms, or customer application.

After you allow it, LinkedIn may receive this landing-page visit, browser identifiers, cookies and technical connection information such as IP address for advertising measurement and retargeting. We do not send form entries, names, email addresses, union membership records, grievance details or purchase events from the landing page. Visits with unsupported URL parameters, fragments or unapproved referrers are excluded. A valid LinkedIn click identifier may be included after consent to connect an ad click to this landing-page visit. Enhanced matching is not configured. See LinkedIn’s Privacy Policy for its processing and retention practices.

Your choice remains in this browser until changed. Use Decline on the Get started page to withdraw; if the tag is loaded the page reloads to stop it. Browser Global Privacy Control and Do Not Track keep it off. This does not erase data already processed by LinkedIn or third-party cookies; manage those through your browser and LinkedIn privacy controls. Contact hello@labornexa.com with questions.

Optional purchase measurement

After a verified live purchase, you may separately choose to share one purchase event with LinkedIn. The customer application does not load LinkedIn code. If you request this option, it creates a short-lived, one-use random receipt that is sent to a separate public confirmation page and removed from the address before any advertising code loads. That page requires a new explicit choice, independent of landing-page measurement.

After you allow measurement, the receipt is verified and consumed once. LinkedIn receives a purchase event plus its permitted browser identifiers and technical connection information; we do not send your name, email, organization, invoice, card details, case records or purchase amount. Test payments, pending payments, missing receipts and replayed receipts do not send events. Browser privacy preferences keep this feature off.

You can decline before the event is queued. Once queued, the one-time event cannot be recalled from LinkedIn here. Blocking or a network failure may prevent delivery; this does not affect your purchase. Receipt tokens expire shortly, are stored hashed by the application and never stored by this page in browser storage. We retain a minimal operational claim record to prevent duplicate reports. LinkedIn processing is described in its privacy policy linked above.