Scaffold Privacy Policy

Last updated: 5 November 2026

Scaffold LLC ("Scaffold", "we"), a Texas limited liability company, turns recurring work you ask Claude for into automations. This policy explains what Scaffold collects, how it's used and stored, who it's shared with, how long it's kept, and how to reach us. It covers Scaffold's server at api.scaffold-ai.tech, the Scaffold connector in Claude, the Scaffold plugin, and the Scaffold for Mac app.

What we collect

Your account

When you sign in with Google: your email address and Google's ID for your account. Google also sends your name and profile picture. We don't store your name. We keep the web address of your picture (not the picture itself) with your browser's sign-in, to show it on your account page. It's deleted when you sign out, or soon after that sign-in ends at 30 days. Your browser loads the picture from Google.
If you use a Scaffold key instead: we store only a one-way hash of the key.
A computer key for each computer linked to your account: a one-way hash of the key and the computer's name. Scaffold for Mac links its Mac when you sign in, and the plugin's link command links a computer once you allow it in your browser. The key itself stays on that computer.
Sign-in records: the apps you've connected (their name and return address), and hashes of their sign-in tokens. When you sign in with Google, your browser keeps a cookie for 30 days so the next app you connect takes one click. We store only a hash of it.

Automations you save

The automation's name, the request you made (for example "Every weekday at 9am, summarize the top Hacker News stories"), its plan (steps, the services and operations they call, and the commands they run), its scripts, and its schedule.

Records of each run, sent from your computer after the automation runs:

Which steps ran and how they ended, timings, the kind of error if one occurred, an estimate of the tokens the scripts saved, and any change Scaffold made to heal a step, including a script Claude repaired.
Never the data your automation reads or produces: inputs, outputs, and file contents stay on your computer.

Shared run outcomes (on by default; you can turn them off)

For each step: the service it called (for example api.github.com), the operation template (for example GET /repos/{owner}/{repo}/issues), whether it ran as a script or by Claude, whether it worked, and the kind of error.
Never inputs, outputs, or file contents. This is how Scaffold learns which steps hold up across everyone's runs. A pattern only influences Scaffold's advice once at least 3 different accounts have reported it.
Turn it off with "Share run outcomes" in the Scaffold plugin's settings, and your outcomes stay on your computer.

Field notes

Short facts about a service that Claude records while building or running an automation (for example "this API limits requests to 60 per hour"). They may be shown to other users once a second, independent account reports the same fact.

If you subscribe to Pro

Stripe, our payment processor, takes your card and billing address. They go to Stripe, not to us.
We keep your Stripe customer and subscription IDs, the subscription's status, and when its paid period ends, to turn Pro on and off.

Scaffold for Mac

The app shows the automations, runs and output that Scaffold keeps on your Mac. They stay on your Mac; the app doesn't send them to us.
It signs in to your Scaffold account like any app you connect (see sign-in records above), checks your plan, and on Pro lists the automations saved to your account.
When you ask it to change or fix a step, it gives that step, its script and your words to Claude Code or Codex on your Mac, which send them to Anthropic or OpenAI under your own account. It also asks them how much of your plan's usage is left.
When you download the app, our server counts downloads by IP address for up to an hour, to limit them. The count is kept in memory only.

Server logs

For each request: the method, path, response status, and timing, plus Scaffold's own reason when a request is refused. We never log request bodies, keys, or tokens. Our hosting provider may record IP addresses in its own logs.

What we don't collect

Scaffold doesn't read your Claude conversations, chat history, memory, or files. It only receives what Claude sends when it uses one of Scaffold's tools for you.

How we use it

To provide Scaffold: signing you in, saving and syncing your automations, showing how they're doing, and checking plans against shared run evidence so automations are built from steps that hold up. We don't sell your data, use it for advertising, or use it to train AI models.

We also publish one figure on scaffold-ai.tech: the total tokens saved, added up from the token estimates in every account's run records. It's a single sum across all accounts and says nothing about any one account or automation.

Where it's stored

On servers run by our hosting provider, Railway. Your automations' working files and full run history are stored on your own computer, in ~/Scaffold/ and ~/.scaffold-connector/.

Who it's shared with

Google: when you choose Google sign-in.
Railway: our hosting provider, which stores and processes data for us.
Stripe: when you subscribe to Pro, your email and Scaffold account ID, to set up and bill the subscription. Stripe's handling of your payment details is covered by its own privacy policy.
GitHub: only when you ask Scaffold to read a public repository.
Other Scaffold users: only shared run outcomes and corroborated field notes, as described above. These never include your account details, your automations' contents, or your data.
Anthropic: Claude sends Scaffold's tools your requests and receives their results. Anthropic's handling of your conversations is covered by its own privacy policy.

We share data otherwise only if the law requires it.

How long we keep it

Your account and saved automations: until you delete them or delete your account.
Run records: for as long as the automation exists, and deleted with it.
Shared run outcomes: Scaffold's advice uses only the last 90 days of outcomes. Older outcomes are kept only as aggregate counts that aren't linked to any account.
Billing records: the Stripe IDs and status above, until you delete your account. Deleting your account cancels any Pro subscription first. Stripe keeps its own payment records as the law requires.
Server logs: kept for up to 30 days, then deleted by our hosting provider.

Your choices

Turn off "Share run outcomes" at any time.
Disconnect Scaffold from Claude at any time, under Customize → Connectors.
Unlink a computer at any time in Scaffold for Mac, under Settings, or by emailing support@scaffold-ai.tech. Its key stops working at once.
Delete your account and all its data at any time in Scaffold for Mac, under Settings → Delete account, or at https://api.scaffold-ai.tech/account/delete. A Pro subscription is cancelled first. Deletion is immediate and permanent, and signs out every app you connected. Scaffold's files on your own computer (~/Scaffold and ~/.scaffold-connector) stay until you delete them or uninstall the plugin.

Contact

Scaffold · support@scaffold-ai.tech · https://scaffold-ai.tech