Privacy notice

LifeLinks helps you organize the information you choose to record about your possessions, projects, routines and calendar, and make it available to agents you authorize.

We store your display name, account email when provided, and a password hash if you choose password sign-in, plus the content you save: records, notes, files, Collections, Routines, history and Calendar information. Session cookies keep you signed in on the website; the iPhone app keeps its session credential in the device Keychain. The app uses the same LifeLinks account and service, temporarily caches private attachment previews on the device, and clears those caches when you sign out or switch accounts. Operational metadata is used to run, troubleshoot and protect the service. LifeLinks is hosted on Railway.

New email/password accounts require an email verification code before account creation. Phone signup, sign-in and linking verify that you can receive a code at the number you supply. Verification messages pass through our configured email or text-message provider, which receives the destination and message needed to send the code. SMS verification is for the codes you request, not marketing messages. We do not sell phone numbers, SMS opt-in data or consent records, or share them with third parties or affiliates for marketing or promotional purposes. Phone sign-in stores a stable sign-in identifier and a masked number for your account settings. Verification destinations, codes and SMS consent time/version are protected in temporary encrypted verification attempts; expiry ends their use for verification, and later cleanup removes expired attempts rather than deleting them immediately at expiry. A phone-only account does not require an email address. Verification or linking a sign-in method does not grant access to your workspace to the delivery provider.

Separately, we keep an SMS consent receipt with a keyed identifier for your phone number, the time you agreed and the disclosure version for 90 days from that consent. This receipt contains no full phone number or verification code. It is kept even if signup or message delivery does not complete; requesting a replacement code does not restart the 90 days. Expired receipts are removed by routine cleanup when the service starts, hourly while it is running, and before sending SMS verification codes. An outage or cleanup failure may delay removal, and backups may retain older copies.

If you choose provider sign-in, LifeLinks uses the account identity and profile information you authorize the provider to share for account creation, sign-in or linking a sign-in method. We store the provider name and stable account identifier, along with the shared display name and available email. Identity-only sign-in consent does not grant calendar access or access for connected agents. Calendar connections and agent permissions are separate choices.

Your workspace is private by default. If you explicitly make a QR-linked record public, its selected public information can be viewed through that link. Attachments remain access-controlled. Anyone using the shared demonstration account can access that account's data. Use a separate private account and test data when evaluating your own connections.

Google and Microsoft calendar connections are optional. With your permission, LifeLinks reads account identity and available calendars, synchronizes calendars you select, and performs event changes you request or authorize within the provider's permissions. Calendar authorization credentials are stored encrypted on the server and are not given to connected agents. Disconnecting removes the saved credentials; it does not delete your original events at Google or Microsoft. Removing a LifeLinks calendar connection removes its local calendar projection. Provider-side consent may need to be revoked separately in your provider account settings.

You separately control access for connected agents and each calendar. An authorized agent client can receive content and perform actions within those permissions. The agent service's own privacy and retention policies apply to information it receives. Revoking access stops future authorized access; it does not erase information already received by that client. Browser and remote agent connections have separate revocation controls.

LifeLinks uses Google user data for account creation, sign-in and linking a sign-in method, and for the connected-calendar features you separately authorize. It does not use that data for advertising, sell it, or use it to train generalized AI models. LifeLinks' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

You can edit or remove content through available application controls. Undo, history and backups may retain copies; removal is not a promise of immediate erasure from every copy. You can permanently delete your account through Account → Delete account in LifeLinks or the Delete account page. This removes your stored account content, sessions, uploads and connected-agent access. Original external calendar events and printed QR identities remain, with your account content detached. Backups and limited records retained under this notice expire separately; an Apple access revocation may finish after local deletion. Older Apple connections may also need you to remove LifeLinks in your Apple Account settings. Contact justin@vmosaic.com for privacy questions or help accessing or deleting your account. Do not send passwords or calendar credentials.