b.
Operators · Builders · Investors · Since 2018
Studio b. · Privacy

Privacy Policy.

Effective May 6, 2026
§01 — Introduction

What this policy covers.

Studio b. ("we," "us," "our") is an operator-owned holding company that runs a portfolio of products and publications. This policy describes how we collect, use, and protect information when you use any Studio b. surface listed below.

We collect only what is required to deliver the surface you're using, and we never sell your data. Where a third party processes data on our behalf, we name them and the data shared.

§02 — Surfaces covered

Products and publications.

This policy applies to the following Studio b. surfaces:

§03 — AcuOps and Bolt

Connecting to your Acumatica.

AcuOps and Bolt connect to a customer's Acumatica ERP instance via the Acumatica REST and SOAP APIs to deliver monitoring, deployment, and warehouse operations.

§04 — Amplify

Engagement intelligence with an approval gate.

Amplify is a horizontal LinkedIn engagement engine sold to agencies and individual operators. The full loop is: discover public engagement signals on LinkedIn (and other platforms as they're added), score them for intent, draft a response in the operator's calibrated voice, and route every draft through a Slack approval before anything publishes. Nothing publishes without an explicit approve action; every step is recorded on an HMAC-chained, append-only audit ledger.

Discovery runs on public platform content via Bright Data residential infrastructure plus Playwright — never the operator's logged-in session, never private content. Publish actions, when they're enabled, run through official platform APIs (LinkedIn Community Management API, etc.) as the operator's authenticated identity.

Amplify persists, per tenant: the calibrated voice and brand profile, the discovered signal records, the per-signal intent scores, the drafts (approved and rejected) with the model used, the approval transcript (who approved, when, in which Slack channel), and the audit ledger. Tenants are scoped per brand; one tenant's signals, drafts, and approvals are not visible to another.

§05 — Newsletters

Markdown and LMMI.

Both newsletters are hosted on beehiiv. When you subscribe, we collect:

You can unsubscribe from either newsletter at any time using the unsubscribe link in the footer of every issue. Unsubscribing removes you from the active send list immediately. We do not share newsletter subscriber lists with third parties or use them to seed advertising audiences.

§06 — Invest with us

Accreditation and LP intake.

The Invest surface at invest.b.studio is the entry point for prospective limited partners in Studio b. LMM Bridge Fund I. Fund I is offered under SEC Rule 506(c), which permits public solicitation but requires verified accredited status before subscription.

If you submit the LP inquiry form, we collect the information you provide (name, email, accreditation status, ticket interest, and any notes you share) into our customer-relationship system, which is HubSpot. This information is used only to evaluate fit and progress an inquiry to the appropriate next step, which may include accreditation verification by a third-party verifier and review of subscription documents.

If you grant consent on the form, we may also send you Studio b. LMMI issues. You can withdraw that consent at any time via the unsubscribe link in any issue.

§07 — Enhancement Portal

Customer change requests.

The Enhancement Portal collects change requests, training questions, and feedback from authenticated users at customer organizations. Authentication is via single sign-on through the customer's identity provider (Microsoft Entra ID for current customers).

The portal stores: the request body, attachments you provide, the requesting user's identity (name, email, role within the customer organization), and the lifecycle state of the request. Requests are scoped per customer; users at one customer cannot see requests from another.

§08 — How we store and protect data

Storage and security.

§09 — Third-party processors

Who processes data on our behalf.

The following third parties process data on our behalf to deliver Studio b. surfaces. We do not sell, rent, or trade data to third parties; data shared with the processors below is used only to deliver the listed function.

ProcessorFunctionData shared
RailwayApplication hostingApplication logs, metrics, and the operational data each surface persists
Anthropic (Claude)AI capabilities inside Studio b. productsTask-scoped inputs (prompts, document fragments, code) — never persisted at Anthropic for training
HubSpotCustomer-relationship management for AcuOps, Bolt, and Invest inquiries; lead routing for AmplifyContact details, interaction history, deal/ticket records, Amplify signal/score upserts
beehiivNewsletter delivery (Markdown, LMMI)Subscriber email, name (optional), engagement events
SlackInternal notifications, customer-facing channels, and Amplify approval routingOperational notifications, messages you send to a Studio b. channel, Amplify approval transcripts
Bright DataResidential infrastructure for Amplify discovery on public platform contentOutbound requests to public LinkedIn (and other platform) URLs — no Studio b. credentials shared
LinkedIn (CMAPI)Publishing reactions, comments, and posts on behalf of Amplify operatorsThe drafted, operator-approved content and the operator's LinkedIn auth (held by LinkedIn, not by us)
Microsoft Entra IDSingle sign-on for the Enhancement Portal and internal surfacesUser identity attributes (email, name, group membership)
Google WorkspaceEmail correspondence with Studio b. staffEmail content addressed to or from Studio b. addresses
§10 — Retention

How long we keep things.

§11 — Your rights

Access, deletion, portability.

You have the right to:

To exercise any of these rights, write to hello@b.studio from the address on file. We respond within 30 days.

§12 — Changes to this policy

How we update.

We may update this policy. Material changes will be communicated via the affected surface (in-app notice for product surfaces, or a footer notice on b.studio) before they take effect. The Effective date at the top of this page reflects the most recent revision.

Questions: hello@b.studio.