Privacy Policy

Who we are

BildrX is a fundraising platform for startup founders, at bildrx.com, with the product at app.bildrx.com.

Privacy questions and requests go to legal@bildrx.com.

Where your data is stored

The application and the database run in Singapore: Amazon Web Services region ap-southeast-1, with Supabase providing the Postgres database, authentication and file storage in the same region. Uploaded documents — decks, financials, contracts, data-room files — are stored there.

This is a correction. An earlier version of this policy said BildrX's infrastructure was hosted in the United States. That is no longer true, and we are saying so plainly rather than quietly editing it.

The public marketing site is static files distributed by CloudFront, which caches them on edge servers worldwide so pages load quickly wherever you are. Those files are the same for every visitor and contain nobody's data.

Some of the third parties listed below process data outside Singapore. Where that happens your information crosses a border. The clearest example is Google Analytics, which is optional: if you accept it, information about the pages you visit — including your IP address — is processed by Google on infrastructure that includes servers in the United States. Decline it and no such transfer happens.

What we collect

Account details: your name, email address and password, or the name, email and profile picture Google gives us if you sign in with Google. Also two-factor settings and session records.

Company profile: company name, stage, industry, location and the other details you enter so the product can tailor what it shows you.

Onboarding answers: when you set up a workspace we ask your role (founder, finance or legal and, for finance and legal, whether you work on your own company or for clients) and which parts of BildrX you want to use, and we use those two answers to arrange your sidebar and dashboard. We also ask where you are based (country and, if you like, city), how big your team is, which advisers you work with, how you heard about BildrX, and your gender. Every one of those last questions is optional: each is marked as such and can be skipped. We ask them to understand who uses BildrX and where, so we can decide what to build next. They do not change what the product shows you, what you can do, or what you pay.

Who sees your onboarding answers: you, and BildrX staff with administrator access, who can view them in an internal dashboard and download them as a CSV file. That table and the CSV list each person's answers next to their role, chosen suites, country of incorporation and signup date, but not their name or email address. Other members of your company cannot see your answers to the optional questions. Your role and your choice of suites are saved on your profile, which the people in your company can see. Our hosting providers, Amazon Web Services and Supabase, store them as they store the rest of your account; apart from them, the answers are not shared with any of the third parties listed below.

Feature waitlists: when you press "Notify me" on a feature that is launching soon, or tick a suite that includes one, we record that you are waiting for it, together with your role, so we can count demand for each feature.

Cap table: stakeholder names and email addresses, security type, share counts, price per share, issue dates, vesting terms and the full transaction history. Most of these people are not BildrX users — see the section on other people's data.

Investor CRM: your notes, pipeline stages, tasks and activity history about the investors you are tracking.

Documents you upload: pitch decks, financial models, contracts, cap-table backups and anything else placed in a data room or legal room.

Sharing analytics: what happens when someone opens a deck or data room you shared — covered in its own section below.

E-signature records: signer names, email addresses, signature data and the audit trail of who opened, viewed and signed a document and when.

Billing: the Stripe customer, subscription and payment identifiers, your plan, billing status and the last four digits of the card. Full card numbers never reach us.

Marketplace: the briefs and requirements you submit, and the deliverables BildrX returns.

Automatically: pages visited, features used, IP address, browser and operating system, and timestamps — the ordinary logs needed to run and secure a web service.

Support: whatever you send us when you get in touch.

AI features, and what they send to Anthropic

AI in BildrX is not just the chat box. Several features send your content to Anthropic, our AI provider, to generate a response:

The pitch-deck analyser sends the text extracted from the deck you uploaded, and the deck score and written feedback come back from it. The legal room sends contract text to produce clause suggestions and to pull out expiry dates. The deal room sends document and workspace context to build diligence checklists. The investor brief and marketplace search send the query and the relevant workspace context. The copilot chat sends your prompt together with a summary of your workspace — which can include CRM notes, cap-table figures and document titles — so the answer is about your company rather than a generic one.

So in practice: uploaded decks, contract text, CRM notes and workspace summaries all reach Anthropic when you use these features. Nothing is sent when you do not use them.

Anthropic processes this to return a response. It does not train models on it. We keep the prompt and the response so you can see your own history.

Output from these features is machine-generated and can be wrong. The Terms of Service says more about that.

Analytics: our own, and the optional Google one

BildrX measures itself first-party. A small number of events — a screen opened, a module used, a deck uploaded, a document signed — are written as rows in BildrX's own database in Singapore, beside the rest of your data. They deliberately carry no email addresses, no personal or company names, no document or deck titles and no share links. No third party sees them, no script is loaded to collect them, and no cookie is set. This is not optional: it is how we know which parts of the product work.

Google Analytics 4, run by Google LLC, is separate and optional, on both bildrx.com and app.bildrx.com. It loads only if you choose "Accept all" in the cookie banner. Until then no Google script is loaded, no Google cookie is set, and your browser makes no request to Google for analytics. On bildrx.com, loading one of the forms connects to Google reCAPTCHA and Google Fonts, as described below.

If you accept, what Google receives from us is the address of the page you are on and its title, plus what your browser tells any site it visits — including your IP address, from which Google derives an approximate location. Google sets its own cookies to recognise the browser on a later visit; the Cookie Policy names them.

What Google never receives: your name, your email address, your company's name, the title of any document, deck or data room, any share link, any cap-table or CRM content, and any identifier we hold for you. We send no user identifier of our own at all. In the product, the address of the page is stripped of record identifiers and share links before it is sent, so a data room reads as "/deal-room/:id" rather than as a link anybody could follow.

We do not use Google Analytics for advertising. Ad storage, ad personalisation and Google Signals are turned off in the code that loads it, so the data is not used to build an advertising audience and is not combined with Google's advertising products by us.

Accepting means this information is processed by Google on infrastructure that includes servers in the United States. You can change your mind at any time — in the product, Settings then Security has an Analytics cookies control; on this site, clearing the site's browser storage makes the banner ask again. If your browser sends Do Not Track or Global Privacy Control we treat that as a decline and do not ask.

What a shared deck or data room records about its viewer

When you share a deck or data room by link, BildrX tracks the visit and shows you the result. This is the point of the feature, and the people you send links to should know it happens.

For each visit we record: the viewer's IP address, a coarse device class (desktop, mobile or tablet), a two-letter country code derived from the request, when the visit started and ended, how long they spent on each individual page or document, and how far through they got. If you used a per-recipient link, all of this is tied to the name and email address you gave that recipient.

We set a cookie called deck_viewer_token in the viewer's browser, which lasts one year. It exists so that the same person returning later is counted as a repeat viewer rather than a new one.

This information is visible to the founder who shared the link, in their deck analytics. It is not sold, not shared with other founders, and not used for advertising.

If you share links from BildrX, you are the one deciding to track those viewers. Telling them is your responsibility.

Other people's data that you enter

A large part of what BildrX stores is not about the account holder. It is about co-founders, employees holding options, investors in a CRM pipeline, and counterparties signing documents — people who never created an account and may not know the record exists.

We hold that data on your instruction, to provide the product to you. We do not email those people on our own initiative or use their details for anything besides running the features you are using.

If one of them contacts us about their data, we will normally refer them to you, because you decided to record it. We will help you respond.

The investor database

BildrX ships with a database of investors — firms, focus areas and contact details — that founders can search and add to their CRM. It is ours, not built from what users enter.

Its provenance is currently under review. We are working through where each record came from, whether the source permitted redistribution, and what notice the individuals named in it are owed. Until that review finishes we are not going to claim the dataset is fully documented, because it is not.

If you are named in it and want your record corrected or removed, write to legal@bildrx.com and we will do it.

Why we process it

To run the features you are using; to authenticate you and keep accounts secure; to take payment and manage subscriptions; to answer support requests; to diagnose faults and improve the product; and to meet legal obligations.

We send product and marketing email only if you opted in — the box at signup is separate from the terms box and is never pre-ticked. You can turn it off at any time. Operational email about your account, billing and security is not marketing and is sent regardless.

We do not sell personal data, and we do not run advertising.

The consent we record at signup

Creating an account requires ticking a box agreeing to the Terms of Service and this Privacy Policy. We store which version you agreed to — the string "2026-09-22" — and the timestamp.

A second, optional, unticked box records whether you want marketing email. Its answer is stored alongside.

If either document changes materially, the version string changes and you will be asked again inside the product.

Who else processes your data

Amazon Web Services — application hosting, compute and storage. Singapore (ap-southeast-1).

Supabase — Postgres database, authentication and file storage. Singapore, on AWS.

Anthropic — AI features, as described above.

Stripe — payments, subscriptions and marketplace purchases.

SignWell — electronic signature generation, routing and audit trail.

Resend — transactional email delivery.

Google — optional sign-in with Google; receives only what an OAuth sign-in involves, and only if you use it. Global.

Google (Google Analytics 4) — website and product usage measurement, and only if you chose "Accept all" in the cookie banner. Receives the page address, the page title and your IP address. United States, among other locations.

Featurebase — the support chat, the help centre and the changelog, in the product and on bildrx.com. In the product it receives your user id, email address and name, so a conversation reaches us against your account, plus whatever you write to us. On bildrx.com you are anonymous. The chat loads only once you press Support, and the changelog only once you press "Load the changelog" on the changelog page, or once you choose "Accept all" in the cookie banner.

Tally — the contact, enterprise, partnership, press, waitlist, webinar and job-application forms on bildrx.com. Receives what you type into a form and the page it was on. A form loads only once you press "Load the form" or choose "Accept all" in the cookie banner; "Open the form in a new tab" goes to Tally directly.

Google (reCAPTCHA and Google Fonts) — loaded by Tally inside its forms, reCAPTCHA to keep out spam and Google Fonts for the form's typefaces, and only once a form has loaded. Receives what your browser tells any site it visits, including your IP address, and, for reCAPTCHA, how the form page is used. United States, among other locations.

Google (Google Sheets) — each form submission is copied from Tally into a Google Sheet so the team can answer it. Receives what you submitted. United States, among other locations.

Marketplace partners — BildrX may engage partners or subcontractors to carry out a marketplace order. When it does, BildrX passes that partner the order details the work needs, which can include the service you bought, the brief and requirements you submitted, and the files and messages on that order. Partners have no login to BildrX and no access to your workspace; they receive only what BildrX passes them for that order, and act on BildrX's instructions to deliver it.

Cloudflare — DNS for bildrx.com. Sees DNS queries, not the contents of your account. Global.

We also disclose information where the law requires it — a valid court order, subpoena or regulatory demand — to protect the rights or safety of BildrX, our users or others, and to a buyer if the business is sold, in which case we will tell affected users.

How long we keep it

We do not have a published retention schedule yet.

What is true today: data stays while the account is active. The cap-table ledger is append-only by design — corrections are recorded as new reversing entries, so historical rows are not deleted. Backups are kept for operational recovery. Logs are kept for a period we have not fixed. When an account is closed we delete data on request, manually, and tell you what was removed.

Your rights, and how to use them

You can ask for a copy of your personal data, ask us to correct it, ask us to delete it, ask us to stop a particular use, and withdraw marketing consent. Withdrawing consent does not undo what was done before.

Be straight with you about the mechanics: export and deletion are handled by a person, not a button. You can edit your own profile and much of your workspace content in the product, but a full export or a full deletion means writing to legal@bildrx.com. We will acknowledge the request, verify you are who you say you are, carry it out, and confirm what was done.

A self-service export and a self-service delete are on the roadmap. Until they exist, the manual route is the route.

Security

Data is encrypted in transit and at rest. Access inside the product is scoped by role and enforced in the database itself, so a query cannot return another company's rows. Signature events carry an audit trail. Two-factor authentication is available and we recommend turning it on.

No system is perfectly secure and we will not claim otherwise. If a breach affects your data we will tell you.

Children

BildrX is for business use and is not directed at anyone under 18. We do not knowingly collect data from children.

Changes to this policy

We will post changes on this page and update the date at the top. Material changes come with a new version string and a fresh prompt inside the product.