Does Airtable work in China?
Airtable is a cloud database that lives offshore, and for mainland China that is the answer. Airtable stores your bases on Amazon Web Services in the United States, Europe or Australia — there is no mainland-China region — so using it to hold Chinese users' personal data moves that data across the border, a compliance decision long before it is a performance one.
In Airtable's own words it "offers data residency in the United States (default), Europe, and Australia," and its subprocessor page names Amazon Web Services for "hosting customer data" across the USA, Germany, Ireland and Australia — every option offshore from the mainland. Save a Chinese user's name, email or any personal detail into a base and you have made a cross-border transfer of personal information that PIPL governs (notice, separate consent and a lawful transfer mechanism, Articles 38–43). And because Airtable is a backend rather than a host, any public mainland site it powers still needs an ICP filing — which Airtable gives you no in-country server to attach to. The table below is Airtable's own wording and the rule each line triggers.
This is a risk map, not a verdict — which obligations bite turns on your entity, your data and who your users are. Our China team can map your exposure with you →
What actually decides whether Airtable is compliant for your mainland-China users
| Fact | Primary source |
|---|---|
| Airtable stores your data offshore, and offers no mainland-China region. In its own data-residency documentation Airtable states it "offers data residency in the United States (default), Europe, and Australia." Those are the only three options — a base created by default sits in the United States, and there is no mainland-China region to choose. For a Chinese audience that placement is the heart of the cross-border data question under PIPL. | Airtable — Data residency at Airtable (support.airtable.com), retrieved 2026-10-07 |
| Airtable's bases run on Amazon Web Services, all of it outside mainland China. Airtable's own subprocessor page says it "may use the following subprocessors for hosting customer data," and lists "Amazon Web Services, Inc" for "Cloud infrastructure" in "USA, Germany*, Ireland*, Australia*" — the starred regions available only under European or Australian data residency. None is in the mainland, so wherever your data lands it is hosted across the border from your Chinese users. | Airtable — Subprocessors (airtable.com/company/subprocessors), retrieved 2026-10-07 |
| Collecting Chinese users' personal data into Airtable is a cross-border transfer. Because the base sits offshore, every name, email or record a mainland user submits leaves the country the moment it is saved. China's Personal Information Protection Law treats that as an export of personal information — requiring notice, separate consent and one permitted transfer mechanism (a CAC security assessment, the CAC standard contract, or certification) under Articles 38–43 — and for a critical information infrastructure operator or large-volume handler it adds an in-country storage duty (PIPL Article 40, with Cybersecurity Law Article 39 (formerly Article 37)). | PIPL Articles 38–43 & 40; Cybersecurity Law Article 39 (formerly Article 37) (npc.gov.cn), retrieved 2026-10-07 |
| If Airtable powers a public mainland site, that site still needs an ICP filing — and Airtable gives you no host to file it against. Airtable is a backend, not a hosting provider: its data-residency options are the United States, Europe and Australia only, so there is no in-country server for an ICP filing to attach to. A public website shown to mainland visitors must carry an ICP filing tied to a licensed in-country host (State Council Order No. 292; MIIT Order No. 33) — a fact about the site Airtable backs, not about Airtable the database. | Airtable — Data residency at Airtable (support.airtable.com), retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
Airtable is a superb place to model data — a relational database you drive like a spreadsheet, and a convenient backend for a website or app. For a mainland-China audience, though, the first question is not how fast a base loads but where that base lives, because Airtable is a cloud database that runs entirely offshore. It stores your data on Amazon Web Services in the United States, Europe or Australia, with no region inside mainland China — so the moment a Chinese user’s name or email lands in one of your bases, their personal data has already left the country. That is a question for China’s data-protection law, and it is the half of “does Airtable work in China” that no amount of tuning answers, because it was never a performance problem to begin with.
Airtable in China at a glance
| What decides it | In Airtable's own words — and China's own law |
|---|---|
| What Airtable is | A cloud database and low-code backend. Airtable runs on Amazon Web Services; its subprocessor page lists AWS for “hosting customer data.” Excellent for modeling and serving content — but hosted, by design, outside the mainland. |
| A mainland-China region? | No. Airtable “offers data residency in the United States (default), Europe, and Australia.” Those are the only three; there is no mainland-China option, so your bases sit offshore. |
| Holding China users' personal data | Saving a mainland user's personal information into an offshore base is a cross-border transfer of personal information, which PIPL governs — notice, separate consent and a lawful transfer mechanism (Articles 38–43). |
| Serving a public site in China | Airtable is a backend, not a host. If it powers a public mainland site, that site still needs an ICP filing tied to a licensed in-country host (State Council Order 292; MIIT Order 33) — and Airtable gives you no in-country server to file. |
| The working design | Keep Airtable as your data source; add an ICP-filed, in-country layer in front for mainland visitors and be deliberate about what personal data crosses the border. An overlay in front of your origin, not a migration off Airtable. |
Where Airtable actually keeps your data
Start with Airtable’s own documentation, because it is unusually clear. Airtable “offers data residency in the United States (default), Europe, and Australia” — three regions, and a base you create without changing anything sits in the United States. Its subprocessor page is just as plain: Airtable “may use the following subprocessors for hosting customer data,” and the one that hosts it is “Amazon Web Services, Inc,” listed for “Cloud infrastructure” in “USA, Germany*, Ireland*, Australia*.” The starred regions are available only to customers who have turned on European or Australian data residency. Read the whole list and the same fact keeps returning: every place Airtable will put your data is outside mainland China. There is no China region to select, and that is not an oversight you can configure around — it is simply where the product lives.
The door that decides it: PIPL and your users’ data
Because the base is offshore, the compliance question is about movement, not speed. When a mainland visitor submits a form, signs up, or has a record written on their behalf, their personal information is saved to a server outside China — and under the Personal Information Protection Law that is a cross-border transfer of personal information. PIPL asks three things of such a transfer: that you give the person notice, that you obtain their separate consent, and that you put one of the permitted mechanisms in place — a CAC security assessment, the CAC standard contract, or certification (Chapter III, Articles 38–43). If your organization is a critical information infrastructure operator, or handles personal information above the regulated volume, a further duty applies: the data must be stored inside China in the first place (PIPL Article 40, with Cybersecurity Law Article 39 (formerly Article 37)). Whether any of those thresholds catch you depends on your role and your numbers, which is a matter to settle with counsel rather than assume either way.
The second door: when Airtable sits behind a public mainland site
There is a separate requirement that appears only when Airtable backs a site the public in China can visit — a listing, a catalogue, a customer portal fed from your bases. A public website shown to mainland visitors must carry an ICP filing (备案) tied to a licensed host physically inside the mainland, under State Council Order No. 292 and MIIT Order No. 33. This is where Airtable’s nature matters: it is a backend, not a hosting provider, and it publishes no in-country server for that filing to attach to. The obligation lands on the public site you serve, not on Airtable the database — but if that site is meant to reach China, the filing has to live somewhere, and Airtable is not that somewhere.
This is a risk map, not a verdict — which of these doors actually applies turns on your entity, your data and who your users are, and it is worth settling with counsel.
Where 21YunBox fits — a compliant overlay, not a migration
You keep Airtable exactly where it is. It stays your data source and your editing surface, with the same bases, the same automations, the same API your app already calls. What 21YunBox adds is the piece a cloud database sitting offshore structurally cannot carry: compliant, ICP-filed delivery from inside the mainland, placed in front of your existing origin — no rebuild, no second codebase, no move off Airtable. Our China team maps which obligations reach your setup, handles the ICP filing for the public site, and helps you design what personal data may cross the border and what should stay in-country — so the parts of your stack that live offshore keep doing their job while your mainland presence is one you are licensed to run.
Related reading:
