1. The public website
Office provides information about personal tools and working practices. These pages do not include a login, file-upload form, advertising, analytics code, or third-party scripts. They do not read your Google Drive or initiate backups.
Delivering a page necessarily sends request information, such as your IP address, requested address, browser information, and timing, to the hosting and network providers. Cloudflare serves the domain's public edge. Hosting or security logs may retain request metadata under the operator's and providers' settings; this notice does not promise a zero-log service or a fixed log-retention period.
Links to the main family website and other services lead to separate experiences with their own data handling.
2. Backup contents and metadata
Laputa Backup is intended to copy source files that the owner explicitly selects. In the configured restic workflow, repository payloads are encrypted locally before upload. Restoring them requires the repository password and access to the stored data.
Encryption of payloads does not conceal all activity from Google. Google can process account and authorization information, storage-object identifiers and names, sizes, timestamps, storage usage, request information, and access activity. It also applies its own service policies.
A separate Google-readable working-document library is outside this backup utility's purpose. Readable documents and their metadata can be processed by Google; they must not be described as restic-encrypted backups or silently added to this application's scope.
3. Google authorization
The utility's intended Google Drive access is limited to selected files created for the application, for backup storage and restoration. It is not intended to browse or reorganize unrelated Drive content.
Review the application name, account, and requested permissions on Google's consent screen before proceeding. The actual grant and file-access boundary must be checked during setup. This notice does not by itself enforce permission limits or establish that an existing credential has the intended scope.
The Office website does not receive your Google password. Authorization is handled through Google's flow and the configured desktop utility.
4. Purpose and sharing
The utility uses the selected data for backup and restoration under the owner's direction. Its operation transfers repository data and required metadata to the Google Drive account authorized for that purpose.
The utility does not send backup contents to AI services, perform runtime AI analysis of them, use them to train models, sell them, or use them for advertising. No AI provider is part of this backup workflow. These statements describe the utility's behavior, not a promise about every independent service or tool the owner may use.
Private project records, operational receipts, and backup contents are not published through this Office website.
5. Credentials and setup limits
OAuth credentials, local configuration, and recovery information belong to the machines and account setup the owner controls. Their protection depends on that setup. The utility does not itself establish encrypted credential storage or an independent recovery-key arrangement.
Local working files, diagnostic output, and restoration destinations also need appropriate access controls. Qualify the exact source selection, authorization, credential handling, and an isolated restore before depending on a backup. This notice is not a claim that those checks are complete.
Do not submit passwords, tokens, recovery keys, or backup contents to this website or through a support request.
6. Retention, revocation, and deletion
The owner decides which backups to retain and when to remove them. This notice does not establish an automatic deletion schedule or promise that every stored copy disappears immediately.
- Revoke access: use your Google account's connected-app controls to withdraw the application's authorization. Local credentials may also need removal from the configured machines.
- Delete backups: separately remove the intended repository objects using a deliberate, verified process. Revoking authorization does not delete existing Drive files.
- Protect recovery: deletion of repository data or loss of its password can make recovery impossible. Verify the retained copies and recovery information before removing either.
Google may apply its own trash, retention, recovery, and account policies. Consult the relevant Google account controls for their current behavior.
7. Contact and updates
For privacy questions, use the support contact displayed on the application's Google consent screen and identify Laputa Backup. Share only the information needed to describe your request.
This page will be updated when the documented behavior changes. A changed purpose or broader access must be explained before it is introduced; publication of a notice alone does not authorize additional access.