VELUMA Commerce ERP
Read-only order management · TEMU US

Privacy policy

VELUMA Commerce ERP · Draft — not yet in effect · Last updated 2026-10-13 · 中文版

1. Who we are and what this policy covers

VELUMA Commerce ERP (“the application”, “we”, “us”) is a read-only order management application for cross-border (SEMI) sellers on the TEMU US site. It is operated by SAGE HOUSE WARES INC.. This policy explains what personal information the application processes, why, who can see it, how long it is kept and how to contact us. It covers this website, the application behind it and its connection to TEMU.

2. How the application works

  • Accounts are created on request by our administrator. There is no self sign-up.
  • A seller authorises the application in TEMU Seller Center and gives the resulting access token to our administrator, who stores it encrypted.
  • The application reads the seller's orders from TEMU. It never changes anything on TEMU.
  • A shipping recipient's details are fetched from TEMU only on demand, one order at a time, when a person who holds an individual recipient-data grant chooses a purpose.

3. Whose information we process, and why we hold it

  • Recipients of TEMU orders. We process order and recipient information to provide the application to the seller whose order it is, and on that seller's instructions. The seller decides why a recipient's details are looked at. We also keep records of who looked at which order, to secure the application.
  • People who use the application (the seller's staff and our administrators). We process their account and security information to run and secure the application.
  • People who contact us. We process what they send us to answer them.

4. Information we process

4.1 Store connection

The store's name and code; the TEMU access token, encrypted with a separate key and never shown again after it is saved; a fingerprint of the token; when it was verified and when it expires; and which administrator connected it.

4.2 Order records (without recipient details)

Parent and item order numbers; order status; order, confirmation, shipping and delivery times; region and site codes; shipping method, payment type and whether a shipping fee applies; goods name and specification; product and SKU identifiers and the seller's item code; quantities; and fulfilment type. These records contain no recipient name, phone number or address.

4.3 Recipient details, only on demand

When a person with the recipient-data grant asks for one order's recipient, the application fetches it from TEMU and keeps only: name, phone number, address line 1, address line 2, address line 3, postcode, region name 1, region name 2, region name 3, region name 4. TEMU's response also contains additional name, backup phone number, TEMU relay e-mail address, single-line address and name parts; these are discarded and never stored.

4.4 Account and security information

Username, an optional display name, the password (stored only as an Argon2id hash), role, store grants and whether the account holds the recipient-data grant. Sign-in session records with the IP address and browser user agent. Audit and security logs recording who did what and when, including the IP address, the browser user agent for recipient-data access, the order number of each recipient view and the purpose chosen, and the username typed at each sign-in attempt, including mistyped ones.

4.5 Server logs

The application log records the username of every sign-in attempt (including mistyped ones), and the username and order number of every access to recipient details. The web server's access log records each request's IP address, browser user agent and the address of the page requested, which can contain an order number or, in some administrative messages, a username.

4.6 Cookies

Two strictly necessary first-party cookies: a session cookie that keeps you signed in and a security cookie that protects forms. Both expire after 8 hours. There are no analytics, advertising or tracking cookies, and no third-party scripts, fonts or embedded content.

4.7 Messages you send us

Your contact details and what you write to us.

5. Where the information comes from

  • TEMU's Open API, under the seller's authorisation: order records and recipient details. The application calls only these read-only interfaces: bg.open.accesstoken.info.get, bg.order.list.v2.get, bg.order.decryptshippinginfo.get.
  • Our administrators: accounts, grants and store connections.
  • Your browser: session, IP address and user agent.
  • You: messages you send us.

6. Why we use it

  • To provide order management to the seller.
  • Recipient details only for one of these purposes, chosen at each view and recorded: create a shipping label; resolve a delivery exception; customer service request; data subject request.
  • To secure the application, prevent misuse and investigate incidents.
  • To answer requests and to meet legal obligations.

We do not sell personal information. We do not share it for cross-context behavioural advertising, and we do not use it for marketing, profiling, automated decisions or to train AI models.

7. Who can see it

  • The seller's staff with accounts for that store. Recipient details are shown only to staff who hold an individual recipient-data grant. New fetches from TEMU are limited to 30 per person and 200 per store per hour, and every view of recipient details is recorded.
  • Our administrators, who run the application, can access all information in it, including recipient details, when needed to operate or secure the application or on the seller's instructions. Their views of recipient details in the application are recorded too.
  • Our hosting provider, IT7 Networks Inc. (BandwagonHost), which runs the server and also makes automatic backups of the whole server (see sections 8 and 9). These backups contain everything on the server, including the database and the keys used to encrypt recipient details and store access tokens. We have asked the provider how the backups are protected and who can access them.
  • TEMU: the application sends TEMU read-only requests using the seller's access token.
  • Our e-mail provider, for messages you send us.
  • Authorities, where the law requires it.

We do not disclose personal information to anyone else, except as described in this policy.

8. Where it is processed

The application server is in the United States (California, United States). The hosting provider also keeps automatic backups of the whole server, which we cannot switch off. It stores them in several of its data centres, which can be in more than one country, and we cannot limit them to one country. We have asked the provider which countries are involved and will list them here once it confirms. The seller's staff may use the application from other countries, including China, and our administrators may also access it from outside the United States; information shown to them is then viewed from there.

9. How long we keep it

  • Recipient details are scheduled for deletion 30 days after TEMU reports the order completed (canceled or received). If TEMU has not reported the order completed within 90 days of its creation time, they are scheduled for deletion 90 days after creation. A daily job deletes them once that date has passed. The order number and timestamps of the record stay. Deleted recipient details are never fetched again.
  • Order records, the store's name and code, and order numbers (including those kept after recipient details are deleted and those in the audit log) have no automatic deletion yet; they are currently kept indefinitely. We will update this policy when deletion is available.
  • The store's access token is kept until our administrator deletes it. That removes it from the application; copies in backups remain until those backups are deleted. To end the authorisation at TEMU, the seller should also cancel it in TEMU Seller Center.
  • Accounts are kept while they are in use. When access ends we disable the account; disabled accounts and their history are kept as part of the audit trail.
  • Audit and security logs are kept to secure the application and investigate incidents. They have no fixed deletion schedule yet.
  • Session records are kept until sign-out, until 60 minutes pass without activity, or at the latest 8 hours after sign-in; expired records are removed by the daily clean-up.
  • Server logs on the application server are kept for up to 30 days, and the application's own database backups for up to 30 days; until such a backup is deleted it can contain recipient details, in encrypted form, that have already been deleted from the application. Separately, the hosting provider's automatic whole-server backups can contain all of the information described in this policy, including details already deleted from the application and the encryption keys. The periods above do not apply to these backups. The provider has not yet confirmed how long it keeps these backups; we will state this here once it does. About deleting these backups, the provider has told us: It cannot guarantee that these backups and their copies are deleted within 30 days.

10. How we protect it

  • Recipient details are encrypted with AES-256-GCM, and store access tokens with a separate key. On the running server the keys are kept in a protected configuration file, not in the database or in the application's own database backups. The hosting provider's automatic whole-server backups, however, contain both the database and that file, so this encryption does not protect the copies in those backups against anyone who can access them. The provider has not confirmed that the database or that file could be left out of these backups.
  • The hosting provider does not guarantee that its automatic backups are available.
  • Connections to TEMU use TLS 1.2 or later, and the website is served over HTTPS.
  • Access is role-based and limited to the stores a person is granted; recipient details need an additional individual grant. Access to recipient details is recorded.
  • Pages are not stored in browser or proxy caches. Passwords are stored only as Argon2id hashes.

No security measure is perfect, and we cannot guarantee that information will never be accessed without authorisation.

11. Your choices and requests

  • Recipients of TEMU orders: please contact the seller you bought from, or TEMU. If you contact us, we pass your request to the seller and help them answer it. We can find records only by order number, and we may ask the seller or TEMU to confirm a request before acting on it.
  • People who use the application: you can ask us for a copy of your account information, to correct it, or to close your account. We close an account by disabling it and removing its grants; the username and activity logs are kept for security.
  • We will not treat you differently for making a request, and we answer requests without undue delay.

12. Children

The application is a business tool and is not directed to children.

13. Changes to this policy

We post any change on this page and update the “last updated” date above.

14. Contact

SAGE HOUSE WARES INC. · Gaoyiyao3@gmail.com