Privacy Policy

Palisade Code is maintained by Tristan Smith. This policy covers the Palisade desktop application, account sign-in, and the website at palisade-code.dev. Last updated: October 8, 2026.

Questions or requests about your information can be sent to tjlsmith0831@gmail.com.

Account sign-in

Versions that support Palisade accounts use Clerk for authentication. You can sign in through Google, GitHub, or a one-time email code. Clerk processes your account information and authentication activity to provide sign-in, manage sessions, and protect accounts against abuse.

Palisade receives your account identifier, email address, and, when supplied by your provider, your display name and profile image. We use this information to identify your account, display your profile, manage access to Palisade, and understand account registrations. Authentication credentials are used to establish and maintain your session. Signing into Palisade does not give us access to your Google Drive files, Gmail messages, or private GitHub repositories.

Google account information is used for authentication and account management. We do not sell it, use it for advertising, or use it to train AI models. Palisade's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

Your identity provider and Clerk also process information under their own privacy policies. Their hosted sign-in pages may use cookies and similar technologies for authentication and security.

Your local workspace

Palisade stores project settings, session history, preferences, logs, and local completion statistics on your computer or in your project files. The bundled completion model runs locally; Palisade does not upload code or a repository index for those local model features. Signing in does not automatically upload your projects or synchronize your workspace to a Palisade cloud service.

Coding agents, git remotes, database connections, previewed websites, and MCP servers that you choose may send prompts, code, files, or other information to their own services. Their permissions, terms, and privacy policies apply. Review those services before giving them access to confidential data. Palisade does not control their processing.

Website and network services

The website is hosted by Vercel and uses Vercel Web Analytics for page views and clicks on downloads, installation guides, and GitHub links. Analytics may include page paths, referrers, approximate location, browser and device information, and event times. Our custom click events include destination categories and page placement. We strip query strings and fragments from page-view URLs and do not send code, clipboard contents, account emails, or provider credentials in these custom events. Vercel Web Analytics does not use third-party tracking cookies. The website stores your theme preference locally in your browser. See Vercel's analytics privacy documentation.

Network requests for sign-in, website hosting, updates, model downloads, and registry lookups expose ordinary request information, such as IP addresses and request times, to the services handling them. Palisade uses services including Clerk, Vercel, Cloudflare, GitHub, and model or registry hosts for these functions. They may process operational logs and security information under their own policies, including in countries different from yours.

Support and feedback

When you send an in-app feedback report, its title and message pass through a Cloudflare service to create a GitHub issue. Reports may include the app version, operating system, processor architecture, detected agents, and whether the local model is installed. GitHub issues on the public Palisade repository are public. Do not include secrets or private project content. The feedback service uses the request IP address for rate limiting.

If you contact us directly, we receive the information you provide and use it to respond and maintain the service. Report security vulnerabilities through GitHub's private vulnerability reporting, rather than a public issue.

Sharing and retention

We do not sell personal information or use account information for targeted advertising. Information is shared with the services needed to deliver the functions described above, with services you choose to connect, or when necessary to comply with applicable law or protect users and the service.

Local workspace information remains on your computer until you remove it; uninstalling the app may leave its data directory intact. Account and support information is retained while needed to provide access, address requests, maintain security, or meet legal obligations. Service-provider logs and backups follow their own retention practices. Deleting an account does not erase local files or copies held independently by services you chose to use.

Your choices and requests

You can stop using connected services, revoke Google or GitHub access in that provider's account settings, and remove local Palisade data. To request access to, correction of, or deletion of account or support information held for Palisade, email tjlsmith0831@gmail.com. We may need to verify your identity before fulfilling a request. Privacy rights depend on your location, and we will handle requests as required by applicable law. Public reports and third-party data may require separate requests to the relevant service.

Palisade is not directed to children under 13. If you believe a child has provided personal information, contact us so we can investigate and address it.

Changes

We will update this page when our practices change and revise the date above. Material changes to account-data use will be communicated through the website, application, or account contact information as appropriate. New uses of Google data will require the disclosures and consent required by Google's policies.