Privacy & data use

Information used by BLU

The private workspace stores project records, agent assignments, decisions, deliverables, activity history and configured operational data. Access is controlled by the workspace operator. This public site does not display those private records or provide public account registration.

Google sign-in

BLU requests basic Google identity information—account identifier, email address and profile information—to identify authorized users. Google handles the sign-in process; BLU does not ask for or store your Google password. Signing in does not by itself grant access to a private BLU workspace.

Google Drive backups

The separately authorized backup connection requests access to the specific Drive files used with the backup app (the drive.file permission). Its purpose is to upload encrypted recovery packages and download them to verify their integrity. It is not used to scan unrelated Drive documents.

Backup archives are encrypted locally before upload. Decryption keys are held separately from the uploaded package. Packages include a manifest and restore instructions; authorized backup operators may use these to recover project systems. Local authorization credentials allow scheduled transfers without repeated sign-in and are stored in a restricted server location.

Service providers

Google processes sign-in and Drive storage through its services. Cloudflare delivers this public site and may process connection information such as IP addresses, request times and browser details for delivery and security. This site includes no advertising trackers or analytics scripts.

When an operator assigns work to a configured AI provider, the relevant project context may be sent to that provider to perform the task. Provider use is separate from the fixed backup scripts, which do not need AI-model calls to package, transfer or verify data. BLU does not use the Drive backup permission for advertising or model training.

Retention and control

Project records and recovery copies remain until the operator removes them under the applicable project’s retention needs. Existing backup copies are not automatically deleted by the current backup schedule. Removing a live record may not immediately remove it from older backups.

You can revoke BLU’s Google access in your Google Account connections. Revoking access stops future authorized transfers but does not erase existing backup files. Contact the operator to request access review or deletion of information held by BLU. Requests involving shared project records may require ownership verification.

Contact

For privacy questions or data requests, contact Mark Louie Gallardo at gallardomarklouie@gmail.com.