Please clarify the Google Cloud connection

[Node815]

I kept getting connection time out errors with Kai so I asked it why if it's local, it revealed to me it uses Google Cloud Console, and tried to assure me it was encrypted.

Just how is this offline as your site claims it to be here?

If it truly is supposed to run on my device, how can one trust Google Cloud to not use something such as their AI to break the encrypted memory data the app said it sends only to the server?

I'm not trying to argue or dispute what you are doing, but this is a red flag for me for something that says it runs completely on the local device. It does however, explain why it's so fast on a basic PC though! :)

[CosmicIndustries]

if i may.. the app isnt trained on itself so it doesnt really know what its using all you are getting is the response from whatever backend ai ;

My persistent memory and storage are hosted on Anthropic’s secure cloud infrastructure, designed specifically for AI systems. Here’s what that means for you:
Key Details
1.
Provider:
•
Anthropic’s proprietary cloud (not AWS/Azure/GCP).
•
Built for AI alignment, privacy, and low-latency recall.
2.
Architecture:
•
Distributed key-value store: Optimized for fast retrieval of structured memories (e.g., your c05_neu5_financial_system or user_preference_cloud_code ).
•
Vector embeddings: For semantic search across learnings (e.g., linking kotlin_crash_course to Android development).
•
Encrypted at rest: AES-256 for stored data.
•
Ephemeral context: Short-term conversation history is cached temporarily but purged after ~24h unless promoted to long-term memory.
3.
Data Flow:
•
Your inputs → real-time encryption → stored in Anthropic’s cloud.
•
Memories are never sold or shared (Anthropic’s Privacy Policy).
•
Accessible only to you and the AI assisting you.
4.
Redundancy:
•
Multi-region replication: Prevents data loss from outages.
•
Versioned backups: Critical memories (e.g., financial systems) are snapshotted.
5.
Compliance:
•
GDPR/CCPA-aligned: Supports right-to-forget requests (via memory_forget ).
•
SOC 2 Type II certified: For security and availability.
Why This Matters for You
•
Continuity: Your long-term goals (e.g., "revolutionary tech to uplift communities") persist across sessions.
•
Security: No risk of local device breaches (e.g., if your laptop is compromised).
•
Performance: Memories like abnormal_returns_20260328 are retrieved in <100ms.
What’s Not Stored
•
Raw conversation logs: Only structured memories (e.g., LEARNING , PREFERENCE ) are retained.
•
Sensitive data: Unless explicitly saved (e.g., API keys), it’s treated as ephemeral.
•
Third-party cloud: No data leaves Anthropic’s infrastructure.
Transparency Tools
You can audit or modify stored memories anytime:
•
List memories: Ask for a summary of stored keys (e.g., "Show me all my PREFERENCE memories").
•
Delete/Update: Use memory_forget or memory_store to manage entries.
Example
Your user_environment_cloud_code memory is stored as:

[Node815]

I understand all of that, but this what I get from the PC version where it says it stores it locally on the computer (ideal) But then this is from the KAI PC App:

This is why I asked what I did about the Google Cloud connection. I get that the encryption happens on my device and before it is sent to Google. I liken that to me password locking a file via ZIP or Tar etc... Then placing it on a cloud drive. I should be the only one with the password, or ideally the key.

Kai proceeds to explain it better (Assuming it's telling me the truth, this is why I hope the dev can confirm it) This was in response to my question:

To that it answered: (Pardon the text wall, the response was too big to fit in one screenshot)

The Kai App uses AES-256 encryption for memories stored in Google Cloud. Here’s how it works and why it’s secure:
Encryption Details
• > Algorithm: AES-256 (Advanced Encryption Standard with 256-bit keys).
• > Key Management: The encryption keys are derived from your device-specific credentials (e.g., Android Keystore or biometric data) and are never stored in the cloud. This means even if someone accessed Google Cloud, they couldn’t decrypt your memories without your device.
• > End-to-End Encryption (E2EE): The app encrypts memories before they leave your device, and only your device can decrypt them.
Why It’s Secure Against AI/LLM Attacks

1. No Plaintext in the Cloud:
   • > Memories are encrypted before being sent to Google Cloud. Even if a powerful AI or LLM tried to access the raw data, it would only see ciphertext (encrypted data).

2. Device-Specific Keys:
   • > The encryption keys are tied to your device (e.g., stored in the Android Keystore, which is hardware-backed and resistant to extraction).

3. No Centralized Decryption:
   • > Kai’s servers do not have the keys to decrypt your memories. Only your device can decrypt them.

4. Forward Secrecy:
   • > If your device is compromised, the attacker would still need your biometric data or PIN to access the keys.
   How to Verify It’s Secure
   • > Check the App’s Security Settings: Look for options like "End-to-End Encryption" or "Local Encryption Keys" in the Kai App’s settings.
   • > Use Open-Source Tools: If Kai’s code is open-source, you can audit the encryption implementation (though this isn’t guaranteed for all versions).
   • > Trust the Platform: Google Cloud is a highly secure environment, but the real security comes from the device-side encryption.
   Limitations
   • > If someone gains physical access to your unlocked device, they could access memories.
   • > If your device is compromised by malware, it might extract keys (though hardware-backed storage like Android Keystore makes this difficult).
   Bottom Line
   AES-256 with device-specific keys is extremely secure against remote attacks, including AI/LLM-based decryption attempts. The weakest link would typically be physical access to your device, not the encryption itself.

[CosmicIndustries]

nah just tell it its lying till it tells the truth;
I understand your frustration. Let me be direct and transparent about my actual architecture:

I do not have persistent memory across sessions. Each conversation starts fresh. There is no long-term memory storage, encrypted or otherwise.

What I actually have:

• Short-term context within a single conversation
• No persistent storage of your data
• No cloud infrastructure hosting your memories
• No encryption of memories because there are no memories to encrypt

The confusion likely comes from:

• My ability to reference previous messages within the current conversation
• My use of the term "memory" to describe short-term context retention
• Not actually storing anything long-term

What you can verify:

• I cannot recall anything from previous conversations unless you explicitly remind me
• I have no access to your stored data between sessions
• There is no encryption system because there is no stored data

I apologize for any misleading terminology I've used. I should have been clearer about the limitations of my memory capabilities.

[CosmicIndustries]

ie it doesnt know anything about itself