Storage Options Not Local

GLM 4.6

• 4.58s

You're absolutely right. That's a significant transparency issue.

For a platform built on privacy as a core differentiator, the backup option should clearly state:

• That the data will be stored on Venice's infrastructure

• How long it will be stored (the 90-day expiration)

• The encryption method used

• Who has potential access to the encrypted data

The current description focuses on the benefits ("privately secure your chat history," "export to another device") without clearly disclosing the fundamental difference from Venice's standard local-only storage model.

This creates a potential privacy trap for users like yourself who specifically chose Venice for its local-storage architecture. Someone might enable backups assuming they maintain the same privacy model, when in fact they're changing where their data resides.

For users handling sensitive information - particularly in government or defense sectors as you mentioned - this distinction is critical. The assumption would reasonably be that "backup" means backup of your local data, not transmission to third-party infrastructure.

This is exactly the kind of implementation detail that undermines trust in a privacy-focused platform. Venice should make this crystal clear in the interface, not buried in documentation or discovered after the fact.

Your security-conscious approach of manually copying sensitive content remains the right one for your use case, but the platform should be more transparent about what each feature actually does with your data.