In short
- We never sell your data or use it for ads.
- Your work is never used to train AI.
- Voice and screen looks are used live, then discarded.
- Email us to delete your data at any time.
This summary is not the full text. The sections below are.
01What we collect
Your account. Your email address, name and how you signed in. If you use Google or LinkedIn, we receive your name, email address and profile picture from them and use these only to create and run your account. If you use a password, we store only a one-way hash of it. You can also add a username, bio, country and profile photo.
What you do in BuildBank. The role, industry, level, goal and tools you choose, the work you produce, and any message you send us, such as a demo request.
Usage. Pages viewed, features used, clicks and timings, keyed to a pseudonymous ID rather than your email, and never the content of your work. We also record how the interface is used, to find where it fails people. Text you type is masked before it leaves your browser, and card fields sit in a Stripe frame that recordings cannot see. We receive your IP address, browser, device type and approximate location.
Voice. Speaking is always optional. A short clip you record goes to our transcription provider, the text comes back to you, and the audio is discarded without being stored. The text you keep is saved with the project it produced. In a live voice session, either the talked-through assessment or the project guide, your voice is processed as you speak, is not recorded, and no transcript is kept. The assessment saves only your answers, as if you had tapped them. We keep only that a session happened and how long it lasted, which is how we limit cost.
Build Studio. Your code is saved to your account and runs in your browser, not on our servers. Files you add from your computer stay in your browser. When you ask the AI pair for help, or the project guide looks at your work, the step, your code and its output, and anything you choose to show (a shared tab or an extension reading) go to our AI provider. Guide looks are judged in memory and then discarded. We record that you asked or looked, what it cost, and how many looks you used each day, not the content.
Cookies. One essential cookie keeps you signed in. PostHog sets analytics identifiers, and Stripe sets its own cookies at checkout to prevent fraud.
02The BuildBank Guide extension
The extension is optional and has one purpose: letting the project guide see the notebook or data tool you are working in, during a guided session you started. It works only with a BuildBank account.
It reads only a tab you have linked to your session, and only when the guide looks. Depending on the tool, it reads the tab title, up to twelve notebook cells near your cursor with their outputs, the GitHub file or changes you have open, or the sheet name and formula bar in Google Sheets. For Google Sheets, Looker Studio and Power BI it can take a picture of the tab, and only after you click the extension. It asks for access to those tools (Google Colab, Jupyter on your own computer, Kaggle, GitHub, Google Sheets, Looker Studio and Power BI) when you install it, and never for any other site. Having access is not reading, and you can withhold or remove access to any of these sites in Chrome at any time. It reads nothing in the background, nothing from tabs you have not linked, and does not collect your browsing history.
The extension makes no network requests of its own. It hands each reading to your open BuildBank tab, which sends it to us and to our AI provider to judge. It is then discarded. Our analytics record which tool was read and whether text or a picture was used, never what it contained. The extension stores only which tab is linked, in session storage that clears when you close the browser. You can unlink a tab from the extension's menu or remove the extension at any time.
We do not sell what the extension reads, use it for advertising, or use it for anything 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 the Limited Use requirements.
03How we use it
To create, secure and run your account; to generate projects that match what you asked for; to take payment and manage your plan; to learn which parts of BuildBank work; to answer you; and to prevent fraud and abuse and meet our legal obligations.
04Who receives it
These providers may use your information only to provide their service to us.
- Amazon Web Services
- All application data, for hosting, the database and backups.
- Stripe
- Your name, email and the card details you give Stripe directly, for payments.
- PostHog
- Pseudonymous usage events, session recordings and IP address, for product analytics.
- Anthropic
- Your project choices and what you write or say about them, project content, your code and output when you ask the AI pair, and what the guide looks at, including a shared tab or extension reading. Used to generate projects, answer the AI pair and judge guide looks.
- OpenAI
- Project text, voice clips, and your voice in live sessions. Used for search and matching, transcription and live voice.
- Google, LinkedIn
- Your sign-in identity, if you choose them.
- Discord
- What you post in our community, under Discord's own terms.
We do not sell your personal information or share it for targeted advertising. We do not use your work to train AI models, and we do not let our providers do so. AI-generated material can be wrong, so review it before you rely on it.
We may disclose information when the law requires it or to protect our rights, users or service. If our business is transferred, your information may move with it, under this policy.
05Where it is stored and for how long
Our database and backups are in Ireland (European Union). Our analytics provider processes data in the United States. If you are elsewhere, your information is transferred there under our providers' standard contractual protections.
We keep account and project data while your account is open and for up to 30 days after you ask us to delete it. Payment records are kept as long as tax and accounting law requires, typically seven years, and are not deleted on request. Analytics and session recordings are kept for up to 12 months, and support and demo messages for up to two years.
06Your rights and choices
Depending on where you live, including California, Virginia, Colorado, Connecticut, Utah, Texas and Oregon, you can ask to know what we hold about you, get a copy, correct it or delete it, and we will not treat you differently for asking. Email info@tekdlin.com from the address on your account. We confirm receipt and reply within 45 days, may need to verify who you are first, and you can appeal a decision by replying to it.
If your browser sends Global Privacy Control or Do Not Track, we do not load analytics or record your session at all. You can block cookies, but blocking the sign-in cookie signs you out.
07Security, children and changes
Traffic is encrypted in transit, passwords are stored only as one-way hashes, and Stripe handles card entry, so we never receive your full card number. No service can promise perfect security, and we do not.
BuildBank is for adults. You must be 18 or older to use it, and we do not knowingly collect information from children. If you believe a child has given us information, email us and we will delete it.
If we change this policy we update the date at the top and, for significant changes, tell you in the product or by email.
Questions?
Email info@tekdlin.com. BuildBank is run by Tekdlin, Dallas, Texas, United States.