Cap Table Administration Agreements

A Cap Table Administration Agreement, Not Fiduciary Law, Protects A Startup’s Equity Data

Executive Summary

Carta’s 2024 exit from secondary trading and Pulley’s December 8, 2026 shutdown show that a cap table administration agreement, not fiduciary law, is what protects a stockholder’s equity data. Delaware corporate law places the stock ledger obligation on the corporation itself under Section 224 of Title 8, and the federal transfer agent rules under Section 17A of the Securities Exchange Act of 1934 bind the administrator to the issuer, not to individual holders. Courts applying Article 8 of the Uniform Commercial Code, including the Nevada Supreme Court in Guilfoyle v. Olde Monmouth Stock Transfer Co., have declined to read an independent fiduciary duty into that statutory relationship. The result is that a startup’s protection against an administrator’s misuse of confidential ownership data, an abrupt exit from the market, or a data breach comes from the contract it signs, not from background legal doctrine.

Two events anchor the analysis. Carta closed its CartaX secondary marketplace after a company representative contacted investors using confidential cap table data without company authorization, a conflict chief executive Henry Ward called inherent to holding both the register and the trading desk. Pulley, a rival funded with more than fifty million dollars, is shutting down entirely on December 8, 2026, and is directing its customers into an assisted migration to Carta that Pulley’s own communications describe as a handover, not an acquisition, meaning no party has assumed Pulley’s existing contractual obligations.

What is settled: the administrator’s statutory duties run to the corporation. What is still being tested, and moving on a compressed timeline, is how much liability protection, audit access, and data portability a company can secure in the new agreement it must now sign, and whether reported 2026 tension inside Carta over a renewed secondary marketplace revives the structural conflict its 2024 exit was meant to close.

Detailed Findings

What triggered Carta’s exit from secondary trading

Carta shut down CartaX, its marketplace for buying and selling private company shares, after a company representative contacted investors about secondary sales without the knowledge or consent of the companies whose confidential ownership data made the contact possible.

On January 7, 2024, Linear’s chief executive Karri Saarinen reported that a Carta representative had approached a family member investor, an investor whose Linear holdings were not public, with an unsolicited offer to buy shares through CartaX. Reporting on the episode documented similar unsolicited outreach involving Airtable, Deel, Navan, Brex, and Flexport, several of them Carta cap table customers whose confidential shareholder data Carta already held under its administration contracts. Chief Revenue Officer Jeff Perry paused sales outreach within a day, stating the pause was not expected to last more than a few days, and by January 8 chief executive Henry Ward posted that Carta would exit the secondary trading business entirely.

Ward’s own account of the problem is the most useful sentence in the episode for a founder reviewing a vendor contract: because Carta had the data, he wrote, people would always worry the data was being used even when it was not, and the appearance of impropriety was, in his word, damning. Carta later sold its Liquidity brokerage unit to Public and gave up an estimated three million dollars a year in secondary trading revenue against roughly 250 million dollars from cap table administration, a trade the company judged worth making to protect the far larger business built on a promise that the data would stay walled off. Reported developments through 2026 describe internal tension over a renewed push by Ward toward a secondary marketplace under a different compliance structure, alongside senior hires with financial services regulatory backgrounds, though no public SEC or FINRA action has confirmed what that structure would actually require.

Does a cap table administrator owe fiduciary duties to stockholders

A cap table administrator ordinarily owes no independent fiduciary duty to individual stockholders. The administrator’s obligations run to the issuing corporation under statute and contract, and Delaware corporate law leaves the corporation itself, not its vendor, responsible for the stock ledger.

Section 224 of Title 8 of the Delaware Code permits a corporation to keep its stock ledger and other records on an electronic network administered by a third party, but the statute places the duty to produce a converted, legible record on the corporation, not on the platform performing the work. Section 220 of the same title gives a stockholder the right to inspect the corporation’s books and records, a right enforced against the corporation in the Delaware Court of Chancery, not against Carta, Pulley, or any other administrator. At the federal level, Section 17A of the Securities Exchange Act of 1934, codified at 15 U.S.C. Section 78q-1, and the rules the SEC adopted under it at 17 C.F.R. Section 240.17Ad-1 and following, register and regulate transfer agents, but that regulatory relationship runs between the agent and the Commission, with the issuer as client.

Courts asked to find a broader duty have been reluctant. The Nevada Supreme Court in Guilfoyle v. Olde Monmouth Stock Transfer Co., 130 Nev. 801, 335 P.3d 190 (2014), affirmed summary judgment for a transfer agent on a stockholder’s fiduciary duty theory, holding that the agent’s obligations track the statutory duty to process a submitted transfer request and nothing broader. Shaw v. Empire Stock Transfer Inc., 381 F. Supp. 3d 286 (S.D.N.Y. 2019), allowed a claim to proceed under Nevada’s codification of Uniform Commercial Code Article 8 for an agent’s failure to remove a restrictive legend, while dismissing the plaintiff’s unjust enrichment and constructive trust theories. Both cases draw the same line: a specific statutory duty survives, a general fiduciary duty does not. The practical result for a founder is that the word fiduciary belongs to the corporation’s own officers and directors under their duties of care and loyalty, not to the software vendor holding the data, and any protection beyond the statutory minimum has to be written into the administration agreement itself.

What changes now that Pulley is transferring customers to Carta

Pulley will cease all operations on December 8, 2026, and is steering its customers into what its own communications describe as an assisted migration to Carta rather than a sale, which means no successor company has assumed Pulley’s contractual obligations to the startups that used its platform.

Pulley, founded in 2020 by Yin Wu and funded with more than fifty million dollars from General Catalyst, Stripe, and Founders Fund, notified customers of the shutdown in mid September 2026. Wu told her network on September 16 that the closing of one chapter would not be the end of her or her strongest team members’ involvement in solving what she called big problems, but the company offered no public account of why a well funded rival to the largest cap table administrator in the market could not sustain the business. A Dealroom.co reporting note on the shutdown states the migration plainly: Carta is picking up Pulley’s business, but no buyer has inherited Pulley’s contracts or its obligations. That distinction carries weight for every company still on Pulley’s platform.

A November 30, 2026 deadline governs eligibility for Carta’s discounted migration offer, and reporting on the transition describes a January 31, 2027 cutoff after which Pulley’s own data access narrows. Carta already administers cap tables for an estimated 40,000 venture backed companies, close to 35 percent of the market by one industry estimate, and has operated as an SEC registered transfer agent since 2017. A rival’s exit that routes its customers to the dominant administrator concentrates a market that was already thin on alternatives, and it means the agreement a migrating company signs with Carta is a new contract negotiated from whatever position the company still holds before the promotional terms expire, not a continuation of whatever protections it negotiated with Pulley.

Which liability and audit terms deserve negotiation

The administration agreement should fix a liability cap tied to fees paid rather than to the value of the equity records at stake, require indemnification for the administrator’s own errors in 409A reports and option grants, and give the company an enforceable right to audit change logs against the board consents and grant agreements that authorized each entry.

A standard of care provision should state plainly who bears the cost when an administrator’s own error, a misstated 409A valuation or a missed 83(b) election deadline caused by the platform rather than the company, creates tax exposure for a founder or an employee. An audit trail requirement tying every cap table change back to its authorizing document is not a theoretical protection: reporting on the Pulley migration recommends that a company reconcile its exported data against board consents, grant agreements, and 409A reports precisely because most contracts do not require the vendor to maintain that linkage automatically.

An assignment and change of control clause requiring the company’s consent before the agreement can transfer to a successor vendor closes the exact gap the Pulley migration exposed. Because Pulley’s move to Carta was structured as a customer handover and not a formal assignment, no consent requirement applied, and each company was left to negotiate a new agreement rather than inherit protections it may have already won. Insurance minimums covering errors and omissions and cyber liability, and a pricing term that survives beyond the first year, matter for the same reason: migration offers run generous in the promotional year, and reporting on the transition specifically flags the second year, once promotional terms lapse, as the number that actually governs the relationship.

Redlining cap table and equity administration contracts across three decades of technology company counseling, the clause a company’s own team deletes first to save review time is almost always the audit trail provision, the one clause that would have mattered most the day an administrator gave its customers two months’ notice before disappearing.

What data protection terms govern personal and financial information

A cap table administrator processes Social Security numbers, tax identification numbers, and banking details for tax withholding and 409A reporting, which makes it a service provider or contractor under the California Consumer Privacy Act as amended by the California Privacy Rights Act, and the agreement must include the contract terms Section 1798.140 of the California Civil Code requires before that data can be shared at all.

Cal. Civ. Code Section 1798.140(ag) defines service provider and Section 1798.140(j) defines contractor, and either designation obligates the administration agreement to prohibit the vendor from selling or sharing personal information, restrict use to the purposes specified in the contract, and require deletion or return of personal information on request or at termination. Cal. Civ. Code Section 1798.82 sets the breach notification standard, requiring disclosure in the most expedient time possible and without unreasonable delay, a standard the agreement should convert into a specific number of days, because a statutory default measured only in reasonableness gives a company no fixed date to plan around when the vendor itself is winding down, as Pulley now is.

Stockholders scattered across states bring Virginia’s Consumer Data Protection Act and Colorado’s Privacy Act into play as well, each with processor contract requirements that substantially track the California model. Beyond the statutory floor, the agreement should require a current SOC 2 Type II attestation, name and require notice before adding any subprocessor, and specify encryption standards for data at rest and in transit. None of this is optional once a company recalls that the confidential data set a Carta employee misused in January 2024 includes exactly the category of information these statutes protect.

How should a wind down and data portability clause work

The agreement should guarantee a minimum notice period before the vendor may cease operations, a complete and independently verifiable export in a specified format, and continued read access to the underlying records for a fixed period after termination, terms that would have given Pulley’s customers more than the roughly twelve weeks between the September 16 shutdown announcement and the December 8 cessation of service.

Guidance published on the Pulley transition recommends that a company export its complete equity data independently and reconcile it against source documents before selecting a destination platform, advice that is only necessary because most cap table contracts do not already guarantee that access on a fixed timeline. A wind down clause should specify the export format as a structured file the company can load into a competing platform rather than a static report, require the vendor to preserve access to the board consents, grant agreements, and valuation reports behind each cap table entry, and fix a minimum notice period, measured in months, before the vendor may terminate service entirely.

Absent that clause, a company’s only position is whatever transition window the exiting vendor chooses to offer, which is exactly where Pulley’s customers found themselves against a November 30, 2026 discount deadline and a January 31, 2027 data cutoff that Pulley, not the customer, set.

Want more industry insights? I publish daily analysis on the intersection of deep tech and venture law.

Subscribe to The Innovation Attorney on Substack

Open Questions

Whether Carta’s reported 2026 push back toward a secondary marketplace, this time under what sources describe as a more compliant and transparent structure, recreates the conflict that forced the 2024 exit matters directly to any company signing a new administration agreement with Carta during the Pulley migration, since the contract terms that would protect against a repeat of the 2024 episode are the same terms a company should negotiate now.

Whether the SEC will treat a transfer agent’s secondary trading arm as requiring separate broker dealer or alternative trading system registration, rather than relying on the issuer relationship alone to police the conflict, affects how much protection federal regulation actually adds on top of whatever the administration agreement itself provides.

Whether state privacy regulators will classify Social Security numbers and tax identification numbers held for 409A and withholding purposes as sensitive personal information carrying heightened contractual requirements beyond the standard service provider terms bears on how far a company needs to push the data protection language in its next renewal.

Whether Pulley’s exit invites scrutiny of market concentration in cap table administration, where one vendor now serves an estimated 35 percent of venture backed companies, or whether regulators and customers simply accept the consolidation as the outcome of a market that rewards one shared system for companies and their investors alike, will shape how much pricing and contract position administrators hold once promotional terms expire.

Whether a company that signed its cap table agreement years before the Pulley shutdown can renegotiate audit, liability, and wind down terms into that existing contract without triggering a full re-papering, or whether the practical path for most companies is to wait for the next renewal cycle, determines how quickly the protections described in this report reach the startups that need them.

Source List

1. Del. Code Ann. tit. 8, Section 224 (2024): governs electronic corporate records including the stock ledger and establishes that the corporation, not its vendor, bears responsibility for the stock ledger’s form.

2. Del. Code Ann. tit. 8, Section 220 (2024): governs stockholder inspection rights, enforceable against the corporation.

3. Securities Exchange Act of 1934 Section 17A, 15 U.S.C. Section 78q-1, and 17 C.F.R. Section 240.17Ad-1 et seq. (2024): federal registration and regulation of transfer agents.

4. Cal. Civ. Code Sections 1798.100 through 1798.199.100, including Section 1798.140 and Section 1798.82 (California Consumer Privacy Act as amended by the California Privacy Rights Act): defines service provider and contractor obligations and sets the breach notification standard.

5. Guilfoyle v. Olde Monmouth Stock Transfer Co., 130 Nev. 801, 335 P.3d 190 (2014): Nevada Supreme Court holding limiting a transfer agent’s duty to its statutory scope.

6. Shaw v. Empire Stock Transfer Inc., 381 F. Supp. 3d 286 (S.D.N.Y. 2019): federal district court decision on transfer agent liability under Article 8 of the Uniform Commercial Code as codified in Nevada.

7. Henry Ward, statement on Carta’s exit from secondary trading, reported January 8, 2024: primary source for the company’s own account of the conflict of interest.

8. TechCrunch, “Pulley, a Carta rival, is shutting down,” September 16, 2026: reports the shutdown date and the migration to Carta.

9. Dealroom.co news note, “Pulley shutting down (cease ops 8 Dec 2026); Carta customer migration, not an acquisition,” September 2026: clarifies that Carta did not assume Pulley’s contractual obligations.

10. Technori, “Cap Table Software Loses a Rival, and Founders Get a Deadline,” September 2026: reports the November 30, 2026 and January 31, 2027 transition deadlines and the specific contract terms founders should examine.

11. Wiki.private.law, “Carta: Cap Table, Fund Administration and Data Privacy,” 2026: background on Carta’s transfer agent registration and market share.

12. Cakeequity, “Pulley Is Shutting Down: How to Transition Your Cap Table,” 2026: practical guidance on data export and reconciliation during the migration.

Bibliography

Cakeequity. “Pulley Is Shutting Down: How to Transition Your Cap Table.” Cake Equity Guides, 2026.

Cal. Civ. Code Sections 1798.100 to 1798.199.100 (West, as amended by the California Privacy Rights Act of 2020).

Dealroom.co. “Pulley Shutting Down (Cease Ops 8 Dec 2026); Carta Customer Migration, Not an Acquisition.” Dealroom News, September 2026.

Del. Code Ann. tit. 8, Section 220 (2024).

Del. Code Ann. tit. 8, Section 224 (2024).

Fortune. “Carta Pauses Sales Outreach After Customer Data Accusation.” Fortune, January 8, 2024.

Guilfoyle v. Olde Monmouth Stock Transfer Co., 130 Nev. 801, 335 P.3d 190 (2014).

Securities Exchange Act of 1934 Section 17A, 15 U.S.C. Section 78q-1 (2018).

Shaw v. Empire Stock Transfer Inc., 381 F. Supp. 3d 286 (S.D.N.Y. 2019).

TechCrunch. “After Taking a Credibility Hit, Carta Announces It Is Exiting the Secondaries Business: We Have Decided to Prioritize Trust.” TechCrunch, January 8, 2024.

TechCrunch. “Pulley, a Carta Rival, Is Shutting Down.” TechCrunch, September 16, 2026.

Technori. “Cap Table Software Loses a Rival, and Founders Get a Deadline.” Technori, September 2026.

Transfer Agent Regulations, 17 C.F.R. Section 240.17Ad-1 et seq. (2024).

Wiki.private.law. “Carta: Cap Table, Fund Administration and Data Privacy.” Private Law Wiki, 2026.

Wu, Yin. Post on Pulley’s shutdown. LinkedIn, September 16, 2026.

Interested in analysis about the intersection of tech, policy and the law? Check out my Substack channel. https://theinnovationattorney.substack.com/