> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/privacy-and-policy/the-tech-law-hangout.md).

# The Tech Law Hangout

Regularly joined by his Perkins Coie colleagues, this podcast dives deep into the essentials and innovative strategies of technology law, including intellectual property (IP), corporate, privacy, and

## Overview

**Authors:** Jordan Becker

**Publication Date:** Ongoing

**Link:** [https://perkinscoie.com/podcasts/tech-law-hangout](https://perkinscoie.com/podcasts/tech-law-hangout?utm_source=chatgpt.com)

**Keywords:** technology law, intellectual property, corporate law, privacy law, tech transactions, legal strategies, entrepreneurship

**Type:** Audio/Podcast

## Summary

Regularly joined by his Perkins Coie colleagues, this podcast dives deep into the essentials and innovative strategies of technology law, including intellectual property (IP), corporate, privacy, and tech transactions. Whether you're an innovator, entrepreneur, or corporate decision-maker in the tech industry, this podcast is your go-to resource for navigating the legal landscape. Tune in and join the conversation at The Tech Law Hangout.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://library.xrguild.org/privacy-and-policy/the-tech-law-hangout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.