Privacy Policy for MD – Google Sign-In and Data Handling

Privacy Policy for MD

Effective Date: 2024-08-20

1. Introduction

MD is committed to protecting the privacy and security of your data. This privacy policy explains how MD accesses, uses, and protects Google user data, including the Google Sign-in process through mdauth.themesia.com.

2. Google Sign-in Process

When you use Google Sign-in through mdauth.themesia.com, the following steps occur:

1. Token Request: MD requests a token for authentication from mdauth.themesia.com.
2. Validation: mdauth.themesia.com validates the request and, if valid, provides a token for login.
3. Login Link: MD provides a link for you to log in using Google.
4. User Authorization: You grant access and are redirected to mdauth.themesia.com.
5. Redirect Back: You click the link to return to MD, where the login process is completed.

3. Data Collection and Usage

• mdauth.themesia.com:
  • Data Collected: Product license key, IP address, and product URL are collected to generate a secure token.
  • Data Handling: mdauth.themesia.com does not store your Google account data, including the Google login token.
• MD Application:
  • Data Stored: MD stores the following data:
    • Google Drive Access Token: This token is used to authenticate your connection to Google Drive and grant MD permission to interact with your Drive.
    • Drive ID: Identifies the specific Google Drive (e.g., My Drive or Shared Drive) where files will be managed. The Drive ID allows MD to perform operations like uploading and organizing files.
    • Folder ID: Used to manage and organize files within a specific folder in your Google Drive. MD creates a folder in your Drive and stores its ID to facilitate file management.
    • Uploaded File IDs: Each file uploaded to your Google Drive is assigned a unique ID. MD stores these IDs to track and manage the files, including actions like deletion or retrieval.
  • Data Usage:
    • Google Drive Integration: MD uses the Google Drive API to interact with your Google Drive account. The access token allows MD to upload backup data to your Google Drive.
    • File Management: MD only accesses and manages files that were uploaded by the app. Uploaded File IDs are used to keep track of and manage these files, ensuring they are properly handled according to your instructions.
    • Storage Information: MD retrieves and displays your Google Drive storage information, including total storage capacity, remaining storage, and total trashed storage, on the app dashboard. This information helps you monitor and manage your storage usage.
    • Personal Information Display: Your Google Drive name and email address are fetched and displayed on the MD app dashboard to personalize your experience and provide relevant information.

4. Data Sharing and Disclosure

• Public Access: Uploaded file IDs are accessible through specific links provided by the app (e.g., example.com?id=x). These links allow visitors to access specific files but do not provide a list of all file IDs or access to other files in the drive. Visitors can only view files if they have the direct link; they cannot browse or access files without it.
• Internal Use: MD does not share, transfer, or disclose Google user data stored in MD, including authentication tokens, except for the sharing of links to uploaded files as described above.

5. Data Protection Mechanisms

• Access Controls: Access to stored data (folder IDs, drive IDs, list of uploaded file IDs, and authentication tokens) is restricted to authorized user only. The app’s internal processes ensure that only necessary data is accessible for managing file operations and user authentication.
• Encryption: The responsibility for securing data in transit, including SSL encryption, depends on the user’s installation and configuration of MD. Users should implement appropriate security measures to protect data.
• Data Retention: MD does not retain data beyond its immediate use. Folder IDs, drive IDs, uploaded file IDs, and authentication tokens are stored only as long as necessary for managing file uploads, user authentication, and session management.
• Regular Audits: Regular security audits and assessments are recommended but are not explicitly conducted by MD. Users are encouraged to review and maintain their own security practices to ensure data protection.

6. Disclaimers

MD is a product sold by Themesia.com but is not directly managed by us. Themesia.com is not responsible for the direct management or operation of MD. Users are responsible for their own installation, configuration, and security of the product.

7. Changes to This Privacy Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated effective date.

8. Contact Us

If you have any questions or concerns about this privacy policy or how your data is handled, please refer to contact us page