Who we are and what this notice covers
Unique Golden Sands FZ LLE is configuring VialTrace Production Backups, a private backup and recovery integration designed to use rclone and an operator-authorised Google Drive connection. Contact us at santhosh@uniquegoldensands.com.
This notice covers this backup integration and its information pages. It is not a complete privacy notice or contract for every function of the Vial Trace SaaS application. The integration is being configured and verified; this notice does not certify that production backup or recovery acceptance has been completed.
Information processed
The integration is designed to process Google OAuth access and refresh credentials so that the authorised operator's Drive connection can continue without repeated manual sign-in. It does not ask us to collect the operator's Google password.
For backup files and folders within its permitted access, it is designed to process metadata needed to upload, identify, verify and retrieve them. This may include file and folder identifiers, names, sizes, timestamps and available integrity metadata.
It is designed to upload and download encrypted Vial Trace backup packages. Once the production application is separately authorised and operating, these packages may contain database records, uploaded files and operational records that include customer, contact or staff information. Encryption does not make the contents anonymous. Access to decrypted contents requires recovery material and an authorised recovery procedure.
We also process limited operational information about backup attempts, integrity checks and recovery tests, and information you include in a support or privacy enquiry. Please do not email credentials, MFA codes, private recovery material or backup packages to the contact address.
Why we use this information
The integration is intended to use this information to maintain the authorised Drive connection, store encrypted backups, verify transferred files, retrieve them for recovery, investigate failures and maintain accountability for authorised operations.
We will not sell Google API data, use it for advertising or marketing, or use it to train general-purpose AI models. Google API data use and any transfer will be limited to the disclosed backup, recovery and security purposes and must follow the Google API Services User Data Policy and applicable Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy
Permissions and account control
The integration requests https://www.googleapis.com/auth/drive.file. Its intended operation is limited to backup files and folders created by the integration. That permission can also cover files explicitly made available to an application through Google's supported file-sharing or selection mechanisms; this workflow does not request such additional access. We do not request full-Drive, Gmail, calendar or contacts permissions for this backup integration.
The Google account owner can revoke the connection through their Google Account third-party connections settings. This prevents continued use of the revoked grant; it does not automatically delete existing backup files or local copies. Removing a browser session alone does not revoke an existing OAuth grant.
Access and service providers
Authorised operations personnel may access encrypted backup files and limited operational metadata. Authorised recovery personnel may access decrypted data only as necessary for an approved recovery task. Custodian access to recovery material and operator access to backup storage are distinct responsibilities.
Google is the intended off-site Drive storage provider and would process the permitted files and associated account/service metadata. DigitalOcean hosts the separate Vial Trace SaaS production infrastructure. Hostinger hosts this public informational website only; it is not the SaaS application host or SaaS backup destination. Email service providers process messages sent to our contact address. Disclosure legally required by an applicable authority must be assessed through the company's authorised process; this notice does not permit unrelated use.
Protection and storage
The intended controls are encryption of backup packages before off-site upload, encrypted transport, protected OAuth configuration and restricted access to recovery material. Secrets are not intended to be included in the backup package or published in website content, application logs or reports.
Independent off-host recovery custody and download-back restore proof remain acceptance gates. These controls must not be described as already proven merely because they are documented. No system or encryption method eliminates every security risk.
The integration is intended to store encrypted off-site backups in Google Drive. Google and other service providers may process files or associated service information in countries outside your country of residence.
We do not promise that all backup files and service information remain exclusively in India or the UAE.
Retention and deletion
The approved default production backup policy is twice daily, around midday and at night, with additional verified backups before production releases or changes. The intended normal retention is 30 days from each backup's individual creation timestamp. Once separately approved and verified, retention automation may prune older backup sets when they exceed 30 days; pruning is not currently activated.
Separately designated release, incident, recovery, audit, legal/regulatory hold or major migration/change checkpoint backups may have longer retention if explicitly specified. Each exception must be documented, scoped and auditable; the normal pruning rule must not delete a protected checkpoint.
The approved policy specifies 12 months from creation for backup and recovery operational logs; automated retention enforcement is not claimed as active. These include backup attempts/failures, transfer/upload results, integrity/hash verification, recovery-test activity and related security events. Specifically designated incident, release-investigation, audit, recovery-investigation or legal evidence may be retained longer; active holds must not be deleted.
The approved policy specifies 24 months for formal release, backup-verification, restore, recovery and incident evidence unless longer explicitly designated. This is distinct from routine operational logs. Routine pruning must not override a formal-evidence designation or active hold.
These periods do not govern laboratory/business records, regulated traceability, report versions, finance records or application-wide audit-history requirements. Those records have separate retention rules and must not be automatically purged by backup or operational-log retention jobs.
Contact/demo enquiries follow a separate intended policy: keep only what is needed for handling, necessary follow-up and a justified response record, for up to 12 calendar months after recorded closure while still needed. Earlier removal may be appropriate when the purpose has ended. Open enquiries are to be reviewed at least every six months; automated or incidental messages do not restart retention. Necessary separate business records, disputes or documented holds follow their relevant separately approved arrangements. Enquiries will not automatically be added to marketing lists. These statements describe intended policy, not verified enforcement by a mailbox provider.
OAuth credentials are intended to be retained only while the connection is authorised and needed, subject to provider expiry or revocation. When retirement is separately approved, an authorised operator revokes the dedicated production Google authorisation and removes separately approved protected local credential copies. Completion is recorded without credential values. This does not automatically delete stored backups, recovery keys or records under a hold, and must not affect other independently authorised connections.
Deletion must account for uploaded copies, file revisions, Drive trash and authorised downloaded or restored copies. Revoking OAuth is not a deletion request and does not erase those copies. We do not promise immediate or universal erasure by performing only one of these actions.
Santhosh Kumar Vijayan is the nominated privacy-request coordinator. The approved handling procedure requires secure minimal request records, identity/authority checks, scope and hold assessment, and documented approval before any particular deletion. Approved disposal must consider controlled copies, attachments, exports, trash/revisions and provider limitations. Disposal evidence is limited to what is necessary, without copying full enquiry contents. Any restored records must be reconciled with approved deletion decisions before ordinary use resumes. No particular deletion or automatic retention job is authorised by this notice.
Your enquiries and requests
Contact santhosh@uniquegoldensands.com to ask about the connection, request clarification or raise an access, correction or deletion request concerning data handled by this integration. We may need to verify your identity and authority before acting. Requests concerning business records must be assessed against applicable obligations and the relevant data owner or customer arrangements.
Information-page logging
These informational pages do not include sign-in, upload or contact forms, advertising, or added analytics scripts. Hostinger's hosting infrastructure processes technical request information, including access-log fields for time, IP address, request, device, country, size and response time. Hostinger's raw-log retention, archive coverage and deletion deadlines have not been confirmed; dashboard viewing filters are not a retention guarantee. Website backups and provider-controlled logs are separate from the SaaS backup-retention policy above. This description concerns these informational pages, not a promise that every provider-served error page or other website route has no tracking. Email enquiries are processed by the relevant mail providers.
Updates and contact
Material changes to these practices require review and an updated notice. Any additional Google API access requires appropriate disclosure and authorisation. The effective date of this notice is shown above.
Unique Golden Sands FZ LLE santhosh@uniquegoldensands.com