This website
You can read Buyout Desk without an account. The site does not currently show a newsletter signup form or any other form that asks for your name or email address. A staff-only administration area uses Google sign-in; it is not part of the public site.
The site uses Google Analytics to measure traffic, with IP anonymization turned on. Google Analytics can set cookies or similar identifiers in your browser and sends page-view information to Google, which handles it under its own terms. The site’s code can also load the LinkedIn Insight Tag when it is configured; if it is switched on, LinkedIn receives page-view information under LinkedIn’s own terms. Neither tag is loaded in the administration area. The site is hosted by Vercel, which processes ordinary web-server request information, such as IP address and the page requested, to serve the site.
The site also keeps a page you arrived on, the site that referred you and any campaign tags in the address (such as utm_source) in your browser’s session storage for the length of your visit.
You can limit or block analytics cookies and site storage in your browser settings.
Our LinkedIn Company Page publishing
On business days Buyout Desk may publish one post, with one picture, to its own LinkedIn Company Page about that day’s news, using LinkedIn’s official API. The post is made only as the Company Page, never as or on behalf of an individual.
The connection asks LinkedIn for only these things: to create that post, to upload its picture, to read the Page’s own recent posts so it does not post a duplicate and can confirm a post exists, and to renew its access. It does not request member profiles, followers, commenters or analytics, and it does not send messages, comment, react or run advertising. Responses from LinkedIn are used while the task runs and are then discarded, except for the records described below.
A Page administrator approved the connection once on LinkedIn’s consent screen, for exactly two permissions: creating posts for the Page and reading the Page’s own posts. Each run obtains a short-lived access token that is kept only in memory and discarded. The longer-lived refresh credential behind it, and the application’s client secret, are kept in a protected secret store of the cloud environment that runs the task; that store adds them only to requests sent to LinkedIn’s token address, and they are not kept in source control. LinkedIn’s authorization lasts about a year, after which, or if LinkedIn ends or refuses it, an administrator must approve again. An administrator can revoke the connection at any time in LinkedIn’s settings.
What we keep
For each day, we keep a record with the Page identifier, the date, fingerprints (hashes) of the post text and picture, the LinkedIn post identifier and link, timestamps, a status, and the website version, edition and lead story the post was based on. We also keep records of any refusal LinkedIn returned and of connection checks (the operation, status code and time, a non-reversible fingerprint of the credential, token lifetimes and counts). Drafts of the post text and picture, with the public deal facts they were written from, are kept as well. The records are not designed to contain passwords or access tokens.
These records are kept as an append-only history in a private GitHub repository. They are not deleted automatically, and removing something from that history is a manual step that is not automated. The post text and picture are processed by the Claude cloud environment (Anthropic) and GitHub while the task runs, and by LinkedIn once posted. How LinkedIn, Anthropic, GitHub, Google and Vercel keep and delete information is governed by their own terms; we do not control it.
Contact
For questions about this policy or about information relating to you, email hello@buyoutdesk.com or write to Buyout Desk, c/o Alta Partners, LLC, 9415 Culver Blvd., Culver City, CA 90232, United States.