Privacy · how images are stored | ImgGo
ImgGo stores the name, email, avatar, and sign-in id returned by Google. Photos and results stay in private object storage and require sign-in. This page covers deletion, credits, processors, and contact.
Last updated: 2026-10-29
Who we are
ImgGo (imagego.qinshuhui.com) redraws a photo you upload and lets you keep editing that result in the same conversation. Email: admin@qinshuhui.com.
Account data
Public email sign-up is closed. Everyday sign-in uses Google. From that sign-in we store the fields the provider returns and the account record keeps: name, email address, avatar URL, and the account id used to recognize the login. We do not ask for a phone number or a contact list.
Administrators can sign in with email and password from a dedicated entry. That path is for administration, not public registration.
Photos you upload and results we store
Originals and generated images are kept in private object storage. Production uses a private Cloudflare R2 bucket. If an administrator later points storage at another compatible object store, that configuration is the one that applies. These files are not placed on public pages. Opening a file under /media/ requires a signed-in session. A signed-out request is rejected.
There is no automatic expiry. An image stays until you delete it in the library, or until we have to remove it for abuse, a fault, or a legal duty. After you delete it, the object is removed from storage when no other record still references the same file. That is a delete, not a move into a public bin.
Who sees an image during generation
Generation runs through FastClaw and the upstream model configured in the admin panel. To produce a result, the original and your instruction are sent along that path. The codebase does not contain a retention period we can quote, and it does not contain a fixed vendor list, so this page states neither a number of days nor a list of companies. The processor is whatever the admin configuration points at.
ImgGo has no public gallery and no switch that says “use my images for training.” We do not put your library on marketing pages. Whether an upstream model uses data under its own terms is that service’s statement. This page does not make it for them.
Credits
A successful generation spends the credit amount set in admin. When that setting cannot be read, the fallback is 5. A first Google sign-in receives the grant amount when the grant is enabled. The seeded amount is 10. Whether that grant expires depends on the configured number of days. Zero means the current grant has no expiry date. A failed generation refunds the credits it spent.
This version does not sell credits. We do not collect card numbers or payment-account details.
Cookies and logs
Sign-in needs a session cookie. Language preference uses the site’s own cookie. We do not sell personal information. The host keeps the technical logs required to complete and debug a request, such as time, path, and error text.
What you can do
After you sign in you can download your images and delete them in the library. To ask about an account, or if a deletion looks incomplete, write to admin@qinshuhui.com.
Changes
When this text changes, the date at the top of the page changes with it. Continuing to use the service means you are looking at the updated text.