Privacy Policy

This Policy applies to Life Design OS websites, applications, communications, AI features, and integrations that link to it (collectively, the “Service”). Separate products, programs, or communities may provide their own privacy notices.

Depending on how you use the Service, we may collect:

• Account and identity information, such as your name, email address, authentication identifiers, membership status, and preferences.
• Information you choose to share with LD, including messages, voice transcripts, files, reflections, goals, relationships, Life Map information, and other life context. You decide what to share.
• Product activity and settings, such as onboarding progress, scheduling preferences, feature usage, feedback, and the controls you select.
• Connected-service information, when you choose to connect a supported calendar, AI provider, or other service. The authorization screen identifies the requested access before you connect it.
• Device, log, and security information, such as browser type, IP address, timestamps, diagnostic events, and information used to keep the Service reliable and secure.
• Communications, including messages you send to support and responses to research or beta invitations.
• Transaction information, if paid memberships are offered. Payment card details may be collected directly by a payment provider rather than stored by LDT.

We use personal information to:

• Provide, personalize, and maintain the Service.
• Preserve relationship continuity, memory, preferences, and developmental context that you ask LD to use.
• Generate responses and operate requested features, including guided onboarding and calendar scheduling.
• Authenticate accounts, administer memberships, and provide support.
• Protect members, investigate abuse, prevent fraud, and maintain service reliability.
• Understand privacy-safe product usage and improve member-facing features.
• Communicate about the Service, including important security, privacy, account, and beta-program updates.
• Comply with law and enforce our agreements.

We do not sell personal information. We do not use or authorize the use of your personal content or Google user data to train general-purpose AI models. Consented advertising measurement is limited to the Meta and Google tags described in section 10 and does not include Purchase events or payment-card data.

To provide LD conversations and related features, portions of the information you submit may be processed by Anthropic's paid commercial API for LD conversations and understanding, and by OpenAI's paid API Platform for optional voice transcription and speech. These are business API services, not consumer Claude or ChatGPT accounts. We limit each provider to the information and access reasonably needed to deliver, secure, and support the requested feature, and we do not opt in to provider model training with member data.

AI output can be inaccurate or incomplete. The Service is designed to support your judgment, not replace professional advice or your authorship of important life decisions.

Google Calendar is optional. Life Design OS accesses Google user data only after you choose to connect an account and approve the permissions shown by Google.

Data accessed. For onboarding scheduling, the Service requests:

• Free/busy availability from your primary calendar for the scheduling window, so LD can locate open 15-minute times.
• Access to events on calendars you own, used to find, create, and update Life Design onboarding appointments created by the Service.
• The connected calendar account email and authorization details, such as the scopes granted and connection timestamps.

How the data is used. Calendar information is used only to provide member-facing calendar features you request, including finding availability and creating or updating your Life Design appointments. The current onboarding feature queries only appointments marked as Life Design onboarding events when it checks for appointments previously created by the Service.

What is stored. Access and refresh credentials are encrypted using AES-256-GCM before they are stored. We also store limited connection metadata, such as the connected account email, granted scopes, token-expiration information, and connection or usage timestamps. Free/busy intervals are processed to calculate availability and are not retained as a calendar-history dataset. We do not retain a copy of the titles, descriptions, locations, or attendees of unrelated calendar events for this feature.

Sharing and limited use. Google user data is not sold, used for advertising, used to determine creditworthiness, or used to train general-purpose AI models. Google Calendar data is not sent to Anthropic, OpenAI, or another AI model provider. It is not transferred except to infrastructure providers acting for us as needed to provide or secure the feature, when you direct us to do so, as part of a business transfer with legally required notice or consent, or when required by law. Human access is limited to circumstances where you affirmatively request support, access is necessary for security or abuse investigation, or access is required by law.

Life Design OS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Zoom is optional. Life Design OS accesses Zoom user data only after an authorized Life Design Advisor chooses to connect their own Zoom account and approves the permissions shown by Zoom. Members do not connect Zoom.

Data accessed. For first-party advisor booking, the Service requests:

• Permission to create, update, delete, and read meetings on the consenting advisor's Zoom account, limited to meeting:write:meeting, meeting:update:meeting, meeting:delete:meeting, meeting:read:meeting, and user:read:user.
• The connected Zoom user identifier from Zoom's official current-user context (/users/me), stored as an account reference. A host identifier alone is not authorization.

How the data is used.Zoom information is used only to create, update, or delete a Life Design Advisor conversation meeting on that advisor's connected Zoom account when a first-party booking command runs, and to maintain or disconnect the OAuth connection. Connecting Zoom does not by itself enable member booking.

What is stored. Access and refresh credentials are encrypted using AES-256-GCM before they are stored. We also store the Zoom user identifier, token-expiration information, and the identifier of meetings the Service creates so those meetings can be updated or deleted. We do not use this connection to retrieve Zoom recordings, chat, or unrelated meetings.

Sharing and limited use. Zoom user data is not sold, used for advertising, used to determine creditworthiness, or used to train general-purpose AI models. Zoom meeting data is not sent to Anthropic, OpenAI, or another AI model provider. It is transferred to Zoom when you direct the Service to create, update, or delete a meeting, to infrastructure providers acting for us as needed to provide or secure the feature, when you direct us to do so, as part of a business transfer with legally required notice or consent, or when required by law. Human access is limited to circumstances where you affirmatively request support, access is necessary for security or abuse investigation, or access is required by law.

We may disclose personal information:

• To service providers that host, secure, maintain, analyze, or support the Service under contractual and confidentiality obligations.
• To a connected service when you direct the Service to create, update, or retrieve information there.
• To protect rights, safety, and security; investigate fraud or abuse; or comply with legal process.
• In connection with a merger, financing, acquisition, reorganization, or sale of assets, subject to applicable notice and consent requirements.
• With your direction or consent.

We may use aggregated or de-identified information that reasonably cannot be linked back to an individual for analytics, research, security, and product improvement.

We retain personal information only for as long as reasonably necessary to provide the Service, preserve the continuity you request, satisfy legal obligations, resolve disputes, maintain security, and enforce agreements. Retention can vary by the type of information and the controls you use.

Google OAuth credentials and associated connection metadata are retained while your calendar remains connected. When you disconnect Google Calendar, Life Design OS attempts to revoke the Google authorization and deletes the locally stored encrypted credentials and connection record. Appointments already created in your Google Calendar remain in your calendar until you delete them.

Zoom OAuth credentials and associated connection metadata are retained while Zoom remains connected. When you disconnect Zoom, Life Design OS attempts to revoke the Zoom authorization and deletes the locally stored encrypted credentials and connection record. Meetings already created in Zoom remain in Zoom until you delete them.

Account-deletion requests are completed subject to legal retention, fraud-prevention, dispute-preservation, and routine backup cycles. When information is retained for one of those limited purposes, it is not used for unrelated product activity.

You can:

• Choose what to share with LD.
• Decline or disconnect optional integrations, including Google Calendar and Zoom.
• Review or change available account and product settings.
• Unsubscribe from optional marketing communications.
• Request access, correction, deletion, or a portable copy of personal information, where applicable.
• Appeal a denied privacy request or contact the relevant supervisory authority where local law provides that right.

We may need to verify your identity before completing a privacy request. Authorized agents may submit requests where applicable, subject to verification of their authority.

We use cookies and similar technologies that are necessary for authentication, security, preferences, and reliable operation. Browser controls can limit cookies, but blocking required cookies may prevent sign-in or other Service functions.

When measurement IDs are configured, we may load Meta Pixel, Meta Conversions API, and Google Tag Manager / Google Analytics (gtag) for Ads and YouTube conversion readiness. These measurement tags load only after you accept measurement cookies, and only when measurement IDs are configured. The only advertising events we send are PageView, TalkToLD_Start, and RequestAccess. We do not send Purchase events, checkout values, or payment-card data to advertising platforms. We store campaign parameters (UTM) and click identifiers (fbclid, gclid, wbraid, and ttclid when present) in a first-party cookie so Talk to LD and Request access can keep attribution. On a successful Life Design OS access request, we may send a RequestAccess event to Meta with a hashed email so the event can be matched. We do not send card numbers.

We use administrative, technical, and organizational safeguards designed to protect personal information. These include access controls, server-side credential handling, encrypted calendar tokens, transport encryption, and monitoring appropriate to the Service. No system is completely secure, and we cannot guarantee absolute security.

LDT and its providers may process information in the United States and other countries. Where required, we use appropriate safeguards for cross-border transfers and honor applicable privacy rights.

The Service is intended for adults and is not directed to children under 18. We do not knowingly collect personal information from a child under 18 through the Service. Contact us if you believe a child has provided personal information.

We may update this Policy as the Service or law changes. We will post the revised Policy and effective date. If a change materially affects how we use personal information, we will provide appropriate notice and obtain consent where required.

Questions and privacy requests may be sent to hello@lifedesigntechnologies.com.

Life Design Technologies, LLC · Nevada, United States