# Restoring without matching Sync Key

**URL:** <https://discuss.zetetic.net/t/restoring-without-matching-sync-key/5494>\
**Category:** Codebook\
**Created:** [July 23, 2022, 11:02pm UTC](https://discuss.zetetic.net/t/restoring-without-matching-sync-key/5494 "2022-07-23T23:02:21Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mmoore](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/mmoore/32/858_2.png) [@mmoore](https://discuss.zetetic.net/u/mmoore)\
**Post date:** [July 27, 2022, 12:21pm UTC](https://discuss.zetetic.net/t/restoring-without-matching-sync-key/5494/5 "2022-07-27T12:21:37Z")

</div>

@mags08

Sorry to hear that none of the restoration options were available for you.

@Marv

> [@Marv](#):
>
> does this mean the synched data is encrypted twice? Once with your DB password and then again with the synch key?

Your Codebook database is encrypted locally (on device) using your Codebook Master Password as key material. When syncing, Codebook encrypts “chunks of changes” (codebook-changeset-[number].db files in your cloud service) with your Sync Key. So to answer your question directly – no. Synced data is encrypted once with the Sync Key.

> [@Marv](#):
>
> Why not use the same DB password for both?  
> I have been trying to find an answer but I can’t so sorry if this is explained somewhere.

I believe this post by my colleague helps explain why we made the decision to use a Sync Key to encrypt synced data: [Why Does Codebook Require a Sync Key?](https://discuss.zetetic.net/t/why-does-codebook-require-a-sync-key/4122)

Let me know if that answers your questions and if you have any further questions. Thanks!

---

_[View the full topic](https://discuss.zetetic.net/t/restoring-without-matching-sync-key/5494)._