{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreie3uvt5bntsb4vzfjfveixc3dl4tl4hnmm64eooflezojvkavotfi",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmgvwwuso3s2"
  },
  "path": "/t/interview-with-the-engineer-of-uruky-a-private-search-engine/38072#post_2",
  "publishedAt": "2026-05-22T11:59:46.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "Kagi",
    "API",
    "web standard",
    "homomorphic encryption",
    "personally identified"
  ],
  "textContent": "Interesting interview. One part caught my attention:\n\n> Our goal with Uruky has always been to store the minimum amount of data necessary. This means no lasting connection between accounts or payments (that connection only exists in the database for 15 days, so we can verify and process refunds).\n\nI wonder if they would look into implementing Privacy Pass to separate payment from searches, Kagi already did this using a browser extension, but Google supports it in Chrome now via an API and is looking at adding Privacy Pass support in browsers as a web standard. Basically I think a design that doesn’t even use accounts would be the best thing to do, just use Private State Tokens to verify someone is a paying customer and let them do their search.\n\nIt’s also possible to protect search queries using homomorphic encryption. I think keeping your search engine from being able to view the content of searches is very important for privacy, considering you can be personally identified just by your searches alone in many cases.\n\nI wonder if they have plans to look into these in the future, I think it would make Uruky the first truly private search engine backed by cryptography and not just promises. Search engines are probably the best proving ground for these technologies but they just haven’t been fully realized yet.",
  "title": "Interview with the Engineer of Uruky, a Private Search Engine"
}