Penv Cloud
Start free
Docs
Referencesince cloud@2026-09-10

Who processes what

The ten third parties in our register, what each can access, and the one that holds a plaintext value in memory.

The register your Data Processing Agreement with us refers to. Our public copy is at /security/subprocessors.

Register

Third partyFunctionAccessPlaintext values
AWS KMSWraps the data key we seal your values withKey material onlynone
NeonOur primary databaseCiphertext and metadata; we encrypt each value before it landsnone
VercelApplication hosting and edgeRequest routing, a coarse geo hint, and the compute that decrypts a value to serve itin memory
Google AnalyticsPage visit counts, only after you accept the cookie noticePage paths, a truncated IP address, browser detailsnone
ResendTransactional emailRecipient address, subject, message bodynone
UpstashRate-limit counters and job locksA counter and a key derived from an account or source IPnone
SentryError reportsError details with account and workspace identifiers, and a masked replay if you accept the cookie notice; never a value, token, password, request body or IPnone
GitHubCopies of error reports, as tickets in a private repositoryThe same error detailsnone
StripePayments, default processorBilling and payment datanone
PaystackPayments in African marketsBilling and payment datanone

Plaintext in memory

Vercel runs the compute that decrypts a value to serve it, so plaintext exists there in memory for one request. See what we can see.

Unset terms

We have not yet set the notice period we give you before a new third party starts, or each third party's hosting region. Our privacy policy highlights every unset value. Confirm a region with us before you rely on it.