Privacy policy

Last updated September 23, 2026

Life is a private personal dashboard operated by Jonathan Wadsworth. Only the owner’s approved Google accounts can sign in. This policy covers Life at life.jrwdev.com.

Information Life accesses

Google sign-in provides your account identifier, name, email address, and profile image. Separately, when you connect a Google account, Life requests read-only access to Gmail messages, Google Calendar calendars and events, and Google Tasks lists and tasks. Synced records can include message subjects and text, senders and recipients, event titles, descriptions, attendees and times, task details and due dates, and links to the originals. Life also stores authorization tokens to keep the selected accounts connected.

If configured by the owner, Life also reads Asana tasks and comments. Information entered directly into Life includes notes, preferences, feedback on recaps, and personal reminders.

If you connect Every Dollar Budget, Life reads up to 120 days of transactions, active recurring transactions, and merchant groups through your read-only API key. The key and cached budget snapshot are encrypted at rest. Matching uses bill notices and saved autopay preferences; a budget entry alone does not prove bank settlement.

How information is used and shared

Life uses this information to display your schedule, organize your priorities, and generate source-linked recaps. It sends selected source titles, excerpts, people, dates, source links, and saved preferences to Anthropic’s Claude API for recap generation. This can include personal information contained in your messages, events, tasks, or notes. The resulting recaps are stored in Life.

Life is hosted on a DigitalOcean server. The hosting provider processes stored application data as infrastructure, and Anthropic processes the information sent for AI generation under its applicable API terms and retention policies. If the optional morning-email feature is enabled, Resend processes the recipient address and recap email for delivery. Life does not sell Google user data or share it with advertisers or data brokers.

Life does not use Google user data to train general-purpose AI models. Feedback is stored as preferences supplied with later recap requests; it does not train a model. Life’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Transfers are limited to providing the described features, security, and applicable legal requirements.

Budget facts are sent to Anthropic only when you enable budget sharing in Settings. This includes relevant matched merchants, amounts, dates, payment evidence, and recurring-bill details, not the API key or unrelated transactions. You can turn this off while continuing to view budget evidence locally in Life.

Storage and security

Synced data, preferences, and recaps are stored in Life’s server database. Google connector tokens are encrypted at rest, and the public application uses HTTPS. Access to dashboard data requires an approved owner login. Service providers may retain data under their own terms; this policy does not promise zero retention by those providers.

Retention, disconnection, and deletion

Life retains synced records, recaps, and preferences until they are deleted by the operator; there is no automatic retention deadline. Disconnecting an account in Sources & settings deletes its stored connection credentials and stops future synchronization. It does not delete previously synced records or recaps, which may still appear in the dashboard or be used in subsequent recap generation.

You can revoke Google authorization in your Google Account connections. To delete stored source data, derived recaps, preferences, or the entire Life account, contact the operator at jon@jrwdev.com. Deletion from Life does not delete the original information in Google or Asana. Copies in infrastructure backups or service-provider systems may remain subject to their retention policies.

Disconnecting the budget connector deletes its key and cached transaction snapshot. Previously generated recaps and saved autopay preferences remain until deleted. Turning off budget sharing stops inclusion of budget facts in future model requests; it does not recall information already sent.

Cookies and changes

Life uses authentication and connection-flow cookies to keep you signed in and secure OAuth requests. This policy is updated when Life’s data practices change. Contact jon@jrwdev.com with privacy questions or requests.