LifeBook - Personal OS
Professional Privacy Policy • Effective 9 October 2026 • Nuevo Digital Lab
Privacy Policy - Identity, Scope and Summary
Who operates LifeBook, what this policy covers, and the local-first promise
Identity
LifeBook - Personal OS (Android package com.nuevo.lifebook) is published by Nuevo Digital Lab, an independent developer in India. Privacy contact: nuevo.digi.lab@gmail.com. This policy is effective 9 October 2026 and applies to the Android application, its optional account and backup functions, advertising and paid-access systems, support interactions, and the feature annexes that follow.
Local-first summary
LifeBook is designed to remain usable without signing in. Most feature content is created and stored on the user’s device. The application starts without an account chooser, restores any existing session silently, and never requires a Google account merely to open ordinary features.
What changes when you connect services
If the user chooses to sign in, connect Backup Vault, buy/restore a paid pass, watch a rewarded ad, use App Open advertising, share/print/export, open external links, or activate device capabilities, limited information is processed by the relevant Google/Android or third-party service as described in this policy.
Important limits
LifeBook cannot guarantee that user-entered content is non-sensitive. Free-text fields can contain health, financial, family, workplace, identity or third-party information. Users should only enter information they are entitled to keep and should use device security, feature locks and backups appropriate to the sensitivity of their records.
How LifeBook Processes Data
The app’s basic data flow and the difference between local content and service data
Local user content
Feature records are generally stored in LifeBook’s private local database or app-private files. LifeBook does not intentionally upload ordinary feature content to the developer merely because the user creates or edits it.
Registered backup data
When Backup Vault is enabled, registered feature namespaces are included in LifeBook backup snapshots. Local-only recovery/quarantine namespaces are deliberately excluded. Media and project files are portable only where the backup media/file collector includes them.
Service data
Google/Firebase/Play/AdMob and Android may process account identifiers, IP addresses, device/service identifiers, authorization tokens, purchase information, ad events, diagnostics and security signals necessary to provide their services. This is separate from the user’s ordinary LifeBook feature records.
No silent cloud conversion
A local LifeBook record does not become a Firebase/Firestore record. Current Firestore use is limited to premium entitlement information; Backup Vault uses Google Drive rather than Firestore for user backups.
Local Storage, Device Security and Feature Locks
What is protected on the device and what is not
App-private storage
LifeBook uses an app-private Hive database and app-private files for most persistent feature state. Android sandboxing helps isolate this data from ordinary apps, but local database records are not represented as universally encrypted-at-rest by LifeBook itself.
System authentication
Feature Lock stores only the titles/identifiers of features the user has chosen to lock. The credential is not stored by LifeBook. Authentication is delegated to Android through local_auth and may use fingerprint, face, PIN, pattern or password where supported.
Device-level responsibility
Anyone who can unlock the device, access an unlocked feature, exploit a compromised device, obtain exported files, or restore an accessible backup may be able to view user content. Users should maintain an updated operating system, secure screen lock and appropriate device/account controls.
Permissions
Camera, microphone, location, sensors, files/media, speech recognition, printing and other capabilities are used only by features that need them. Android permission choices can be denied or revoked, although some functions will then be unavailable.
Google Account, Firebase and Paid Entitlements
Optional identity services are separate from ordinary local records
One optional identity
LifeBook uses one optional Google identity for Firebase Authentication, Drive Backup Vault authorization and paid-pass ownership/restoration. Google UI is intended to appear only after an explicit sign-in/connect/reconnect action.
Firebase Authentication
Firebase Authentication can process account identifiers, email/profile information, authentication tokens, IP address/user-agent/security information and service logs under Google’s terms. Firebase Authentication is not the storage location for journals, tasks, finance records or other ordinary LifeBook feature content.
Firestore entitlement ledger
Current Firestore use reads premium entitlement information under the signed-in Firebase UID. Paid entitlement is intended to be written by verified server-side purchase logic, not directly by the client. Backup/restore metadata compatibility methods do not write user backups to Firestore.
Google Play purchases
Product information, purchase tokens, order/transaction information and related verification data may be processed by Google Play, Cloud Functions and Google APIs to verify and grant paid access. Google controls payment-account and billing records under its own terms.
Backup Vault, Encryption, Restore and Retention
Optional Google Drive appDataFolder backup
Drive scope
Backup Vault uses the restricted Google Drive appDataFolder scope. This gives LifeBook access to its application-specific Drive data area rather than general access to the user’s ordinary Drive files.
Snapshot design
Backups contain registered LifeBook feature state and supported media references/objects. Local-only recovery and quarantine namespaces are excluded. Before a restore, LifeBook may create a separate safety backup when meaningful local data exists.
Protection and verification
LifeBook’s backup design uses encrypted snapshots and integrity/verification information. Offline backup export can require a user-supplied passphrase. No security control removes all risk, and losing access to the relevant Google account or passphrase may prevent recovery.
Retention
Automatic recovery points are retained as 7 daily, 4 weekly, 12 monthly and 3 yearly copies. Protected/manual categories follow their own rules. Deleted cloud snapshots move to a 30-day recycle period where supported; pre-restore safety snapshots also use a 30-day safety retention.
Start Fresh
Start Fresh creates a new local chapter while preserving/protecting the previous cloud recovery point when available. Signing out or disconnecting Drive does not automatically delete existing Drive snapshots.
Advertising, Free Passes and Paid Access
How monetization works without blocking features
Features remain usable
Passes are ad-free entitlements, not feature-access gates. The application is designed so ordinary features remain available even when no Free, Monthly or Yearly Pass is active.
App Open Ads
When no active ad-free entitlement exists, LifeBook may preload/show Google AdMob App Open Ads at cold start or after returning from the background, subject to cooldown and availability. The app does not intentionally delay Home merely to wait for an ad.
Rewarded ads
A user may voluntarily watch a rewarded ad to earn Free Pass time when eligible. Reward handling may use an installation identifier and server-side verification data to prevent abuse and grant the reward.
Advertising data
Google Mobile Ads may process advertising identifiers or comparable identifiers, IP address, coarse location, device/app information, ad impressions/clicks and anti-fraud signals under Google’s policies. LifeBook does not intentionally send diary, finance, health/wellness or other feature-record contents to AdMob for ad targeting.
Paid access
Monthly/yearly products are obtained through Google Play and verified using Google/Cloud services. Paid entitlement status is associated with the optional LifeBook Google/Firebase account.
Exports, Sharing, Printing and External Files
User-directed disclosure outside LifeBook
Exports
Many features can create PDF, image, audio, structured or other files. Once saved to a user-accessible location, shared, printed or opened by another application, the copy is outside LifeBook’s control.
Share and print destinations
Email apps, messaging apps, social platforms, browsers, print services, cloud drives, file managers and recipients may receive the selected content and related metadata. Their privacy and retention rules apply.
Open with / File Hub
Android can hand a file to LifeBook through Open with/share flows. A content URI may be materialized into a LifeBook-managed private copy. Deleting a LifeBook-managed copy does not delete the original external file.
PDF rendering
LifeBook may render standard searchable PDFs or screenshot-based multilingual PDFs. Screenshot-style PDFs preserve visual appearance but the text behaves as image content.
External actions
Calls, messages, maps, URLs, radio streams and external apps are initiated only after user action. LifeBook cannot guarantee the security, accuracy or privacy of an external destination.
Retention, Deletion and User Choices
How users control local and cloud data
Local deletion
Most user content can be viewed, edited, deleted or replaced directly in the feature. Clearing LifeBook app data or uninstalling generally removes app-private local data, but it does not remove exported copies, recipient copies, cloud backups or records held by Google/third parties.
Cloud deletion
Drive snapshots must be removed through Backup Vault/Google controls. Firebase account or entitlement data is a separate cloud category. Deleting or signing out of one cloud service does not automatically delete the other.
Rights requests
Depending on applicable law, users may request information, access, correction, deletion, consent withdrawal or grievance handling for developer-controlled personal data. Most purely local feature content is not available to the developer and must be managed on the device or through the user’s backups.
Support
Privacy or deletion requests may be sent to nuevo.digi.lab@gmail.com with the subject 'LifeBook Privacy Request'. Reasonable identity verification may be required for account-linked information.
India Privacy Framework, Children and Legal Basis
Current compliance posture for an India-based application
India framework
The Digital Personal Data Protection Act, 2023 and Digital Personal Data Protection Rules, 2025 use staged commencement. LifeBook applies the transparency, minimization, security, correction/deletion and grievance principles described here and will update this policy as additional provisions become effective.
Consent and user action
Optional cloud sign-in, Drive connection, device permissions, rewarded advertising, exports and external actions are initiated by the user. Where law requires consent or another lawful basis, the developer and service providers must apply the required mechanism before the relevant processing.
Children
LifeBook is a general personal-organization application and is not designed specifically for children. The developer does not knowingly seek unnecessary child data through its cloud services. Users responsible for a child should avoid entering a child’s personal data unless lawful and appropriate, and should consider the additional protections required for children in India and other jurisdictions.
Third-party people
Features such as contacts, attendance, fees, tasks, transport, hotel/restaurant/warehouse operations and resumes can contain data about other people. The user is responsible for having authority to collect, store, use, export and share that information.
Security, International Processing, Providers and Contact
Final governance provisions
Security measures
LifeBook uses app-private storage, optional system-auth feature locks, restricted Drive app-data authorization, backup verification/encryption controls, Firebase/App Check and server-side purchase verification. These controls reduce risk but cannot guarantee absolute security.
International processing
Google/Firebase/AdMob/Play services may process data in countries outside India. Firebase states that Authentication is operated from U.S. data centers and other Firebase services can use global Google infrastructure unless a service offers a location choice.
Primary providers
Relevant providers can include Android/Google Play services, Google Sign-In/OAuth, Google Drive API, Firebase Authentication, Cloud Firestore, Cloud Functions/Google Cloud, Google Play Billing/Developer API, Google Mobile Ads/AdMob, and external apps selected by the user.
Changes
Features, SDKs, permissions, storage structures and legal requirements can change. The policy date will be updated when material changes affect privacy practices. Material new cloud collection should not be silently covered by vague language; the disclosure should be revised before release.
Contact
Developer: Nuevo Digital Lab | App: LifeBook - Personal OS | Package: com.nuevo.lifebook | Country: India | Privacy/grievance email: nuevo.digi.lab@gmail.com
Daily Diary
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Record dated diary entries and personal reflections.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Permanent diary records use a registered record namespace and are eligible for LifeBook backup. Internal recovery/quarantine data is local-only.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use speech recognition or rich text/input services when selected; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Journal
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Record permanent, timestamped 15-minute rich-text journal blocks with local draft recovery.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Permanent journal records and journal settings use registered raw namespaces and are eligible for LifeBook backup. Recovery drafts and quarantine records are local-only and intentionally excluded from cloud snapshots.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use speech recognition or rich text/input services when selected; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Recorded blocks remain until the user permanently deletes them. Unsaved recovery drafts are temporary local-only records and are cleared after successful recording/discard or by applicable cleanup.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Notes
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create and organize general-purpose notes and related attachments.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Note records and UI settings use registered raw namespaces and are eligible for LifeBook backup. Recovery/quarantine namespaces are local-only. Attachments remain files and require supported media backup to be portable.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use speech recognition or rich text/input services when selected; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Checklist
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create reusable or one-off checklists and completion records.
Information processed: user-entered feature records, settings, timestamps and outputs necessary to provide the feature.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Daily Scheduler
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Plan time blocks, activities and day-specific schedules.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Year Planner
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create dated plans across the year and manage deleted plans through the feature’s recycle workflow.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Routine Planner
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Define recurring routines, schedules and completion-related information.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Meal Planner
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Plan meals and related food information.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
TaskBook
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage WorkBooks, tasks, members, assignments, subtasks, instructions, feedback and follow-up history.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature can launch user-directed external actions such as calls, messages, email, browsers or other URI handlers; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
OfficePad
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Draft office-oriented notes or working documents and export them when requested.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use speech recognition or rich text/input services when selected; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
FormBook
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Design forms and export completed designs, with recovery data kept separately from permanent form records.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Permanent form records use the registered form-record namespace and are eligible for backup. Recovery and quarantine data are local-only.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
MindBook
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create structured mind-map or knowledge documents and snapshots.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
TravelBook
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Organize trips, travel notes, locations, itinerary information and optional photos.
Information processed: trip names, dates, itinerary or note content, locations, photos and other travel details entered by the user.
Storage and Backup Vault
Travel state is stored in the registered TravelBook namespace and is eligible for backup. Photos remain media files and are portable only when the backup media collector includes them or the user exports them.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use location and/or device sensors when the user activates the relevant function; may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Play Instruments
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Provide interactive virtual instruments and remember lightweight instrument preferences.
Information processed: instrument favourites, recent selections and audio-engine preference; live notes/touches are processed during use.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature uses audio capabilities; Voice Book/DJ Studio create or play user-selected audio files.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
FitnessBook
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Plan workouts, sessions and measurements entered by the user.
Information processed: workout plans, exercises, sessions, measurements, dates and notes entered by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Quit Smoke
Planning & Personal Records • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Track smoking-related progress, goals and user-entered history.
Information processed: smoking-related goals, dates, counts, progress, notes and calculations entered by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
File Hub
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Organize files opened or managed through LifeBook, including LifeBook-managed copies received through Android.
Information processed: file names, paths, MIME/type metadata, managed-copy status, sizes and user-selected files opened or organized through the feature.
Storage and Backup Vault
File Hub state is stored in the registered File Hub namespace. LifeBook-managed copies received from Android remain private app files; backup portability depends on supported file/media backup.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Database references remain until removed. LifeBook-managed file copies may remain in app-private storage until deleted through File Hub or app-data clearing. Original external files are not deleted by removing a managed copy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Color Book
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create or save colour-related work and preferences.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Logo Maker
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create logo projects and retain project state selected by the user.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Calculator
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Perform calculations and optionally retain calculator settings/history supported by the feature.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Smart Converter
Tools & Creation • NO DURABLE CORE RECORD
Purpose and data handled
Convert units and values. Current core conversions can be used without creating a cloud account.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Code Reader
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Scan or enter supported codes, keep scan history and user-selected scanner settings.
Information processed: scanned or entered QR/barcode content, scan timestamps, labels, favourites and scanner settings.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use camera/scanner capabilities for QR or barcode capture; can launch user-directed external actions such as calls, messages, email, browsers or other URI handlers.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
DrawBook
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create drawings and save drawing state inside LifeBook.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
SmartTable
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create structured tables and retain each table as an independent LifeBook record.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Voice Book
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create audio recordings and retain recording metadata and related files on the device.
Information processed: recording metadata, filenames, durations, timestamps and audio content created by the user.
Storage and Backup Vault
Recording metadata is stored in the registered Voice Book namespace and is eligible for database backup. Audio files are device media and are portable only when included by the backup media collector or separately exported.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature uses audio capabilities; Voice Book/DJ Studio create or play user-selected audio files.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Timer & Stopwatch
Tools & Creation • NO DURABLE CORE RECORD
Purpose and data handled
Provide timer and stopwatch functions; ordinary timer state is primarily session-oriented.
Information processed: user-entered feature records, settings, timestamps and outputs necessary to provide the feature.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Mini CAD
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create lightweight CAD-style drawings or designs and retain project state.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
CodeBook
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create and manage coding workspaces, including web-code workspace data and local SQL snapshots where used.
Information processed: project content, names, design/code/table data, settings, timestamps and outputs created by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
CareerBook
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Browse and use curated career guidance content and related user interactions.
Information processed: mostly curated career-reference content plus any local search, preference or saved interaction state implemented by the feature.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Chess
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play chess and retain game state/history where enabled.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Ludo
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Ludo and retain saved games/history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Property Tycoon
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play the Property Tycoon game and retain preferences, saved games and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Picture Puzzle
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play image-based puzzles and retain active-game/history information and user-selected source references.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Active game, history and selected-source reference use the registered Picture Puzzle namespace. A user-selected source image remains a device file unless separately included in media backup.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
WordTrail
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play the WordTrail puzzle and retain active game, history and metadata.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Billiards
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Billiards and retain saved game, history and preferences.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Carrom
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Carrom and retain game preferences, saved games and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Gem Cascade
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Gem Cascade and retain active run, history and metadata.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
2048
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play 2048 and retain active-game and game-history information.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Pallanguzhi
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Pallanguzhi and retain saved game, history and preferences.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Tic-Tac-Toe
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Tic-Tac-Toe and retain saved game and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Sudoku
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Sudoku and retain game state, statistics and related saved-game information.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Klondike
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Klondike Solitaire and retain saved game, statistics, settings, daily data and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Spider Solitaire
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Spider Solitaire and retain saved game and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
FreeCell
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play FreeCell and retain saved game, statistics, settings, daily data and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Blackjack
Games • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Play Blackjack and retain session, statistics, settings and history.
Information processed: game position/state, difficulty or mode, preferences, statistics, recent history, timestamps, and player-entered names/settings where the feature exposes them.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
LoanBook
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Record loans and related dates, amounts, parties, repayments or notes entered by the user.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Cashbook
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Maintain cash books and nested cash-entry records.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Expense Book
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Record expenses and purchase-related information.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Bill Book
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create and manage bill records.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
FinanceBook
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage financial-plan records and expense records, including user-entered monetary information.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Power Planner
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Plan electricity/power usage and related estimates or records.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
XIRR Calculator
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Calculate annualized returns from dated cash flows and optionally save calculation scenarios and a working draft.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Estimate Book
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create estimates using rates, items and related financial inputs.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Personality Test
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Run an archetype/personality assessment and retain draft/history information when used.
Information processed: assessment responses, draft progress, generated archetype/result information and history.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Goals
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create personal goals, milestones and progress information.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Closet
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Catalog wardrobe items and related care or organization information.
Information processed: wardrobe item details, categories, care information, notes and optional photo references.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Collections
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Catalog collections, categories and favourites.
Information processed: collection categories, item/favourite information, notes and user-entered catalog details.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Reviews
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Write personal reviews and ratings.
Information processed: review titles, ratings, categories, dates and free-text opinions.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Recipes
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store recipes, ingredients and preparation notes.
Information processed: recipe names, ingredients, steps, categories, notes and related cooking information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
My Profile
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store user-created profile information and, where selected, a local profile photo reference.
Information processed: profile fields and optional profile-photo reference/content selected by the user.
Storage and Backup Vault
Profile state is stored locally in LifeBook. A profile-photo path may reference a device file; the image itself is portable only if it is included in media backup or separately exported.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
My Data
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store user-defined personal records and optional images or attachments supported by the feature.
Information processed: user-defined records, labels, values, notes and optional images or attachments.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
My Home
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Catalog home inventory locations and items.
Information processed: home locations, item names, categories, quantities, values, notes and other inventory details.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Appointment Book
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create appointment records.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Attendance Book
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage registers, members and attendance records.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Hotel Manager
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage hotel operational records entered by the user.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Restaurant Manager
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage restaurant operational records entered by the user.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Wedding Planner
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Plan wedding-related tasks, events, contacts, budgets or other planning state supported by the feature.
Information processed: user-entered feature records, settings, timestamps and outputs necessary to provide the feature.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Transport Manager
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage transport-related operational records.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Warehouse Manager
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage warehouse records, inventory/operations and audit-related information entered by the user.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Expense Splitter
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Split expenses between participants and retain related records.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
FeeBook
Finance & Calculation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Track fee-paying clients, fee schedules and payment-related records.
Information processed: amounts, dates, categories, descriptions, counterparties or participant names, schedules, notes and calculated financial results.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Resume Book
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create and manage resume-profile and resume-section records.
Information processed: profile and resume information such as name, contact details, education, skills, experience, projects and other career information entered by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Vehicle Book
Home & Reference • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store vehicle details, maintenance or other vehicle-related records.
Information processed: vehicle identifiers/details, service or maintenance records, dates, costs, notes and optional media references.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Pet Book
Home & Reference • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store pet-related profiles, notes and care information.
Information processed: pet names/profile details, care records, notes, dates and optional photo references.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Grocery Book
Home & Reference • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Track grocery stock and consumption-related records.
Information processed: grocery items, quantities, stock/consumption values, categories, dates and notes.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
StoreBook
Operations & Management • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Manage store/inventory records.
Information processed: operational records, names or identifiers, dates/times, status, notes, quantities, assignments and other user-entered business information.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Important Contacts
Home & Reference • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store important contact information entered by the user and launch user-directed communication actions.
Information processed: names, phone numbers, alternate numbers, email addresses, addresses, categories and notes entered by the user.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature can launch user-directed external actions such as calls, messages, email, browsers or other URI handlers; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Important Dates
Home & Reference • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Store important dates, categories and notes.
Information processed: free-text content, titles, dates/times, categories, status/progress fields and any personal or third-party information the user chooses to enter.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
PDF Tools
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Create, transform or manage PDFs; store signature-vault records and local-only recent generated-file history where supported.
Information processed: PDF files selected by the user, generated outputs, signature-vault content and operation history that the user chooses to create.
Storage and Backup Vault
Signature-vault records are stored in the registered PDF Tools namespace and are eligible for LifeBook backup. Recent generated-file history is local-only because a device path is not a portable cloud record by itself.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media; may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Signature-vault records remain until the user deletes them or clears LifeBook data. Local generated-file history can be cleared locally. Exported PDFs/signatures outside LifeBook remain under the destination’s control.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Toolbox
Tools & Creation • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Provide measurement and utility tools and store lightweight calibration, favourites and settings.
Information processed: user-entered feature records, settings, timestamps and outputs necessary to provide the feature.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use location and/or device sensors when the user activates the relevant function.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Image Cropper
Tools & Creation • NO DURABLE CORE RECORD
Purpose and data handled
Crop and transform user-selected images. Core edit state is temporary unless the user saves or shares an output.
Information processed: selected image bytes, crop/transform settings and output image data during the editing session.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
EMI Calculator
Finance & Calculation • NO DURABLE CORE RECORD
Purpose and data handled
Calculate loan EMI scenarios from user-entered numbers without requiring durable feature storage.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
SIP & SWC
Finance & Calculation • NO DURABLE CORE RECORD
Purpose and data handled
Calculate SIP, SWP, FD and RD scenarios from user-entered numbers without requiring durable feature storage.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
DJ Studio
Media, Learning & Exploration • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Mix local audio on two decks, record master mixes and retain prepared-track BPM/grid/cue information.
Information processed: local audio-file paths, track fingerprints, BPM/grid/cue/hot-cue preparation, mixer state during use and master recording files created by the user.
Storage and Backup Vault
Prepared-track records use the registered DJ Studio namespace and are eligible for database backup. Source audio and recorded mixes are files on the device and are portable only when separately exported or included by supported media backup.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature uses audio capabilities; Voice Book/DJ Studio create or play user-selected audio files.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
World Radio
Media, Learning & Exploration • LOCAL PREFERENCES
Purpose and data handled
Play internet radio and remember user preferences such as favourites or recent stations where enabled.
Information processed: station selections, favourites, recent stations, playback quality or similar preferences; streaming requests also reveal network information to radio/stream providers.
Storage and Backup Vault
Lightweight preferences/history are stored locally on the device. They are not treated as substantive user-content records unless explicitly incorporated into LifeBook’s backup system.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature requires network access to external radio/stream providers selected by the user.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Preferences/history remain until cleared by the feature, app settings or app-data clearing. Streaming providers retain their own logs under their policies.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
SkyBook
Media, Learning & Exploration • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Provide offline astronomy planning, saved events/notes, observation information, user-selected locations and map preferences.
Information processed: saved astronomical events, notes, observation sessions, user-selected or device-derived location information, map preferences and local astronomy calculations.
Storage and Backup Vault
SkyBook state and preferences use the registered SkyBook namespace and are eligible for LifeBook backup.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may use location and/or device sensors when the user activates the relevant function.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature can hold sensitive, confidential, financial, location, health/wellness, workplace or third-party personal information depending on what the user enters.
Tools & Creation • NO DURABLE CORE RECORD
Purpose and data handled
Send user-selected content to Android printing or related system destinations; the print feature itself need not keep a separate user record.
Information processed: content the user selects for printing plus temporary print-job data handed to Android or the chosen print service.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may create PDFs, print or share files through Android.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
Creator Studio
Tools & Creation • FILES + PROJECT STATE
Purpose and data handled
Create projects and media/artifacts stored in LifeBook-managed project or file locations.
Information processed: project files, imported media, edits, generated assets, project metadata and export destinations selected by the user.
Storage and Backup Vault
Projects and generated assets may be stored as LifeBook-managed files rather than only database records. Backup coverage depends on the current backup media/file collector.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature may open a file or image picker and process user-selected media.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.
Wiseman Book
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Present curated wisdom/knowledge content and any user interactions supported by the feature.
Information processed: primarily bundled knowledge/reference content plus any searches, bookmarks, favourites or notes implemented locally.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
QuizCraft
Media, Learning & Exploration • NO DURABLE CORE RECORD
Purpose and data handled
Open or connect users to the separate QuizCraft exam-preparation experience through a user-directed external link.
Information processed: LifeBook itself mainly handles the user-directed link/navigation action; the external QuizCraft service/app applies its own privacy practices after the user leaves LifeBook.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature opens an external website/app selected by the user.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
EquationBook
Tools & Creation • NO DURABLE CORE RECORD
Purpose and data handled
Plot or calculate equations and mathematical visualizations; core calculation state is generally session-oriented unless exported.
Information processed: numbers, dates, rates, cash flows, formulas, units, assumptions and calculated outputs entered or generated on the device.
Storage and Backup Vault
Core use does not require a durable feature record. Inputs and intermediate state are processed on the device; an exported or shared result becomes a separate file outside that temporary state.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Temporary in-memory state normally ends when the feature/session is closed. Files the user explicitly saves, prints or shares persist wherever the user or destination places them.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
The feature ordinarily works with settings, calculations, game state or creative data, but users can still place personal information into free-text fields or exported files.
IQ Test
Personal & Lifestyle • LOCAL-FIRST • BACKUP ELIGIBLE
Purpose and data handled
Run a cognitive/IQ-style assessment and retain completed-result history and an unfinished draft.
Information processed: assessment answers, timing/progress, generated scores or result summaries, completed-result history and unfinished draft state.
Storage and Backup Vault
Feature records use a LifeBook-owned raw namespace in the local Hive database and are eligible for registered LifeBook backup when Backup Vault is enabled.
Backup is optional and depends on the user connecting the LifeBook Backup Vault. Ordinary feature use does not require a Google account.
Device access and external processing
This feature does not require a cloud account for ordinary local use; Android permissions are requested only by functions that need them.
When the user deliberately exports, shares, prints, streams, opens a URL, selects a file, or hands data to another app, the destination may receive the selected content and technical metadata under its own privacy terms.
Retention, deletion and control
Local records remain until the user deletes them, uses a feature-specific recycle/delete action, clears LifeBook app data or restores/replaces storage. Cloud backup copies follow Backup Vault retention until deleted or expired under the backup policy.
Deleting a LifeBook record does not delete copies already exported, printed, sent to another person, stored by another app, or retained in an older cloud backup until that backup is deleted or expires.
Privacy impact depends mainly on the content selected or entered by the user and whether it is exported, backed up or shared.