BaseLinker Report Automation
Privacy policy
Last updated: 17 September 2026
How this private desktop application handles information.
1. Who operates the application
BaseLinker Report Automation is operated by T&Y, the Allegro seller TY-Pokusa, for its own business reporting and approved operators. This policy covers the local application and this information website. For privacy or support questions, contact ty.looking.gorgeous@gmail.com.
2. Google access and the information used
The current application requests the Google Drive OAuth scope https://www.googleapis.com/auth/drive. Google describes this as permission to see, edit, create and delete all of your Google Drive files. It can include shared files accessible to the authorizing account, subject to that account’s permissions. It is not a permission limited by Google to one report folder.
The program uses this access to locate its configured report folders, upload Excel reports, inspect file and folder metadata, move reports between staging, current and archive folders, and remove redundant live copies when matching archived content has been verified. Metadata includes file and folder IDs, names, parent folders, file types, sizes and checksums.
The application also downloads BaseLinker sales analytics reports onto the operator’s laptop. These files may contain business or personal information present in the source reports. Local diagnostic logs, screenshots and transaction records can include report details, file metadata and operational errors.
OAuth access and refresh tokens are stored locally so scheduled runs can reconnect to Google. The application does not receive the operator’s Google password and does not request Gmail, Calendar or Contacts access.
3. Purpose and sharing
Information is used to produce, synchronize, verify and recover the business’s report sets and maintain their history. Reports are transferred from BaseLinker to the laptop and then to the designated Google Drive folders through Google’s API. People with access to those folders can access the reports according to the folder’s sharing settings.
The application does not sell Google user data, use it for advertising, or use it to train AI or machine-learning models. It does not send reports or OAuth tokens to this public website or its hosting provider. Authorized operators may view reports and diagnostics for the business’s reporting and support purposes.
Use and transfer of information received from Google APIs are limited to the reporting functions described here and must follow the Google API Services User Data Policy, including its Limited Use requirements.
4. Storage and protection
Reports, credentials, logs and transaction records are stored on the operator’s Windows computer. Uploaded reports and archives are stored in Google Drive. Connections to Google’s services use HTTPS.
The current desktop version stores OAuth credentials in local JSON files; it does not add its own encryption to those files. Access depends on the protection of the Windows account, device and local file permissions. Credentials must be kept private and must not be uploaded with the public website. Google Drive access is controlled by Google account authorization and the existing file and folder sharing permissions.
5. Retention and deletion
Current local reports are replaced during later runs, and temporary backup files are removed as part of cleanup. Earlier Drive report sets are kept in dated archive folders. If an identical archive already exists, the program may permanently delete the redundant live copy before promoting the new set; the verified archived copy remains.
The program does not impose a fixed automatic expiry on archived reports or all local diagnostic records. These remain until the operator removes them under the business’s retention requirements. OAuth credentials remain locally until replaced or removed.
You can ask the operator to review or delete information by emailing the contact above. The operator can remove the relevant local files and Drive copies it controls, subject to applicable retention obligations. Other copies or backups must be handled separately.
6. Withdrawing Google access
You can withdraw access through your Google Account’s third-party connections by selecting BaseLinker Report Automation and removing its access. This stops future authorized Drive operations after Google processes the revocation. It does not delete existing reports, archives or local credentials. Contact the operator if you also want those reviewed or removed.
7. Visitors to this website
These are static information pages. They contain no application sign-in, report upload form, advertising or added analytics scripts. Cloudflare hosts the pages and may process technical request information, including IP addresses and traffic information, to deliver and protect them. See Cloudflare’s privacy policy for its practices. Following an external link takes you to a service with its own privacy practices.
8. Changes and contact
This page will be updated when the application’s data practices change. If a change introduces a new use of Google data or new permissions, affected operators must be informed and any required consent obtained before that use begins. Contact: ty.looking.gorgeous@gmail.com.