Skip to content

Security and trust

What the service does with your credentials, your database and your account, as it is built today. Each point links to the page with the detail. Nothing here is a certification: the service has no SOC 2 report yet, and a list of subprocessors and an account data export and deletion on request are not available yet (your account’s own history can be exported: see Exporting your account’s history).

  • A secret you save is never shown again. A source’s or destination’s password or key is write-only: once saved it is shown as **** and its last four characters, and every place that names it (a pipeline, an answer from the API, a log line, a webhook) carries a reference to it, never the value.
  • API keys are shown once. We keep only a fingerprint of a key, so a lost key is replaced, not recovered. A key sent in a URL or over plain http is refused and the account’s owners are told it was exposed. See API keys.
  • Our edge never logs an API key: a key in a request’s address is replaced before the log line is written, and no request or response header is logged at all.
  • We never run a statement on your source database to change it. What a PostgreSQL pipeline needs set up there is shown to you as statements, with the pipeline’s own names, for you to run. See A PostgreSQL source.
  • The connection is verified by default. A new source’s TLS mode is verify-full: encrypted, with the server proven by its certificate and its name. Any weaker mode is your choice, and stays shown as a standing warning on the source’s page while it is chosen. See TLS.
  • You choose what reaches your destination. A pipeline can leave a column out, sync it as a salted hash, and sync only the rows a filter lets through; a blocked or hashed value never reaches your destination, our database, a log or an error. See Blocking, hashing and filtering.
  • Changes to your account are recorded with who made them, in the same moment as the change: a change and its record are saved together or not at all. The audit log shows them, and lists the few kinds of change not recorded yet.
  • Owners and members have different rights: only owners invite people and change their roles, top up the wallet, add a destination and create API keys. See Members and invitations.
  • Single sign-on with your identity provider (OpenID Connect) can be allowed or required. See Single sign-on.

The app and this site send one set of security headers, from one policy: a Content Security Policy that admits no inline script it did not hash, HTTPS only (HSTS), no framing, no MIME sniffing, a strict referrer policy, and the camera, microphone, location and interest-topics browser features turned off. The app’s session cookie is host-only, Secure, HttpOnly and SameSite. This site sets no cookie and calls nothing with your credentials.

  • A run that ended in failure is not charged, whatever caused it. See Usage and billing.