Your API key, and how we guard it.

What we store

We never store your API key as plain text. The moment you save it, it is encrypted by Google Cloud KMS — a hardware-backed key vault that uses AES-256-GCM — and the key that locks it never leaves Google’s vault, designed so that not even Google’s own staff can extract it. Our database holds only an unreadable, scrambled version, and each stored key is cryptographically bound to your account so it can never be reused on anyone else’s.

What happens when you generate

Your server asks Google’s vault to briefly decrypt your key, uses it to make a single API call to generate your image, and immediately discards the plaintext. Your key is never cached, never kept in memory longer than that call, and never returned to your browser. Every decryption can be individually logged and audited, and access can be revoked instantly if anything looks suspicious.

The risk we cannot eliminate

We want to be honest: for a fraction of a second during image generation, your decrypted key exists in our server’s memory. This is unavoidable — any service that makes API calls on your behalf faces the same constraint, including every major image platform. No architecture removes this window entirely. What we can do, and have done, is make it as small, observable and revocable as possible.

What this means in practice

A breach of our database alone gives an attacker nothing usable — only scrambled ciphertext. Exploiting your key would require a live, authenticated compromise of our running server at the exact moment of a generation — an attack that is simultaneously logged and that we can shut down by disabling the encryption key within seconds.

What you can do

• · Set a spending limit on your key in Google AI Studio — this caps any potential damage.
• · Delete your key from myda at any time in your account settings. Deletion is immediate and permanent.
• · If you ever suspect your key is compromised, revoke it in Google AI Studio — that invalidates it everywhere, including here.