Security & data protection

Your Airtable data, handled carefully

Simplified Webhooks sits between your Airtable base and your automation, so it sees your records. This page describes exactly where that data goes, how it is protected, and who else is involved — in enough detail for a security review.

Last updated: 25 August 2026

encrypted in transit · TLS 1.3
encrypted in transit · TLS 1.3
Source
Airtable
Records & schema
Destination
Your endpoint
Make · Zapier · n8n
Simplified Webhooks
Encrypted at rest
AES-256-GCM

Infrastructure

Simplified Webhooks runs on managed cloud platforms. Every component that receives, processes, or stores your webhook data is hosted in the EU.

  • API and background jobs on Google Cloud Run, region europe-west1 (Belgium)
  • Scheduling and delivery queues on Google Cloud Scheduler and Cloud Tasks, same region
  • Managed PostgreSQL and authentication on Supabase, EU region — Frankfurt (eu-central-1)
  • Marketing site and dashboard on Vercel, with server-side rendering pinned to the Frankfurt region (fra1)
  • Secrets held in Google Secret Manager, never in source control or container images

Encryption

Data is encrypted in transit everywhere, and your Airtable credentials get an additional layer of application-level encryption on top of disk encryption.

  • TLS for all traffic: Airtable to us, browser to us, and us to your endpoint
  • Airtable personal access tokens and OAuth tokens encrypted with AES-256-GCM before they are written to the database
  • Encryption keys kept in Google Secret Manager, separate from the database
  • API keys are never stored in readable form — only a SHA-256 hash is kept, so a database dump cannot be replayed against the API
  • Storage-level encryption at rest provided by our database and hosting platforms

Authentication and access control

Every request is authenticated, and every row in the database is scoped to its owner.

  • API access via a Supabase-issued JWT or a personal API key; both resolve to a single user account
  • Row-level security in PostgreSQL, so a session can only read rows belonging to that user
  • Incoming Airtable pings are verified against Airtable’s HMAC signature before they are processed
  • Administrative access is restricted to an explicit allowlist, protected by two-factor authentication, and every administrative action is written to an audit log
  • Least-privilege service accounts for scheduled jobs, authenticated with signed OIDC tokens

What we store

You stay in control of what flows through the service. This is the complete list of what lands in our database.

  • Account data: email address, name, and plan
  • Connection credentials: your encrypted Airtable token, plus the base and table IDs you connect
  • Event data: the Airtable payload of each change event and the transformed payload we forward, so you can inspect deliveries in the dashboard — the content is whatever your Airtable records contain. It is deleted automatically 30 days after the event
  • Delivery metadata: timestamps, HTTP status codes, error messages, and retry state — kept without any record content once the payload has been deleted
  • Record-count snapshots: per-table row counts for the bases you choose to track, no record content

Reliability

A missed webhook is a data-integrity problem, so delivery is built to survive failures on either side.

  • Failed deliveries are retried automatically with exponential backoff
  • Deliveries run through a managed queue, so a slow endpoint of yours never blocks other events
  • Airtable webhooks are refreshed on a schedule so they cannot silently expire
  • Continuous monitoring with automated alerting on delivery failures
  • Managed database hosting with provider-side automated backups

Data protection and GDPR

Simplified Webhooks is operated by Synergetic GmbH, a company registered in Germany, and is therefore subject to the GDPR.

  • When we forward your Airtable data, you are the controller and we act as your processor under Art. 28 GDPR
  • A Data Processing Agreement, including our technical and organisational measures and this sub-processor list, is available to every customer on request — on paid and free plans alike
  • Payload content is deleted automatically 30 days after the event; only content-free delivery metadata is retained beyond that
  • All processing of webhook data happens in the EU, on the infrastructure listed above
  • You can delete a webhook or your entire account at any time, which removes the associated event history
  • For a copy of your data, a deletion request, or questions from your data protection officer, contact us and we will respond

Transparency

Sub-processors

These are the providers that may process personal data on our behalf. We list them in full so your data protection team does not have to ask.

ProviderPurposeProcessing location
Google CloudGoogle Cloud EMEA Limited, IrelandAPI hosting, job scheduling, delivery queues, secret managementEU — europe-west1 (Belgium)
SupabaseSupabase, Inc., United StatesManaged PostgreSQL database and user authenticationEU — Frankfurt (eu-central-1)
VercelVercel Inc., United StatesHosting of the marketing site and the customer dashboardEU — Frankfurt (fra1)
PostHogPostHog, Inc., United StatesProduct analytics and error trackingEU Cloud — Frankfurt

Announced, not yet in use

We announce providers before we start using them, so nothing appears in your data flow unannounced. These process nothing today:

  • Vercel AI GatewayRouting requests for planned AI-assisted features to language model providers. Not in use. Before this is activated, the model providers it routes to will be named here, the routing will be pinned to those providers, and no-training and retention terms will be agreed with them.

Airtable is not listed here: it is your own system, which we access on your instruction with the credentials you provide.

Frequently asked

Security & data protection FAQ

Where is my data processed?

All webhook processing and storage happens in the EU: the API runs on Google Cloud Run in europe-west1 (Belgium), the database is a Supabase instance in Frankfurt, the dashboard is served from Vercel’s Frankfurt region, and product analytics go to PostHog’s EU Cloud. Airtable itself is your own system — we read from it with the token you provide and never copy your base anywhere else.

Is Airtable a sub-processor of yours?

No. Airtable is the source system you already have a contract with. Simplified Webhooks connects to it on your instruction with the credentials you provide; data flows from Airtable through us to the endpoint you configure.

Do you store the content of my records?

Yes, but not indefinitely: we store the Airtable payload of each change event and the payload we forwarded so you can inspect and debug deliveries, and an automated job deletes that content 30 days after the event. What remains is delivery metadata — timestamps, status codes, errors — with no record content in it. Deleting a webhook or your account removes the history entirely.

Can I get a signed Data Processing Agreement?

Yes, on every plan, including the free one. Contact us and we will send our standard DPA with the technical and organisational measures and sub-processor list attached.

What happens to my Airtable token if I stop using the service?

You can disconnect Airtable at any time from your profile settings, which deletes the stored token. Revoking the token or the OAuth grant in Airtable also cuts off our access immediately.

Are you ISO 27001 or SOC 2 certified?

Simplified Webhooks itself is not certified. Our infrastructure providers are — Google Cloud and Supabase both hold ISO 27001 and SOC 2 certifications for the platforms we build on. We are happy to answer a security questionnaire instead.

Need a DPA or a security review?

We are happy to provide a Data Processing Agreement under Art. 28 GDPR, our technical and organisational measures, or answers to your security questionnaire — on any plan.

Security & Data Protection | Simplified Webhooks