Privacy Policy

1. Who this policy covers

This policy covers Laboratory Backup as offered through the Life Heart Laboratory portal at labdeskportal.abrdns.com. The laboratory owner administers the portal and chooses whether to connect a Google account. Google provides the connected Google Drive service.

This feature-specific policy does not replace the laboratory's wider patient-record or clinical privacy notices. If another laboratory operates a separate portal, that laboratory must provide its own accurate operator details and privacy information before using this feature.

2. Information the feature processes

Google account and connection details

The connected Google account email, authorization tokens, backup-folder identifier, connection identifier, selected schedule, timestamps, upload status and limited error information.

Backup files and file metadata

Encrypted backup contents, file names, identifiers, sizes, creation times and integrity-check values for files associated with the laboratory's connection.

Laboratory records included in a backup

Depending on the portal contents, a backup may include patient and report records, billing and operational information, user-account records, catalogue entries, images and documents. The portal processes these records to create the encrypted copy. Their contents are not posted on this information website.

Connection security information

Temporary sign-in state and an encrypted backup key are used to complete the owner's connection and support authorized backups.

3. Purpose and Google permission

Google data is used to identify the connected account, create the backup folder, upload encrypted copies, list and download the feature's files, check their integrity and help the owner recover laboratory records.

The requested scope is https://www.googleapis.com/auth/drive.file. Google limits this permission to files created by, or explicitly made available to, the app. This integration operates on its dedicated backup folder and files associated with the current laboratory connection. It does not request full Google Drive access, Gmail access or Google Contacts access.

The integration does not use Google user data for advertising, sale of data or AI model training. Its use and transfer of Google API data must follow the Google API Services User Data Policy, including Limited Use requirements.

4. Storage and protection

The portal's live database remains the working source of laboratory records. A recovery copy is encrypted on the portal server before it is sent over HTTPS to Google Drive. Backup contents use AES-256-GCM encryption. Google can still process file and account metadata needed to provide its service.

The backup passphrase is used on the owner's device to derive an encryption key. For unattended operation, the owner explicitly allows the portal to store that derived key and the Google refresh token in encrypted form on the server. The passphrase itself is not stored by this connection flow. Because the server can use the stored key, this is not a zero-knowledge or device-only encryption arrangement.

Access to backup operations requires the portal's owner authorization. Restoring a copy requires the passphrase and owner authorization. Encryption reduces exposure but cannot guarantee protection against every compromise. Keep the Google account, portal login and restore passphrase secure.

5. Where information is processed

Google receives the encrypted backup file and related metadata in the Google account selected by the owner. Google's handling of that data is also subject to its Privacy Policy and account terms.

The portal's hosting and storage services process the records and connection information necessary to run the feature. The current portal uses OpenAI Sites and its Cloudflare hosting infrastructure. Authorized laboratory personnel may access data through their permitted portal functions. The static information-site host processes ordinary web requests, as described below.

The backup integration does not intentionally send Google Drive data to unrelated recipients. Service providers may process information across countries under their applicable terms. The laboratory is responsible for assessing whether its selected accounts and providers are appropriate for its records.

6. Retention, disconnecting and deletion

• Portal connection: connection details and encrypted authorization/key material remain while the connection is configured. An expired or revoked Google authorization does not by itself delete this stored information.
• Disconnect: the portal's Disconnect action removes the active Drive connection and pending sign-in records from the portal database. It stops that connection's future backup operations. It does not delete the portal's working laboratory records.
• Google permission: disconnecting the portal does not revoke the complete Google account grant. The account holder can separately remove the application's access through Google Account connections.
• Drive copies: existing backup files remain in Google Drive until the owner deletes them. There is no automatic backup-retention deletion schedule in this feature. Drive Trash and any provider retention rules also apply.
• Other copies: files already downloaded to a device, recovery copies held elsewhere and provider-managed retention are not erased by Disconnect. The owner must manage those separately.

7. Your choices

Connecting Drive is optional. The owner can choose the Google account, select Manual, Daily or Weekly, download available copies or disconnect. Selecting Manual stops scheduled copies for that connection. Automatic backups require an active server schedule, sufficient Google storage and valid authorization.

The present feature has a 32 MiB limit per encrypted Drive backup. Reconnecting can create a new backup folder; earlier copies remain in the previous folder even if they are not listed by the new connection. Changes to the portal owner's login details may require reconnection.

For access, correction or deletion requests involving laboratory records, contact the laboratory responsible for those records. Deleting a Drive copy does not delete the corresponding working record in the portal.

8. This information website

These Homepage and Privacy Policy pages contain no sign-in form, upload form, advertising code, analytics script or app-controlled cookie/storage mechanism. Visiting them does not connect a Google account or initiate a backup.

The hosting provider may process IP addresses, browser information, requested URLs and ordinary access/security logs to deliver and protect the pages. The laboratory does not promise a particular retention period for provider-managed logs. Links to the portal and other websites take you to services with their own data handling.

9. Contact and policy changes

Contact Life Heart Laboratory through the current contact details on its official website or the support email displayed on the Google consent screen. Identify the issue without initially sending patient records, passwords, access tokens or backup passphrases.

This page will be updated when the described practices change. The policy version date above identifies the text being presented. Any materially different access to Google data must be explained before the owner is asked to grant it.