1. Use of this website
This website provides brand, product, service and partnership information. Interactive examples illustrate services without connecting to live AI conversations, creating orders or charging fees. Browsing does not place an order, establish a contract or give blanket authorization for future data processing.
For inquiries and related personal-information questions, contact Mr. Bai at 15526188088 or bb@xiongqingqing.com.cn. Provide only information necessary for your request. Do not send passwords, verification codes or unrelated identity documents or financial-account information.
The website pages use no analytics tracking, advertising cookies or persistent browser storage and request no camera, microphone or location permissions. Telephone links invoke the device dialer; external websites apply their own rules. Technical logs processed for website operation and security are limited to those purposes under data minimization and are not used for advertising profiles or model training.
2. Data use by service scenario
| Scenario | Data scope | Purpose and access boundaries |
|---|---|---|
| Accounts and identity | Account identifiers, necessary contacts, roles and eligibility | Authentication, access control and eligibility; separate personal and organizational roles |
| Everyday services and delivery | Needs, service address, timing, order and progress | Access for actual providers and roles that need it for delivery |
| AI tasks | Necessary inputs, authorized context and material | Current-task execution, without automatic access to all history, private chats or other organizations |
| Operations and customer service | Offerings, customers, knowledge, orders and authorized business information | The organization’s operations and services, not default training or assistance to other businesses |
| Property and homeowner governance | Necessary lists, work orders, eligibility and public-affairs records | Separate processing by property managers and committees within responsibility and authority |
| Payments and entitlements | Specific orders, amounts, human confirmation and accounting references | Confirmed transactions, reconciliation and support; secrets and payment credentials are not ordinary model context |
| Support and disputes | Issue description, related order and necessary evidence | Authorized handling and review, without default access to all private conversations |
We process necessary information for the service you choose. Accessing one entry point does not open all information. This inventory explains service-level purposes; function notices and actual inventories supplement fields, recipients, retention and basis.
3. Conversations, memory and organizational separation
People or agents joining a conversation see messages after joining by default; authorized users choose earlier context to share. Private messages are not automatically given to AI. Model, agent, organization or role changes use the corresponding permissions and do not carry another party’s private information across.
Long-term memory and task records are based on authorized content, with traceability, correction and deletion. Handover covers authorized work material, not all private staff conversations. Formal order and accounting states follow business records, not chat summaries.
4. Training, improvement and aggregated analysis
Raw orders, customer information, private knowledge and conversations are not used by default for training or other businesses. Additional training, evaluation or secondary purposes require separate explanation and authorization; refusing those purposes is not refusal of ordinary service. Providers follow the same purpose limits.
City trends and industry comparisons are limited to anonymous aggregation that does not reveal specific businesses or people. Removing names or replacing identifiers is not itself anonymization; aggregate results also require re-identification-risk controls.
5. Providers, locations and authorization inventory
Actual providers, functions, received information, processing locations, retention and training restrictions belong in the inventory. A user-supplied API or self-hosted model does not authorize sending all data, and switching models cannot silently expand processing or charges.
Services involving third-party models, computing or SDKs disclose the provider, information received, purposes, processing locations and retention arrangements before use. Cross-border transfers or processing by independent third parties require applicable notices, authorization and procedures before they occur. Browsing this website does not grant that authorization.
6. Retention, export, deletion and rights requests
Conversations, memory, source material, summary indexes, caches and business records are managed by purpose. Export and deletion scope, backups, legally retained records and limitations should be clear. There is no blanket promise of permanent retention, one-click export of all third-party data or immediate deletion of every record.
Use the actual published rights channel to request access, correction, deletion or withdrawal, subject to applicable conditions. Authorized users still manually confirm decisions involving money or entitlements; data permission and task budgets do not replace transaction confirmation.
7. Consumer incentive project data
Projects use registration and authorization, eligibility, budgets and receipts, reserved or used limits, orders and delivery evidence, redemption and refunds, and closure records for execution and review. Subsidies, business offers and platform points are separately managed and accounted for; reports must not merge them into an untraceable balance.
Officers, finance, headquarters and participating businesses access records by responsibility. Businesses participate under approved rules and cannot change institutional project rules. Integrations and imports require authorization, validation and auditability; AI output does not replace manual confirmation of funds, budgets or entitlements.
8. Voice and project-audit data boundaries
Voice supports communication, reminders and discussion. Final evidence links the actual confirmation card, authentication, permissions and execution state; an isolated transcript of “yes” is not payment authorization. Recordings, transcripts, summaries and account-action records are managed separately by purpose, without default permanent retention or training use.
Institutional projects provide necessary records to authorized reviewers or auditors under agreements with traceability: eligibility, transactions, purposes, delivery, funds, changes, exceptions and actual results. Officer and reviewer roles and forecast versus actual measures remain distinct; audit purposes do not open minors’ or other private information to every participant.
9. Website browsing and interactions
This website uses static pages and system fonts. Language switching, filters, menus and examples use page memory and URL fragments, without AI calls, cookies, persistent browser storage or analytics SDKs. Information necessary for website operation and security is handled separately from product conversations, orders and other business records.
10. Licence conditions for transaction records
For transaction-platform transmission and processing records subject to the licence’s special conditions, the certificate requires retention for at least one year. The applicable records, start date, access controls and deletion arrangements must be specified for the actual service. This does not impose a blanket one-year retention period on all chats or other personal information.
11. Work identity and organizational data
The personal workspace in 小张罗 can bring together tasks from multiple organizations. Work is performed under a clear organizational role, and business records remain subject to that organization’s permissions. Private diaries do not become organizational data; schedule conflicts are flagged for authorized people to resolve.
Organizations can define observers with limited access to information, AI queries and summaries. Viewing does not grant editing, payment or approval rights. Export and sharing need separate authorization; revocation stops the relevant access and subscriptions.
Drafting references
These public rules inform the copy. Actual processing must follow the functions and applicable requirements; citation does not replace performance.