{
  "id": 666443,
  "title": "How much can one use LLMs without violating the rule on Data Security?",
  "url": "/competitions/deep-past-initiative-machine-translation/discussion/666443",
  "author_name": "",
  "post_date": "2026-01-07T07:01:12.822333300Z",
  "votes": 3,
  "comment_count": 5,
  "views": 0,
  "content": "<p>On the competition rules page, under Data Security, it states <em>\"You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\"</em></p>\n<p><a href=\"https://www.kaggle.com/deeppast\" target=\"_blank\">@deeppast</a> I am not sure how to interpret this in the context of using LLMs to interact or understand the competition datasets. I know the rules does not forbid the use of LLMs. However, it appears to me that using models like Gemini with competition data, would constitute permitting persons who have not agreed to the rules, access to competition data.</p>\n<p>An example would be the use of online services for translating some of the non-English translations in the <code>publications.csv</code>. Ryan's response in this <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517\" target=\"_blank\">thread</a> only seem to relate to the generation of synthetic data, whereas my question regards allowing access to the competition data. What is the recommended way to translate some of these translations that are in German, French, etc without allowing access to third party applications?</p>",
  "messages": [
    {
      "id": "3387512",
      "postDate": "01/07/2026 07:01:12",
      "content": "<p>On the competition rules page, under Data Security, it states <em>\"You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\"</em></p>\n<p><a href=\"https://www.kaggle.com/deeppast\" target=\"_blank\">@deeppast</a> I am not sure how to interpret this in the context of using LLMs to interact or understand the competition datasets. I know the rules does not forbid the use of LLMs. However, it appears to me that using models like Gemini with competition data, would constitute permitting persons who have not agreed to the rules, access to competition data.</p>\n<p>An example would be the use of online services for translating some of the non-English translations in the <code>publications.csv</code>. Ryan's response in this <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517\" target=\"_blank\">thread</a> only seem to relate to the generation of synthetic data, whereas my question regards allowing access to the competition data. What is the recommended way to translate some of these translations that are in German, French, etc without allowing access to third party applications?</p>",
      "rawMarkdown": "On the competition rules page, under Data Security, it states *\"You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\"*\n\n@deeppast I am not sure how to interpret this in the context of using LLMs to interact or understand the competition datasets. I know the rules does not forbid the use of LLMs. However, it appears to me that using models like Gemini with competition data, would constitute permitting persons who have not agreed to the rules, access to competition data.\n\nAn example would be the use of online services for translating some of the non-English translations in the `publications.csv`. Ryan's response in this [thread](https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517) only seem to relate to the generation of synthetic data, whereas my question regards allowing access to the competition data. What is the recommended way to translate some of these translations that are in German, French, etc without allowing access to third party applications?",
      "votes": null
    },
    {
      "id": "3387588",
      "postDate": "01/07/2026 10:49:35",
      "content": "<p>You may find <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/664775#3382894\" target=\"_blank\">this comment by DeepPast</a> of some use.</p>\n<p>I asked a similar question on text processing using externally sourced LLM models.</p>",
      "rawMarkdown": "You may find [this comment by DeepPast](https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/664775#3382894) of some use.\n\nI asked a similar question on text processing using externally sourced LLM models.",
      "votes": null
    },
    {
      "id": "3387598",
      "postDate": "01/07/2026 11:06:50",
      "content": "<p>Thank you for the link. I have seen their response, but it seems to me not clear enough.  When they say \"… advisable to keep the use of this data for ML and not public display, and for any models as outcomes to cite the bibliography we provided for continuity.\", they don't seem to explicitly speak on the use of external LLMs for processing.</p>\n<p>Your response to their comment seem to indicate that you're unsure of what to make of their comment. Let me know if you have anymore insights on this.</p>",
      "rawMarkdown": "Thank you for the link. I have seen their response, but it seems to me not clear enough.  When they say \"... advisable to keep the use of this data for ML and not public display, and for any models as outcomes to cite the bibliography we provided for continuity.\", they don't seem to explicitly speak on the use of external LLMs for processing.\n\nYour response to their comment seem to indicate that you're unsure of what to make of their comment. Let me know if you have anymore insights on this.",
      "votes": null
    },
    {
      "id": "3387812",
      "postDate": "01/07/2026 16:56:35",
      "content": "<p>I don't. I think that generally speaking, the data processed in this competition should only be processed for the purpose of the Competition. If so, any processing by a third party should be excluded as we cannot guarantee that it is not copied while being processed on the external servers. Enterprise Tiers sometimes give that kind of guarantee but that's a pinky promise and cannot be verified on the user's end.</p>\n<p>So, my take on it is that we can use LLM as much as we like, so long as we:</p>\n<ol>\n<li>process the data while making sure it does not leak beyond our control (local LLM training, fine-tuning, etc.)</li>\n<li>make our end results public and cite the source material.</li>\n</ol>\n<p>But for official statement we should wait for the Hosts' response.</p>",
      "rawMarkdown": "I don't. I think that generally speaking, the data processed in this competition should only be processed for the purpose of the Competition. If so, any processing by a third party should be excluded as we cannot guarantee that it is not copied while being processed on the external servers. Enterprise Tiers sometimes give that kind of guarantee but that's a pinky promise and cannot be verified on the user's end.\n\nSo, my take on it is that we can use LLM as much as we like, so long as we:\n1. process the data while making sure it does not leak beyond our control (local LLM training, fine-tuning, etc.)\n2. make our end results public and cite the source material.\n\nBut for official statement we should wait for the Hosts' response.",
      "votes": null
    },
    {
      "id": "3387907",
      "postDate": "01/07/2026 19:18:59",
      "content": "<p>Thank you. I agree with your observation that it would generally be a violation of the rules to involve an LLM owned by a third party for any form of processing.</p>\n<p>Indeed! I'm curious to hear the host's opinion on this.</p>",
      "rawMarkdown": "Thank you. I agree with your observation that it would generally be a violation of the rules to involve an LLM owned by a third party for any form of processing.\n\nIndeed! I'm curious to hear the host's opinion on this.",
      "votes": null
    },
    {
      "id": "3388804",
      "postDate": "01/09/2026 16:07:28",
      "content": "<p>I found this response from the host: <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517\" target=\"_blank\">https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517</a></p>",
      "rawMarkdown": "I found this response from the host: https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 3387588,
      "author_name": "angantyr",
      "author_url": "",
      "post_date": "01/07/2026 10:49:35",
      "content": "<p>You may find <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/664775#3382894\" target=\"_blank\">this comment by DeepPast</a> of some use.</p>\n<p>I asked a similar question on text processing using externally sourced LLM models.</p>",
      "votes": null,
      "replies": [
        {
          "id": 3387598,
          "author_name": "anaphase21",
          "author_url": "",
          "post_date": "01/07/2026 11:06:50",
          "content": "<p>Thank you for the link. I have seen their response, but it seems to me not clear enough.  When they say \"… advisable to keep the use of this data for ML and not public display, and for any models as outcomes to cite the bibliography we provided for continuity.\", they don't seem to explicitly speak on the use of external LLMs for processing.</p>\n<p>Your response to their comment seem to indicate that you're unsure of what to make of their comment. Let me know if you have anymore insights on this.</p>",
          "votes": null,
          "replies": [
            {
              "id": 3387812,
              "author_name": "angantyr",
              "author_url": "",
              "post_date": "01/07/2026 16:56:35",
              "content": "<p>I don't. I think that generally speaking, the data processed in this competition should only be processed for the purpose of the Competition. If so, any processing by a third party should be excluded as we cannot guarantee that it is not copied while being processed on the external servers. Enterprise Tiers sometimes give that kind of guarantee but that's a pinky promise and cannot be verified on the user's end.</p>\n<p>So, my take on it is that we can use LLM as much as we like, so long as we:</p>\n<ol>\n<li>process the data while making sure it does not leak beyond our control (local LLM training, fine-tuning, etc.)</li>\n<li>make our end results public and cite the source material.</li>\n</ol>\n<p>But for official statement we should wait for the Hosts' response.</p>",
              "votes": null,
              "replies": [
                {
                  "id": 3387907,
                  "author_name": "anaphase21",
                  "author_url": "",
                  "post_date": "01/07/2026 19:18:59",
                  "content": "<p>Thank you. I agree with your observation that it would generally be a violation of the rules to involve an LLM owned by a third party for any form of processing.</p>\n<p>Indeed! I'm curious to hear the host's opinion on this.</p>",
                  "votes": null,
                  "replies": []
                },
                {
                  "id": 3388804,
                  "author_name": "anaphase21",
                  "author_url": "",
                  "post_date": "01/09/2026 16:07:28",
                  "content": "<p>I found this response from the host: <a href=\"https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517\" target=\"_blank\">https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517</a></p>",
                  "votes": null,
                  "replies": []
                }
              ]
            }
          ]
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "3387512": "On the competition rules page, under Data Security, it states *\"You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\"*\n\n@deeppast I am not sure how to interpret this in the context of using LLMs to interact or understand the competition datasets. I know the rules does not forbid the use of LLMs. However, it appears to me that using models like Gemini with competition data, would constitute permitting persons who have not agreed to the rules, access to competition data.\n\nAn example would be the use of online services for translating some of the non-English translations in the `publications.csv`. Ryan's response in this [thread](https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517) only seem to relate to the generation of synthetic data, whereas my question regards allowing access to the competition data. What is the recommended way to translate some of these translations that are in German, French, etc without allowing access to third party applications?",
    "3387588": "You may find [this comment by DeepPast](https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/664775#3382894) of some use.\n\nI asked a similar question on text processing using externally sourced LLM models.",
    "3387598": "Thank you for the link. I have seen their response, but it seems to me not clear enough.  When they say \"... advisable to keep the use of this data for ML and not public display, and for any models as outcomes to cite the bibliography we provided for continuity.\", they don't seem to explicitly speak on the use of external LLMs for processing.\n\nYour response to their comment seem to indicate that you're unsure of what to make of their comment. Let me know if you have anymore insights on this.",
    "3387812": "I don't. I think that generally speaking, the data processed in this competition should only be processed for the purpose of the Competition. If so, any processing by a third party should be excluded as we cannot guarantee that it is not copied while being processed on the external servers. Enterprise Tiers sometimes give that kind of guarantee but that's a pinky promise and cannot be verified on the user's end.\n\nSo, my take on it is that we can use LLM as much as we like, so long as we:\n1. process the data while making sure it does not leak beyond our control (local LLM training, fine-tuning, etc.)\n2. make our end results public and cite the source material.\n\nBut for official statement we should wait for the Hosts' response.",
    "3387907": "Thank you. I agree with your observation that it would generally be a violation of the rules to involve an LLM owned by a third party for any form of processing.\n\nIndeed! I'm curious to hear the host's opinion on this.",
    "3388804": "I found this response from the host: https://www.kaggle.com/competitions/deep-past-initiative-machine-translation/discussion/663656#3380517"
  },
  "source": "meta"
}