Skip to content

GoCodebook Privacy Policy

Effective Date: August 13, 2026

At GoCodebook, operated by GoCodebook Inc, a Delaware corporation ("Company," "we," "our," or "us"), we respect your privacy and are committed to protecting it. Please read this Privacy Policy to learn how we collect, use, share, and safeguard your personal data when you use our Services.

By using or accessing the GoCodebook Services, you agree to the practices described below. This Privacy Policy is part of our Terms of Service. Any capitalized terms not defined here have the meanings given in the Terms of Service.

We may update this Privacy Policy from time to time. When we do, we will notify you by posting the revised version on our website, updating the "Effective Date," and, where appropriate, providing additional notice (such as by email). Continued use of our Services after changes become effective constitutes acceptance of the revised Privacy Policy.

Table of Contents

  1. What This Privacy Policy Covers
  2. Personal Data We Collect
  3. Categories of Sources of Personal Data
  4. How We Use Personal Data
  5. How We Share Personal Data
  6. Cookies, Tracking, and Advertising
  7. Data Security and Retention
  8. Children's Privacy
  9. State and International Privacy Rights
  10. Contact Information

1. What This Privacy Policy Covers

This Policy covers how we treat personal data that we collect when you use the Services. "Personal Data" means information that identifies, relates to, or could reasonably be linked to an individual. This Policy does not cover the practices of third parties we do not control.

2. Personal Data We Collect

We may collect the following categories of Personal Data (with examples):

  • Profile or Contact Data: Name, email address, phone number, employer, job title.
  • Account Credentials: Username, hashed and salted passwords.
  • Payment Data: Payment card type, number, billing address, email (processed securely by our payment providers).
  • Device/Usage Data: IP address, device type, operating system, browser type, and your interactions with our Services — including which pages you arrived on, which pages of our code library you viewed, and where you came from (for example, a search engine or a link on another site).
  • Geolocation Data: General location inferred from IP address.
  • Communications: Emails, surveys, support messages, or inquiries you send us.
  • User Content: Prompts, uploaded files, and other data you submit for AI processing.
  • Chat Assistant Conversations: If you use the Ask AI chat panel on our pages, we store the messages in that conversation and the AI's answers — including when you are not signed in — so the conversation continues as you move between pages and after you reload, and so past conversations can be reopened from the panel's history. When you are not signed in, the conversation is linked to a random identifier stored in your browser, not to your name. We do not store your IP address or browser user-agent string with it; only an irreversible hash of your IP, used to detect abuse. When you are signed in, conversations are saved to your account as history. Photos you attach to a question are stored with the conversation. If you choose to tell the assistant who you are — your name, your role (for example homeowner, real-estate agent, architect, or contractor), or what your project is — we store that with your contact record and use it to tailor the assistant's answers and suggestions to you. Sharing it is optional and can be skipped. See Section 7 for how long conversations are kept.
  • Property Lookup Data: When you ask about a specific street address, select a parcel on the zoning map, or share your device location for a nearby lookup, we send that location to a geocoding provider and to property-records providers so we can answer for the right parcel. What comes back is drawn from public records: zoning designation, parcel boundaries and identifiers such as the assessor's parcel number, lot and building characteristics, and assessor and recorder data that can include the recorded owner's name, the last sale price and date, and the assessed value. You can look up a property you do not own, so this data often describes someone other than you. See Section 7 for what we keep and for how long.

3. Categories of Sources of Personal Data

We collect Personal Data from:

  • You – when you create an account, submit prompts, upload documents, or contact us.
  • Automated Means – such as cookies, analytics tools, and server logs.
  • Third Parties – including payment processors, analytics providers, marketing partners, and anti-abuse providers. To keep our free AI features available, we use Cloudflare Turnstile to tell real visitors apart from automated traffic; Cloudflare receives your IP address and browser signals to assess that request, and we do not store the result.
  • Public Sources – such as government or professional directories, and public property records (county assessor and recorder data, and municipal zoning and parcel maps) returned when an address is looked up.

4. How We Use Personal Data

We use Personal Data to:

  • Provide, maintain, and improve the Services.
  • Process transactions and billing.
  • Customize outputs, search results, and recommendations.
  • Respond to inquiries, provide customer support, and communicate updates.
  • Improve AI accuracy, safety, and performance through aggregated analysis.
  • Conduct security monitoring, fraud prevention, and compliance checks.
  • Market our Services (with your opt-out options available).
  • Comply with legal obligations.

How we personalize the emails we send you. If you give us your email address — in the chat panel, in a form, or by creating an account — we may write to you individually rather than as part of a mass mailing. Those messages draw on what you have already shared with us: the questions you have asked and the answers we gave, in any of our chat surfaces and in any project workspace you create; your earlier email exchanges with us; your activity on our site, such as which pages you arrived on and which pages of our code library you viewed; and, if you have an account, your plan and how much of it you have used. We use AI to compose these messages. Some are reviewed and edited by a member of our team before they are sent, and others may be sent automatically; either way GoCodebook is responsible for the message, and your reply reaches our team. We do this so the message answers your actual situation instead of repeating a generic pitch.

Every message we send includes a one-click unsubscribe link. Unsubscribing stops promotional email — such as messages about plans, pricing, or upgrading — immediately. We may still reply to a question you asked us, or send you something you specifically requested (such as the written summary of your chat), because those are answers to you rather than advertising.

We do not sell your conversations, and we do not use them to target advertising to you on other companies’ websites.

5. How We Share Personal Data

We may share Personal Data with:

  • Service Providers – hosting, payment processing, analytics, support, and marketing.
  • Analytics Partners – who help us understand how users engage with our Services.
  • Advertising Partners – for targeted ads (unless you opt out).
  • Affiliates – within GoCodebook Inc.
  • Authorities – when required by law, regulation, or legal process.
  • Business Transfers – if we undergo a merger, acquisition, or sale of assets.

We may also use aggregated or de-identified data that cannot reasonably identify you for analytics, research, and product improvement.

6. Cookies, Tracking, and Advertising

We use cookies and similar technologies (e.g., web beacons, pixels) to:

  • Enable core features of the Services.
  • Remember your settings and preferences.
  • Measure website traffic and performance.
  • Deliver relevant ads (where permitted).

You can control cookies through your browser settings, though disabling them may limit functionality.

We currently do not respond to "Do Not Track" signals.

7. Data Security and Retention

We use reasonable physical, technical, and administrative safeguards to protect your data. However, no method of storage or transmission is 100% secure.

We retain Personal Data as long as necessary to provide the Services, comply with law, resolve disputes, or enforce agreements. Some anonymized data may be retained indefinitely for research and improvement.

Chat Assistant conversations. How long we keep a conversation from the Ask AI chat panel depends on whether you are signed in. If you are signed in, your conversations are saved to your account as history — you can reopen them from the panel — and they remain until you close your account; closing your account deletes them. If you are not signed in, the identifiers that could link the conversation back to you — the random identifier in your browser, the session's access token, and the hashed IP address — are erased after 30 days of inactivity, and cannot be recovered. What remains of the visit record is not identifying: which page you arrived on, where you came from, and coarse browser information such as “Chrome”. The conversation text itself is retained after that point in de-identified form, no longer linked to your browser or device, and is used for product improvement and market research (aggregate analysis of what visitors ask). That aggregate research use applies to de-identified conversations; if you gave us your email address, see Section 4 for how we may use your conversation to write to you individually. If you gave us your email address in the panel, the conversation stays linked to your contact record so we can send the summary and resume link described below. Starting a new conversation in the panel begins a fresh thread, but your previous conversations remain reachable from the panel's history on that browser (and, when signed in, from your account) until the schedules above run out. To make conversations unreachable from a browser, clear that browser's site data for gocodebook.com; to have a stored conversation or contact record deleted, contact us at support@gocodebook.com.

Photos you attach. A photo attached to a question is stored at an unguessable address and follows the conversation, with one difference: photos are not kept for the de-identified research retention described above. A photo attached while not signed in is deleted after the session's 30 days of inactivity; a photo that was uploaded but never sent is deleted within about a day; and a photo in a signed-in conversation remains with your account history and is deleted shortly after that conversation — or the account — is deleted. We also strip camera metadata (such as GPS location) from JPEG photos before storing them.

Shared conversations. If you create a share link for a conversation (from the chat panel or the signed-in chat), a copy of that conversation is saved as a snapshot for others to read. Creating a share link is always your action; we never publish a conversation on our own. Which people can open the link depends on your account: if you are signed in and belong to an organization on GoCodebook, the link is private to your organization — only other signed-in members of that organization can open it, and it does not expire on its own. Otherwise, the link is public — readable by anyone who has it — for 30 days, after which it expires.

Property lookups. How long we keep a lookup depends on where you ran it. If you are signed in and look up a property in the chat or on the zoning map, we save that property to your account — including the records described in Section 2 — so it stays in your recent properties and you can return to it; it remains until you delete it or close your account. If you are not signed in, we do not keep our own copy of the records at all: they are used to compose the answer and then discarded. What does persist in that case is the conversation itself — the address you typed, and whatever the answer repeats back, which can include owner, sale, and assessment figures — retained on the conversation schedule above: linked to your browser for up to 30 days of inactivity, and in de-identified form after that. In every case the address and the records retrieved for it are sent to our AI provider to generate the answer, and are retained by that provider as part of the conversation's processing history, under the provider's own retention terms, so that follow-up questions can build on earlier answers.

Follow-up summaries. If you gave us your email address in the chat panel, we may send you a written summary of that conversation once it ends, so you have a record of the answers and can pick the thread back up. The email contains a link that reopens your own conversation in the chat panel; that link works for 30 days, is tied to that one conversation, and is stored only in hashed form on our servers. Every such email includes an unsubscribe link, and unsubscribing stops these summaries immediately. We send a summary of a given conversation only once.

8. Children's Privacy

Our Services are not intended for children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect Personal Data from children. If we learn that we have, we will delete it promptly.

9. State and International Privacy Rights

Depending on where you live, you may have rights under applicable laws, such as:

  • California (CCPA/CPRA) – right to know, delete, correct, and opt out of sale/sharing of data.
  • Nevada – right to opt out of the sale of certain personal data.
  • European Economic Area/UK – rights to access, rectify, erase, restrict, port, and object to processing under GDPR.

To exercise rights, contact us. We may require verification of your identity.

10. Contact Information

If you have questions or concerns about this Privacy Policy or our data practices, please contact us at:

GoCodebook Inc

95 3rd Street, 2nd Floor

San Francisco, CA 94103, United States

Contact Us

Phone: +1 (415) 323-0019

By using GoCodebook, you acknowledge that you have read and understood this Privacy Policy.