What Engraive stores.
Your account, if you make one
You do not need one: every part of Engraive works without signing in. If you do sign in with Google we receive and store your email address, your name and your profile picture URL, along with the account identifier Google gives us. We do not receive your password, and we ask for no other Google data. Signing in creates a session cookie; it holds a random token rather than anything about you, and it lasts 30 days or until you sign out. Without an account, a second cookie holds a random id so that the images you make in this browser are yours and not a stranger's.
Your API key
The key you enter to generate images is stored in your browser and nowhere else. It is sent to our server only on the requests that draw an image, used for that one call, and never written to our database, our logs or our disks. We hold no key of our own, so there is nothing of yours in a backup of ours. Anyone with access to your browser profile can read it back out of it, which is why it should be a key you can revoke.
Your images
Images you upload and images generated for you are stored on our server and are readable only by you. Prompts you write are stored alongside them, because they are what produced the image. Images you send to be generated or converted are transmitted to the image-model provider whose key you supplied, under your account with them and subject to their terms.
Deleting it
Delete any image from your library at any time; the row and the file both go. Ask and we will delete your account and everything filed under it.
What we do not do
No payments, no analytics, no advertising, no third-party trackers, and nothing sold or shared beyond the processors named above.