Privacy Policy

This policy explains what BuildBank collects, why, who else receives it, where it is stored, and what you can ask us to do about it. BuildBank is operated by Tekdlin, based in Dallas, Texas, United States.

1. Information we collect

Information you give us

• Account details: your email address, your name, and the sign-in provider you used. If you sign in with Google or LinkedIn we receive your email address, name and profile image from them. If you register with a password, we store only a one-way hash of it and never the password itself.
• Profile details: anything you choose to add: first and last name, username, a short bio, country, and a profile image.
• Your project choices: the role, industry, skill level, goal and tools you select, and the work you produce against a project.
• Messages you send us: if you request a demo or contact support, we keep your message and any preferred time you give.

Information we collect automatically

• Product analytics: pages viewed, features used, clicks, and timings. These events are keyed to a pseudonymous account identifier rather than your email address, and our event definitions deliberately carry counts, identifiers and category values rather than the content of your work.
• Session recordings: we record how the interface is used so we can see where it fails people. Text you type into forms is masked before the recording leaves your browser, and payment card fields are rendered by Stripe in a separate frame that recordings cannot capture at all.
• Voice recordings, which we do not keep: where you choose to speak rather than type, your browser records a short clip and sends it to us. We pass it straight to our transcription provider, return the text to your screen so you can read and edit it, and discard the audio. It is never written to a disk, never stored in a database, never attached to your account, and no recording of your voice is recoverable from us afterwards. The text you keep is saved with the project it produced, because it is what the project was written from. Speaking is always optional: every surface that offers it also accepts typing.
• Talking through the assessment, which we do not record: if you choose to talk through Find Your Fit, your browser opens a live voice conversation with our speech provider for the length of the sitting, at most seven minutes. The assistant reads each task aloud and turns what you say into the same answers a tap would give. Your voice is processed as you speak and is not recorded, stored or attached to your account by us, and no transcript of the conversation is kept; what is saved is only the answers, exactly as if you had tapped them. We keep a record that a session took place and how long it lasted, which is how we limit cost. You can switch to tapping at any point.
• Your code in the Build Studio: code you write in a project is saved to your account so it is there when you come back, and runs in your own browser, not on our servers. Files you add from your computer stay in your browser and are never uploaded. If you ask the AI pair for help, the step, your code and its last output are sent to our AI provider to answer you; we record that you asked and what it cost, not what you asked.
• The project guide in the Build Studio, which we do not record: if you start a guided session, your browser opens a live voice conversation with our speech provider, as in the talked-through assessment. When the guide looks at your work, the step, your studio code and its last output, and anything you have chosen to show it (a tab you share, or a reading from the BuildBank Guide extension described below) are sent to our AI provider to judge where you are and suggest the next thing to try. That material is judged in memory and then discarded: it is not stored, not logged and not attached to your account. We keep a record that a session took place and how long it lasted, and a count of how many looks you used each day, which is how we limit cost.
• Technical data: IP address, browser, device type, and approximate location derived from your IP.
• Cookies: a session cookie that keeps you signed in (essential; the product cannot work without it), and analytics identifiers from PostHog. Stripe sets its own cookies during checkout for fraud prevention.

The BuildBank Guide browser extension

The BuildBank Guide extension for Chrome is optional. It has one purpose: letting the project guide see the notebook or data tool you work in during a guided session you started. It works only with a BuildBank account.

• What it reads: only a tab you have linked to your BuildBank session, either by opening it from the Build Studio or by choosing “Let the guide read this tab” in the extension. From that tab it reads the tab's title and, depending on the tool, up to twelve notebook cells around your cursor with their outputs, the file or changes open on GitHub, or the sheet name and formula bar in Google Sheets. For tools that draw their work as a picture, such as Google Sheets, Looker Studio and Power BI, it can take a picture of the tab, and only after you click the extension.
• When it reads: only when the guide looks during a guided session, one reading at a time. It reads nothing in the background and nothing from tabs you have not linked, and it does not collect your browsing history.
• Which sites: access to each tool (Google Colab, Jupyter running on your own computer, Kaggle, GitHub, Google Sheets, Looker Studio and Power BI) is requested one tool at a time, the first time you link that tool, and you can refuse or remove it in Chrome at any time.
• Where the reading goes: the extension makes no network requests of its own. It hands each reading to your open BuildBank tab, which sends it to us, and we pass it to our AI provider to judge, as described above. It is then discarded. Our analytics record which tool was read and whether text or a picture was used, never the content.
• What it keeps: only which tab is linked to your session, held in your browser's session storage and cleared when you close the browser. You can stop the guide reading a tab at any time from the extension's menu, or remove the extension.

We do not sell what the extension reads, do not use it for advertising, and do not use it for any purpose other than the guide's answer to you. Our use of information received from the extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

2. Why we use it

• To create and secure your account, and to keep you signed in.
• To generate projects and tasks matched to what you told us you want.
• To take payment, and to manage your subscription.
• To understand which parts of the product work and which do not.
• To answer you when you contact us.
• To detect and prevent fraud and abuse, and to meet our legal obligations.

3. Who else receives it

We use the following service providers. They may only process your information to provide their service to us.

We do not sell your personal information, and we do not share it for targeted advertising. We may disclose information if the law requires it, or to protect our rights, users or service. If our business is transferred, your information may transfer with it, subject to this policy.

Artificial intelligence

Projects and tasks are generated using large language models operated by Anthropic and OpenAI. Generated material can be wrong or incomplete and is meant to be reviewed by you, not followed blindly. We do not use your work to train AI models, and we do not permit our providers to train their models on it.

4. Where it is stored

Our application database and backups are hosted in Ireland (European Union). Our analytics provider processes data in the United States. If you are outside those places, your information will be transferred to them. We rely on our providers' standard contractual protections for those transfers.

5. How long we keep it

• Account and project data: while your account is open, and for up to 30 days after you ask us to delete it.
• Payment records: for as long as tax and accounting law requires, typically seven years. These are not deleted on request.
• Analytics events and session recordings: according to our analytics provider's retention settings, currently no more than 12 months.
• Support and demo messages: up to two years.

6. Your choices and rights

Depending on where you live, including California, Virginia, Colorado, Connecticut, Utah, Texas and Oregon, you may have the right to know what we hold about you, to get a copy, to correct it, to delete it, and not to be discriminated against for asking.

To exercise any of these rights, email info@tekdlin.com from the address on your account. We will confirm receipt and respond within 45 days. We may need to verify who you are first. You can also appeal a decision by replying to it.

Tracking. If your browser sends a Global Privacy Control or Do Not Track signal, we do not load analytics or record your session at all. You can also block cookies in your browser; the session cookie that keeps you signed in is essential, so blocking it will sign you out.

7. Security

Traffic is encrypted in transit. Passwords are stored only as one-way hashes. We never receive or store your full card number. Stripe handles card entry directly. No service can promise perfect security, and we do not.

8. Children

BuildBank is for adults. You must be 18 or older to use it. We do not knowingly collect information from children. If you believe a child has given us information, email us and we will delete it.

9. Changes

If we change this policy we will update the date below and, for significant changes, tell you in the product or by email. Last updated 5 November 2026.

10. Contact

Tekdlin, Dallas, Texas, United States: info@tekdlin.com