Privacy Notice

Effective date: October 12, 2026
Product: CRE Build at https://cre.build
Controller / operator: Jamie Robinson, an individual doing business as CRE Build (“we,” “us,” “our”).
CRE Build is not a separate corporation or LLC; the person named above operates the service.
Privacy contact: support@cre.build · Mailing: 106 Cameron St, Shelby, NC 28152

This notice explains what we collect when you use CRE Build, how we use it, and your choices. It pairs with our Terms of Service. The Security page states operational claims we make today about accounts, data, and sharing; if something is not on Security, we are not claiming it.

1. What we collect

Account and profile. Email address, name and avatar if you provide them, password (stored hashed by our authentication provider — we do not see plaintext passwords), preferences, plan and billing status, and security settings (including whether two-factor authentication is on and session metadata).

Authentication. Sign-in with password or emailed magic link. Optional authenticator-app 2FA. We process sign-in events and active sessions so you can review and sign out other devices.

Deal and product data. Deal models, assumptions, versions, pipeline metadata, shares and invite records, proposals, exports you request, and similar content you create or upload while using the service (“Deal Data”).

Free Feasibility Model. You can run the free feasibility model on cre.build without an account, and running it stores nothing. If you ask for the branded PDF, you give us your email address and check a consent box. You can download the PDF right away, and we also email it to you unless that address has unsubscribed from CRE Build email. We then store your email address, the inputs you entered (such as project name, property type, and model assumptions), and the time you consented. You don't need a CRE Build account for this, and these details are kept apart from account data.

Billing. If you subscribe, our payment processor (e.g. Stripe) collects payment details. We receive limited billing metadata (plan, status, invoices, customer id) — not full card numbers.

Email. Transactional, nurture, and Free Feasibility Model follow-up email is delivered by Resend.

Usage and device. Approximate technical logs needed to run and secure the service (e.g. IP address, browser type, timestamps, error logs).

Advertising conversion measurement. After you start a free trial, an app page you open shortly afterward loads a Google Ads conversion tag one time, so we can tell whether our ads led to a trial. Google receives that conversion event plus the standard identifiers its tag uses, such as cookies, IP address, browser details, and ad click identifiers. We set the tag to measure conversions only: it does not record page views, and ad personalization, Google signals, and remarketing are all turned off. It does not load at any other time, and it never loads for Free Collaborator signups or for people opening a shared deal. We do not send Google your deal data, your name, or your email address. Google's handling of this data is described in its privacy policy and how Google uses information from sites that use its services. If we add other analytics or advertising tools, we will update this notice first.

Trial source. When you visit cre.build from a link that carries campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) or a Google click identifier (gclid), we save them in a first-party cookie named crebuild_attr on your browser. It lasts up to 90 days. We don't save the gclid if your browser sends a Global Privacy Control signal. If you then start a free trial, we copy the first and most recent set of those values, each with the time we saw it, onto your account, so we can tell which campaigns lead to trials and paying customers. We don't store them for Free Collaborator accounts or invited users. This record is kept by us, separately from the Google Ads conversion tag described above. We don't send it to Google or to anyone else, and it doesn't include your deal data.

If you use the demo at cre.build/demo without an account, the changes you make stay in your browser and are not sent to us. We record that the demo was opened, that you made a first edit, and whether you clicked to start a trial, so we can understand how the demo is used. We store this ourselves and do not share it with Google or other advertising services. Your browser also remembers whether you finished the demo walkthrough, so it doesn't show it again.

Support. Messages you send us about your account or the product.

We do not knowingly collect information from children under 18.

2. How we use information

We use the information above to:

• Provide, operate, secure, and troubleshoot CRE Build;
• Authenticate you and enforce access controls (including row-level security);
• Create and manage shares and invites you initiate;
• Process trials, subscriptions, renewals, and cancellations;
• Respond to your export or deletion requests;
• Meet legal obligations and prevent abuse;
• Improve the product using aggregated or de-identified signals where practical.
• Deliver the feasibility PDF you asked for and, if you consented, send you follow-up email about CRE Build. Every follow-up email has an unsubscribe link.

Deals are never used to train models. We do not use your Deal Data to train machine-learning models (ours or a third party’s). CRE Build AI, when released, will be governed by this notice as updated and by any add-on terms. AI features are not yet available in the service.

3. Sharing and disclosure

We do not sell your personal information for money. We do not use it for ad personalization or remarketing, and we turn off ad personalization and remarketing in the tag. The one exception to “we share only with providers working for us” is the Google Ads conversion tag described in Section 1. Some state privacy laws may treat that as “sharing.” You can opt out as described in Section 6.

We share information only as follows:

• With people you invite or share with. Recipients get the deal copy and sections you allow (see Terms and Security/Methodology). They see the email or identity needed to open the share. You control whether to share; we do not independently send your Deal Data to other customers.
• Service providers. Hosting, database, auth, email delivery (Resend, for transactional, nurture, and Free Feasibility Model follow-up email), error monitoring, and payment processors, which process data on our instructions and for the service.
• Google, for advertising conversion measurement only (Section 1). Google processes this data under its own terms and privacy policy.
• Legal and safety. If required by law, or to protect rights, safety, or the integrity of the service.
• Business transfer. In a merger, acquisition, or asset sale, subject to continuing protection consistent with this notice.

Staff access to customer data is limited to operating and supporting the product.

4. Retention and deletion

We keep account and Deal Data while your account is active and as needed to provide the service.

Trial source. The crebuild_attr cookie expires after 90 days, or sooner if you clear your cookies. Campaign values copied onto a trial or paid account are kept while the account exists and are deleted with the account.

You may export profile, preferences, accounts, and plan information as JSON from Settings (deals are not in that file). You may request deletion of your account, accounts you own, and deals in them. We aim to complete deletion within 30 days of the request; you may cancel the request until then, as the product describes. Backups and legal holds may lag a short time. We may retain limited records (e.g. billing, abuse, or legal) as required by law.

Free Feasibility Model leads. We keep your email address, model inputs, and consent time for up to 24 months after your last export or email engagement, unless you ask us to delete them sooner. Unsubscribing stops follow-up email. To delete your lead record, email support@cre.build from that address with the subject “Delete my feasibility data”. We aim to delete it within 30 days. We may keep a minimal suppression record (just your email address) so we don't email you again.

5. Security

We use industry-standard measures appropriate to a hosted SaaS product, including hashed passwords, optional 2FA, session controls, and database row-level security. No method of transmission or storage is 100% secure. Details of claims we make today are on /security. We do not claim SOC 2 until an auditor is engaged.

6. Your choices

• Update profile and security settings in-app;
• Turn on 2FA; review and revoke sessions;
• Cancel a paid plan in Settings › Plan and billing;
• Export account JSON; request account/deal deletion;
• Stop using the service and close your account.
• Free Feasibility Model: use the unsubscribe link in any follow-up email, or email support@cre.build to have your lead data deleted.
• Opt out of ad measurement: if your browser sends a Global Privacy Control signal, we don't load the Google Ads conversion tag and we don't store the Google click identifier (gclid), either in our cookie or on your account. Campaign parameters (UTMs) may still be stored when you start a free trial. You can also block or delete cookies in your browser, which removes the crebuild_attr cookie, or manage Google ad settings at myadcenter.google.com. Opting out doesn't affect your trial or your use of CRE Build.

Depending on where you live (for example under US state privacy laws), you may have rights to access, correct, delete, or obtain a copy of certain personal information, and to appeal a denial. Email the privacy contact above to exercise those rights. We will not discriminate against you for exercising them. If we need to verify your request, we will ask for information reasonable to confirm it is you.

7. International users

We operate primarily from the United States. If you access CRE Build from elsewhere, you understand your information may be processed in the U.S. If we later target the EEA/UK as a market, we will update this notice with transfer and rights details as needed.

8. Changes

We may update this notice by posting a new version with a new effective date. Material changes that reduce your rights will be called out; where required, we will ask for consent again.

9. Contact

Questions or privacy requests: support@cre.build.
Operator mailing address: 106 Cameron St, Shelby, NC 28152.