Using Base means agreeing to these terms. They are short on purpose.
You need an account, and you are responsible for what happens under it — including anything done with API keys or connected assistants you have authorised. Keep your keys to yourself, and revoke one the moment you think it has leaked.
You keep every right you have in the data you put into Base. You give us permission to store, process and display it only so far as running the service requires. We claim no ownership of it, and we do not train models on it.
You can export it at any time: CSV per table or the REST API at /v1. That is deliberate — leaving should be as easy as arriving.
Automated abuse detection runs on public form traffic. A workspace that trips it can be suspended, which blocks access until we have looked at it.
When you connect an outside account — Airtable, say — you authorise us to act within the scopes you approved there, and nothing beyond them. Those services have their own terms, and we are not responsible for what they do or for outages on their side. You can revoke a connection with them at any time. See Privacy for what we hold, which for Airtable is nothing.
We aim to keep Base up and we do not promise it will be. There is no uptime SLA today. We may change or remove features; where a change would lose data, we will say so first.
Base is provided as is, without warranties. To the extent the law allows, our liability is limited to the amount you paid us in the twelve months before the claim. Nothing here limits liability that cannot lawfully be limited.
You can stop using Base and ask for deletion at any time. We may suspend or close an account that breaks these terms, and will tell you why unless the law prevents it. Export your data first — after deletion we cannot recover it.
If these terms change materially, we will say so in the product before the change takes effect. The date at the top is the version you are reading.