Privacy notice
Updated: October 18, 2026 (guardian consent rules are pending activation)
This notice covers account sign-in, draft storage and image creation on the Jichuang website at jichuangrobot.com. Local website drafts are separate from local iPhone App drafts. You can read this page without signing in.
Google sign-in
Only after you choose Google sign-in and authorize it does the website verify your identity through official Google services. It requests openid profile, uses the stable account identifier (sub) to create or find your account, and uses your display name as the account label. Matching email addresses or names are not used to merge separate accounts automatically.
The website does not request email permission or access Gmail, Google Drive, Google Photos or contacts. It requests no write permissions and no offline access. The Google access token is used only for the server-side identity lookup during sign-in. It is not saved as a draft or stored in your browser.
The Google account identifier and account display name are stored on the website server for sign-in, account linking and display. They are not used as image-model input, for advertising or for sale. You can revoke the authorization in your Google Account third-party application settings. Revocation does not delete existing account records on this website.
Other sign-in methods and account records
For phone sign-in, the phone number you enter is sent to Alibaba Cloud SMS authentication to send and check a verification code. The code is submitted when you verify it. The website stores the phone number, request identifiers, validity status and retry information for the challenge, but does not store the plaintext verification code. After sign-in, your phone number is stored on the server as the identifier for that sign-in method.
For Alipay sign-in, the website obtains the account identifier needed for sign-in through official Alipay authorization and APIs. Linking another sign-in method requires a check of the currently signed-in account. Accounts are not merged just because display names match. The sign-in page shows which methods are available.
Sign-in state and security records
Necessary cookies maintain your session and connect the authorization or verification challenge to the browser that started it. They help prevent forged requests, repeated callbacks and account mix-ups between tabs. The server stores session-token hashes, account associations, validity status and necessary flow records. SMS abuse protection also uses the request source IP address and sending frequency.
Signing out ends the relevant session. It does not delete your account or saved work. Blocking necessary cookies may prevent sign-in from completing.
Local drafts and server data
Text, reference images, sketches and drafts in the local workspace remain in the current browser. Clearing site data or changing browser, device or website address can make these local records unavailable. Signing in does not automatically upload local drafts. They do not automatically sync to the iPhone App or other devices.
When you use account projects or image generation that submit data to the server, the server stores the relevant project inputs, revisions, submitted images, generation jobs, results and request associations to process requests and retrieve results. These records are separate from browser-only drafts.
Image generation and external services
When you confirm sending a generation or editing request, the relevant idea, edit instructions, reference image or source image is sent to the external image service for the selected model. Attaching an image or saving a local draft does not start generation automatically. Submit only content you have the right to use, and avoid unnecessary personal information in prompts or images.
External image services process submitted content under their own rules. The website uses results and job status to deliver the feature you requested. It does not attach your Google sign-in identifier or display name to image-model input.
Access, correction and deletion requests
You can remove local drafts by clearing this website’s data in your browser. This does not also delete server accounts, generation records or data already processed by external services.
If you use Google sign-in, contact the operator through the application support email shown on the Google authorization page to request access, correction or deletion of account data. The operator needs to verify which account the request concerns. The website currently does not offer self-service account deletion. Do not send passwords, SMS verification codes, API keys or private keys.
Declaration and separate choices
After activation, before first online processing, users declare either under 14 or 14 and over. No ID document, precise birthday or real name is collected. Everyone uses the same interface; there is no child mode, guardian account or child sub-account.
For under-14 users, a guardian separately confirms core account/our cloud processing, Qwen processing and GPT processing. Age and guardianship are declarations. SMS checks control of a contact number, not adult identity or legal guardianship. Unconfirmed scopes and scopes without applicable provider facts stay unavailable.
Contact and processing
A guardian voluntarily supplies a contact phone for verification, consent contact and necessary review through Alibaba Cloud PNVS. It is not a login identity, linked account phone or authorization to access work.
The server retains age band, scopes, notice versions, times and necessary transaction/device proof hashes and minimal audit. Contact numbers are encrypted with a separately derived matching digest. Core covers the account and our cloud project data. Qwen/GPT additionally process explicitly submitted descriptions, reference/source images and analysis content; guardian contact numbers are not sent as model inputs.
Retention and cleanup
After activation, the website keeps its device consent cookie for 30 days to resume the consent flow on the same device after a sign-in session expires. The cookie itself grants no sign-in or account access. Sign-in sessions remain valid for 24 hours, and explicit sign-out clears the device cookie. Short-lived confirmation receipts last 300 seconds; browser flow bindings last 600 seconds.
Unattached transactions and contact data are cleared within 24 hours. Necessary contact data stays while core consent is valid; recoverable numbers and matching digests are cleared within 24 hours of core withdrawal or account deletion. Withdrawing only a model retains necessary core contact data.
Valid consent records remain for the authorization period. Minimal audit for replaced, withdrawn or deleted consent is removed 180 days after that event. Required/revoked restrictions remain until safe reconfirmation or account deletion. These are product retention periods; protected digests and audit are not anonymous.
New backups owned by the dedicated manifest are retained for seven days. A separate durable revocation/deletion journal is replayed before restoration. Unknown historical backups need separate review. Provider retention/deletion follows applicable service rules; local deletion does not promise immediate deletion of all provider records.
Withdrawal and review
Qwen and GPT can be withdrawn separately. Core withdrawal closes both models for new processing. Already submitted tasks retain their original reconciliation and safety boundaries. Withdrawal is not account deletion and grants no other person access.
Use the current official support channel for access, correction, deletion or guardian contact review. Review must match the original account and guardian records; a new number cannot take over an account. An approved review may withdraw or permit renewed verification, never directly grant scopes. Do not send passwords, verification codes, private keys or unnecessary child identity documents.
Provider conditions
General PNVS API terms can support adult guardian contact verification. General Bailian business-data terms may conditionally cover lawfully authorized under-14 data. Actual account terms, service/model, region, logging and data flow still need confirmation.
The GPT intermediary’s basic processing terms and child-data scope remain unresolved. Scopes with unknown facts remain disabled. Guardian consent does not replace applicable provider conditions.
