LemonLime policy evolution
Before/after stance changes across captured policy versions, with exact citations. If no before/after delta is available yet, AIRIN shows the latest citation-backed stance events instead.
No before/after stance delta is available for this filter yet. Latest citation-backed stance events are shown below.
Jul 20, 2026traininghigh
data sharing
Latest stance: sale or sell
“When a Customer or end user authorizes the Services to connect to Google Workspace — including Gmail, Google Drive, or Google Calendar — LemonLime requests OAuth access only to the scopes required to deliver the feature the user enabled, and uses the data received from those APIs only for the purpose the user authorized. LemonLime’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements. Specifically, LemonLime does not: transfer or sell Google user data to third parties such as advertising platforms, data brokers, or any information resellers; transfer, sell, or use Google user data for serving ads, including retargeting, personalized, or interest-based advertising; transfer, sell, or use Google user data to determine creditworthiness or for lending purposes; and transfer, sell, or use Google user data to create, train, or improve any generalized or non-personalized AI or machine-learning model. Where a user has explicitly enabled a feature that uses Google data to train or fine-tune a model scoped to that user, the resulting model is isolated to that user and is not used to serve other users. Scopes we request and why. The specific scopes requested are presented to you in Google’s OAuth consent screen at the time you authorize the integration. The features those scopes power, and the data we store as a result, are documented at the point of authorization and again in our in-product integration settings.”
Open citationJul 20, 2026trainingmedium
data sharing
Latest stance: third party or vendor sharing
“When a Customer or end user authorizes the Services to connect to Google Workspace — including Gmail, Google Drive, or Google Calendar — LemonLime requests OAuth access only to the scopes required to deliver the feature the user enabled, and uses the data received from those APIs only for the purpose the user authorized. LemonLime’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements. Specifically, LemonLime does not: transfer or sell Google user data to third parties such as advertising platforms, data brokers, or any information resellers; transfer, sell, or use Google user data for serving ads, including retargeting, personalized, or interest-based advertising; transfer, sell, or use Google user data to determine creditworthiness or for lending purposes; and transfer, sell, or use Google user data to create, train, or improve any generalized or non-personalized AI or machine-learning model. Where a user has explicitly enabled a feature that uses Google data to train or fine-tune a model scoped to that user, the resulting model is isolated to that user and is not used to serve other users. Scopes we request and why. The specific scopes requested are presented to you in Google’s OAuth consent screen at the time you authorize the integration. The features those scopes power, and the data we store as a result, are documented at the point of authorization and again in our in-product integration settings.”
Open citationJul 20, 2026traininghigh
data sharing
Latest stance: sale or sell
“When a Customer or end user authorizes the Services to connect to a Slack workspace, LemonLime requests OAuth scopes only as required to deliver the feature the user enabled, clearly describes the scope use in our App Directory listing, and uses Slack data exclusively for the purpose the user authorized. Real-time access; no persistent storage of Slack content. Consistent with the Slack API Terms of Service, LemonLime accesses Slack content in real time to answer a user’s request at the moment it is made, and does not create persistent copies, archives, indexes, or long-term data stores of Slack messages, files, or other Slack content. Any handling or caching of Slack content is limited to what is essential for the immediate operation of the requested feature, is minimized, and is deleted promptly once the request is served. This treatment is specific to Slack; other connected sources may, with the Customer’s authorization, be indexed as described in Section 6.9. With respect to data received from the Slack API, LemonLime: does not use Slack data to train any large language model, foundation model, or other AI or machine-learning model — under any circumstances, on any tier; does not create persistent copies, archives, indexes, or long-term stores of Slack content, and does not bulk-export Slack data; does not rent, sell, share, or otherwise transfer Slack data to any third party except (a) to subprocessors strictly required to deliver the feature the user enabled and (b) where required by law; does not use Slack data for advertising, retargeting, interest-based targeting, or to contact users for marketing purposes; does not combine Slack data with external data sources for purposes unrelated to the authorized feature; and does not use one organization’s Slack”
Open citationJul 20, 2026trainingmedium
data sharing
Latest stance: third party or vendor sharing
“When a Customer or end user authorizes the Services to connect to a Slack workspace, LemonLime requests OAuth scopes only as required to deliver the feature the user enabled, clearly describes the scope use in our App Directory listing, and uses Slack data exclusively for the purpose the user authorized. Real-time access; no persistent storage of Slack content. Consistent with the Slack API Terms of Service, LemonLime accesses Slack content in real time to answer a user’s request at the moment it is made, and does not create persistent copies, archives, indexes, or long-term data stores of Slack messages, files, or other Slack content. Any handling or caching of Slack content is limited to what is essential for the immediate operation of the requested feature, is minimized, and is deleted promptly once the request is served. This treatment is specific to Slack; other connected sources may, with the Customer’s authorization, be indexed as described in Section 6.9. With respect to data received from the Slack API, LemonLime: does not use Slack data to train any large language model, foundation model, or other AI or machine-learning model — under any circumstances, on any tier; does not create persistent copies, archives, indexes, or long-term stores of Slack content, and does not bulk-export Slack data; does not rent, sell, share, or otherwise transfer Slack data to any third party except (a) to subprocessors strictly required to deliver the feature the user enabled and (b) where required by law; does not use Slack data for advertising, retargeting, interest-based targeting, or to contact users for marketing purposes; does not combine Slack data with external data sources for purposes unrelated to the authorized feature; and does not use one organization’s Slack”
Open citationJul 20, 2026traininghigh
data sharing
Latest stance: sale or sell
“Where a Customer or end user authorizes LemonLime to connect to another third-party tool (for example, HubSpot, Salesforce, Notion, GitHub, Linear, Stripe, or a custom system the Customer operates), the same general commitments apply: we request only the scopes required to deliver the authorized feature, we do not use that data to train generalized AI or machine-learning models, we do not sell or share that data for advertising, and we delete data from our active systems when the integration is uninstalled or the underlying account is deleted. Specific scope use, retention, and deletion behavior is documented in our in-product integration settings at the point of authorization.”
Open citationJul 20, 2026traininglow
model training
Latest stance: no training claim
“LemonLime does not train our own models on identifiable Customer Data. Whether a third-party model provider may use data routed to it is governed by that provider’s own terms; where they offer a no-training setting, we generally configure our integration to use it. See Section 6.2. Your rights: Depending on where you live, you may have rights to access, correct, delete, port, or limit our use of your personal information. See Section 8.”
Open citationJul 20, 2026traininglow
model training
Latest stance: no training claim
“LemonLime does not train, fine-tune, or improve our own (or any shared or foundational) AI or machine-learning models on Customer Data — in identifiable, de-identified, or aggregated form. We do not share Customer Data in identifiable form between Customers. When Customer Data is routed to a third-party AI provider to generate a response (for example, OpenAI, Anthropic, Google, Meta, xAI, Perplexity, or Microsoft), whether that provider may use the data to train or improve its own models is governed by that provider’s own terms and default configuration, not by LemonLime. Where a provider offers a no-training setting, enterprise API tier, or zero-retention option, we generally configure our integration to use it. Customers are responsible for reviewing the terms of any specific model they direct LemonLime to route Customer Data through, and may restrict which models we route their data to through in-product settings. A Customer may also explicitly opt in to a feature that involves training a model on that Customer’s own data for that Customer’s own use (for example, a Customer-specific fine-tune or retrieval embedding). When a Customer does so, the resulting model artifacts are isolated to that Customer’s tenancy and are not used to serve other Customers.”
Open citationJul 20, 2026traininglow
model training
Latest stance: no training claim
“We may use de-identified, aggregated, or anonymized data derived from Customer Data and from your use of the Services to operate, secure, troubleshoot, analyze, and improve the Services. We do not use Customer Data — in identifiable, de-identified, or aggregated form — to train, fine-tune, or improve our own (or any shared or foundational) AI or machine-learning models. Where required by law or by our contract with a Customer, we will provide a means to opt out of certain forms of service-improvement processing. Customers can contact us at the email addresses below to discuss available options.”
Open citationJul 20, 2026trainingmedium
model training
Latest stance: training with opt out
“We may use de-identified, aggregated, or anonymized data derived from Customer Data and from your use of the Services to operate, secure, troubleshoot, analyze, and improve the Services. We do not use Customer Data — in identifiable, de-identified, or aggregated form — to train, fine-tune, or improve our own (or any shared or foundational) AI or machine-learning models. Where required by law or by our contract with a Customer, we will provide a means to opt out of certain forms of service-improvement processing. Customers can contact us at the email addresses below to discuss available options.”
Open citationJul 20, 2026trainingmedium
model training
Latest stance: training with opt out
“We retain personal information for as long as necessary to fulfill the purposes for which it was collected, including to provide the Services, comply with our legal, accounting, tax, or reporting obligations, resolve disputes, enforce our agreements, and operate our business. Specific retention periods depend on the type of information and the context in which it was collected, and may include: for active accounts and Customer Data, the duration of the Customer relationship plus a reasonable period afterward (typically not exceeding ninety (90) days unless retention is required by law or our contract with the Customer); for billing and tax records, the period required by applicable accounting and tax laws; for sales and marketing data, until you opt out or until the data is no longer reasonably useful for those purposes; for support communications, the period necessary to resolve the matter and to maintain a record for quality, training, and audit purposes; for security, audit, and legal-claim purposes, the period necessary to investigate and resolve issues, and to satisfy applicable statutes of limitation; and for recruiting data, the duration of the recruiting process plus, where you consent, a reasonable additional period for future opportunities. When personal information is no longer required, we delete it or de-identify it, except that we may retain de-identified or aggregated information indefinitely.”
Open citationJul 20, 2026traininghigh
model training
Latest stance: training permitted
“When a Customer or end user authorizes the Services to connect to Google Workspace — including Gmail, Google Drive, or Google Calendar — LemonLime requests OAuth access only to the scopes required to deliver the feature the user enabled, and uses the data received from those APIs only for the purpose the user authorized. LemonLime’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements. Specifically, LemonLime does not: transfer or sell Google user data to third parties such as advertising platforms, data brokers, or any information resellers; transfer, sell, or use Google user data for serving ads, including retargeting, personalized, or interest-based advertising; transfer, sell, or use Google user data to determine creditworthiness or for lending purposes; and transfer, sell, or use Google user data to create, train, or improve any generalized or non-personalized AI or machine-learning model. Where a user has explicitly enabled a feature that uses Google data to train or fine-tune a model scoped to that user, the resulting model is isolated to that user and is not used to serve other users. Scopes we request and why. The specific scopes requested are presented to you in Google’s OAuth consent screen at the time you authorize the integration. The features those scopes power, and the data we store as a result, are documented at the point of authorization and again in our in-product integration settings.”
Open citationJul 20, 2026traininglow
model training
Latest stance: no training claim
“When a Customer or end user authorizes the Services to connect to a Slack workspace, LemonLime requests OAuth scopes only as required to deliver the feature the user enabled, clearly describes the scope use in our App Directory listing, and uses Slack data exclusively for the purpose the user authorized. Real-time access; no persistent storage of Slack content. Consistent with the Slack API Terms of Service, LemonLime accesses Slack content in real time to answer a user’s request at the moment it is made, and does not create persistent copies, archives, indexes, or long-term data stores of Slack messages, files, or other Slack content. Any handling or caching of Slack content is limited to what is essential for the immediate operation of the requested feature, is minimized, and is deleted promptly once the request is served. This treatment is specific to Slack; other connected sources may, with the Customer’s authorization, be indexed as described in Section 6.9. With respect to data received from the Slack API, LemonLime: does not use Slack data to train any large language model, foundation model, or other AI or machine-learning model — under any circumstances, on any tier; does not create persistent copies, archives, indexes, or long-term stores of Slack content, and does not bulk-export Slack data; does not rent, sell, share, or otherwise transfer Slack data to any third party except (a) to subprocessors strictly required to deliver the feature the user enabled and (b) where required by law; does not use Slack data for advertising, retargeting, interest-based targeting, or to contact users for marketing purposes; does not combine Slack data with external data sources for purposes unrelated to the authorized feature; and does not use one organization’s Slack”
Open citationJul 20, 2026traininglow
model training
Latest stance: no training claim
“Where a Customer or end user authorizes LemonLime to connect to another third-party tool (for example, HubSpot, Salesforce, Notion, GitHub, Linear, Stripe, or a custom system the Customer operates), the same general commitments apply: we request only the scopes required to deliver the authorized feature, we do not use that data to train generalized AI or machine-learning models, we do not sell or share that data for advertising, and we delete data from our active systems when the integration is uninstalled or the underlying account is deleted. Specific scope use, retention, and deletion behavior is documented in our in-product integration settings at the point of authorization.”
Open citationGenerated from live stance events. Informational only, not legal advice.