Data processing agreement

The terms that apply when Scaffold processes personal data for you, such as your app's users.

Version v1Effective 2026-11-05Updated 2026-11-11
Contents16 sections
  1. 01Get the DPA
  2. 02Definitions
  3. 03Roles
  4. 04Processing details
  5. 05Instructions and confidentiality
  6. 06Security
  7. 07Subprocessors
  8. 08Requests from people
  9. 09Security incidents
  10. 10Audits and information
  11. 11International transfers
  12. 12Return and deletion
  13. 13General
  14. AAnnex A: processing details
  15. BAnnex B: security measures
  16. CAnnex C: subprocessors

Get the DPA

This DPA is part of the Terms of service. You accept it when you accept them, so you don't need to sign anything. If you need a signed copy, we send one.

Request a copy to sign

Definitions

Personal data, processing, controller, processor, data subject and personal data breach mean what they mean in the GDPR (Regulation (EU) 2016/679). Your personal data means personal data Scaffold processes for you under the Terms of service.

Roles

For personal data you or your apps keep on Scaffold, like your app's users and what your workspace holds about other people, you are the controller and Scaffold is your processor. For your own account and billing, Scaffold is the controller, as the Privacy notice explains.

Processing details

Scaffold stores, shows and sends the personal data in your workspaces and apps so you can use the service, for as long as you use it. The types of data and people are in Annex A.

Instructions and confidentiality

We process your personal data only on your documented instructions: the Terms of service, this DPA and what you do in Scaffold. If the law makes us process it otherwise, we tell you first, unless that law forbids it. If we think an instruction breaks data protection law, we tell you at once. Everyone at Scaffold who can reach your personal data is bound to keep it confidential.

Security

The measures Scaffold keeps are in Annex B.

Subprocessors

You give us general authorisation to use subprocessors. The current ones are on the Subprocessors list. Each must meet the same data protection duties as this DPA, and we stay responsible to you for them. Before we add or replace one, we announce it as that page describes, and you can object.

Requests from people

You can list and delete your app's users, and end their sessions, from the console, the API or the MCP server. Owners can export a workspace at any time.

If someone asks us directly about personal data we hold for you, we pass the request to you without undue delay, and don't answer it ourselves unless you ask us to. For anything you can't do yourself, write to us and we help without undue delay. We also help you with security, breach notices, impact assessments and consulting your authority, as far as we can with what we know.

Security incidents

If we learn of a personal data breach that affects your personal data, we tell the owners of the workspace by email without undue delay. We say what happened, the kinds and rough numbers of people and records, the likely effects, and what we did and will do about it. If we don't know everything yet, we send what we know and follow up.

Audits and information

On request, we give you the information you need to show that we meet this DPA. If that isn't enough, you or an independent auditor you choose can audit us, with reasonable notice, at your cost and under confidentiality, once a year, or more often if an authority requires it or after a breach.

International transfers

Scaffold stores your personal data on servers in Paris, in France, and its backups with Cloudflare in the European Union. Where a subprocessor processes it outside the EEA, the transfer relies on the EU-US Data Privacy Framework for certified companies, like Cloudflare, or on the European Commission's standard contractual clauses, as with Anthropic. The Privacy notice names the safeguard for each, and the Subprocessors list where each is.

Return and deletion

An owner can export a workspace at any time; each export can be downloaded for 24 hours. A deleted workspace can be restored for 24 hours, then it is erased with its projects, app users, pages, databases and agent runs. Deleting an app user or a project erases that data the same way.

When the Terms of service end, we erase your workspaces the same way after the end date, so export what you need before then. Copies in backups are gone within 7 days. We keep only what EU or Cypriot law requires us to keep, such as invoices, and tell you what that is if you ask.

General

This DPA lasts as long as we process your personal data. Where it conflicts with the rest of the Terms of service, this DPA wins for personal data. Liability under it follows the Terms of service, as far as the law allows, and the same law governs it.

Annex A: processing details

Processing details
PeopleDataPurposeKept for
Your app's usersEmail, password hash, confirmation and reset tokens, sessions and refresh tokensSigning them in to your appUntil you delete the user, project or workspace. Access tokens last 1 hour, refresh tokens 30 days from their last use.
Your app's usersSign-in events: what happened, the sign-in method, the IP address and the city and country it came from. Each session's browser, system and placeShowing you who signs in to your app, and locking an account after wrong passwords90 days, or until you delete the user. A session's browser, system and place go within a day of it ending.
Visitors to your appIP address, the address asked for, the time, the result, the referring page and the browser string of each requestDelivering your app and keeping it up14 days in our server logs.
People in your workspace contentWhatever you, your members and your agents write into tasks, databases and pagesStoring and showing your workspace, and the agent runs you startUntil deleted. Archived pages and databases are erased after 30 days.

Annex B: security measures

  • Passwords are stored only as Argon2 hashes, and new ones are checked against known breaches.
  • Session, token, invite and link secrets are stored only as hashes.
  • Each environment variable is encrypted with its own key, which a platform key wraps, and no command returns a secret's value.
  • The sign-in cookie is HttpOnly, Secure and SameSite=Lax.
  • Sign-in locks for 15 minutes after 5 wrong tries, requests are rate limited, and two-factor sign-in is available to everyone.
  • Uploaded pictures are re-encoded with their metadata removed.
  • Every read checks that the caller still belongs to the workspace, and one workspace can't read another's data.
  • Only the people at SPINZ who run Scaffold can reach the servers that hold your data, and they are bound to keep it confidential.
  • Scaffold's own database, with accounts and workspace content, is backed up continuously to storage in the European Union, and the files apps store and the app sources uploaded for deploys every hour. Deleted data stays in those backups for up to 7 days, then it is gone.

Annex C: subprocessors

The current list is on Subprocessors.