Cross-Border Engine (跨境引擎) is a cross-border e-commerce operations platform operated by Feihe Cross-border E-commerce (Guizhou) Co., Ltd. — "we", "us", "our". We are the data controller for the personal data described in this policy.
Our company registration number, registered address and tax identification details are available on request under section 13. We do not publish them here because this page is served from a separate infrastructure host; we will provide them in writing, and they appear on every invoice.
This policy applies to kuajingyinqing.shop and its subdomains, to the web application at /app, and to any related service that links to this page.
Data protection contact: [email protected] — please use the subject line "Privacy request". We do not currently have a statutory Data Protection Officer; privacy enquiries are handled by our founder-level operations team, who are accountable for this policy.
We collect only what the service needs to work. We do not buy personal data from data brokers, and we do not run advertising trackers on this site.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | Email address, display name, password hash, language and site preferences, plan and subscription status | You, at sign-up and in settings |
| Authentication data | Session identifier, sign-in timestamps, IP address at sign-in, failed-attempt counters | Automatically, when you sign in |
| Technical data | IP address, browser and device type, requested URL, HTTP status, response time | Automatically, from your requests |
| Usage data | Which features you open, which actions you run, error states | Automatically, inside the app |
| Your content | Products you research, pricing inputs, generated listing copy, images and documents you upload, notes and saved views | You |
| Billing data | Plan, invoice history, order IDs, last four digits and card brand as reported by our payment provider, billing country | You, and our payment provider |
| Support data | Messages you send us, and the order or account details needed to answer them | You |
What we do not collect: full card numbers, CVV codes or bank credentials (these go directly to our payment provider); your government ID; your health data; precise device geolocation.
Where the EU or UK GDPR applies, we rely on the legal bases in the table below. Where another law applies, we process on the equivalent grounds.
| Purpose | Legal basis |
|---|---|
| Creating and running your account, delivering the features you use, providing support | Performance of a contract (Art. 6(1)(b)) |
| Taking payment, issuing invoices, meeting tax and accounting obligations | Contract; legal obligation (Art. 6(1)(b), (c)) |
| Keeping the service secure: rate limiting, abuse and fraud detection, credential protection, audit logs | Legitimate interests (Art. 6(1)(f)) — operating a service that users can trust |
| Diagnosing faults and improving existing features | Legitimate interests (Art. 6(1)(f)) |
| Sending service messages: trial expiry, renewal reminders, security notices, material changes to terms | Contract; legal obligation |
| Optional product updates and marketing email | Consent (Art. 6(1)(a)) — withdrawable at any time; every marketing email has a one-click unsubscribe |
| Analytics that go beyond aggregate server logs | Consent — loaded only after you choose "Accept all" in the cookie banner |
Where we rely on legitimate interests, we have weighed those interests against your rights and expect no adverse impact: the processing uses data you already give us, stays within the service, and never involves profiling that produces legal effects. You may object at any time (see section 10).
We do not use your data for automated decision-making that produces legal or similarly significant effects, and we do not build advertising profiles of you.
Several features (listing copy, translations, product-image work, analysis summaries) are generated with large language models. We are explicit about what that means:
The identity of our current model provider is part of the sub-processor list in section 6 and is available on request. We notify account holders by email before adding a new sub-processor that processes your content.
Our application servers are located in the United States (Silicon Valley), and backups are replicated to object storage in another region. If you access the service from the EEA, the UK, Switzerland or another jurisdiction with transfer restrictions, your data will be transferred outside your country.
Where required, we rely on Standard Contractual Clauses approved by the European Commission (and the UK Addendum where applicable) as the transfer mechanism, supported by a transfer impact assessment covering the provider, the data categories and the legal environment of the destination. Technical measures — encryption in transit with TLS, access control, and minimisation of what is transferred — apply to every transfer.
You may request a copy of the relevant safeguards under section 13. Because our servers are outside the EEA, we cannot offer a version of the service where your data never leaves your region.
| Data | Retention |
|---|---|
| Account and profile data | While your account is open, then deleted within 30 days of closure |
| Your content (products, copy, images, documents) | While your account is open. Delete it yourself at any time; it is purged from live systems immediately and from backups within 7 days |
| Application and access logs | Up to 90 days, on a rolling basis |
| Security and rate-limit records | Up to 90 days |
| Invoices and transaction records | As long as tax and accounting law requires (currently up to 10 years). These records are kept even after account closure, and are limited to what the law demands |
| Support correspondence | Up to 24 months after the matter is closed |
| Encrypted backups | 7 daily generations, then rotated out; off-site copies follow the same cycle |
Where we cannot delete data yet because it is inside a backup generation, it stays encrypted and inaccessible until that generation expires, and is never restored except to recover from a failure.
The measures below are in production today. We describe them concretely rather than with adjectives, so you can judge them.
HttpOnly, SameSite=Lax and Secure; they carry an opaque identifier, not your identity.0600 permissions on the server, outside the web root, and are absent from source code, exports and backup archives.No service can promise perfect security. If we become aware of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority without undue delay and, where required, notify you directly — including what happened, what data was involved, and what we did about it.
If you believe you have found a vulnerability, please contact us under section 13 before disclosing it publicly. We will acknowledge within 2 business days and will not pursue legal action against researchers who act in good faith and avoid privacy violations, data destruction or service disruption.
If you are in the EEA, the UK or Switzerland, you have the right to:
If you are a California resident, you have the right to know what personal information we collect and how it is used, to delete it, to correct it, to opt out of its sale or sharing (we neither sell nor share it for cross-context behavioural advertising), to limit the use of sensitive personal information (we do not collect any), and not to be discriminated against for exercising these rights.
In all cases: we respond to verified requests within 30 days, and tell you if we need up to 60 further days because a request is complex. Requests are free. We verify identity by confirming control of the account email; we will never ask you for your password in order to process a request. To exercise any right, email [email protected] with the subject "Privacy request", or use the support widget in the app after signing in.
If you are a business customer acting for your own customers, we act as your processor for their data and will assist you in responding to their requests.
The service is a business tool. It is not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.
The version number and last-updated date at the top of this page always reflect the current text, and we keep earlier versions so you can compare them. For material changes — a new category of data, a new purpose, a new class of recipient — we will notify registered users by email at least 30 days before the change takes effect, unless the change is required sooner by law or is strictly in your favour.
Continuing to use the service after a change takes effect means you accept the updated policy. If you do not, you can close your account before the effective date.
If you are not satisfied with our response, you may complain to the data protection authority in your country of residence, place of work, or the place of the alleged infringement. We would rather hear from you first.