This Privacy Policy explains how our apps (Ceres and others) handle data when used as browser extensions, IDE tools and Desktop/Mobile experiences.
Overview
Our apps are designed to run close to the user's browser, editor, and project files.
App settings, local workspace data, conversations, images, and audio workflows are handled through the user's browser, editor, operating system, or configured AI provider.
We do not provide our own sync server for user conversations, API keys, audio recordings, images, source code, or project files.
Products Covered
This policy covers:
- Ceres
- Luna Crop
- Related browser extension experiences
- Related VS Code and IDE extension experiences
- Related local web app experiences provided with our apps
Browser extension packages and VS Code or IDE extension packages are built separately. The Chrome build does not include the VS Code extension host code, and the VS Code build does not include Chrome-only extension runtime files unless they are genuinely needed for compatibility.
Data The Products Handle
Depending on which features the user chooses to use, our apps may handle:
- User prompts and chat messages
- Selected text from a web page or editor
- Source code selected or attached by the user
- Project files selected or opened by the user
- Terminal output, diagnostics, git context, or IDE context requested by the user
- Images opened, pasted, generated, edited, exported, or saved by the user
- Audio captured for voice or dictation features
- API keys, provider connections, selected models, and app preferences
- License state and local usage information
- Error reports when error reporting is triggered
Local Storage And Settings
App settings and local working data are stored using storage available in the user's environment.
This can include:
- Chrome Storage
- Chrome Storage Sync
- Chrome Storage Local
- Browser local storage
- Local project files when the user saves assets or files
API keys, provider connections, selected models, language settings, and preferences are stored in these local or browser-provided storage systems.
Chrome Storage Sync
Some small settings can be stored with Chrome Storage Sync when one of our apps is running as a Chrome extension and Chrome Sync is available.
Chrome Storage Sync is a browser storage feature provided by Chrome. It can sync extension settings between the user's Chrome browser installations when the user is signed in and has Chrome Sync enabled.
This sync is handled by Chrome as part of the user's browser account. It is not a sync service operated by us, and the synced settings do not pass through our servers.
Larger local data, working content, images, and local app state are handled through Chrome Storage Local, browser local storage, IDE storage, or local project files depending on the environment and feature.
Local And Device-To-Device Communication
Some products may communicate locally with each other to provide a smoother user experience. This can include communication through localhost on the user's own device, or peer-to-peer communication between the user's own devices, such as a phone and a computer.
This communication is used only for product features the user chooses to enable or approve. It may help connect companion apps, browser tools, desktop tools, mobile tools, or local workflows without using our server as a data sync service.
For peer-to-peer features, we may use WebRTC. Discovery servers may help the user's devices find each other, but they do not mediate the actual traffic. We do not monitor, collect, or have access to that peer-to-peer traffic.
AI Providers And External Endpoints
Some AI features require a model provider or provider connection. When the user configures or selects an external AI provider, the data needed for that request is sent to that provider.
Supported provider types may include:
- OpenAI-compatible providers
- OpenRouter
- Google-compatible providers
- Anthropic-compatible providers
- Custom provider connections
- Local providers such as Ollama or LM Studio
When a local provider is used, requests are handled by the user's local provider setup.
Chrome Web Store Limited Use
When our browser extensions access information made available by Chrome APIs, that information is processed locally by the extension to provide the user-facing features of our apps.
Website content, selected text, active tab context, browsing-related context, and similar Chrome API data are used only when needed for the user-facing features the user chooses to run.
Our handling of information made available by Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information handled through Chrome APIs is not sent to our servers as part of a tracking, analytics, or product sync system.
We do not use information made available by Chrome APIs for unrelated advertising purposes, selling user data, or building unrelated user profiles.
Data Sharing
Data is shared only when needed for the feature the user chooses to use.
This can include:
- Sending AI requests to the provider configured or selected by the user
- Sending license verification requests to a licensing provider such as Gumroad
- Contacting our server for product update checks, version information, announcements, notices, or UI tips
- Sending runtime error reports only when the user manually chooses to allow or submit them
External AI providers process requests according to their own terms and privacy policies.
We do not sell user data.
We do not use user conversations, prompts, audio, images, source code, web data to train our own or partners' AI models.
We do not control or guarantee the practices of external providers selected or configured by the user, including their retention or model training policies.
Voice And Audio
Audio is captured only when the user starts a voice or dictation feature. The user must approve microphone access for the active tab or product experience before recording starts.
Audio is used for transcription or voice-related features. In the normal product flow, voice recordings are not saved as permanent audio files by our products.
For browser speech-to-text, our products may use browser-provided speech recognition technology, such as the speech recognition available in Google Chrome. This technology is provided by the browser or platform, not by us.
Depending on the browser, device, language, and available support, speech recognition may run locally or may be processed through a cloud service operated by the browser or platform provider. For example, Google chrome speech recognition can use a server-based recognition engine.
If the user configures an external audio LLM model, the audio required for transcription is sent to that configured LLM provider.
In VS Code and IDE experiences, audio is handled by the operating system or by the audio model configured by the user.
Learn more: MDN Web Speech API SpeechRecognition.
Images And Luna Crop
Our image editing app (Luna Crop) is designed for local image editing workflows.
Images can be opened, pasted, edited, converted, exported, and saved through the user's browser, IDE, local storage, or project files.
Luna Crop does not require our server to crop, resize, convert, edit, export, or save images.
If another product feature sends an image to an AI provider, that happens only as part of an AI request chosen by the user.
Code, Terminal, And IDE Context
IDE features can work with code selections, open files, diagnostics, terminal activity, git context, and project information.
This context is used when the user chooses a feature that needs it, such as adding a file to chat, asking about terminal output, or requesting help with project code.
When the configured AI provider is remote, the selected context needed for the request is sent to that provider. When the configured provider is local, the request is handled by the local provider setup.
On-Device Browser AI
Some products may use on-device AI provided by the browser when it is available.
When a feature runs through browser-provided on-device AI, processing is handled locally by the browser.
When a feature is configured to use an external provider instead, the request is sent to that provider.
License Verification
License-related features may store license state locally and may contact a license provider to verify a license.
For paid licensing flows, license verification may be handled through Gumroad.
Product Updates And Notices
Our extensions may contact our server to check for available app updates, version information, announcements, or notices that can be shown inside the user interface.
These requests are used to help keep users informed about new versions, available updates, app changes, tips, or important messages related to our apps.
This update and notice mechanism is separate from app data storage and is not used for sync.
Analytics
Our extensions and apps do not include our own analytics or tracking system for app usage.
Marketplace-level statistics, such as install counts or store dashboard metrics, may be provided to us by the relevant marketplace platform, such as the Chrome Web Store or Visual Studio Marketplace, according to that platform's own policies.
Our public websites may use website analytics to understand site traffic and improve the website experience. Website analytics are separate from extension and app data. Our apps do not load complete public web pages into the apps at any case.
Error Reports
Our apps include error handling features for runtime errors.
Runtime error reports are not sent by default.
Runtime error reports are sent only when the user manually chooses to allow or submit them.
When submitted, error reports are intended to help diagnose crashes and bugs.
Data Deletion
Users can remove locally stored app data by:
- Removing saved API keys and provider settings from the app settings
- Clearing browser extension storage
- Clearing browser local storage
- Uninstalling the browser extension
- Uninstalling the VS Code or IDE extension
- Deleting local project files or exported assets created by the user
- Removing local provider configuration from tools such as Ollama or LM Studio
Data Retention
Locally stored data, including API keys, provider settings, selected models, local chat state, local usage state, and app preferences, remains in the storage environment where it was saved until the user removes it, clears storage, uninstalls the extension, changes settings, or deletes the relevant local files.
Runtime error reports, when manually submitted by the user, may be retained for debugging, reliability, and product maintenance purposes.
Security
We use the storage and permission systems provided by the browser, Chrome extension platform, VS Code, the user's operating system, and the user's configured providers.
Users should protect their browser profile, editor profile, local machine, API keys, provider accounts, and local project files.
When users configure third-party or local AI providers, the security of those providers depends on the provider or local setup selected by the user.
Legal Basis
Where applicable, we process data on the following bases:
- To provide the app features requested by the user
- To store user-selected settings and preferences
- To operate configured AI provider requests chosen by the user
- To verify licenses when licensing features are used
- To maintain app reliability, updates, notices, and user-facing support features
- Based on user consent where optional runtime error reports are manually allowed or submitted
Children
Our apps are intended for developers, creators, and general productivity users. They are not directed to children.
Users who are not old enough to use browser extensions, marketplace extensions, AI providers, or developer tools under the laws of their country should not use our apps without appropriate permission from a parent or guardian.
International Transfers
Users may configure AI providers, licensing providers, browser sync, or local/remote provider connections that operate in different countries.
When data is sent to an external provider selected or configured by the user, that provider may process data in locations described in its own terms and privacy policy.
Chrome Sync, marketplace services, AI providers, Gumroad, and other third-party services are governed by their own infrastructure, terms, and privacy practices.
Changes To This Policy
We may update this Privacy Policy as our apps, features, or provider integrations change.
When the policy changes, the updated version will include a new last updated date.
Contact
For privacy questions, contact: