aska.work

Privacy Policy

Last updated: 8 October 2026

This policy describes how aska.work (“the application”, “we”) handles data, including data received from Google APIs. Questions: hello [at] aska [dot] work.

1. How aska.work runs

aska.work is business software for online sellers. Each shop has its own instance of the application, with its own database, settings and access keys, running on equipment controlled by the shop or operated on its behalf. There is no central database: one shop’s data is never combined with another’s, and it is not sent to aska.work.

2. Google user data

The application uses Google Drive only if the seller connects a Google account, and only to store backups of the seller’s own store.

  • Permission requested: https://www.googleapis.com/auth/drive.file. It gives the application access only to files and folders the application itself creates. The application cannot see, read, list, change or delete any other file in the user’s Drive.
  • Data accessed: the account’s e-mail address and display name, and the Drive storage quota (to show which account is connected and whether there is space); and the folder aska.work and the files the application uploads into it.
  • How it is used: the application creates the aska.work folder, uploads backup archives of the seller’s Shopify store, product images and, if the seller chooses, other business data from the application into it, and lists that folder’s contents to show what has been uploaded. It does not delete files from Drive.
  • Storage of credentials: the access token granted by Google is stored only in the settings of that shop’s instance of the application. It is not sent to aska.work or to anyone else.
  • Sharing: Google user data is not sold, not transferred to third parties, and not used for advertising, credit decisions or any purpose other than the backup described above.
  • AI and machine learning: Google user data is not used to develop, improve or train generalised or personalised artificial-intelligence or machine-learning models.
  • Human access: no person reads the uploaded files on our side. They are in the user’s own Drive and readable by that account.
  • Revoking access: at myaccount.google.com/permissions at any time. Uploads stop immediately; files already uploaded remain in the user’s Drive until the user deletes them.

aska.work’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. What the backups contain

A backup is a copy of the seller’s own Shopify store: products, variants, metafields, collections, the theme, redirects, price lists, shipping and other settings, and product images. Orders are copied as what was sold and where it was shipped, without buyer names or e-mail addresses. The customer list is not included unless the seller turns that option on. If the seller chooses, archives can also hold other business data from the application, such as catalogue snapshots and reports, under the same rules.

4. Other services the seller connects

With the seller’s own credentials, the application also talks to marketplaces and shop platforms (such as Shopify, Amazon, Walmart, eBay, Reverb and Newegg) to read and, when a person confirms it, update the seller’s listings, prices and stock, and to read orders and reports. Buyers’ names, e-mail addresses, phone numbers and street addresses from those orders are discarded and not stored. Each service is subject to its own terms and privacy policy.

5. This website

aska.work is a static website. It uses no cookies, no analytics and no advertising. The hosting provider (Cloudflare) processes standard request data to deliver the pages and protect them from abuse.

6. Retention and deletion

Data stays in the shop’s instance for as long as the shop keeps it. To delete it, the shop removes the instance’s data and, if it wishes, the aska.work folder in its Google Drive. We hold no copy, so there is nothing further to delete on our side. Requests can be sent to hello [at] aska [dot] work.

7. Security

Access keys and tokens are kept in the instance’s settings, not in its database, logs or code backups. Remote access to an instance’s web interface requires sign-in through a private, identity-checked tunnel.

8. Children

aska.work is a business tool and is not intended for children.

9. Changes

Changes to this policy are published on this page with a new date. Changes to how Google user data is used are published here before they take effect.