1. Technologies We Use

The platform uses browser local storage to save login tokens, language selection, layout width, quick templates, commonly used marketplaces, and similar preferences so that you can stay signed in and reduce repeated setup.

The backend may use necessary cookies or equivalent identifiers for sessions, verification codes, risk control, login security, and payment callbacks. These technologies are necessary to provide the service and protect security.

2. Categories of Use

Necessary: used for authentication, account security, verification codes, duplicate-submission prevention, payment status, language routing, and service stability. Disabling them may prevent the platform from working properly.

Preferences: used to save language, UI layout, quick entries, and recent configurations. Disabling them does not affect core functions but may require repeated setup.

Optional example analytics are off by default. With your permission, we record random session identifiers, example, module, category, device class, interface language, event, and time. Registration and first-use events are deduplicated by account after sign-in. Images, prompts, and email addresses are excluded; no data is sent to third-party analytics services.

3. How to Manage

You can clear cookies and local storage in your browser settings. After clearing them, you may need to sign in again, and some preferences, quick templates, and layout settings will return to default.

Everyone can allow, decline, or withdraw example analytics using Privacy preferences in the footer. Your choice is stored in localStorage. Analytics attribution is stored in sessionStorage for the browser tab session, up to 30 days. Retaining a chosen example so you can continue creating is a necessary feature and does not require analytics consent.

4. Security Reminder

Do not save sign-in state on public computers, shared devices, or untrusted browsers. Sign out after use to prevent others from accessing your assets, orders, and generated records.