iTravel AI · Desktop + cloud services
Privacy notice
How information is handled in the current desktop, backend and public information-site workflows, and how to contact the operator about your data.
1. Who operates the product
iTravel AI is operated by 赵家兴. Contact: 13180226075@163.com.
The product is intended for travel-agency customers and their authorized staff. An agency may provide information about its customers, travelers, suppliers and personnel; the agency must have appropriate authority for those inputs. This notice does not determine every party's legal role for every customer's deployment or replace a needed agreement.
2. Information processed and why
| Category | Examples | Purpose |
|---|---|---|
| Account and organization | Organization identifier, user name/email, password verification record, roles and session records. | Sign-in, authorized organization access, account administration and session security. |
| Travel-business records | Customer contacts, inquiries, itineraries, quotations, orders, supplier/resource records, service and necessary traveler details entered by authorized users. | Deliver the agency workflows selected by its staff; apply organization permissions and preserve relevant changes. |
| Financial records | Exact amounts, currencies/rate snapshots, approvals and employee-recorded payment/refund evidence. | Business accounting, reconciliation and audit. The current feature does not execute a bank transfer. |
| TikTok authorization | Creator account identifier, display information, granted scopes, expiry information and access/refresh tokens returned through official OAuth. | Identify the connected account and perform only permitted account/publishing operations. Tokens are encrypted on the backend, not returned as ordinary page data. |
| Media and posting records | Selected video and asset files, review/rights evidence, captions, privacy/interaction choices, approvals, publish session identifiers and returned states. | Prepare and review content, submit explicitly confirmed operations and investigate their results without duplicate posting. |
| AI and optional media input | A task request and the limited business/media information required for an enabled provider call; execution and token/usage records. | Perform the specifically invoked assistant or generation function. Optional external providers require separate configuration and are not all verified as available. |
| Operational and audit data | Request/task identifiers, operation time, actor, target, status, error category and relevant change records. | Troubleshooting, access enforcement, incident investigation, recovery and accountable business transitions. |
3. Official login and credential handling
Enter TikTok passwords and verification codes only on TikTok's official interfaces. iTravel AI does not ask for them. OAuth consent determines the scopes granted to this app; you can refuse or revoke the connection.
Backend sessions and role checks govern application access. The current desktop design keeps its running session in the Rust host; the client must sign in again after it closes. Business records remain in the backend database. TikTok tokens and backend configuration must not be copied into browser storage, ordinary logs or public files.
4. Recipients, providers and transmission
Authorized people in your organization can access records according to backend roles and assignments. Operator access for support or investigation must be limited to what is needed and permitted.
TikTok receives the selected content and authorized API requests when you connect an account or explicitly confirm a post. TikTok applies its own privacy policy and platform rules. Other enabled social, AI, video, voice or avatar providers receive only the input required for the invoked function; their separate configuration and applicable notices must be checked before use.
Network hosts, backend/storage operators and any expressly enabled HTTPS relay may process traffic needed to provide that environment. Some providers or network routing may involve processing in other countries. Actual hosting location, provider arrangements and any required safeguards must be confirmed for the environment before live customer data is accepted; no data-residency guarantee is asserted here.
This public information site uses Cloudflare Pages for static hosting. It has no analytics, advertising, tracking script, login form, upload form or business API. Cloudflare may process ordinary network request information needed to deliver and protect the static site under its own operational settings and privacy policy. The desktop's authenticated cloud services, business database and TikTok credentials are separate from this static hosting.
5. Retention and deletion
Records are retained in the applicable development/test or agreed service environment while needed for the enabled workflows, support, auditing, security and applicable obligations. No single automatic deletion period or backup expiry has been configured and confirmed for all categories; this notice does not promise an invented deadline.
You may request access, correction, export, restriction, disconnection or deletion through 13180226075@163.com. Requests are manually verified and assessed for the relevant records and authority. Some necessary business/audit records, backups or independent platform records may need separate handling. A local disconnect does not remove an already published TikTok post or establish that the platform deleted all associated data.
Before production onboarding, the operator must confirm the relevant retention settings and any customer-specific processing arrangement.
6. Your choices and data requests
You can decline an optional provider feature, avoid submitting unnecessary personal information, revoke TikTok authorization in its official security settings, or contact the operator to stop product access and discuss data handling.
For a request, email 13180226075@163.com with the request type and your iTravel AI account/organization. Do not send passwords, tokens, identity-document copies or a full customer export. The operator may use an established account channel to verify identity or representative authority and ask only for necessary additional information. See Support and data requests.
7. Security and limitations
Current controls include backend authentication, organization-scoped authorization, encrypted platform-token storage, controlled private-file access and audit records for key operations. No system is guaranteed to be risk-free. Production security certification, completion of all external integrations and signed cross-platform distribution are not asserted.
Users should safeguard their own accounts and devices, assign appropriate employee roles and promptly report suspected misuse without sending secrets.
8. Updates and status
This notice is effective from 16 November 2026. Material changes will be documented and the applicable notice made available before the changed practice is used. Product or platform approval does not substitute for review of data practices and required customer information.