Privacy Policy

Life Load
Effective Date: December 5, 2025
Last Updated: December 5, 2025

Introduction

Life Load ("Life Load", "we", "our", or "us") is a voice-first assistant app designed to help busy parents manage tasks, events, and reminders.

Life Load is developed and operated by Life Load (ABN 90 608 249 128), based in Caloundra, QLD, Australia. We are committed to protecting your privacy and being transparent about our data practices.

This Privacy Policy explains what information we collect, how we use it, how we protect it, and your rights regarding your data.

Summary of Key Points

Local-first storage: Most of your data stays on your device.
End-to-end encryption for Family Space: Family sharing data is encrypted on your device before it leaves and can only be decrypted by devices that have joined your Family Space.
Encrypted email delivery (with honest caveats): Emails you forward to your Life Load alias are briefly processed in plaintext by our email service to apply your rules, then encrypted with your device’s public key before delivery. Large attachments are stored temporarily by our infrastructure so your devices can download them.
No advertising trackers: We do not run ads, build marketing profiles, or sell your data.
Minimal telemetry: We use limited, privacy-conscious tools (like anonymised crash reports and infrastructure logs that avoid message content) to keep the app reliable.
You control your data: Export, delete, or modify your information at any time. We do not know your backup password or private encryption keys, so we cannot recover encrypted data if you lose them.

1. Information We Collect

1.1 Information You Provide

Profile Information

Display name (optional)
Child profiles: names, ages, birthdates, photos (stored locally on your device)

Tasks and Events

Task titles, descriptions, notes, due dates
Event titles, descriptions, dates, times, locations
Recurring event patterns
Task assignments (who is responsible)

Location Data

Saved places (home, work, custom locations)
GPS coordinates for location-based reminders
Addresses from location searches

Voice Input

Speech-to-text transcriptions used to create tasks, events, or commands.
We rely on your device’s built-in speech-to-text capabilities (for example, those provided by Apple or Google). Depending on your device settings, audio may be processed locally or by your device provider’s services.
We do not keep voice recordings in the app, and we do not build voice profiles.

Email-to-Task Feature (optional)

Email alias configuration (for example, the alias itself, its association with your account/Family Space, and the public key we use to encrypt messages for your devices).
Email processing rules you create (for example, "if subject contains ‘appointment’ then create an event").
Sender and recipient email addresses for emails forwarded to your Life Load alias.
Subject line, body text, and HTML content of emails forwarded to your Life Load alias, which our email processing service parses in memory to apply your rules and prepare the message for delivery.
Attachments included with those emails. Small attachments may be embedded directly in the encrypted message. Larger attachments are temporarily stored by our infrastructure so that your devices can download them (see Section 3.3).
Encrypted email message objects that are delivered to your devices and used to create tasks or events.

File Attachments

Photos, documents, and files you attach to tasks in the app itself (stored locally on your device).
For attachments that arrive via the Email-to-Task feature, see Section 3.3 below.

1.2 Information Collected Automatically

Device Information

Device platform (iOS or Android)
Operating system version
App version

Usage Information

Feature usage counts (e.g., tasks completed, events created)
Error and crash information (with personal information removed where possible)

1.3 Information We Do NOT Intentionally Collect

We do not intentionally collect or require:

Browsing history
Contact lists (unless you manually add family members)
Health or fitness data
Biometric data
Financial information (subscriptions are handled by Apple/Google/RevenueCat)
Advertising identifiers or cross-app behavioural tracking data

Some of this information may be collected directly by your device provider (Apple/Google) or app store under their own privacy policies.

2. How We Use Your Information

We use your information solely to provide and improve the Life Load app:

Purpose: Display your tasks and events
Data Used: Task/event content, dates, locations

Purpose: Location-based reminders
Data Used: GPS coordinates, saved places

Purpose: Voice input processing
Data Used: Speech-to-text transcriptions

Purpose: Family sharing
Data Used: Encrypted task/event data and child profiles shared with invited members

Purpose: Email-to-task conversion
Data Used: Email sender and recipient addresses, subject, body content and attachments (processed by our Email Bridge to apply your rules and decide whether to create a task or event), and the encrypted email message that is delivered to your devices and decrypted only there.

Purpose: Crash reporting and bug fixes
Data Used: Error reports (configured to avoid personal information as far as practicable, with additional scrubbing of things like email addresses, phone numbers, coordinates and quoted user content)

Purpose: Subscription management
Data Used: Purchase verification via RevenueCat

We do not use your information for:

Advertising or marketing profiles
Selling to third parties
Training external AI models on your personal data
Any purpose not directly related to app functionality or legal requirements

3. How We Store and Protect Your Information

3.1 Local Storage (On Your Device)

Most of your data never leaves your device. We use a tiered security approach:

Tier 1 – Hardware-Secured Storage

Encryption keys stored in iOS Keychain or Android Keystore (for example, your device encryption key, Family Space key and email private key).
Protected by your device’s security (PIN, biometrics, etc.).
These private keys are generated or derived on your device and never sent to our servers.

Tier 2 – Encrypted Local Storage

GPS coordinates
Addresses and location data
Child information
Family Space configuration

Sensitive data in this tier is encrypted using modern, industry-standard cryptography (for example, AES-256-GCM) with keys stored in hardware-backed secure storage on your device. For backups, we additionally use strong password-based key derivation as described in Section 3.4.

Tier 3 – Standard Local Storage

Task and event titles
Dates and times
User preferences and settings

3.2 Cloud Storage (Family Sharing Only)

If you use Family Space sharing:

Shared data (tasks, events, child profiles and related content) is encrypted on your device using a Family Space encryption key before transmission.
The Family Space encryption key is generated or derived on your devices (for example, from your invite code plus other secret values) and stored in secure storage on those devices.
Our relay server (hosted on Cloudflare Workers) receives only encrypted payloads plus routing metadata (for example, network identifiers, device identifiers and timestamps). It does not have the ability to decrypt your Family Space content.
For subscription validation, we store a copy of your Family Space key in Cloudflare’s key-value storage so the relay can derive a separate signing key to validate subscription tokens. The relay does not use this stored key to decrypt your messages and does not implement any decryption endpoint or tools for reading Family Space content.
The relay acts as a "dumb pipe": it forwards encrypted messages between devices and logs only technical metadata (for example, connection counts and anonymous identifiers), not message content.

3.3 Email-to-Task Feature

If you enable email forwarding:

Emails sent to your Life Load email alias are routed via Cloudflare Email Routing to our Email Bridge, which runs on Cloudflare Workers. The full email (including headers, subject, body and attachments) is made available to that Worker.
Our Email Bridge parses the email in memory to extract fields like sender, recipient, subject, body text and HTML, and to evaluate the rules you have configured (for example, "if subject contains ‘appointment’ then create an event").
During this processing, the email content is present in plaintext in memory on our infrastructure for a short period (typically hundreds of milliseconds). We do not log email subjects, bodies, or attachment content, and after our recent updates we no longer log sender or recipient email addresses either.
The Email Bridge then builds a structured email message object (for example, from, subject, body, attachment references, suggested action) and encrypts that message using your device’s public encryption key (for example, via modern cryptography such as X25519 with ChaCha20-Poly1305).
After this encryption step, the relay only sees the encrypted email payload and metadata required for routing. Only your devices, which hold the corresponding private key in their secure storage, can decrypt and read the email message content.
Small attachments may be included or referenced as part of the encrypted message that only your devices can read. Larger attachments are stored in Cloudflare’s key-value storage in base64 form for a limited time (currently up to 7 days) so that your devices can download them. These attachments are protected by Cloudflare’s standard encryption at rest and HTTPS in transit, but they are not additionally encrypted with your device key until your device downloads them.
Because the Email Bridge must process messages in plaintext before encryption and temporarily store large attachments, we describe email content as "encrypted before delivery" rather than strictly "end-to-end encrypted" in the same way as Family Space data.
We log only generic, non-identifying technical data about email processing (for example, that an email was processed as a task or event, rule counts, attachment IDs and counts, and HTTP status codes). Our logs do not contain sender or recipient email addresses, email subjects, email bodies or attachment contents.

3.4 Backup Files

When you create a backup:

Backups are protected with a password you choose.
We use modern, industry-standard cryptography (for example, a strong password-based key derivation function plus AES-256-GCM) to encrypt backup contents.
Backup files are stored locally on your device or wherever you choose to export them (e.g., cloud storage you control).
We never automatically upload backups to any server we control.
We do not know or store your backup password. The key used to decrypt your backup is derived from your password on your device each time you restore. If you lose your password, we cannot recover your backup data.

4. Information Sharing

4.1 Family Space Members

When you invite family members to your Family Space:

Shared with invited members (via encrypted sync):

Tasks (titles, descriptions, due dates, assignments)
Events (titles, dates, times, locations)
Child profiles
Calendar sync settings

Not shared with family members:

File attachments you keep only on your device
Email configuration and rules
Backup files
Personal notes marked as private

4.2 Third-Party Service Providers

We use the following services to operate Life Load:

Service	Purpose	Data Shared
RevenueCat	Subscription management	Purchase transactions, subscription status, anonymous customer identifier
Sentry	Crash reporting	Error details, app version, device/OS information, and limited contextual information about where in the app an error occurred. We configure Sentry not to collect default PII (for example, names and emails), disable screenshots and session replay, and actively scrub patterns such as email addresses, phone numbers, coordinates, quoted user content and file paths before sending crash reports.
Google Places API (Android)	Location search	Search queries, approximate location
Apple MapKit (iOS)	Location search	Search queries, search region
Cloudflare Workers / Cloudflare network	Family sync relay, Email Bridge (including the Email-to-Task feature), and edge infrastructure.	End-to-end encrypted Family Space payloads and related routing metadata (for example, network and device identifiers and timestamps); email messages forwarded to your alias (including headers, subject, body and attachments) processed in memory by our Email Bridge; temporary storage of large email attachments (typically up to 7 days) so your devices can download them; IP addresses; and generic routing and error logs that do not contain email subjects, bodies, sender or recipient addresses, or attachment content.
Apple Push Notification service (APNs)	Push notifications on iOS	Device push token, notification metadata
Firebase Cloud Messaging (FCM) or similar	Push notifications on Android	Device push token, notification metadata

These providers act as our data processors and may store limited data (such as logs) in data centres located in other countries.

4.3 What We Do NOT Share

We never:

Sell your personal information
Share data with advertising networks for behavioural advertising
Provide data to data brokers
Share unencrypted Family Space data (tasks, events, child profiles) with any third party

4.4 Legal Requirements

We may disclose information if required by law, such as:

To comply with a legal process, court order, or government request
To protect the rights, property, or safety of our users or the public
To enforce our Terms of Service or investigate potential violations

5. Third-Party Services in Detail

5.1 RevenueCat (Subscription Management)

RevenueCat processes subscription purchases made through Apple App Store or Google Play Store. They receive:

Purchase transaction details
Subscription status and renewal information
An anonymous customer identifier

RevenueCat does not receive your task or event content.

RevenueCat Privacy Policy

5.2 Sentry (Crash Reporting)

When the app crashes or encounters an error, Sentry may receive:

Error stack traces and messages
Device platform and OS version
App version
Limited contextual information about where in the app the error occurred

We configure Sentry to avoid including personal information and actively scrub data before sending crash reports. For example, we disable features such as session replay, view hierarchy and screenshots; we turn off collection of default PII; and we remove patterns that look like email addresses, phone numbers, coordinates, quoted user content and file system paths from error messages.

Our intention is that crash reports do not contain personal information; if we discover that any has been sent, we will treat it as personal information and handle it accordingly.

Sentry Privacy Policy

5.3 Google Places API (Android Only)

When you search for locations on Android, Google receives:

Your search query (for example, "grocery store")
Your approximate location (to find nearby results)

We cache search results locally to minimise API calls. Google’s privacy policy applies to their processing of this data.

Google Privacy Policy

5.4 Apple MapKit (iOS Only)

When you search for locations on iOS, Apple receives:

Your search query
Your search region

Apple’s privacy policy applies to their processing of this data.

Apple Privacy Policy

5.5 Push Notification Services

To send push notifications to your device, we use:

Apple Push Notification service (APNs) for iOS
Firebase Cloud Messaging (FCM) or a similar service for Android

These services receive:

A device-specific push token
Basic notification metadata (such as that a reminder exists)

We aim to keep notification content minimal and avoid including sensitive details where possible.

5.6 Cloudflare Logs and Telemetry

Cloudflare provides the infrastructure that runs our relay and Email Bridge. In addition to the data described in Section 4.2, Cloudflare automatically collects standard HTTP and Worker metrics, such as:

Request timestamp
Client IP address
Request URL and HTTP method
Response status code and size
Worker CPU time and duration

Cloudflare’s standard logs do not capture request or response bodies unless our code explicitly logs them. We design our Workers so that:

We do not log Family Space sync payloads (which are end-to-end encrypted).
We do not log email subjects, bodies, sender or recipient addresses, or attachment content.
Application-level logs from the Email Bridge now contain only generic technical information such as whether an email was processed as a task or event, rule counts, attachment IDs and counts, and HTTP status codes.

Cloudflare retains logs in line with its own retention policies. We do not use these logs to build behavioural profiles of users; they exist to help us keep the service reliable, secure and abuse-resistant.

6. Permissions We Request

6.1 Location Permission

Why we need it:
To remind you of tasks when you arrive at or leave specific locations (geofencing).

How we use it:

Check if you are near a saved location
Trigger location-based reminders
Location data is not shared with third parties except as described for encrypted Family Space data and location search providers

Background location (optional):
Required only if you want reminders when the app is closed or running in the background.

6.2 Microphone Permission

Why we need it:
To convert your spoken words to text for hands-free task creation and commands.

How we use it:

Use your device’s built-in speech-to-text capabilities
Depending on device settings and platform, audio may be processed locally or by services operated by your device provider (for example, Apple or Google)
We do not keep voice recordings in the app

6.3 Calendar Permission

Why we need it:
To sync Life Load events with your device calendar.

How we use it:

Read existing calendar events (optional)
Write Life Load events to your calendar
Calendar data stays on your device unless you sync your device calendar with other services

6.4 Notification Permission

Why we need it:
To send you reminders about tasks and events.

How we use it:

Time-based reminders
Location-based reminders
Family Space notifications (task assignments, updates, and similar)

7. Your Rights and Choices

7.1 Access Your Data

All your data is visible within the app. You can view your tasks, events, saved places, and settings at any time.

7.2 Correct Your Data

You can edit most information directly in the app (for example, change a task title, update a child profile, or modify a saved location). If you believe we hold other personal information about you that you cannot access via the app, you can contact us at privacy@lifeload.app and request details or corrections. We will respond within a reasonable time.

7.3 Export Your Data

Use the Backup feature to export your data:

Go to Settings > Backup & Restore
Create a backup file
Save or share the backup to a location you control

Because we do not know your backup password or hold your decryption keys, you are responsible for keeping backups and passwords safe. If you lose both your device and your backup (or its password), we cannot reconstruct your encrypted data from our side.

7.4 Delete Your Data

You can delete data at any time:

Individual items: Swipe to delete tasks or events.
All local data: Uninstall the app to remove data stored on your device.
Family Space data: Leave or delete the Family Space to remove synced data for that shared space.

When you delete data in the app, it is removed from your device and from Family Space for other members. Residual copies may remain for a limited time in system backups or logs maintained by us or our service providers, but these are removed after their respective retention periods.

7.5 Revoke Permissions

You can revoke permissions in your device settings at any time:

Location
Microphone
Calendar
Notifications

Revoking certain permissions may limit the functionality of the app (for example, no location-based reminders without location permission).

7.6 Opt Out of Crash Reporting

Crash reporting helps us fix bugs, but you can disable it:

Go to Settings > Privacy
Toggle off "Send crash reports"

7.7 Complaints and Access Requests (Australia)

If you have concerns about how we handle your personal information, or if you wish to request access to, or correction of, personal information we hold about you, you can contact us at privacy@lifeload.app.

We will respond in writing within a reasonable time (usually within 30 days).

If you are not satisfied with our response, you may be able to lodge a complaint with the Office of the Australian Information Commissioner (OAIC) . Details on how to do this are available on the OAIC website.

8. Data Retention

Data Type	Retention Period
Tasks and events	Until you delete them or uninstall the app
Location cache	30 days (automatically refreshed)
Voice command history	10 most recent commands
Crash reports (Sentry)	Typically up to 90 days (subject to Sentry’s retention policies)
Email processing metadata (for example, alias configuration and rules)	Until the email alias is rotated, removed, or your account is deleted
Large email attachments stored by the Email-to-Task feature	Typically up to 7 days in our Cloudflare-based storage so your devices can download them, then automatically deleted
Server logs and telemetry (for example, Cloudflare logs)	Short periods consistent with our operational needs and our providers’ retention policies (typically from near real-time up to a few months, depending on the service)
Backup files	Until you delete them from where you stored them

We do not maintain long-term archives of your personal data beyond what is necessary to operate the app, comply with legal obligations, or resolve disputes.

9. Children’s Privacy

Life Load allows you to create profiles for your children to help manage family schedules.

Child profile information (names, ages, photos) is stored locally on your device and, if you use Family Space, shared in encrypted form with invited family members only.
Child data is encrypted using the same protections as other sensitive data.
We do not require children to create accounts or provide information directly to us. Life Load is intended to be used by adults (parents and carers); children should only use the app under adult supervision.
We do not knowingly collect personal information directly from children. If we become aware that we have inadvertently received personal information directly from a child, we will delete it as soon as reasonably practicable.

10. International Users

Life Load is operated from Australia. If you use the app from outside Australia:

Your data may be processed by our service providers in other countries, including the United States, the European Union, and other regions where our providers operate data centres.
For example, RevenueCat, Sentry, Cloudflare, Google, Apple, and push notification services may process limited data (such as subscription status, error logs, routing metadata, and push tokens) outside Australia.
All communication between your device and our services uses HTTPS/TLS. Data shared within Family Space is additionally end-to-end encrypted so only participating devices can read it.

10.1 For European Users (GDPR)

Where the EU General Data Protection Regulation (GDPR) applies, Life Load (ABN 90 608 249 128) is the data controller for your personal data processed in connection with the app.

Legal bases for processing may include:

Contract performance: To provide the app and its features you choose to use.
Consent: For optional features (such as certain permissions or crash reporting).
Legitimate interests: To maintain and improve the security and reliability of the app, in a way that respects your rights and freedoms.

Subject to applicable law, you may have the following rights:

Right of access to your personal data
Right to rectification (correction) of inaccurate data
Right to erasure ("right to be forgotten")
Right to restrict processing in certain circumstances
Right to data portability
Right to object to certain types of processing
Right to withdraw consent at any time, where processing is based on consent

You can exercise most rights directly via the app (viewing, editing, deleting, and exporting data). For any other GDPR-related requests, contact privacy@lifeload.app. You also have the right to lodge a complaint with your local data protection authority.

10.2 For California Users (CCPA/CPRA)

If the California Consumer Privacy Act (CCPA), as amended by the CPRA, applies to you, then:

We do not sell your personal information as "sell" is defined in the CCPA/CPRA.
You may have rights to:
- Know what categories of personal information we collect and use.
- Access specific pieces of personal information.
- Request deletion of personal information, subject to certain exceptions.
- Correct inaccurate personal information.
- Not be discriminated against for exercising your privacy rights.

We do not use or disclose "sensitive personal information" (as defined in the CCPA/CPRA and its regulations) for purposes other than those permitted by applicable California law, including Section 7027(m) of the CCPA regulations.

You can exercise many of these rights through the app (view, edit, delete). For additional requests under California law, contact privacy@lifeload.app.

11. Security Measures

We implement industry-standard security measures to protect your data, including:

Encryption in transit: All communication between your device and our servers uses HTTPS/TLS.
Encryption at rest (sensitive data): We use modern cryptography (for example, AES-256-GCM with strong key management) for sensitive data such as locations, child profiles, Family Space keys and backup contents.
Hardware-backed key storage: Use of iOS Keychain and Android Keystore for key material where available.
End-to-end encryption for Family Space: Shared family data is encrypted on your device using keys that we do not know, and our relay infrastructure has no capability to decrypt it.
Password-based encryption for backups: Backup keys are derived from a password that only you know; we do not store the password or backup keys.
Minimal administrative access: We have not built administrative tools that allow our staff to view decrypted Family Space content, and our Email Bridge logs avoid email content and addresses.
Input validation and security controls: To protect against common attacks such as injection and unauthorised access.
PII scrubbing for telemetry: We configure crash reports and logs to exclude personal data as far as reasonably possible.

No system is 100% secure. We cannot guarantee absolute security, but we work to protect your information and continually improve our safeguards.

If you discover a security vulnerability, please contact us at security@lifeload.app.

12. Data Breaches

If we become aware of a data breach involving personal information that is likely to result in serious harm, we will:

Promptly investigate and assess the breach.
Take steps to contain and remediate the issue.
Where required by law, notify affected individuals and relevant regulators (for example, under Australia’s Notifiable Data Breaches scheme).
Review and improve our systems to reduce the risk of similar incidents in the future.

13. Business Transfers

If Life Load is involved in a merger, acquisition, reorganisation, or sale of assets, your personal information may be transferred as part of that transaction. If this happens:

We will take reasonable steps to ensure the recipient continues to protect your personal information in a manner consistent with this Privacy Policy, or notifies you of any material changes; and
We will inform you of the transfer within the app or via other appropriate means.

14. Changes to This Policy

We may update this Privacy Policy from time to time. When we make changes:

We will update the "Last Updated" date at the top.
For significant changes, we will notify you in the app or through other appropriate channels.
Continued use of the app after changes take effect constitutes your acceptance of the updated Privacy Policy.

We encourage you to review this policy periodically.

15. Contact Us

If you have questions about this Privacy Policy, our data practices, or if you wish to exercise your privacy rights or make a complaint, you can contact us at:

Email (general privacy questions and rights requests): privacy@lifeload.app
Email (security issues): security@lifeload.app

If you are in Australia and are not satisfied with our response to a privacy complaint, you may be able to contact the Office of the Australian Information Commissioner (OAIC) for further assistance.

16. Summary Table

What We Collect	Stored Where	Encrypted	Shared With
Task/event titles	Your device; encrypted Family Space sync	No on device by default; yes when included in Family Space encrypted payloads	Family members (via encrypted sync)
Locations (coordinates, saved places)	Your device	Yes (encrypted with a device-specific key)	Family members (encrypted); Google (Android) or Apple (iOS) for search
Child profiles	Your device	Yes	Family members (encrypted)
Voice input	Handled via device STT services	Not stored by Life Load	Device provider (Apple/Google) depending on settings
Emails forwarded to your Life Load alias (subject, body and metadata)	Cloudflare infrastructure (in memory during processing), then your devices (as encrypted email messages)	Present briefly in plaintext in memory on our Email Bridge, then encrypted with your device’s public key before storage or delivery	Your devices (which decrypt the email content); Cloudflare (email processing infrastructure and logs without email subjects/bodies)
Email attachments via Email-to-Task	Cloudflare key-value storage (for large attachments, up to 7 days); your devices after download	Protected by Cloudflare’s encryption at rest and HTTPS in transit while stored server-side; then encrypted with your device key once downloaded and stored by the app	Cloudflare (temporary storage); your devices
Crash reports	Sentry	Yes (encrypted in transit and at rest by Sentry; additional scrubbing by us)	Sentry (configured to avoid personal information)
Purchases	RevenueCat and app stores	According to their policies	RevenueCat, Apple/Google
Location searches	Cached locally	No (cache); yes in transit to Google/Apple via HTTPS	Google (Android) or Apple (iOS) for search
Family sync payloads	Devices and Cloudflare infrastructure	Yes (end-to-end encrypted payloads using keys we do not know)	Cloudflare (encrypted payloads plus limited routing metadata only)
Backup contents	Your device and wherever you store backup files	Yes (encrypted with a password-derived key that only you know)	Only the storage providers you choose (for example, your personal cloud storage)

This Privacy Policy is effective as of December 5, 2025.

Questions?

For privacy-related enquiries, email us at privacy@lifeload.app

For general support, contact support@lifeload.app