mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-20 10:42:26 +00:00
Brendan Clement
198812fd53
The existing docs have 254 findings from our shared Vale rules. Contributors would otherwise inherit these when editing the same lines. Clean up the prose across 80 pages: correct product names and a repeated word, simplify a few phrases, and replace dashes with punctuation that fits each sentence. The pinned Vale scan now reports zero findings, with no suppressions.
21 lines
770 B
Plaintext
21 lines
770 B
Plaintext
---
|
|
title: "Compliance"
|
|
sidebarTitle: "Compliance"
|
|
description: "Certifications, data handling, and the controls a deployment provides."
|
|
icon: certificate
|
|
keywords: ["compliance", "security", "soc2", "encryption", "audit"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge>
|
|
|
|
This page describes a LanceDB Enterprise capability. The embedded form
|
|
of LanceDB has no server to provide it. See
|
|
[Architecture](/architecture) for what differs between the two.
|
|
|
|
Compliance posture (certifications, data residency, encryption at rest and in
|
|
transit, audit logging) is a property of a deployment, so it is documented
|
|
with LanceDB Enterprise.
|
|
|
|
For embedded LanceDB, these are properties of the object store you point it at
|
|
and the process you run it in; LanceDB adds no layer of its own.
|