• Account Information: Name, email address, phone number, business name, and password when you create an account.
• Payment Information: Credit card details, billing address, and transaction history. Payment processing is handled by Stripe — we do not store full card numbers on our servers.
• Business Data: Contacts, leads, appointments, quotes, invoices, email content, and other business data you enter into the CRM.
• Communications: Messages sent through our unified inbox (SMS, email, chat), support requests, and feedback.
• Custom Quote Requests: Company name, project details, budget range, and service selections submitted via our quote request form.

• Usage Data: Pages visited, features used, session duration, click patterns, and scroll depth.
• Device Information: Browser type, operating system, screen resolution, and device identifiers.
• Network Data: IP address, approximate geographic location, referring URL, and ISP.
• Analytics: We use Google Analytics 4, Microsoft Clarity (heatmaps and session recordings), and our own self-hosted analytics to understand how visitors use our site.

When you sign in with Google, Microsoft, Facebook, or LinkedIn, we receive your name, email address, and profile picture from the provider. This information is used to create or authenticate your LPAI account.

Our Lead Scraper collects business information from publicly available sources, including Google Maps, Google Business Profiles, and public business registries. See Section 4 for details.

When you connect third-party business accounts to LPAI, we receive and store data necessary to operate the features you’ve enabled. We access only the minimum data required for the features you authorize.

• Google Business Profile: Account ID, account name, role, location IDs, business name, address, hours, categories, attributes, photos, posts you create through our Social Scheduler, reviews (text, ratings, reviewer name, response history), questions and answers, and performance metrics (calls, direction requests, profile views, post views) for the locations you authorize.
• Facebook Pages and Instagram Business Accounts: Page IDs, page names, page access tokens, post content you create through our Social Scheduler, basic engagement metrics, and your name, email, and profile picture if you sign in with Facebook.
• LinkedIn Company Pages: Organization IDs, organization names, post access tokens, post content you create through our Social Scheduler, and basic engagement metrics for posts you publish through LPAI.
• Microsoft and Google Workspace (calendar, email): Calendar event metadata for availability display and event creation through our booking system. We do not read the content of your email inbox.

• What we access: Google Business Profile account and location data, posts, reviews, Q&A, performance metrics, and (where you sign in with Google) basic profile information for locations and accounts you have explicitly authorized via OAuth.
• How we use it: Solely to provide the user-facing features you have activated — Social Scheduler publishing, review management, performance dashboards, and Google sign-in.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens and refresh tokens are encrypted with industry-standard symmetric encryption.
• How we share it: We do not sell or transfer Google user data to third parties except as needed to provide the services you’ve requested (to the hosting providers listed in Section 3), to comply with applicable law, or as part of a merger or acquisition with prior notice.
• AI/ML use: We do not use Google user data to develop, improve, or train generalized AI/ML models.
• Revoking access: You may revoke our access at any time through your Google Account permissions or by disconnecting Google Business Profile from within LPAI Settings → Integrations. To delete data already stored, see our Data Deletion Instructions.

LPAI’s use of data from Meta Platforms (Facebook, Instagram, Messenger) complies with the Meta Platform Terms and Developer Policies.

• What we access: Page IDs, page names, page access tokens, post content you create through our Social Scheduler, basic engagement metrics, and (where you sign in with Facebook) basic profile information for pages and accounts you have explicitly authorized.
• How we use it: Solely to provide the Social Scheduler, CRM inbox, and Facebook/Instagram sign-in features you have activated.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens are encrypted with industry-standard symmetric encryption.
• How we share it: We do not sell Meta user data. We share it only with the service providers listed in Section 3 to operate the platform, or as required by law.
• AI/ML use: We do not use Meta user data to develop, improve, or train generalized AI/ML models.
• Revoking access: You may revoke our access through Facebook → Settings & Privacy → Settings → Apps and Websites, or by disconnecting from within LPAI Settings → Integrations. To delete data already stored, see our Data Deletion Instructions.

LPAI’s use of data from LinkedIn complies with the LinkedIn API Terms of Use, the LinkedIn User Agreement, and the data handling requirements applicable to the API products we use.

• What we access: LinkedIn organization (company page) IDs and names, post access tokens, post content you create through our Social Scheduler, basic engagement metrics on posts published through LPAI, and (where you sign in with LinkedIn) basic profile information.
• How we use it: Solely to provide the Social Scheduler and LinkedIn sign-in features you have activated.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens are encrypted with industry-standard symmetric encryption.
• Data restrictions: We do not aggregate, combine, or supplement LinkedIn data with data from other sources. We do not sell, rent, lease, sublicense, distribute, or transfer LinkedIn data to third parties. We do not use LinkedIn data to develop, improve, or train generalized AI/ML models.
• Retention: We retain LinkedIn member profile data only as long as necessary to provide the active feature, and in any event no longer than permitted by LinkedIn’s API data storage requirements. If LPAI’s LinkedIn API access is suspended or terminated, we will permanently delete all LinkedIn data within 10 days.
• Revoking access: You may revoke our access at LinkedIn → Settings → Data privacy → Permitted services, or by disconnecting from within LPAI Settings → Integrations. We will delete the associated data promptly upon disconnection. To delete other data, see our Data Deletion Instructions.

LPAI’s use of Microsoft Graph data (Outlook calendar, contacts where authorized) complies with Microsoft’s APIs Terms of Use. We access only the minimum data required for the features you activate, store it encrypted in transit and at rest, and do not use it to train AI/ML models. You may revoke access through your Microsoft Account or within LPAI Settings → Integrations.

• Account Information: Name, email address, phone number, business name, and password when you create an account.
• Payment Information: Credit card details, billing address, and transaction history. Payment processing is handled by Stripe — we do not store full card numbers on our servers.
• Business Data: Contacts, leads, appointments, quotes, invoices, email content, and other business data you enter into the CRM.
• Communications: Messages sent through our unified inbox (SMS, email, chat), support requests, and feedback.
• Custom Quote Requests: Company name, project details, budget range, and service selections submitted via our quote request form.

• Usage Data: Pages visited, features used, session duration, click patterns, and scroll depth.
• Device Information: Browser type, operating system, screen resolution, and device identifiers.
• Network Data: IP address, approximate geographic location, referring URL, and ISP.
• Analytics: We use Google Analytics 4, Microsoft Clarity (heatmaps and session recordings), and our own self-hosted analytics to understand how visitors use our site.

When you sign in with Google, Microsoft, Facebook, or LinkedIn, we receive your name, email address, and profile picture from the provider. This information is used to create or authenticate your LPAI account.

Our Lead Scraper collects business information from publicly available sources, including Google Maps, Google Business Profiles, and public business registries. See Section 4 for details.

When you connect third-party business accounts to LPAI, we receive and store data necessary to operate the features you’ve enabled. We access only the minimum data required for the features you authorize.

• Google Business Profile: Account ID, account name, role, location IDs, business name, address, hours, categories, attributes, photos, posts you create through our Social Scheduler, reviews (text, ratings, reviewer name, response history), questions and answers, and performance metrics (calls, direction requests, profile views, post views) for the locations you authorize.
• Facebook Pages and Instagram Business Accounts: Page IDs, page names, page access tokens, post content you create through our Social Scheduler, basic engagement metrics, and your name, email, and profile picture if you sign in with Facebook.
• LinkedIn Company Pages: Organization IDs, organization names, post access tokens, post content you create through our Social Scheduler, and basic engagement metrics for posts you publish through LPAI.
• Microsoft and Google Workspace (calendar, email): Calendar event metadata for availability display and event creation through our booking system. We do not read the content of your email inbox.

• What we access: Google Business Profile account and location data, posts, reviews, Q&A, performance metrics, and (where you sign in with Google) basic profile information for locations and accounts you have explicitly authorized via OAuth.
• How we use it: Solely to provide the user-facing features you have activated — Social Scheduler publishing, review management, performance dashboards, and Google sign-in.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens and refresh tokens are encrypted with industry-standard symmetric encryption.
• How we share it: We do not sell or transfer Google user data to third parties except as needed to provide the services you’ve requested (to the hosting providers listed in Section 3), to comply with applicable law, or as part of a merger or acquisition with prior notice.
• AI/ML use: We do not use Google user data to develop, improve, or train generalized AI/ML models.
• Revoking access: You may revoke our access at any time through your Google Account permissions or by disconnecting Google Business Profile from within LPAI Settings → Integrations. To delete data already stored, see our Data Deletion Instructions.

LPAI’s use of data from Meta Platforms (Facebook, Instagram, Messenger) complies with the Meta Platform Terms and Developer Policies.

• What we access: Page IDs, page names, page access tokens, post content you create through our Social Scheduler, basic engagement metrics, and (where you sign in with Facebook) basic profile information for pages and accounts you have explicitly authorized.
• How we use it: Solely to provide the Social Scheduler, CRM inbox, and Facebook/Instagram sign-in features you have activated.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens are encrypted with industry-standard symmetric encryption.
• How we share it: We do not sell Meta user data. We share it only with the service providers listed in Section 3 to operate the platform, or as required by law.
• AI/ML use: We do not use Meta user data to develop, improve, or train generalized AI/ML models.
• Revoking access: You may revoke our access through Facebook → Settings & Privacy → Settings → Apps and Websites, or by disconnecting from within LPAI Settings → Integrations. To delete data already stored, see our Data Deletion Instructions.

LPAI’s use of data from LinkedIn complies with the LinkedIn API Terms of Use, the LinkedIn User Agreement, and the data handling requirements applicable to the API products we use.

• What we access: LinkedIn organization (company page) IDs and names, post access tokens, post content you create through our Social Scheduler, basic engagement metrics on posts published through LPAI, and (where you sign in with LinkedIn) basic profile information.
• How we use it: Solely to provide the Social Scheduler and LinkedIn sign-in features you have activated.
• How we store it: Encrypted in transit (TLS 1.2+) and at rest. Access tokens are encrypted with industry-standard symmetric encryption.
• Data restrictions: We do not aggregate, combine, or supplement LinkedIn data with data from other sources. We do not sell, rent, lease, sublicense, distribute, or transfer LinkedIn data to third parties. We do not use LinkedIn data to develop, improve, or train generalized AI/ML models.
• Retention: We retain LinkedIn member profile data only as long as necessary to provide the active feature, and in any event no longer than permitted by LinkedIn’s API data storage requirements. If LPAI’s LinkedIn API access is suspended or terminated, we will permanently delete all LinkedIn data within 10 days.
• Revoking access: You may revoke our access at LinkedIn → Settings → Data privacy → Permitted services, or by disconnecting from within LPAI Settings → Integrations. We will delete the associated data promptly upon disconnection. To delete other data, see our Data Deletion Instructions.

LPAI’s use of Microsoft Graph data (Outlook calendar, contacts where authorized) complies with Microsoft’s APIs Terms of Use. We access only the minimum data required for the features you activate, store it encrypted in transit and at rest, and do not use it to train AI/ML models. You may revoke access through your Microsoft Account or within LPAI Settings → Integrations.