1. Introduction & Overview

Welcome to Rektech Work (rektech.work), the enterprise resource planning (ERP) and operational management platform for Krishna Minerals. We value your privacy and are committed to protecting the data processed by and stored in our systems.

This Privacy Policy explains how our platform collects, uses, stores, and protects information when authorized users, administrators, and partners access the system, with specific emphasis on our integration with third-party cloud services like Google Drive API.

2. Information We Collect

We collect and process the following categories of information strictly to provide enterprise operational services:

• Account Credentials & Profiles: Usernames, employee names, email addresses, phone numbers, and encrypted passwords assigned to authorized personnel.
• Operational & Commercial Records: Sales challans, royalty passes, purchase orders, vehicle trip logs, weighing records, blaster/driller logs, vendor invoices, and financial statements.
• Google User Data (via Google OAuth 2.0): When an administrator connects a Google account to enable Google Drive storage, we collect the administrator's Google email address, account name, and profile identifier to authenticate the storage connection and display active connection status.
• System Audit Logs: Access timestamps, IP addresses, browser user agents, and transaction audit trails to ensure enterprise data integrity and security.

3. Google Drive Integration & Scope Usage

Our application connects with Google Drive using Google's official OAuth 2.0 authentication protocol. We request the minimum necessary permissions to fulfill document management:

Strict Limits on Google Drive Access:

• Restricted Scope Isolation: Because we use the drive.file scope, our application CANNOT view, read, search, modify, or delete any personal files, photos, or existing documents in your Google Drive. It only interacts with folders and files created directly by this app (under your configured root directory, e.g. KrishnaMineral/).
• Automated Document Archiving: Uploaded operational documents (e.g. royalty receipts, vendor vouchers, employee KYC files, and sales statements) are organized into structured directories (Year / Module / Month / file).
• No Human Access to Files: Application developers and staff do not browse or view your Google Drive files unless requested by you for technical troubleshooting.

4. How We Use and Share Information

Information collected is used exclusively for:

• Managing mineral logistics, quarry operations, sales, billing, and accounting.
• Securely streaming uploaded documents back to authenticated users with appropriate role-based access permissions.
• Maintaining audit logs for accounting and regulatory compliance.

5. Data Storage, Security & Encryption

We implement robust technical and organizational measures to safeguard all data:

• Token Encryption: Google OAuth 2.0 refresh tokens, access tokens, and client secrets are stored using strong AES-256 application-level encryption in the database and are never rendered in HTML or exposed in client-side scripts.
• HTTPS / TLS: All communication between user browsers, our application servers, and Google APIs is strictly encrypted in transit via Transport Layer Security (TLS 1.3 / HTTPS).
• Role-Based Access Control: System features and document view screens are protected by granular permission gates and Super Admin authorization checks.

6. User Control, Data Retention & Revocation

Administrators and users have complete control over their connected accounts and data:

• Disconnect Anytime: The Super Admin can disconnect Google Drive at any time from the Google Drive Settings page. Disconnecting immediately deletes the stored access and refresh tokens from our database.
• Google Account Permissions: You can revoke our application's access directly at any time via your Google Account Permissions Manager.
• Retention: Business transaction records are retained for compliance with mineral royalty and taxation regulations. Uploaded files remain in your Google Drive under your ownership and control even if you disconnect the application.

7. Updates to This Policy

We may update this Privacy Policy periodically to reflect enhancements in application functionality or statutory requirements. Any revisions will be published on this page with an updated "Effective Date".

8. Contact Information

If you have questions, concerns, or requests regarding this Privacy Policy or your data, please contact: