Privacy Policy

When you register, we collect your name and email address. Sign-up, sign-in, email verification, password storage and hashing, password reset, multi-factor authentication, and session management are performed by our authentication provider, Clerk, Inc. (see Section 4.7). We do not store your password or a password hash on our systems; your account is identified on our systems by the user identifier Clerk assigns to it. Your email address is verified before billing or product access is enabled. You may optionally upload brand assets (logo, business name) to personalize reports — these are stored on your behalf and are not used for any other purpose.

All payment card data is collected and processed directly by Stripe, Inc. We do not store card numbers, CVVs, expiry dates, or full payment credentials on our systems. We retain non-sensitive billing metadata returned by Stripe, including your Stripe customer and subscription identifiers, plan, trial status, trial end date, billing status and dates, scheduled first charge, and invoice history. To prevent repeated free-trial abuse, we retain keyed pseudonymous identifiers derived from verified email addresses and Stripe-provided card fingerprints. These identifiers cannot be used to reconstruct the original email address or a card number and are retained only as long as justified by the one-trial policy and fraud, dispute, or legal requirements under our reviewed retention schedule.

When you use the Service, we automatically collect operational log data on our own infrastructure, including your IP address, browser and device type and version, operating system, requested pages, and timestamps. We also record the searches and questions you run within the platform, including listing IDs and geographic filters you interact with, together with counts of product events such as a completed Analyst conversation. That one product event — completing an Analyst conversation — is also sent to our survey provider, because it is what activates the usage survey described below. It is sent for every signed-in account each time it occurs, whether or not you answer a survey, and it carries only the area of the product it happened in and whether it came from our production or staging environment. Listing IDs in this context refer to property-record identifiers and do not contain your personal financial decisions. We use this information to operate, secure, and improve the Service. We do not use session replay, and no third party receives an automatic record of your clicks or page interactions.

We ask for feedback through two short in-product surveys: a usage survey shown after you complete an Analyst conversation, and a periodic question about whether you would recommend Princeps. If you answer, our survey provider receives your answers, your account identifier, the date your account was created, and the date each survey was last shown to you. The account-creation and last-shown dates exist only so that a survey is not shown to a new or recently surveyed account. The survey provider does not receive your name, email address, brokerage, province, primary market, or subscription details.

If you contact us by email or through support channels, we retain your messages and our responses to resolve your inquiry and improve the Service.

When you use Princeps Analyst, we collect and store your prompts, analyst responses, model and usage metadata, tool traces, generated artifacts, and related errors so we can provide support, debug issues, monitor abuse, and improve the Service.

We use your account information to authenticate you, personalize your dashboard, and deliver analytics and reports. This is the primary purpose for which information is collected and the reason you entered into a subscription agreement with us.

We use billing metadata to administer free trials, schedule the first subscription charge after a trial ends, charge for your subscription, issue invoices, maintain billing records, and assess and configure applicable Canadian sales-tax obligations. Launch prices are tax-inclusive and automatic tax calculation is disabled; we will obtain qualified advice and update our configuration and disclosures before changing that treatment.

We analyze usage patterns, trial activity, billing metadata, and IP data to detect unauthorized account access, fraudulent subscription or trial activity, and abuse of the platform. This is a legitimate interest that is proportionate to and does not override your privacy interests.

We use the answers you give in our in-product surveys, together with our own operational logs, to understand how the platform is used, prioritize new features, and fix defects. Answering a survey is always optional and you may dismiss it. Account holders accept the Terms of Service and acknowledge this Privacy Policy through the mandatory checkbox at signup; that stored signup record is our consent record for the disclosed processing.

Under Quebec Law 25, we collect information only for explicit, defined purposes. We do not use personal information for any purpose incompatible with those stated here without seeking fresh, informed consent.

Stripe processes subscription payments and collects your payment card data directly. Stripe may process information in the United States and other jurisdictions under its published service, privacy, and security documentation. See Stripe's privacy policy at stripe.com/privacy. We remain accountable for personal information transferred under our arrangement as required by applicable Canadian privacy law.

Cloudflare hosts the Princeps web application and serves it via a global edge network. Cloudflare processes network traffic — including IP addresses and HTTP metadata — in data centers across the United States and other jurisdictions as part of normal content delivery and security functions (DDoS protection, DNS). See Cloudflare's privacy policy at cloudflare.com/privacypolicy.

We use Resend to deliver our own transactional account emails, such as bug-report messages. Verification, password-reset, and other sign-in emails are sent by Clerk (see Section 4.7), not through Resend. Your email address and the minimum message metadata needed for delivery are transmitted to Resend solely for that purpose under its applicable terms.

We use Sentry for engineering error monitoring and performance tracing. Sentry may receive error messages, stack traces, request and runtime metadata, browser and device details, IP address, and account context needed to diagnose a failure.

We use PostHog's United States cloud to run the two in-product surveys described in Section 2.3, and for nothing else. PostHog receives your survey answers, your account identifier, the account-creation and last-shown dates used to decide whether to show a survey, the single product event that activates the usage survey — a completed Analyst conversation, carrying only the area of the product it happened in and the environment name — and the IP address and device metadata carried by the request. That product event is sent each time it occurs, whether or not you go on to answer a survey. Your browser contacts PostHog directly. PostHog product analytics, web analytics, session replay, and error tracking are all disabled.

Princeps Analyst is powered by a third-party language model. Each Analyst turn is sent to OpenRouter, Inc., which routes the request to OpenAI, the model provider we pin for production inference. Both process the request in the United States. See OpenRouter's privacy policy at openrouter.ai/privacy and OpenAI's at openai.com/policies/privacy-policy.

They receive what the model needs to answer that turn: your prompts, the earlier turns of that conversation, and the listing, market, and broker business-contact data returned by the tools the Analyst runs for you. Where you attach an image — such as the photo of a for-sale sign you can upload in the Analyst composer — that image is sent with the turn. A photo taken at a property may incidentally capture people, faces, vehicles, licence plates, or bystanders in the scene, so please do not upload images of people. Your account record — your name, email address, and billing details — is not part of an Analyst request.

An image is sent only on the turn you attach it to and only to generate that response; Princeps does not store the image bytes, and a resumed conversation contains the resulting text only. We rely on each provider's applicable service, privacy, and data-protection terms and remain accountable for personal information transferred under our arrangement as required by applicable Canadian privacy law. If we route Analyst inference to a different provider, we will update this policy as described in Section 11.

Clerk provides sign-up, sign-in, email verification, password storage and hashing, password reset, multi-factor authentication, and session management for the Service, and sends the verification and password-reset emails those flows require. Clerk processes your email address, name, a hash of your password, sign-in metadata, and the IP address and browser details of your sessions, and may do so in the United States and other jurisdictions under its published service, privacy, and security documentation. See Clerk's privacy policy at clerk.com/legal/privacy. Deleting your Princeps account also deletes your Clerk user; if your Clerk user is deleted, our account-deletion process described in Section 7.3 starts automatically.

Your name, email, and trial and subscription history are retained for the duration of your active trial or subscription and for twelve (12) months after your account is closed or your subscription ends. This period covers potential billing disputes, tax record requirements, and any support inquiries arising after cancellation.

Princeps operational usage logs are retained for ninety (90) days. Information held by Sentry and PostHog is retained according to the applicable service and project retention settings, after which it is deleted or de-identified.

Non-sensitive billing and trial metadata from Stripe is retained only for the period justified by applicable tax, accounting, fraud-prevention, dispute, and legal obligations under our reviewed retention schedule; this is not a blanket retention period for every billing field.

After applicable retention periods expire, personal information is securely deleted or anonymized. You may request earlier deletion subject to the limitations described in Section 7.

Princeps Analyst transcripts and related metadata are retained only under a bounded, documented schedule reviewed for support, debugging, abuse prevention, and product-improvement needs. We delete or de-identify them when that period ends, unless a shorter deletion request applies or a specific legal hold requires longer retention.

You have the right to know what personal information we hold about you and to receive a copy of it in an intelligible format.

You have the right to request correction of inaccurate or incomplete personal information. Account information such as your name can be corrected directly in your account settings.

You may request that we delete your personal information. We will fulfill deletion requests subject to legal obligations that require us to retain certain records (e.g., tax records). Deletion of your account will be processed upon request and confirmed by email. Deleting your account also deletes your Clerk user; if your Clerk user is deleted, the same deletion process starts automatically.

You have the right to receive your personal information in a structured, commonly used, machine-readable format and to have it transmitted to another organization where technically feasible. Submit portability requests to privacy@princep.org.

You may withdraw your consent to any non-essential data processing at any time, subject to legal or contractual restrictions. Withdrawal of consent to processing required to deliver the Service may result in termination of your subscription.

If you believe we have handled your personal information in a manner inconsistent with PIPEDA, you have the right to file a complaint with the Office of the Privacy Commissioner of Canada (OPC) at priv.gc.ca. If you are a Quebec resident, you may also file a complaint with the Commission d'accès à l'information du Québec (CAI) at cai.gouv.qc.ca.

Princeps has designated a Privacy Officer responsible for compliance with Quebec Law 25 and PIPEDA. The Privacy Officer can be reached at privacy@princep.org. If you are a Quebec resident and wish to submit a privacy request or complaint, contact the Privacy Officer directly.

Before a relevant project or cross-border disclosure begins, we assess whether Quebec Law 25 requires a privacy impact assessment and complete and document one when required. This statement describes our obligation and does not claim that every possible assessment has already been completed.

In the event of a confidentiality incident (data breach) that presents a risk of serious harm to an individual, we will promptly notify the CAI and affected individuals, as required by Law 25. Notice will describe the nature of the incident, the categories of personal information involved, the number of individuals affected, and the measures we have taken or plan to take in response.

Princeps's analytics engine produces market-intelligence outputs (price indices, absorption rates, days-on-market trends). These outputs are informational and are presented to you as one input among many in your professional decision-making. We do not make consequential automated decisions about individual Subscribers — such as creditworthiness determinations, eligibility decisions, or employment decisions — based solely on automated processing of your personal data.