Your Code Now Syncs to SpaceX. The Data Terms Don't Exist.

Somewhere this week, an agency owner will open a client’s security questionnaire and hit a standard question that they can’t answer: Is our source code being used to train AI?

How did we get here? On August 14, SpaceX completed its acquisition of Anysphere, the company behind the Cursor editor, per an 8-K filed with the SEC. The transaction, first announced June 16, was textbook: X67 Inc., a wholly-owned subsidiary of SpaceX, merged into Anysphere, and Cursor survived as a wholly-owned subsidiary of SpaceX. Shares of Cursor were converted to roughly 389 million shares of SpaceX Class A stock for an implied equity value of $60 billion. Cursor now sits inside a division named SpaceXAI.

Three days later, Cursor turned on Origin, its new platform for hosting source code, but not as a select group of invitees, nor as a beta available on a voluntary basis. Instead, per Cursor’s changelog, Origin is “rolling out in early beta to all paid plan users starting today, except enterprise orgs whose admins opt out.”

Read that again. All users of paid plans (Pro, Teams, and Enterprise) receive access to Origin, and only administrators of enterprise accounts have the authority to decline access.

The Paperwork That Didn’t Ship

The resulting service was entirely real and included repositories, bidirectional integration with GitHub, full capabilities for code browsing and searching, and immediate access to integration with Vercel, Depot, and Buildkite. In the view of most observers, it represented an entirely credible model for the appearance of code hosting services in an era of first-class use by AI agents.

But that was the set of features. The experience of managing and controlling the service was entirely different. What Origin lacked at the time of launch was of primary importance to anyone providing services to clients.

In particular, as Tech Times reported, Cursor provided no information about data retention, location of data storage, disclosures regarding use of subprocessors, policies for use of data for training purposes, and no tools for exporting repositories to alternative, non-Origin-based configurations of data storage.

Cursor’s documentation included descriptions of namespaces, plan gating, and inheritance of privacy mode. But it stopped there.

This represents an unusually large gap for a product that was, in effect, a facility for storing the intellectual property of others. Incumbent code hosts provide retention schedules, lists of subprocessors, and paths for data exports because their customers require them contractually. Agencies and individual developers enter data processing agreements with their clients, and pass those obligations down to all vendors that touch their code.

It sounds like paperwork, but it can kill a deal. If an agency can’t answer the security questionnaire, the client may never make it to the signing table.

The Code Is Sitting Next to the GPUs

Would the question of training even arise if the buyer were anyone else? Probably not. But Cursor’s own description of the transaction is a story of computing. The company noted in its announcement that it will have access to “the largest fleet of GPUs in the world, giving us the compute to build stronger models,” and cited the release of Grok 4.6 as an initial demonstration of what the two can now build together.

SpaceX now owns a company that hosts developers’ code, while also giving that company access to massive computing power to build better AI models. But Cursor has said nothing about whether the code that it hosts contributes to that process. That’s not proof they’re doing anything wrong, but it is a question that customers need answered.

There’s also a degree of irony with the timing of these events: On August 13, the day before the merger closed, Cursor published a blog announcing that it achieved AIUC-1 certification for agent security and reliability. But it’s unclear whether that certification extends to code hosted natively on Origin.

Who Actually Gets to Say No?

Enterprise administrators have the option of disabling operation on Origin for their entire organization.

But a small agency operating under a license for the Teams edition of the product, or for an individual developer operating under a license for the Pro edition and maintaining records for client repositories through use of the company’s service, Origin was about as optional as U2’s “Songs of Innocence” was in 2014.

Analyst Jason Andersen of Moor Insights & Strategy has already warned that enterprise customers could be concerned about what SpaceX’s ownership means for Cursor. One of his biggest questions is whether customers will still be able to choose models other than Grok.

Meanwhile, GitHub’s August 17 outage was a reminder that hosting code is a little more complicated than putting repositories on a server. GitHub has had to dramatically rethink its infrastructure as AI-driven development pushes demand to new levels. Cursor is now entering the same business, just under the ownership of a rocket company.

For developers, the acquisition isn’t about valuation and restructuring. They know the sync is on, the code is there, and that the documentation needed to justify putting that code on Origin isn’t.

To be clear, none of this means improper conduct on the part of Origin with regard to hosted code. In all likelihood, there’s none. But “probably” is no longer a valid description of events that are subject to review for compliance purposes. Until written policies for retention and for use of information are established, every account of paid Cursor users engaged in client work reflects an unacceptably large gap that can’t be compensated for.

Cursor has always had a reputation for moving faster than everyone else, but when you’re hosting someone else’s code, speed isn’t the only thing customers are buying. The policies, controls, and documentation that explain what happens to that code are part of the product, too.