Pinecone
Pinecone · Vector database
Public sources reviewed . Risk classification and recommended policy are Ayliea's subjective assessments — not vendor certifications.
Scope of this recommendation
Configured vector database with application-enforced tenant authorization; other Pinecone products need separate review.
Public documentation review only. Current audit reports, certificate scope, executed contracts and customer settings were not independently examined. An omitted assurance claim is not evidence that the vendor lacks it.
- Storage and processing locations
- Selected cloud/region and deployment determine location; review integrated embedding/model services separately.
- Retention and ZDR scope
- A database intentionally persists records and backups. Deletion, metadata and any integrated inference have separate retention paths; ZDR is not the database model.
- Vendor-reported audits / certifications
- SOC 2 Type II
Why this rating
Embeddings, metadata and stored source text can be sensitive. Namespaces help partition data but application authorization must prevent cross-tenant access; do not assume records contain only irreversible vectors.
Considerations before deploying
- Enforce tenant identity and namespace selection server-side; test cross-tenant access.
- Minimize sensitive metadata/source text and review integrated embedding or reranking providers.
- Review scoped API keys, private endpoints, backups and deletion; obtain applicable BAA coverage before PHI.
Sources
- Pinecone security and access controls (www.pinecone.io)
Need a vendor review for your use case?
A scoping call defines the systems, data flows and vendor evidence to review for your use case.