Privacy Policy

JurisBuild (“we,” “us”) provides case management software for law firms. This policy describes how we handle information collected through jurisbuild.com. Data inside a law firm’s JurisBuild workspace is governed by our agreement with that firm, not by this policy. One exception is set out below and governs regardless of any firm agreement: data JurisBuild receives from Google APIs is handled exactly as the “Google user data” section describes.

If you request a demo or book a walkthrough, we collect what you submit: firm name, your name, work email, phone number, and any additional details you choose to provide in the form, along with technical details of the submission (IP address, browser user agent, timestamp) used for security and abuse prevention.

We use privacy-respecting analytics (Vercel Analytics, plus Vercel Speed Insights for performance monitoring) to understand aggregate site usage. We do not use advertising trackers on this site.

To respond to your inquiry, schedule and conduct walkthroughs, and follow up about JurisBuild. We do not sell your information, and we do not share it with third parties except service providers that help us operate this site (hosting, email, scheduling), bound by their own confidentiality obligations.

JurisBuild offers an optional Google Calendar connection. A staff user connects their own Google account from Settings inside the JurisBuild portal, and nothing is read from Google until that user completes Google’s consent screen. This section describes how JurisBuild handles data received from Google APIs, and it applies whether the account was connected by an individual or on a firm’s instruction.

The permissions we request, and why

• calendar.events.readonly on read-only connections: read the events on the connected calendar so they appear beside the firm’s events in JurisBuild.
• calendar.events on two-way connections: the same, plus create and update in that Google calendar the events the user schedules in JurisBuild, and remove them when the user deletes them.
• calendar.calendarlist.readonly: read which calendars the account holds and what color each one is, so a Google event renders in JurisBuild the color the user already sees in Google.
• openid, userinfo.email, and userinfo.profile: show which Google account is connected on the connection card, so the user can tell one account from another.

We do not request access to Gmail, Drive, Contacts, Photos, or any other Google service, and we request no permission to create, delete, or share calendars.

What we store

For each event on the connected calendar we store its title, start and end time, all-day flag, location, video meeting link, color, and Google’s event identifier, for a rolling window of 60 days back and one year ahead. We do not store attendees or guest lists, event descriptions, or attachments.

How we use Google data

Only to operate the calendar feature for the user who connected the account: showing that user their own calendar inside JurisBuild, sending that user the reminders they set for their own events, and, on two-way connections, writing back the events they create in JurisBuild. We do not use Google user data for advertising, we do not sell it, we do not share it with other firms or with any other JurisBuild customer, and we do not use it to build a profile of anyone.

Google user data and AI

JurisBuild includes an AI assistant, Scribe. Data received from Google APIs is not sent to Scribe, is not sent to any third-party AI or machine-learning service, and is not exposed to the AI connectors described below. Neither raw nor derived Google user data is used to develop, train, improve, or evaluate any foundational or generalized artificial intelligence or machine-learning model, whether ours or anyone else’s.

Who can see it, and for how long

No JurisBuild employee reads Google user data except with the user’s explicit permission (for example, to resolve a support request that user raised), where it is necessary for security purposes such as investigating abuse, or where the law requires it. Disconnecting the account in Settings, or removing JurisBuild at myaccount.google.com/permissions, revokes the token at Google, deletes the stored authorization and deletes every mirrored event. A removal made at Google is detected the next time JurisBuild refreshes the connection, at most a day later. JurisBuild keeps only the account’s email address and a record of which of its own events it had placed on that calendar, so reconnecting does not create duplicates.

Limited Use

JurisBuild’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

We keep inquiry information as long as needed to handle your request and our business records. You can ask us to correct or delete your inquiry information at any time by emailing info@jurisbuild.com.

Firms can connect AI assistants such as Claude or ChatGPT to their JurisBuild workspace. Those connections authenticate through OAuth as an individual staff user; the assistant reads only what that user can already see in the portal, and JurisBuild receives only the requests the assistant makes, not the user’s conversations. Workspace data accessed this way remains governed by our agreement with the firm. Staff can revoke a connection at any time from Connected Apps in their portal settings, and deactivating a staff account ends its connections immediately. See AI Connectors for setup and details. Data received from Google APIs is outside these connections: a connected assistant cannot read it, and it is never passed to one.

Information is encrypted in transit and at rest. See our security overview for how we protect data across the platform.

If we change this policy, we will update this page and the date above. Questions: info@jurisbuild.com or 718-355-1812.