Privacy & website analytics

1. Information used for website and demo analytics

When these features are enabled, we may record the page visited, which website link or call-to-action was selected, approximate scroll-depth milestones, time of the interaction, broad device category, referring website, and campaign parameters contained in the page URL (such as UTM parameters and advertising click identifiers).

Where a visitor opts in to optional Meta ads measurement, the Meta Pixel may receive a page-view event and selected actions. On the early-access page, it sends a Lead event after the waitlist accepts an email submission and a CompleteRegistration event only after the email address is verified. These events contain no email address, referral code, verification token, resume text or career details. Verification, unsubscribe and referral tokens are removed from the page URL before the Pixel loads. Meta may receive the cleaned page URL, campaign parameters and technical information associated with the browser request.

To understand whether a visitor moves from the Princive website to an owned Agent or Pulse demo and then selects an outbound app handoff, we may generate a random, pseudonymous journey ID. That ID connects event records across princive.ai and start.princive.com. This measurement records an app handoff click, not whether someone registered, purchased or obtained a job.

The website measurement code also uses browser session storage for a random website-session identifier, the first landing-page path, and permitted campaign attribution. This browser session storage is different from an authenticated Princive application account.

2. What the journey measurement does not send

The website-to-demo journey event schema is designed not to transmit resume text, job-search form contents, passwords, application-account identifiers, email addresses or payment details. The early access signup uses a separate service and stores your email, signup and verification dates, waitlist status, referral code and verified referral count, your consent to weekly updates, and campaign parameters you choose to share in the page URL. It does not ask for or collect resume or career-profile information.

3. Why we use this information

We use this limited event data to understand how visitors navigate Princive, assess which product previews are helpful, troubleshoot broken handoffs, measure acquisition campaigns, and protect the collection endpoint against abuse. It is not a complete record of an individual's career activity.

4. Security and retention

Our journey event records are protected by database access controls and are subject to a scheduled deletion process for records older than 45 days. Because deletion runs daily, removal can occur shortly after the 45-day mark. This schedule applies to the new journey-event table, not necessarily to other website analytics, app records, backups or provider security logs.

For endpoint abuse prevention, our service processes the connection's IP address to derive a keyed pseudonymous fingerprint used for short-lived rate-limit counters. The counter cleanup is scheduled daily for records more than 48 hours old. We do not store the raw IP address in that rate-limit counter table. Hosting and security providers may separately process IP addresses in their own operational logs.

5. Service providers

Our website and demo infrastructure uses Cloudflare and Supabase to deliver pages, process requests, store these events and operate security controls. The early access waitlist uses Supabase to store signup and queue data and Resend to deliver verification and weekly status emails. These providers may process technical request information under their service agreements and applicable privacy terms. Other providers used by Princive are described in the existing Privacy Policy.

6. Early access, referrals and email

If you join the early access list, we use your email to verify your address and manage your place in line. Your referral code identifies people who join through your invite link. We count a referral only after that person verifies their email; verified referrals can change your queue position. Queue position is based on verified referrals and signup time, with an initial place baseline for existing Princive customers.

By joining, you ask us to send verification messages and weekly updates about your place and referral activity. You can stop weekly updates using the unsubscribe link in any weekly email. Verification and essential waitlist messages may still be sent while your place is active. We retain waitlist information while the early access program is active and to handle deletion requests; contact [email protected] to request removal.

7. Choices and privacy requests

Depending on where you live, you may have rights to request information about personal data, access, deletion, correction or other controls under applicable law. Where consent or additional choices are required for optional analytics, Princive must provide those controls before enabling the applicable collection. Publishing this notice by itself is not a substitute for obtaining required consent.

To ask a question or exercise an available privacy right, contact [email protected]. Because website journey IDs are pseudonymous and short-lived, we may need information sufficient to locate a specific record and may not be able to connect an event to a person without an identifier.

8. Changes to this notice

We may revise this notice as our site, demo experience and privacy practices change. The updated date above indicates when the current version was prepared.