DSFulfill

Privacy Policy

Last updated: 2026/11/06
Operated by Shenzhen StellarWhale Technology Co., Ltd.

How the DSFulfill application accesses, uses, stores, and shares Google user data

The DSFulfill application (web and mobile), operated by Shenzhen StellarWhale Technology Co., Ltd., uses Google Sign-In / OpenID Connect only so a person can register and log in. This section states how that application accesses, uses, stores, and shares Google user data.

Google user data the DSFulfill application accesses: only the identity data you approve on Google's consent screen for the openid, email, and profile scopes. That is your Google account ID, email address, name, profile photo URL, and the short-lived token required to complete sign-in. The DSFulfill application does not access Gmail, Google Drive, Google Calendar, Google Contacts, YouTube, or any other Google user data.

How the DSFulfill application uses Google user data: only to create or match your DSFulfill account, authenticate later sign-ins, show your name and profile photo inside DSFulfill, keep the session secure, and send essential account or security notices to that email address. The DSFulfill application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How the DSFulfill application stores Google user data: we store Google user data on secured servers with access limited to staff who operate sign-in. We use encryption to protect your information. Security procedures are in place to protect the confidentiality of your data.

How the DSFulfill application shares Google user data: we do not sell Google user data. We do not transfer or disclose your information to third parties for purposes other than providing or improving DSFulfill registration and login. We do not use or transfer Google user data for targeted advertising, selling to data brokers or information resellers, credit-worthiness, lending, or training generalized or non-personalized AI or machine-learning models. We may share it only with infrastructure providers that host or secure DSFulfill under contract, with an administrator of a company workspace you joined, or when the law requires it.

How long the DSFulfill application keeps Google user data, and how to delete it: we retain Google user data only while your DSFulfill account is active and sign-in still needs it. You can revoke DSFulfill in your Google Account under Security → Third-party access, and you can ask us to delete the account by emailing [email protected]. We then delete or irreversibly de-identify that Google user data from active systems within 30 days, unless the law or security requires a longer period.

1. Introduction

This Privacy Policy explains how Shenzhen StellarWhale Technology Co., Ltd. ("DSFulfill," "we," "us," or "our") collects, uses, stores, shares, and deletes personal data when you use our products and services, including:

This Policy applies to the DSFulfill brand and applications operated by Shenzhen StellarWhale Technology Co., Ltd. It is intended to help users, customers, and reviewers (including Google OAuth verification) understand our data practices in plain language.

By creating an account, signing in (including with Google), connecting third-party platforms, or otherwise using the Services, you acknowledge this Privacy Policy. If you do not agree, please do not use the Services.

2. Who We Are

Controller / operator: Shenzhen StellarWhale Technology Co., Ltd.

Address: Room 301, Jiangnan Times Building, Longgang District, Shenzhen, Guangdong Province, China.

Privacy and data requests: [email protected]

Sales / product inquiries: [email protected]

Application names covered by this Policy include DSFulfill (web and mobile) and our Google Cloud OAuth / OpenID client used solely for user registration and login.

3. Information We Collect

Depending on how you use the Services, we may collect the categories of information below.

3.1 Account and profile information

When you register or manage an account, we may collect your name, email address, phone number, company / team name, role, password or authentication credentials, billing contact details, and preferences you set in the product.

3.2 Google user data (OpenID Connect / Google Sign-In for registration & login)

DSFulfill uses Google OpenID Connect (Google Sign-In / OAuth) only so you can register and log in to your DSFulfill account. We do not use Google to read your Gmail, Drive, Calendar, Contacts, or other Google Workspace content.

When you choose “Continue with Google,” we receive only the basic identity information you authorize on Google’s consent screen for OpenID authentication, typically:

  • OpenID subject identifier (a unique Google account ID used to recognize your login);
  • email address (to create / match your DSFulfill account);
  • name / display name;
  • profile photo URL (if provided by Google); and
  • short-lived authentication tokens needed to complete sign-in and maintain a secure session.

3.3 Business and operational data you submit to the Software

As a fulfillment / operations platform, DSFulfill processes business data you or your team upload or sync, which may include merchant/client records, product and quotation data, order and shipment information, inventory and warehouse activity, tracking numbers, invoices / wallet activity, messages, and files you attach.

Where that business data includes personal data of your merchants, buyers, or end customers (for example shipping names, addresses, phone numbers, or email addresses), you are typically the business that decides why the data is processed, and we process it to provide the Services to you. You are responsible for having a lawful basis to provide that data to us.

3.4 Connected storefront and marketplace data

If you connect Shopify or other storefront / sourcing platforms, we access the account and catalog / order data you authorize through that platform’s OAuth or API connection, solely to provide the connected features you request (for example order sync, product import, quotation, or fulfillment workflows).

3.5 Device, log, and usage information

We automatically collect technical information such as IP address, device type, browser type, operating system, app version, approximate location derived from IP, timestamps, pages or screens viewed, referring URLs, and diagnostic / crash logs. We use this information to operate, secure, and improve the Services.

3.6 Cookies and similar technologies

We use cookies and similar technologies on our websites for essential site operation, preferences, security, and analytics. For EU-facing cookie disclosures, see our Cookie Policy (EU). You can control cookies through your browser settings.

3.7 Support and communications

If you contact us (email, WhatsApp, contact forms, or in-product support), we collect the information you provide in that conversation so we can respond and keep a support record.

4. How We Access, Use, Store, and Share Google User Data

Purpose of Google integration: registration and login only (OpenID Connect). This section explains how DSFulfill handles Google user data for Google OAuth verification and the Google API Services User Data Policy.

4.1 What Google user data we access

We use Google as an OpenID identity provider so users can register and log in to DSFulfill with an existing Google account.

We access only basic OpenID identity information you authorize on Google’s consent screen for authentication scopes such as openid, email, and profile — typically your Google account ID, email, name, and profile photo.

We do not access Gmail messages, Google Drive files, Calendar events, Contacts, YouTube content, or other non-identity Google data. We do not request sensitive or restricted Google scopes for this Sign-In use case.

4.2 How we use Google user data

Google user data obtained via OpenID is used only to provide DSFulfill’s registration and login functionality, specifically to:

  • create a new DSFulfill account or match an existing account to your Google identity;
  • authenticate you each time you choose Google Sign-In;
  • display basic account identity in the product (for example name and avatar);
  • secure your session, prevent unauthorized access, and troubleshoot sign-in problems; and
  • send essential account / security notices to the email associated with your login when needed.

4.3 Limited Use and prohibited uses

DSFulfill’s use of information received from Google APIs / Google Sign-In adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We use Google user data solely to provide and improve user-facing registration and login features. We do not use Google user data for targeted advertising, personalized / interest-based / retargeted ads, selling data to brokers or information resellers, determining credit-worthiness or lending, building unrelated databases, or developing / improving / training generalized or non-personalized AI or ML models.

4.4 Sharing, transfer, or disclosure of Google user data

We do not sell Google user data.

We do not transfer or disclose Google user data to third parties for purposes other than providing DSFulfill’s registration / login service and operating the authenticated product experience.

We may share Google identity data only with:

  • infrastructure processors that host or protect the Services under contract (for example cloud hosting or security monitoring), solely to operate authentication and account storage;
  • your organization administrators if your login belongs to a company workspace you joined; and
  • authorities when required by applicable law, legal process, or to protect rights, safety, and security.

4.5 Storage and protection of Google user data

Security procedures are in place to protect the confidentiality of your data. Google OpenID identity information and related authentication tokens are stored on secured servers with least-privilege access. We use encryption in transit (HTTPS/TLS) and industry-standard controls to protect account credentials and session data.

4.6 Retention and deletion of Google user data

We retain Google OpenID identity information (such as Google account ID, email, and name) only while your DSFulfill account remains active and as needed to keep registration / login working.

You may disconnect Google Sign-In at any time in your Google Account permissions (Google Account → Security → Third-party access) and/or request deletion of your DSFulfill account by emailing [email protected].

After you revoke Google access or we complete a verified account-deletion request, we delete or irreversibly de-identify the associated Google identity data from active systems within a reasonable period (and no later than 30 days, unless a longer retention is required by law or for security / fraud prevention). Backup copies may remain for a limited period until rotated under our backup schedule.

5. How We Use Non-Google Information

We use the information described in Section 3 to:

6. How We Share Information

We do not sell personal data.

We may share personal data with:

7. Data Retention and Deletion (General)

We retain personal data only as long as needed for the purposes described in this Policy, including providing the Services, complying with legal obligations, resolving disputes, and enforcing agreements.

Operational order / shipment personal data processed for fulfillment customers may be deleted according to platform rules and our product settings. Where fulfillment-platform policies require it, buyer personal identity information may be deleted after shipment (for example within about 28 days) without offline backup.

To request deletion of your account or personal data, email [email protected]. Facebook-linked activity deletion instructions are also described on our User Data Deletion page.

We aim to complete verified deletion requests from active systems promptly and, for end-seller deletion notices affecting stored personal information, no later than 72 hours after a valid request where that commitment applies to the relevant integration.

8. Security

Security procedures are in place to protect the confidentiality of your data. We use administrative, technical, and organizational measures appropriate to the risk, including encryption in transit, access controls, least-privilege practices, logging, and staff access restrictions. No method of transmission or storage is 100% secure; please use strong unique passwords and protect your account credentials.

9. International Data Transfers

We are based in China and may process and store information on servers or with processors located in China or other countries. Where data is transferred across borders, we take steps designed to provide appropriate protection consistent with applicable law and this Policy.

10. Your Rights and Choices

Subject to applicable law, you may request access, correction, deletion, or restriction of your personal data, or object to certain processing. You may also:

11. Children’s Privacy

The Services are designed for business users and are not directed to children under 16 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact [email protected] and we will take appropriate steps to delete it.

12. Changes to This Policy

We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will change when we do. Material changes that affect how we use Google user data will be reflected in this Policy, and we will provide additional notice where required. Continued use of the Services after an update means you accept the revised Policy.

13. Contact Us

For privacy questions, Google user data questions, access/deletion requests, or OAuth-related inquiries about DSFulfill:

Shenzhen StellarWhale Technology Co., Ltd.
Room 301, Jiangnan Times Building, Longgang District, Shenzhen, Guangdong Province, China
Email: [email protected]