Skip to content

Commit ecb9453

Browse files
authored
Add E2EE example (#271)
1 parent d9b4396 commit ecb9453

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

usage/use-case-examples/data-encryption.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,11 +49,13 @@ The client-side database can be encrypted at rest. This is currently available f
4949
</Note>
5050

5151

52-
5352
### End-to-end Encryption
5453

5554
For end-to-end encryption, the encrypted data can be synced using PowerSync. The data can then either be encrypted and decrypted directly in memory by the application, or a separate local-only table can be used to persist the decrypted data — allowing querying the data directly.
5655

56+
[Raw SQLite Tables](/usage/use-case-examples/raw-tables) can be used for full control over the SQLite schema and managing tables for the decrypted data. We have a [React & Supabase example app](https://github.com/powersync-community/react-supabase-chat-e2ee) that demonstrates this approach. See also the accompanying [blog post](https://www.powersync.com/blog/building-an-e2ee-chat-app-with-powersync-supabase).
57+
58+
5759
## See Also
5860

5961
* Database Setup → [Security & IP Filtering](/installation/database-setup/security-and-ip-filtering)

0 commit comments

Comments
 (0)