Skip to main content


How can I get started with Privy?โ€‹

You should first sign-up for a Privy account and then generate your API key using the Privy console. Once you have an API key, the easiest way to ramp up is to then check out our Quickstart guide.

We are currently in open beta. This means that while our security and infrastructure has been tested and hardened, we're actively working to improve our API based on your feedback. If you have any comments about your experience using Privy, please reach out!.

How much does Privy cost?โ€‹

Privy is entirely free for up to 5,000 users and 2GB of data stored for your account. We'll reach out to you as you get close to these limits. Read more about our current pricing and reach out to with any questions.

This is web3 -- why charge under a SaaS model?โ€‹

While our pricing will evolve as we decentralize, today Privy is running infrastructure so you can secure your users' most sensitive data. This has tremendous value for your users, but a cost to host. We do charge so we can continue to secure your user data in perpetuity, without ever analyzing or selling it (something we will never do).

What uptime and performance guarantees does Privy provide?โ€‹

Today, Privy runs infrastructure to guarantee high uptime, low latency, and data redundancy. While we're still compiling uptime data based on historicals, you can read up on the support and availability guarantees we make to Privy users.

How does Privy know who is making a request?โ€‹

Authenticating requests can be done in one of two ways:

Why shouldn't I be storing user data in Postgres?โ€‹

There are a number of reasons why you should not be handling user data directly but here are a few:

  • Leakage. Storing this data yourself means you risk exposing user data if you get breached. Large companies have full teams dedicated to safeguarding user data stored on their stack. Privy helps you do this with minimal overhead by taking your users' data off of your stack.
  • Compliance. Managing user data exposes you to regulatory overhead (GDPR, CCPA and other alphabet soup). Privy simplifies compliance so that you get back to your core product.
  • Interoperability. Web3 is about ownership; your users should stay in control of their data. Privy is building an interoperable datastore so you can better serve your users, but users always stay in charge of their data. Down with data silos!

Where does Privy store user data?โ€‹

Today, user data is stored in the cloud, encrypted. Neither Privy nor cloud providers have access to your plaintext data.

Privy's main threat model is data leakage, not censorship resistance. Right now, our focus is on data control: who controls data permissions and the keys under which data is encrypted. Over time, we'll integrate more decentralized storage solutions like IPFS to allow you to choose how your data is stored, while using the exact same interface.

Does Privy have access to my user data?โ€‹

No. All user data stored with Privy is encrypted client-side. Privy currently only manages the KMS (which runs in separate, hardened VPCs) on your behalf. We are currently working to integrate with Web3 cryptography primitives to enable your users to encrypt data with their own secret keys.

What happens to my users' data if I stop using Privy?โ€‹

Your user data is not our data. We do not now, nor will we ever, use data as a lock-in mechanism. If you go, your data goes with you. If Privy is no longer to your liking for any reason, we will help you offboard. This is not our data.

Privy will decentralize its infrastructure over time so you can control how your data is stored. In the interim, we guarantee simple exporting of data by you and your users. Specifically, Privy uses proxy reencryption to enable you to export ciphertext (alongside with the schemas which structure it) without it ever being decrypted. This means all user data is encrypted end-to-end and Privy cannot see it, even during export.

Can I tell my users about Privy?โ€‹

Absolutely. In fact, you should! User trust is hard to earn and easy to lose. Privy gets you back to earning it. As a starting point you may want to point them to

What's next?โ€‹

Today Privy is focused on three main quests:

  • User-controlled data. We are moving to a system in which data permissions are controlled by users instead of developers, meaning users will have complete, seamless control over how their data is used and can port their data between services. New experiences on the Web await!
  • Decentralization. We are working to decentralize the infrastructure on which Privy runs, starting with key management (via wallet integrations), followed by the permissions system and storage providers. You shouldn't have to run your data on Privy infrastructure if you don't want to.
  • More integrations. We are natively integrating Privy with external libraries (like email service providers, and more!) to make common use cases very simple and handsfree for developers.

Read more about our coming work. We're thrilled to be on this journey with you.

My question wasn't answered here!โ€‹

Just as with our core product, we're continually working to refine and improve our documentation. If your question wasn't addressed here, please reach out to! We would be delighted to share any information that would be helpful.