Privacy Policy
Effective date: October 10, 2026 · Contact: lrpapp.admin@gmail.com
Purpose and authorized users
LRP Backup Automation is an administrator-operated utility for creating and verifying encrypted recovery archives. Only Google accounts intentionally authorized by the LRP administrator are connected. The informational pages on this website do not request Google sign-in or collect Google Drive files.
Google data accessed
The local backup client requests Google Drive's drive.file scope. This scope permits access to Drive files that the application creates or that the Google account holder explicitly authorizes for the application. The utility uses authorized file and folder metadata, including file IDs, names, sizes and checksums where available, and encrypted archive bytes to upload, locate, download, verify and restore backups.
Google account authorization provides the access credentials necessary for the selected account. OAuth tokens are stored locally in restricted configuration files and are not included in public pages or encrypted recovery archives.
Use, storage and sharing
Backup contents are encrypted on the administrator's computer before being uploaded to authorized Google Drive storage. Copies may be held in the LRP administrative Drive account and an independently authorized administrator-controlled Drive account. Google processes files according to its own service terms and privacy practices.
Google user data is used only for the described backup, verification, and recovery operations. It is not sold, used for advertising, or supplied to third parties for unrelated purposes. No Google Drive access tokens or private decryption keys are intentionally published on this site.
Retention and removal
Archives are retained as versioned recovery points under configurable backup-retention rules; selected release or recovery-baseline archives may be held longer. The authorized account owner may inspect or delete archives in their own Drive and may revoke the utility's OAuth authorization in Google Account settings under third-party access. Revocation stops future Drive API access but does not automatically delete archives already stored in Drive or local/offline copies.
To request assistance with identifying or removing backups controlled by LRP, contact lrpapp.admin@gmail.com.
Safeguards and limitations
Encrypted archives use client-side encryption, with recovery keys held separately, and integrity verification. Backup logs and account authorization metadata are managed locally with access restrictions. The verified backup scope currently covers application source code and backup infrastructure. Full production D1 database and uploaded-file export/recovery are not yet enabled or independently verified.
If this utility's data practices or the categories of archived data change materially, this notice will be reviewed and updated before enabling the expanded scope.
Política de Privacidade
Esta política refere-se exclusivamente à automação de backup do LRP, não à plataforma escolar. A ferramenta é utilizada pelo administrador para criar, enviar, conferir e recuperar arquivos de backup criptografados.
Dados e permissão: o aplicativo solicita o escopo Google Drive drive.file, restrito a arquivos criados pelo aplicativo ou expressamente autorizados. Processa metadados de arquivos, identificadores, tamanhos, verificações de integridade e os arquivos criptografados necessários aos backups. Tokens de autorização ficam em configuração local protegida.
Armazenamento: os arquivos são criptografados localmente antes de serem enviados às contas Google Drive autorizadas. O conteúdo não é vendido nem usado para publicidade. As cópias obedecem a regras de retenção configuráveis, e pontos de recuperação especiais podem ser preservados por mais tempo.
Revogação e exclusão: é possível revogar a autorização de acesso do aplicativo nas configurações da Conta Google. A revogação não exclui automaticamente arquivos anteriormente armazenados. Para dúvidas ou solicitações sobre arquivos sob administração do LRP, escreva para lrpapp.admin@gmail.com.
Limitação atual: foram validados os backups do código e da infraestrutura. A exportação independente do D1 e dos arquivos de produção ainda não está habilitada ou verificada. Esta política será revisada caso o escopo de tratamento seja ampliado.