ACE Commerce EnginePrivate operations platform

Privacy Policy

Last updated: 25 September 2026

In short
  • ACE Commerce Engine is a private e-commerce operations system. It is used only by its operator and authorized operators, and is not available to the public.
  • With the ACE administrator's authorization, ACE uses three Google permissions: Google Sheets, running its own scheduled tasks, and reading the signed-in account's email address.
  • Google data is used only to operate ACE. It is not sold and is not used for advertising.
  • OAuth credentials are held server-side and are never exposed to a browser.

1. Current operator

ACE Commerce Engine ("ACE") is currently operated by Proud Marketplace LLC-FZ, United Arab Emirates (the "operator", "we").

The operator of ACE may change. If it does, this section will be updated. ACE is a private e-commerce operations platform used by the operator and by operators it authorizes. It is not offered to the public, and there is no public sign-up or account creation.

2. What this policy covers

This policy explains how ACE accesses and uses data from Google services under the authorization of the ACE administrator (the Google account that administers ACE's Apps Script project and controls its authorization). It also covers this website. It describes ACE as it is currently built (see section 11).

This policy is limited to ACE's access to and use of Google user data. It is not a complete privacy notice for the operator's marketplace or customer-facing activities. Any notices for those activities are separate from this policy.

3. Google data ACE accesses

ACE runs as a Google Apps Script project in the ACE administrator's Google account. Google requires the administrator to authorize the permissions ("OAuth scopes") that the project uses. ACE requests exactly these three scopes and no others:

https://www.googleapis.com/auth/spreadsheets Google's description: see, edit, create and delete your Google Sheets spreadsheets

ACE's operational records are kept in Google Sheets. ACE reads and writes the spreadsheet its Apps Script project belongs to, and specific operational spreadsheets it is configured to use. Google grants this permission for all spreadsheets the account can access. ACE's code opens only the spreadsheets it is configured to use.

https://www.googleapis.com/auth/script.scriptapp Google's description: allow this application to run when you are not present

ACE's Apps Script project contains functions that create, check and remove its own time-based triggers, so that scheduled operational tasks can run when no one is present. Google requires this scope as part of the project's authorization set.

https://www.googleapis.com/auth/userinfo.email Google's description: see your primary Google Account email address

ACE reads the email address of the Google account of the authorized operator performing certain actions, as part of its operator security model, and records it with those actions in ACE's own operational logs (for example, queue decisions and order transmissions to fulfilment) so there is a record of who performed them.

ACE does not request access to Gmail, Google Drive files other than spreadsheets, Google Calendar, Google Contacts or any other Google service.

4. How the data is used

Data obtained through these permissions is used only to provide ACE's own operational functions, such as:

  • tracking orders and their fulfilment status;
  • building and recording the daily work queue and the decisions made on it;
  • passing orders to fulfilment (see section 6);
  • managing customer-service cases;
  • keeping an audit trail of what was done and by which account;
  • showing authorized operators ACE's current state in ACE's private operator console.

The operator console reads from ACE only through ACE's read functions. It does not use the authorized permissions to edit spreadsheets.

5. Where data is stored

ACE's operational records are stored in Google Sheets under the ACE administrator's Google account, and are subject to Google's own terms and privacy policy. How long those records are kept is controlled by the operator in those spreadsheets.

ACE's private operator console has no database of its own. It reads what it needs from ACE when a page is requested and does not keep a copy. Its connection logs record request outcomes (for example, success or the type of failure, and timings), not the data returned.

The console's server runs on third-party infrastructure. Infrastructure and hosting service providers may process data where this is necessary to provide that service. Error reports from ACE's Apps Script project are sent to Google Cloud's logging service, as configured in that project.

6. Sharing and disclosure

  • No sale. Google user data is never sold.
  • No advertising. Google user data is not used for advertising, including personalised, retargeted or interest-based advertising.
  • Fulfilment. ACE may share with the operator's fulfilment provider the operational order information needed to fulfil customer orders, such as order identifiers, delivery information, item and quantity details, and fulfilment status.
  • Google. Google processes data as the provider of Google Sheets and Apps Script.
  • Infrastructure providers. Infrastructure and hosting service providers may process data where this is necessary to provide ACE.

Apart from the above, Google user data is not transferred to anyone else.

7. OAuth credential handling

  • The Google authorization used by ACE's server is started and controlled by the ACE administrator, signed in to the administrator's own Google account.
  • OAuth credentials (the client secret and the ACE administrator's refresh token) are held only in the private configuration of ACE's server. Short-lived access tokens are held in that server's memory until they expire.
  • Credentials are never included in web pages, browser code, public files or source code, and are never sent to a browser.
  • ACE's connection logs are built to exclude credentials and tokens.

8. Google API Services User Data Policy

ACE's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

9. This website

This website is a set of static information pages. It has no login, forms, cookies, analytics or tracking, and it loads nothing from other websites. It does not collect personal information. Like any website, the hosting provider that delivers these pages processes standard technical information, such as IP addresses, in order to serve them.

10. Revoking access

The ACE administrator can revoke ACE's access at any time from the Google Account permissions page at myaccount.google.com/permissions. Once access is revoked, ACE can no longer use these permissions until the administrator authorizes it again.

11. Changes to this policy

This policy will be updated when ACE's relevant data practices materially change, and the "Last updated" date above will change with it.

12. Contact

Questions about this policy or ACE's use of Google data: t.proudfoot90@gmail.com.