Effective 3 September 2026

This policy covers the LexBlog Library Connector, the Model Context Protocol (MCP) service operated by LexBlog, Inc. that lets an AI assistant such as Claude search the LexBlog Library of law-firm publications on your behalf. It is specific to that connector. Your use of lexblog.com and the Library website is covered by our general Privacy Policy (https://www.lexblog.com/privacy/).

If you have not connected the LexBlog Library Connector to an AI assistant, none of this applies to you.

What we receive when you sign in

The connector has no accounts and no passwords of its own. You sign in with Google, and we request three standard scopes — openid, email and profile. From the identity token Google returns, we keep four fields:

– your email address, which is the identity your access and your subscription attach to;
– your name, as Google supplies it;
– your Google account identifier (the sub claim), a stable id Google assigns you;
– your hosted domain (the hd claim), if your account is a Google Workspace account.

We use these for one purpose: to know which account is making a request, so we can apply the right access level and the right query allowance. We do not use them to build a profile of you, and we do not combine them with data from anywhere else.

Google user data. Our use of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. We do not sell Google user data, use it for advertising, or use it to train AI models.

What we store

Three things, all on a single encrypted volume in the United States:

1. Sign-in state — the four identity fields above, plus the OAuth tokens that keep you signed in between sessions.
2. Subscription state — your access tier, and, if you are a paying customer, your Stripe customer and subscription identifiers.
3. Usage counters — how many queries your account has made in the current period. This is a count, not a history.

What we do not store

We do not log your searches. The words you search for, the questions you ask, and the articles returned to you are not recorded, not retained, and not associated with your account. Our usage counters record that a query happened, never what it was.

We never receive your payment card details. Those go directly to Stripe.

Server logs

Like any web service, our servers record each request: the time, the HTTP method and path, the network address the request came from, and an opaque session identifier. These are diagnostic records held briefly by our hosting provider and not archived by us. They do not contain query text.

Our systems send operational alerts to LexBlog staff — a service outage, a failing sign-in handshake, an account refused at its limit. An alert may name the account involved so we can respond to it.

Payments

Paid subscriptions are handled by Stripe (https://stripe.com/privacy). When you subscribe, Stripe collects your billing details and shares with us a customer identifier, a subscription identifier and status, and the email address you gave Stripe at checkout.

Your subscription attaches to the Google account you sign in with, never to the address you typed at checkout — those are often different, and we treat the signed-in one as authoritative. We keep the checkout email only for a payment that has not yet been matched to a sign-in, so you can claim it; unclaimed payment records are discarded after 30 days.

Issue reports

The connector offers a tool for reporting bad metadata — a wrong author, a broken link, a mis-categorised post. If you file one, your email address is attached to the report so that LexBlog’s data-quality team can follow up, and the report is stored in LexBlog’s editorial systems. Reporting is currently limited to LexBlog accounts; searching and reading are not.

Who we share information with

Our service providers, and no one else:

– Google — sign-in
– Stripe — payments
– Fly.io — hosting, in the United States

We do not sell your information, share it with advertisers, or disclose it to third parties for their own purposes. We may disclose information where the law requires it, or to protect the rights and safety of LexBlog and its users.

How long we keep things

Access tokens expire after an hour and sign-in sessions after 30 days of inactivity. Unclaimed payment records are discarded after 30 days. Usage counters are overwritten each period and keep no history. Subscription records are kept while your subscription is active and afterwards as our tax and accounting obligations require.

Your choices

Disconnect at any time. Remove the connector from your AI assistant, and revoke its access at https://myaccount.google.com/permissions. Revoking there immediately stops the connector from identifying you.

Ask us to delete your data. Email us at the address below and we will delete your sign-in and usage records, and your subscription records to the extent we are not required to keep them, within 30 days. Depending on where you live you may also have the right to access, correct, or export the information we hold, and to object to how we use it. Ask, and we will help.

Children

The connector is a professional research tool and is not directed at anyone under 16. We do not knowingly collect information from children.

Changes

If we change this policy we will update the date at the top, and, for a change that meaningfully affects you, tell you through the connector itself.

Contact

LexBlog, Inc.
library@lexblog.com