Skip to main content
GladeKit is built for professional and indie teams alike. We take the security of your project and account data seriously and document our practices below. For security inquiries or to report an issue, contact glade@gladestudio.ai.

​
What does GladeKit collect from my project?

When you connect GladeKit to a Unity or Unreal project, we gather only what’s needed to give you relevant, project-aware answers. That includes:
  • Scripts: paths, file names, and source content (used for search and retrieval).
  • Project context: scene hierarchy, scene summary, list of scripts, and installed packages - used to build context for your prompts.
Binary assets (textures, meshes, audio, etc.) are not indexed for AI. We process only the script and context data required to answer your questions accurately.

​
Who owns the code and outputs GladeKit generates?

You do. Scripts and other project outputs produced by GladeKit are yours. We don’t claim any ownership over code or content created in your project. Our EULA confirms that you retain ownership of your project and your use of the Software.

​
Do LLM providers train on my code?

No. The models we call (e.g. OpenAI, Anthropic) receive your project data only to fulfill a single request. Our contracts with these providers forbid them from using your data for model training. Your code and project data are not used to train any third-party models.

​
Where is my data stored, and how long do you keep it?

  • Search index (scripts): Script content is stored in our cloud database to support semantic search. When you run “index project” again, we replace your existing index with the new one - we keep a single project index per account.
  • Temporary caches: Context (e.g. scene info, script list) is cached for a few minutes to speed up requests, then discarded.
  • Sessions: Chat session metadata lives in our backend and may be cached for up to 7 days so sessions persist across restarts.
We don’t retain project data beyond what’s needed for indexing, caching, and sessions. Re-indexing or disconnecting updates or stops our use of your indexed data.

​
How is my data protected in transit and when stored?

  • In transit: All requests to our services use HTTPS (TLS). Data leaving the GladeKit app is encrypted in flight to our backend and to any storage or AI providers we use.
  • At rest: Stored data and caches sit on our backend infrastructure with encryption at rest. We don’t keep your project data in plaintext.
We follow standard encryption and access-control practices and will pursue further certifications over time.

​
What do you do with my account and sign-in data?

We use personal data only to operate the service (e.g. identity and authentication). Details on what we collect and how we handle it are in our Privacy Policy (gladekit.com or in the app). Sign-in (email/password or OAuth with Google/GitHub) is handled by our backend. The app keeps session tokens locally and sends them with requests to our backend for authorization.

​
At a glance

AreaIn short
What we collectScript paths, names, and content; project context (scenes, hierarchy, packages). No binary assets.
LLM trainingYour data is not used to train provider models.
StorageOne project index per account (replaced on re-index); short-lived context cache; session data up to 7 days.
ProtectionHTTPS in transit; encryption at rest on our backend.
Account dataSee Privacy Policy; sign-in via our backend; sessions stored locally for API access.
OwnershipYou own all scripts and outputs from GladeKit.
Questions or concerns? Email glade@gladestudio.ai.