Updated October 1, 2026. This notice supplements the LifeMaster Privacy Policy, which describes our information collection, processors, retention, deletion and contact arrangements.
When you connect LifeMaster to ChatGPT, Claude or another supported assistant, sign in to your own LifeMaster account and choose its permissions. Access is limited to that account, the granted capabilities and the connected services you permit. A native-agent permission can allow reading and changing private financial, health, journal, contact and other records, sending requested messages and using paid features within your plan. Native approval and plan rules continue to apply.
The assistant may receive the records and action results returned by the tools you permit, including requested task, project, reminder and calendar data, native-agent replies and action evidence, and permitted call reports or transcripts. The assistant provider processes that information under its own terms and privacy policy. LifeMaster also uses the AI and infrastructure providers described in its general Privacy Policy to carry out native-agent requests.
Phone calls require additional calling permission and use the connected account's current LifeMaster plan, free allowance and credit balance, just as calls made inside LifeMaster do. Free, Pro and Premium retain their own native entitlements. You may choose optional stricter daily call, duration and credit limits for a connection; these do not add credits or increase your subscription allowance. Capability checks can return the connected account's plan, credit balance and feature limits. Calls may be recorded and transcribed as described in the general Privacy Policy. Calendar access and connected-service execution require their additional permissions. A permitted connected service may receive the request and data needed for the action and return results to LifeMaster and the assistant. Some actions use paid features or provider credits. Recording an expense or income changes your LifeMaster ledger; it does not send a bank payment.
LifeMaster keeps app grants, authorized capabilities, security audit events and operation records to enforce permissions, track results and prevent duplicate actions. A finished agent reply does not mean every requested action completed; a pending approval or submitted call remains pending until its actual outcome is known.
Use LifeMaster's Connections controls to revoke an app grant or change its permissions, and disconnect it in the assistant's settings. Revoking a grant blocks future tool access checked against that grant. It does not undo actions already performed, delete records created by those actions, erase information already received by the assistant provider, or necessarily stop a call or external job already submitted. Manage those records and operations separately through their normal controls. Contact support@lifemaster.ai for account or privacy help.
With separately selected mission permissions, the full connection can create, inspect and manage native missions and their schedules. Missions may keep running after chat ends, access private account data, send approved messages and spend native account credits. Native Free, Pro and Premium plan rules, action approvals, additional call/calendar/connector permissions and any optional connection caps apply. Standing OAuth access is checked before future steps and provider dispatches; revoked or reduced access pauses future work. Already accepted provider jobs can finish. Existing connections need reauthorization for new mission scopes. The published Claude personal-record directory profile excludes missions, calls, media and external execution. Legacy scheduled jobs, direct delegated-agent tools, server administration, arbitrary code execution and credential changes still require LifeMaster itself. The supported actions are shown by the connection's capability tools.