SaSaCode SaSaCodeLast updated 2026-08-23. This describes what the SaSaCode desktop app and its backend (run by Mainstream Net Services) collect, where it's stored, and what's sent to an AI provider while you use it.
When you sign up, we store your email address, a hashed password (never the password itself), and your subscription status. Payments are processed by our payment processor, CHIP — we don't receive or store your card details.
Your chat messages, the tool calls SaSaCode makes on your behalf, and their results are stored on our servers so you can reopen a past session from Session History. This history is tied to your account and isn't shared with other customers.
To generate a response, your message — and any file or code content relevant to it — is sent to whichever AI model is powering that session: our included provider by default, or your own OpenAI/Claude/DeepSeek/Gemini account if you've turned on "Bring your own key." This is inherent to how the assistant works — it has to see the content to reason about it. We don't use your conversations to train our own models.
If you save your own provider API key, it's encrypted and stored on our servers so it can be used on your behalf during your sessions. It's shown to you once at save time and never displayed back in full afterward. You can remove it at any time from the key manager in the app.
SSH credentials and other secrets you add to the in-app Vault are encrypted using your own operating system's credential store (Windows DPAPI) and stored only on your machine. They are never transmitted to or stored by our servers — not even in encrypted form. When a secret is used in a command, the AI model sees the variable name, never the value.
The microphone button uses your browser engine's built-in speech recognition. Depending on your system, this may send audio to a third-party speech-recognition service (not an AI provider you've configured) to produce the transcript — the resulting text is then handled the same as anything you typed.
The desktop app reads and writes files directly — on your own machine, or on a server you've connected it to over SSH using your own credentials. We don't keep a copy of your project files on our servers; the only record we keep is the conversation log described above.
You can delete individual sessions yourself from Session History at any time. To close your account and remove your remaining data, contact us at the address below.
Questions about this policy or your data: info@msnet.my.