Private information retrieval

<jats:p> Publicly accessible databases are an indispensable resource for retrieving up-to-date information. But they also pose a significant risk to the privacy of the user, since a curious database operator can follow the user's queries and infer what the user is after. Indeed, in cases where the users' intentions are to be kept secret, users are often cautious about accessing the database. It can be shown that when accessing a single database, to completely guarantee the privacy of the user, the whole database should be down-loaded; namely <jats:italic>n</jats:italic> bits should be communicated (where <jats:italic>n</jats:italic> is the number of bits in the database). </jats:p> <jats:p> In this work, we investigate whether by replicating the database, more efficient solutions to the private retrieval problem can be obtained. We describe schemes that enable a user to access <jats:italic>k</jats:italic> replicated copies of a database ( <jats:italic>k</jats:italic> ≥2) and <jats:italic>privately</jats:italic> retrieve information stored in the database. This means that each individual server (holding a replicated copy of the database) gets no information on the identity of the item retrieved by the user. Our schemes use the replication to gain substantial saving. In particular, we present a two-server scheme with communication complexity <jats:italic>O(n</jats:italic> <jats:sup>1/3</jats:sup> ). </jats:p>