Last updated: 11 October 2026
1. Scope and responsibility
This policy describes the intended handling of information by TIKGRAM DMS Backup V1, a company-use enterprise email backup component managed by HK TIKGRAM TECHNOLOGY LIMITED. It is not yet operational. The actual implementation and data handling must be verified before the component is used.
2. Google Drive permissions and information
The planned integration uses the Google Drive API. The currently recorded configuration lists https://www.googleapis.com/auth/drive.file. This is a per-file permission for files created by the application or opened or shared with it by the authorised user, rather than general access to every file in a Drive account. Within that boundary, the application may create, read, update or delete authorised backup files and access their associated metadata, such as file identifiers, names, sizes and modification information, as required for backup management.
The actual OAuth request, granted scopes and usable authorisation have not been verified. The account holder should review the consent screen before authorising access. Any change to the proposed permissions must be reviewed and reflected in the disclosures before it is used.
3. Purpose and use
If approved and activated, the component would use authorised Drive access to store and manage encrypted company backup archives and support integrity checks and authorised restoration. Archives may contain company email data and related system information, including information about employees and business correspondents. Operational records may contain file metadata and backup outcomes. Access credentials would be handled through controlled credential storage, not published on this website.
Google data obtained for this integration is intended to be used only for company backup administration. It is not intended for advertising, sale, unrelated profiling or training general-purpose AI models.
4. Storage and security
The planned design encrypts backup contents locally before upload and restricts access to authorised company administrators and controlled systems. Encrypted archives would be stored in a company-managed Google Drive destination. Local source data, operational information and the separate materials needed for authorised recovery require their own access controls.
Encryption does not make file metadata invisible or eliminate all risks. Security depends on implementation, credential and key management, service operation and administrator practices; this policy does not promise absolute security or a verified recovery capability.
5. Sharing and service providers
The company intends to limit access to authorised personnel and service providers needed to operate the approved backup arrangement. Google would provide the Drive storage and API service and may process uploaded encrypted files and service metadata under its applicable terms and policies. Other providers, if used, would be limited to the approved operational purpose. Information may also need to be disclosed where required by applicable law.
This description does not mean that Google operates the company’s email system, that the backup is a Google product or that Google has approved this application.
6. Retention and deletion
Backup retention would be governed by a company-approved schedule, business continuity needs and applicable legal obligations. Superseded archives would be removed through authorised backup administration when no longer required, subject to relevant retention holds. Deleting a source message does not necessarily remove it immediately from retained backup copies.
An account holder may contact the company about access, retention or deletion concerns. The company must assess the request, the copies involved and any legal or operational requirements. No fixed deletion deadline or immediate removal from all provider recovery copies is promised here.
7. Withdrawing authorisation
If Google authorisation is granted, the account holder can withdraw it through their Google Account’s connected-app settings and notify the company. Company administrators may also disable the integration or remove its authorisation. Revocation can stop future authorised API access; it does not by itself erase previously stored archives or local company records. Those copies remain subject to the applicable retention and deletion process.
8. Contact and updates
For questions about this policy, the proposed Google Drive access or company-held information, contact HK TIKGRAM TECHNOLOGY LIMITED at [email protected]. Material changes to the intended data handling should be reviewed and reflected in this policy before they are introduced.
[email protected]