コンテンツへスキップ

Privacy Policy: what personal data do you collect and how do you handle it?

Operational Privacy Policy: the data controller is S-LINKDA TECHNOLOGY CO., LIMITED (Hong Kong), operating the Aegisky platform — exactly what the website, accounts, RFQs, orders, KYC/KYB and tickets collect, who processes it, your rights, and how to exercise them via [email protected].

This article is currently provided in English, the platform’s working language for international trade. Professional translations are being added.

1. Who this policy applies to and who the controller is

This policy applies to www.aegisky.com ("the platform"), business accounts, RFQ/RFI/RFP requests, quotations, orders, supplier onboarding, and customer support. The data controller and operator of the platform is S-LINKDA TECHNOLOGY CO., LIMITED, a Hong Kong company incorporated under the Companies Ordinance (Cap. 32), Companies Registry No. 1437572, Business Registration No. 52012879, registered at Flat/Floor F, 11/F, Golden Bear Industrial Centre, 66–82 Chai Wan Kok Street, Tsuen Wan, New Territories, Hong Kong; reachable at [email protected]. It acts as data controller and as the contracting and selling entity for orders; the contracting entity and commercial beneficiary are also named on the proforma invoice. The platform serves businesses, integrators, and government/institutional buyers; it is not directed at consumers or children.

Enterprise, public-sector, or academic customers requiring a signed Data Processing Agreement (DPA), Standard Contractual Clauses, or a vendor security pack can request them through the Contact channel or [email protected] before ordering.

2. What personal data we collect

  • Account data from the registration form: full name, work email, password (stored only as a salted hash — never in plain text), company name, phone number, and country.
  • Organization and KYC/KYB data from Account → KYC / KYB Verification: legal and trading names, registration and tax/VAT numbers, registered address, industry, website, expected volume and frequency, end-use description, beneficial owners (natural persons owning 25% or more), and uploaded documents (business license, certificates of incorporation/tax, proof of address, UBO declaration, export documents, End-User Certificate, passport/national ID/driver license where required).
  • RFQ and order data: part lists/BOMs, quotations, order numbers (ORD-YYYYMMDD-XXXXXX), delivery addresses and recipient contacts, Incoterms, and order correspondence.
  • Payment data: payment status, method, transaction references, and bank-receipt information you send. For wire/escrow/L/C we receive only the banking details needed to reconcile payments. Card checkout is not currently enabled; if it is enabled later, the full card number will be entered into and held by the card processor only — Aegisky will never store complete card numbers.
  • Export-compliance data: KYC/KYB records, end-user/end-use statements, certificates, and sanctions/denied-party screening results required for controlled goods (for example items classified ECCN 9A012).
  • Support data: tickets submitted on the Contact page (ticket numbers TKT-XXXXXXXX, type, subject, messages), RMA threads, photos, videos, and documents you upload.
  • Technical data: server logs (IP address, browser/device type, referring pages, error logs) and the cookie/local-storage data described in section 5.

If you provide data about colleagues, recipients, warehouse contacts, or beneficial owners, you must have a valid basis to provide it for shipping, fulfilment, and compliance, and you should make those individuals aware of this policy.

3. Where the data comes from

  • Directly from you: registration, organization and KYC forms, RFQs, orders, tickets, and emails.
  • From colleagues in your organization: team owners/admins inviting members and entering order or address data.
  • From Aegisky (operator of the platform), its fulfilment partners, and service providers acting under its instructions.
  • From your browser/device: technical logs and the consent-controlled cookies described below.
  • The platform does not offer social-login (Google/Facebook/etc.) and does not buy marketing lists or broker data; no such data is imported.

4. How we use personal data, and the legal basis

  • Performance of contract: providing the catalogue and quotations, accounts, order processing, fulfilment, and after-sales/RMA services.
  • Legal obligations: export control, sanctions and denied-party screening, customs and tax documentation, KYC/KYB verification, and accounting records.
  • Legitimate interests: payment fraud prevention, account/security protection, and (aggregated and anonymized) platform improvement and reliability.
  • Consent: marketing and market-update emails, and optional analytics cookies, each of which you can withdraw at any time.

Service/transactional messages — order confirmations, payment instructions and receipts, shipping updates, RFQ quotations and replies, RMA updates, KYC/compliance requests, and security notices — cannot be disabled while an account or order is active because they are part of the service. Compliance screening is human-reviewed; it is not a decision based solely on automated processing that legally binds you.

5. Cookies, local storage and analytics

  • Strictly necessary cookies/local storage: session and cart state, language/currency preference, security (CSRF/auth), and the cookie-consent record itself. These cannot be disabled.
  • Analytics (optional): anonymous usage statistics used to improve the platform, loaded only if you accept the analytics category.
  • Marketing (optional): personalization and promotional cookies, off by default unless you accept them.

The cookie banner (shown on first visit) lets you accept all, reject optional categories, or save a custom choice; you can change it later by clearing site data or using the cookie-settings control. The platform runs no advertising networks, no social-media tracking pixels, and no cross-site advertising. No third-party error/performance monitoring service is currently enabled; application errors are written to local server logs.

6. Who we share data with (operating entity, subprocessors and recipients)

  • The operating entity: Aegisky, operator of the platform, which provides contracting, fulfilment, finance, and support services for your region or order. The registered legal entity is named on the proforma invoice and order documents.
  • Supplying brands and manufacturers: only the minimum needed to fulfil or source an order (for example delivery details and product specifications).
  • Carriers, freight forwarders, and customs brokers (such as DHL, FedEx, UPS, EMS and quoted freight partners): shipment and clearance data.
  • Payment providers: card checkout is not currently enabled; the banks involved in wire/escrow/L/C settlement process payments. PayPal and consumer wallets are not connected.
  • Infrastructure providers acting under our instructions: hosting and compute (self-hosted Docker on our own infrastructure at Hetzner, fronted by the Cloudflare CDN), the PostgreSQL database (self-hosted on the same infrastructure), product media and uploads (local Docker volumes on the host, served by Nginx, with no third-party object storage), and transactional email delivery (Resend, sending from [email protected]).
  • Compliance tooling and public authorities: screening providers where used, and customs/export-control or law-enforcement authorities where legally required.

We do not sell personal data, do not share it with data brokers, and never share it with third parties for their own marketing. Suppliers and processors are contractually restricted to processing data for the relevant order or service.

7. International data transfers

Cross-border trade inherently involves transfers between your country, the Aegisky operating entity, regional fulfilment hubs, suppliers, and cloud infrastructure (including US-hosted services). Where required by law (for example GDPR transfers from the EEA/UK), transfers to processors are governed by appropriate safeguards such as Standard Contractual Clauses and suppliers’ equivalent measures; intra-group transfers are covered by the same framework. A copy can be requested via the DPA channel noted in section 1.

8. How long data is retained

  • Accounts and organization data: while the account is active, then deleted or anonymized except where records must be retained.
  • Orders, commercial invoices, payment records, customs and export-control records (including KYC/KYB files, End-User Certificates, and screening results): retained for the periods required by applicable tax, customs, accounting, and export-control law in the relevant jurisdictions (these vary by country; we retain for the longest applicable period for the record type).
  • Support tickets and RMA cases: retained as long as needed for the case and any statutory warranty/claims period, then anonymized.
  • Marketing data and optional consents: until you unsubscribe or withdraw consent.

Order-line compliance snapshots are stored immutably for audit and cannot be edited after order creation; this is a legal/security requirement, not a marketing use.

9. How data is protected

  • All site traffic uses encrypted HTTPS/TLS; passwords are stored only as salted hashes.
  • Role-based access controls and least-privilege staff access; team members see only what their role (owner/admin/buyer/finance/compliance/member) permits.
  • Card checkout is not currently enabled; if switched on, card data is handled by the processor’s PCI-DSS infrastructure, and full card numbers are never stored by Aegisky.
  • Immutable order and compliance snapshots, access logging, and reputable infrastructure providers (Hetzner hosting, Cloudflare CDN, Resend) with their own security programmes.

No transmission or storage method is completely secure. If you suspect a security incident involving your account, report it immediately via the Contact channel or [email protected].

10. Your data-protection rights and how to exercise them

Subject to applicable law (including the EU/UK GDPR and equivalent regimes), data subjects may: (1) access and receive a copy of their data; (2) correct inaccurate or incomplete data; (3) request erasure where legally available; (4) restrict or object to certain processing; (5) request data portability; (6) withdraw marketing/analytics consent at any time; and (7) lodge a complaint with a supervisory authority.

  1. 1Submit a ticket on the Contact page (or email [email protected]) from the email on the account, describing the request and, for organizations, confirming you are authorized for the named individuals.
  2. 2We verify identity before acting and respond within 30 days as required by GDPR-standard regimes; complex requests may be extended with notice.
  3. 3Some requests cannot be fully granted where records must be kept for tax, customs, export-control, or active-order purposes; we explain what is retained and why.
  4. 4California (CCPA/CPRA) and equivalent US-state residents have the same access, correction, deletion, and non-discrimination rights under applicable state law, exercisable through the same channel.

11. Children

The platform serves business and institutional procurement and is not directed to children. We do not knowingly collect personal data from children. If you believe a child’s data was submitted, contact support and it will be removed.

12. Changes to this policy

Material changes are posted on this page; the version in force at order time applies together with any order-specific terms stated on the proforma invoice. Transactional users are notified of material changes through the service where appropriate.

13. Contact

Privacy requests, DPA/SCC requests, and questions: use the Contact page (ticket types General inquiry or Order / after-sales support) or email [email protected]. Commercial/L/C correspondence uses [email protected]; automated order mail is sent from [email protected] (an unmonitored address — do not reply to it). Never send identity documents to an unverified sender; official channels are listed on the Contact page.

Was this article helpful?