Skip to main content

Data & Security

What personal data does Copilot4Eclipse collect and how is it used?

Data Transmission
Copilot4Eclipse passes all user data (e.g., source code, filenames, chat prompts and file context) except user preferences directly to GitHub Copilot where it is managed according to the user’s GitHub Copilot subscription type: individual subscription or business subscription. No user data is communicated from Copilot4Eclipse to any Genuitec computer or any 3rd party computer.

Data Analysis and Interpretation
Copilot4Eclipse does not directly analyze any user data beyond the Copilot4Eclipse user preferences.

Data Persistence and Storage
Copilot4Eclipse stores user preferences and Chat conversations on the user's local computer in subfolders of the current Eclipse workspace folder. User preferences consist of user-created parameters that are used by Copilot4Eclipse to customizing the user's experience. Chat conversations consist of the user's prompts, (e.g., questions, instructions, commands), and GitHub Copilot responses for each prompt. Conversations are stored in a single Exodus database file and persisted until the user deletes them individually or collectively.

User preference data consists of the following:

    Automatically show inline completions: (boolean, default: true)
    Strict SSL certificate checking for proxy connections: (boolean: default: true)
    Poll for GitHub Copilot status changes: (boolean, default: true)
    Completion text color: (RGB string, default:”128,128,128”)
    Disabled Copilot Language Identifiers: (String array, default: “abap,bibtex,c,csharp,cpp,clojure,coffee,dart,diff,elixir,erlang,fsharp,fortran,go,groovy,haml,handlebars,haskell,ini,kotlin,lisp,latex,less,lua,makefile,markdown,matlab,php,perl,plaintext,powershell,pug,r,razor,ruby,rust,scala,shaderlab,shellscript,stylus,swift,vb,bat,xsl”)

Conversation data consists of the following:

    Conversation name or title
    User prompts (text)
    GitHub Copilot Chat responses (text)
    Filenames that make up the query context