Skip to main content

Easy Distribution

Privacy Policy

How Easy Distribution handles your business data and your Google account information, including the Google Drive folder used for encrypted backups.

Effective date: 20 August 2026Last updated: 20 August 2026

1. Introduction

This Privacy Policy explains how Easy Distribution (“the application”, “the app”) collects, uses, stores, protects and deletes information. It is published by ThinkInICT (“we”, “us”, “our”), which develops and supports the application.

Easy Distribution is a business application for pharmacy distributors. It is designed to keep your business records on your own device, and it is built so that we do not receive a copy of them. Where the application connects to Google Drive, it does so on your behalf and into your own Google account.

This policy applies to the Easy Distribution application and to this website at https://app.thinkinict.com. Please read it before connecting a Google account to the application.

2. Application information

  • Application name: Easy Distribution
  • Published by: ThinkInICT
  • Application website: https://app.thinkinict.com
  • Type: pharmacy distribution, inventory and sales management software
  • Intended users: owners and staff of pharmacy distribution businesses
  • Contact: support@app.thinkinict.com

Easy Distribution is a business record-keeping application. It does not hold patient records, does not process prescriptions, and is not a medical device.

3. Information we collect

We do not operate a server that receives your business data, and we have no ability to read the records you enter into the application. The information described below is stored on your device, except where this policy explicitly says otherwise.

3.1 Business data you enter

The application stores the records you create in a database on the device. This includes products and prices, stock and stock movements, customers (the pharmacies you supply) and suppliers, purchases, sales invoices, credit balances, collections, customer and supplier returns, deliveries, expenses and the resulting reports, along with your business details and logo as they appear on your documents.

This data is created by you, belongs to you, and is not transmitted to us.

3.2 Device and application identifiers

  • A randomly generated device identifier, so the activity history can distinguish one device from another.
  • A randomly generated owner identifier, used to attribute the records created on the device.

Both are random values generated on the device and held in the operating system’s secure storage. Neither is a hardware identifier, an advertising identifier, an IMEI or a phone number, and neither is sent to us.

3.3 Diagnostic information

The application keeps a short technical log on the device to help diagnose faults, and applies redaction to it before anything is recorded. This log stays on the device. It is not uploaded automatically and no third-party crash-reporting or analytics service is integrated into the application. If you choose to send us diagnostic information while reporting a problem, you send it to us yourself and you can see what it contains first.

3.4 This website

This website is a set of static pages. It has no accounts, no sign-in, no contact form, no analytics or tracking scripts, no advertising and no cookies set by us, and it loads no fonts, scripts or images from third-party services. As with any website, our hosting provider processes standard server request logs (such as IP address, timestamp and requested page) for the purpose of operating and securing the service.

4. Google account information

Connecting a Google account is optional. The application runs, and can back up to the device, without one. You are asked to connect an account only when you choose to use Google Drive backup.

When you sign in with Google, the application receives the basic profile information Google returns for the account you select:

  • your Google account identifier;
  • your email address;
  • your display name, where your account has one; and
  • your profile picture URL, where your account has one.

This information is used to show you which account your backups are going to, and to remember that the device has been set up, so the app does not have to ask again at every launch. It is stored on the device in the operating system’s secure storage. It is not transmitted to us and it is not used for any other purpose.

The application also derives the encryption key for Drive backups from your Google account identifier, so that a backup can be restored on a new device simply by signing into the same Google account. See section 8.

Sign-in is handled by Google’s own official sign-in library. The application never sees or handles your Google password.

5. Google Drive data

Easy Distribution requests exactly one Google API scope, and no other:

https://www.googleapis.com/auth/drive.appdata

This is Google’s application data folder scope. It grants access only to a hidden, per-application folder (appDataFolder) inside your Google Drive. That folder is created for this application, is not visible in the Drive interface, and cannot be read by any other application.

This scope does not permit Easy Distribution to open, read, list or modify any other file in your Google Drive, and the application does not attempt to do so. The application requests no scope for Gmail, Contacts, Calendar, Photos or any other Google service.

Within that folder, and only within it, the application performs four operations against the Google Drive API:

  • List the backups it has created, reading only their file identifier, file name, size and creation time;
  • Upload a new encrypted backup archive;
  • Download an archive you have chosen to restore; and
  • Delete its own older archives, as described in section 12.

The Drive authorisation is requested separately from sign-in, at the point where a backup is actually being set up or taken — not as a condition of seeing your account name.

6. How Google data is used

Google account information and Google Drive access are used for one purpose: to provide the backup and restore feature you have asked for. Specifically:

  • to identify and display the Google account that backups are being sent to;
  • to obtain an access token that allows the application to write to, read from and tidy up its own application data folder;
  • to upload encrypted backups of your business data on the schedule you choose, or when you press Back up now;
  • to list and download your backups so you can restore one; and
  • to derive the key that encrypts and decrypts those backups, as described in section 8.

Google data is not used for advertising, profiling, marketing, analytics, training machine learning or artificial intelligence models, or for any purpose unrelated to backup and restore. It is not used to build a profile of you, and it is not combined with data from other sources.

7. How Google data is stored

  • Backup archives are stored in the application data folder of your Google Drive account. They are not stored on any server operated by us, because we do not operate one for this purpose.
  • Your Google account details (identifier, email, display name, picture URL) are stored on your device in the operating system’s secure storage, so that the application can show which account is connected.
  • Access tokens are issued by Google to the official Google sign-in library on your device and are held there for the session. The application requests a token when it needs one and does not write tokens into its own database. Refresh and revocation are handled by Google’s library and by your Google account settings.
  • We store none of it. ThinkInICT holds no copy of your Google account information, no access or refresh token for your account, and no copy of your backups.

8. How Google data is protected

Backups are never uploaded in readable form. Before an archive leaves the device it is compressed and then encrypted with AES-256 in GCM mode, an authenticated cipher, using:

  • a key derived with PBKDF2-HMAC-SHA256 over 210,000 iterations;
  • a random 16-byte salt generated for every archive, so two backups never share a key;
  • a random 12-byte nonce generated for every archive; and
  • a 128-bit authentication tag, so an archive that has been altered or truncated fails verification and is refused rather than restored.

A small plaintext header accompanies each archive so that a restore can check compatibility before attempting to decrypt. It contains format and schema version numbers, the application version, the date, the business name, row counts, a checksum and the cryptographic salt and nonce. It contains none of your business records, and it is bound into the encryption so that altering it invalidates the archive.

What this protects against, stated plainly. The encryption key for a Drive backup is derived from your Google account identifier, which is what allows you to restore on a new device by signing in again, without a separate passphrase to lose. The archive is therefore protected by two things together: the fact that the application data folder is reachable only by this application acting for your account, and the security of your Google account itself. It is not protected by a secret that we hold, because we hold none. Protecting your Google account — with a strong password and two-step verification — is the most important thing you can do to protect your backups.

All communication with Google is over encrypted HTTPS connections to Google’s own API endpoints.

9. Google API Services User Data Policy

Easy Distribution’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In particular, and without qualification:

  • we use Google user data only to provide and improve the backup and restore features that are visible to you in the application;
  • we do not transfer Google user data to third parties, except as necessary to provide those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to users;
  • we do not use Google user data for serving advertisements of any kind, including retargeting, personalised or interest-based advertising;
  • we do not sell Google user data, and we do not use it to train generalised artificial intelligence or machine learning models; and
  • we do not allow humans to read Google user data — including the contents of your Drive backups — unless we have your affirmative agreement for a specific purpose, it is necessary for security purposes such as investigating abuse, it is required to comply with applicable law, or the data has been aggregated and anonymised. In normal operation this does not arise, because your backups are held in your own Google account, encrypted, and we have no access to them.

10. Data sharing

We do not sell, rent, trade or share your personal information or your Google user data with third parties for their own purposes.

Your business records stay on your device. Your Google account details stay on your device. Your backups go from your device to your own Google Drive account and nowhere else. There is no advertising network, data broker, marketing platform or analytics vendor involved in the application.

The only circumstances in which information could be disclosed are where we are legally required to do so by a valid legal process, or where it is necessary to protect our rights or the safety of others — and in the case of your business records and your backups, we would have nothing to disclose, because we do not hold them.

11. Third-party services

  • Google Sign-In and the Google Drive API — used only where you have chosen to connect a Google account, for the purposes described in sections 4 to 9. Your use of Google’s services is governed by Google’s Privacy Policy.
  • Managed cloud database — where a deployment of the application has been specifically configured for team use across several devices, business data synchronises through a managed cloud database service so that colleagues share the same records. This is a separate configuration from the single-device, Google Drive backup arrangement described above, and the two are not used together. If this applies to your deployment it will have been agreed with you beforehand, and you can ask us at any time which configuration you are using.
  • Website hosting — this website is served by a commercial hosting provider, which processes standard server request logs as described in section 3.4.

No advertising, analytics, attribution, crash-reporting or social-media service is integrated into the application or this website.

12. Data retention

  • Business records on your device are kept until you delete them, clear the application’s data, or uninstall the application. They are under your control.
  • Google Drive backups: the application keeps the five most recent archives in its application data folder. When a new backup uploads successfully, older archives beyond the newest five are deleted automatically. Deletion happens only after the new archive is safely uploaded.
  • Your Google account details on the device are kept for as long as the account remains connected, and are removed when you disconnect it.
  • Diagnostic logs are short and are held only on the device.
  • We retain nothing, because we receive nothing. The exception is ordinary correspondence: if you email us for support, we keep that email as long as needed to help you and to keep a record of the enquiry.

13. Data deletion

You can remove your data at any time, and you do not need us to do it for you.

13.1 Disconnect the Google account

In the application, open Settings › Google Drive backup and choose Sign out. The application forgets the stored account details and stops backing up. Your business records on the device are not affected.

13.2 Revoke the application’s access to your Google account

Go to https://myaccount.google.com/permissions, select Easy Distribution, and remove its access. The application can then no longer reach its application data folder.

13.3 Delete the backups held in your Google Drive

Because the archives live in your own Google account, you delete them through Google. In Google Drive, open Settings › Manage apps, find Easy Distribution, and choose the option to delete hidden app data. Removing the app’s access as described in 13.2 also allows you to delete the data it stored.

13.4 Delete the business data on your device

Uninstalling the application, or clearing its data through your device’s application settings, removes the local database. The application also provides a hand over device function in Settings, which clears the business data from the device deliberately. Please make sure you have a backup you can restore before using either.

13.5 Ask us

If you would like help with any of the above, or you want written confirmation of what we do and do not hold about you, email support@app.thinkinict.com and we will respond.

14. Your rights

Depending on where you live, you may have rights to access, correct, export, restrict the processing of, or delete personal information held about you, and to withdraw consent you have given.

The design of Easy Distribution makes most of these rights something you can exercise directly and immediately: your records are on your device, in your possession; you can export them from the application; you can correct or delete them yourself; and you can withdraw the Google permission at any time as described in section 13. Where you need our help, or you want to make a formal request, contact support@app.thinkinict.com.

Connecting Google Drive is entirely your choice, and declining it does not limit any other feature of the application.

15. Security

  • Backups are encrypted with AES-256-GCM before they leave the device, and verified before they are restored (section 8).
  • Google account details and device identifiers are held in the operating system’s secure storage rather than in an ordinary file.
  • All network communication with Google uses encrypted HTTPS connections.
  • The application requests the narrowest Google Drive scope that can perform the job, so a compromise cannot reach the rest of your Drive.
  • Your business records are held on your device and are protected by your device’s own lock screen and encryption. Keeping your device locked, updated and in your possession is an important part of keeping those records safe.

No system can be guaranteed completely secure. We aim to use appropriate technical measures and to be honest about what they do and do not protect against — see the plain statement in section 8.

16. Children’s privacy

Easy Distribution is business software intended for use by pharmacy distribution businesses and their staff. It is not directed at children, it is not intended for anyone under the age of 16, and we do not knowingly collect personal information from children. If you believe a child has provided information through the application, please contact us and we will act on it.

17. Changes to this policy

We may update this policy — for example if the application gains a feature that handles data differently. When we do, we will change the effective date shown at the top of this page and publish the revised policy at https://app.thinkinict.com/privacy-policy.

If a change materially affects how Google user data is handled, or requires a new Google permission, you will be asked to review and approve it in the application before it takes effect for you.

Continuing to use the application after a change takes effect means you accept the revised policy.

18. Contact us

If you have any question about this policy, about what the application stores, or about a request relating to your data, please write to us. We aim to reply within two working days.

See also our Terms of Service and our support guide.