Privacy Policy
Revision from November 18, 2025
Definitions
- Company: “Soarailabs”, “Soar AI Labs”, “we”, or “us” refers to the maintainers and operators of the Soar AI Labsopen source projects and any associated hosted services.
- Maintainers: Core contributors/developers who operate Soar AI Labs's infrastructure, websites, and managed offerings (if any).
- Software/Services: Soar AI Labs tools, Glide MCP, merge conflict resolver, semantic commit splitter, context engines, any hosted APIs, and affiliated open source projects.
- Website: soarailabs.com and soarailabs.vercel.app, along with related documentation and project pages.
Scope
This Privacy Policy describes how we handle information when you:
- Visit our Website;
- Use any hosted or managed Services we operate; or
- Interact with us via community channels (for example, GitHub issues at https://github.com/SoarAILabs).
Local‑First Design and Zero Data Retention
Our design goal, as described on our sites and blog, is that your code stays with you. Glide MCP and similar tools are intended to run locally in your environment, against your own repositories, with your own API keys.
By default:
- We do not receive your repository contents, diffs, or commit history when you run Glide locally.
- Version control context (history, branches, diffs) is processed on your machine or your chosen infrastructure.
- We do not retain your Git data on our servers unless you explicitly opt into a hosted feature that requires it.
Information We Process
Depending on how you use our projects, the following categories of information may be involved:
Local use / self‑hosted tools
When you run Glide MCP or other tools locally, they may access:
- Repository metadata (paths, branch names, commit IDs, file paths).
- Diff contents and commit messages, to generate semantic commit splits or conflict resolutions.
- Configuration and API keys for third‑party providers that you configure.
For local or self‑hosted use:
- This data stays within your environment and is not sent to Soar AI Labs by default.
- Any processing of that data by third‑party providers (for example, LLM or embedding APIs) is governed by their privacy policies.
Hosted or managed Services (if you opt in)
If you choose to use our hosted context engine, managed inference, or other cloud offerings, we may process:
- Code snippets, diffs, commit messages, and repository metadata needed to provide semantic indexing, retrieval, or automation.
- Derived artifacts such as embeddings, summaries, or metadata about your repository structure.
- Basic account information or identifiers needed to provide access control and usage tracking.
We aim to minimize the amount of data we ingest, retain data only as long as necessary to provide the service, and provide a way for you to request deletion where feasible.
Website and analytics
When you visit our Website, we may collect limited technical information:
- Standard HTTP request logs (IP address, user agent, referrer, timestamps).
- Aggregated analytics (for example, page views, time on page) using privacy‑respecting analytics tools, such as Plausible or equivalent, where we avoid using cookies or cross‑site tracking whenever possible.
We use this information solely to maintain and improve the Website, monitor performance, and prevent abuse.
Third‑Party Services and Data Flows
Our tools and sites may integrate with or rely on third‑party services, such as:
- Git hosting platforms (e.g., GitHub).
- LLM providers (e.g., Cerebras Systems Inc).
- Embedding/vector providers (e.g., Voyage AI Innovations, Inc.).
- Graph databases or infrastructure (e.g., HelixDB, if used via hosted endpoints).
- Hosting, CDNs, or analytics providers.
When you configure Glide or related tools with your own API keys, requests may send code snippets, diffs, file paths, and repository metadata from your environment directly to those providers. Those requests are governed by the third‑party’s own terms and privacy policies.
Soar AI Labs does not receive or control those data flows unless we are operating the third‑party service ourselves as part of a managed offering.
If we operate a managed context engine or hosted API, we may route your requests through our infrastructure in order to call external providers on your behalf. We will document which providers are involved and what data they receive. We will avoid retaining raw code and diffs longer than necessary to provide the feature, and may store only derived artifacts (for example, embeddings or summaries) where required.
Community and Communication Data
If you interact with us via GitHub, forums, social media, or email, we may see your username, profile information, and the content you choose to share (issues, PRs, comments, emails). That information remains subject to the terms of the platform where you submit it (for example, GitHub’s policies) and is also visible to other users as dictated by that platform.
We may use this information to maintain our projects, respond to issues, and improve our tools and documentation.
Children’s Privacy
Our Software and Services are intended for developers and technical users. They are not directed at children under 13 (or the minimum age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have inadvertently collected information from a minor, please contact us so we can delete it.
Security
We use reasonable technical and organizational measures to protect any data we control, including encryption in transit where applicable and access controls on our infrastructure.
However, no system is perfectly secure. You are responsible for securing your own environment, including local clones, API keys, and self‑hosted deployments. We strongly recommend following best practices for secrets management, access control, and backups.
Data Retention
- Local and self‑hosted use: We do not control or retain your data; retention is determined by your own environment and configurations.
- Hosted or managed Services: We retain data only as long as necessary to provide the service, comply with legal obligations, or resolve disputes. Where feasible, we will document retention periods in service‑specific documentation.
- Logs and analytics: Server logs and analytics may be retained for a limited period (for example, 24–90 days) for security, debugging, and performance monitoring, after which they may be aggregated or deleted.
Your Rights and Choices
Depending on your jurisdiction, you may have rights to access, correct, or delete personal data that we control, or to object to or restrict certain processing.
If you believe Soar AI Labs holds personal data about you (for example, from a hosted account, support interaction, or newsletter), you may contact us to request:
- Access to the data we hold about you;
- Correction of inaccurate data;
- Deletion of data where legally permissible.
We will respond in accordance with applicable law.
Legal Basis and Jurisdiction
Soar AI Labs is operated from [your jurisdiction]. By using our Website or any hosted Services, you consent to the processing and transfer of information as described in this policy, subject to applicable law.
When we rely on consent (for example, for optional analytics or specific hosted features), you may withdraw that consent at any time, though this will not affect processing that has already occurred.
Updates to this Policy
We may update this Privacy Policy from time to time. When we make significant changes, we will post the updated version on the Website and may announce it via our GitHub organization or other channels.
Your continued use of the Website or any hosted Services after the effective date of changes constitutes your acceptance of the updated policy.
Contact
For privacy inquiries, data requests, or security concerns, contact us at the.kite.squad@protonmail.com.