Unbalanced PSI is a variant of private set intersection specifically designed for scenarios where the set sizes of the two participating parties are highly asymmetric, such as a mobile client with a few hundred contacts querying a server with millions of registered users. Unlike standard PSI protocols that treat both parties symmetrically, unbalanced PSI shifts the computational and communication complexity to the party holding the larger set, allowing the client to perform minimal work proportional to its small input size rather than the server's massive dataset.
Glossary
Unbalanced PSI

What is Unbalanced PSI?
Unbalanced Private Set Intersection (PSI) is a cryptographic protocol optimized for scenarios where one party holds a significantly smaller dataset than the other, minimizing the communication and computation burden on the resource-constrained client.
Modern unbalanced PSI protocols achieve this efficiency by combining oblivious pseudorandom functions (OPRFs) with data structures like Cuckoo hashing and Bloom filters on the server side. The client interacts with the server to privately evaluate the OPRF on its inputs, while the server pre-processes its large set into an encoded structure that enables sub-linear or constant-time lookups. This construction ensures the client learns only the intersection and the server learns nothing, making it the cryptographic backbone for real-world applications like contact discovery in end-to-end encrypted messaging platforms.
Key Features of Unbalanced PSI
Unbalanced PSI protocols are engineered for scenarios where one party's dataset is orders of magnitude smaller than the other's, optimizing communication and computation to scale with the smaller set size.
Linear Complexity in the Small Set
The defining characteristic of unbalanced PSI is that its communication and computation complexity scales linearly with the size of the smaller set, not the larger one. This is achieved by having the party with the larger set encode its data into a specialized data structure, while the party with the smaller set drives the protocol by querying this structure. For example, a mobile device with 1,000 contacts can privately check intersection against a server's database of 500 million users with minimal bandwidth.
Two-Message Round Complexity
Most modern unbalanced PSI protocols achieve optimal two-message (one round-trip) communication. The client sends a single query derived from its small set, and the server returns a single response containing the intersection result. This minimal round complexity is critical for latency-sensitive applications like real-time contact discovery or ad conversion measurement. Protocols like the CLR17 construction and its successors achieve this using a combination of fully homomorphic encryption and carefully designed query compression techniques.
Malicious Security with Minimal Overhead
While early unbalanced PSI protocols assumed semi-honest adversaries, modern constructions provide malicious security—protection against parties that arbitrarily deviate from the protocol—with surprisingly low overhead. Techniques include:
- Cut-and-choose verification of the large set's encoding
- Zero-knowledge proofs that the server correctly computed on its encrypted data
- Consistency checks that prevent the client from adaptively crafting queries to extract information This allows deployment in adversarial environments where either party may attempt to cheat.
Precomputation for Amortized Efficiency
Unbalanced PSI protocols heavily leverage offline precomputation to minimize online latency. The server can pre-process its massive dataset once, generating a reusable encrypted structure. When a client initiates a query, only lightweight operations are required. This amortization is particularly powerful in VOLE-based constructions, where correlated randomness is generated in advance. The result is that the online phase can be orders of magnitude faster than computing everything from scratch, making the protocol practical for high-throughput services.
Frequently Asked Questions
Clear answers to common questions about unbalanced private set intersection protocols, their performance characteristics, and real-world deployment considerations.
Unbalanced PSI is a private set intersection protocol specifically optimized for scenarios where the set sizes of the two participating parties are significantly different—typically where one party holds a much smaller set (the client) and the other holds a much larger set (the server). In standard PSI, both parties often bear roughly symmetric computational and communication costs proportional to their set sizes. In unbalanced PSI, the protocol is engineered so that the party with the smaller set performs work proportional to its own small set size, while the server's work scales with the larger set but remains computationally feasible. This asymmetry is critical for real-world applications like contact discovery, where a user's phonebook of a few hundred contacts must be privately compared against a service's database of hundreds of millions of users. Protocols such as those based on oblivious pseudorandom functions (OPRF) and homomorphic encryption are commonly used to achieve this efficiency imbalance, ensuring the client's communication and computation remain low even when the server's set is massive.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Unbalanced PSI relies on a stack of cryptographic building blocks optimized for asymmetric set sizes. These primitives shift the computational and communication burden to the party holding the larger dataset.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us