Privacy policy

Who is responsible

The data controller for the processing described here is Shanai Labs Ltd, a company incorporated under Israeli law under number 517293031, 6 Yehuda Amihai, 6967164 Tel Aviv-Jaffa, Israel (“the publisher”).

The publisher is established in Israel, a country the European Commission recognizes as providing an adequate level of protection for personal data (Decision 2011/61/EU, upheld in the review of January 15, 2024). Because it offers DevOne to people located in the European Union, the GDPR applies to its processing. Its representative in the Union, within the meaning of Article 27 of the GDPR, is To provide: name and address of the representative in the European Union.

For any question or to exercise your rights: contact@dev-one.app. The publisher has not appointed a data protection officer, as this is not mandatory for its activity.

In short

DevOne is a desktop app. Your conversations, meetings, files and settings stay on your computer. Some data leaves it so DevOne can work. This page says which data, where it goes and when.

DevOne contains no audience measurement or tracking tools: no analytics, no crash reports sent, no advertising.

The following sections repeat the text shown in the app, then spell out what the General Data Protection Regulation (GDPR) requires: purposes, legal bases, recipients, transfers and rights.

What you agree to at first launch

At first launch, DevOne shows this sentence:

“DevOne sends the content of your conversations and meetings to your AI provider to assist you and summarize them.”

Your consent is saved on your computer, in the file privacy-consent.json in DevOne’s data folder. An installation that existed before this screen is treated as having already accepted.

Data sent to your AI provider

Your AI provider is the one you choose and connect in DevOne: Anthropic, OpenAI, OpenRouter or another. DevOne has no AI server of its own. What your provider receives is processed under its own terms, including how long it is kept.

When you write to the agent

With each message, the agent sends your provider:

• your message and the conversation history;
• the files and code it reads;
• the output of the commands it runs;
• the screenshots it takes.

Between messages, DevOne may resend the last request to your provider to keep its cache warm. The next replies are then faster.

Background assistance tasks

DevOne also makes small requests on your subscription, without you starting them one by one:

• the titles and summaries of your sessions (up to 60,000 characters per session), including engine sessions started from a terminal;
• descriptions of the agent’s actions, with an excerpt of their output;
• suggestions for your next reply;
• corrections of your dictation;
• the tech watch summary;
• reviews, deployment reports and document reading.

These requests may go through a smaller model than the conversation’s. Depending on your setup, that model may belong to another provider.

Meetings

Meetings are recorded and transcribed on your computer. When you stop recording, DevOne sends the transcript to your provider to summarize it. The transcript can be up to 120,000 characters. It contains the speakers’ names and the titles of shared windows.

The transcript contains what everyone present says. Let them know before you record: DevOne suggests a sentence to paste into the video call chat.

Urgent message triage

“Urgent” triage for WhatsApp, Gmail and Slack is off by default. If you turn it on, DevOne sends your provider the last 4 messages of each conversation to judge how urgent they are.

Web search

When the agent searches the web, its query goes to your provider’s search service. Otherwise, it goes to a public search engine: Startpage, Google, DuckDuckGo, Ecosia or Mojeek. The query may include words from your conversation.

Secrets

DevOne can mask secrets before anything is sent (Data & privacy setting). For a new project, the values in the .env file are masked by default: the agent sees the variable names, not their values. You can make them visible project by project.

When values are masked:

• the agent can’t read credential locations: the engine’s login database, ~/.ssh, the Vercel, GitHub and Supabase logins, DevOne’s private data and browser profiles;
• secrets are also masked in their encoded forms (base64, hexadecimal, URL, JSON) and when they are short.

Limits: the agent can still use a variable without reading it, for example in a curl command. A program that scans an entire folder isn’t detected.

On your computer, the DevOne account tokens, your Slack token and your private calendar addresses are stored in the system keychain: Windows Credential Manager, the macOS Keychain or Secret Service on Linux. The DevOne account in the web admin keeps its session in that browser’s local storage. The engine’s login tokens (file ~/.omp/agent/agent.db) remain readable in plain text, because the command-line engine shares this file. DevOne only restricts access to it to your user account.

Your AI provider processes this data as a separate data controller, under the contract you have with it. The publisher has no access to it.

Other data that leaves your computer

The community and your DevOne account

Your DevOne account uses Supabase for sign-in with Google, GitHub or an email link. This account is shared by the app, usage rights, the community and the admin; it stays separate from the AI accounts you connect to the engine. There is no license key to enter. Google and GitHub are involved only when you choose their sign-in method.

The community is optional: only the messages, replies, reactions, requests, votes and attachments you send are published. Other members see the published content and your display name, not your sign-in address. Attachments are kept in private storage. Authorized members get links valid for one hour; forwarding one of these links also gives access to the file until it expires. A member can’t get a link to another member’s unpublished draft.

The currently configured project is hosted in Frankfurt, Germany. This region covers the project’s database and storage; it doesn’t mean that all processing by the authentication, email or payment providers stays in the European Union.

Once you’re signed in to your DevOne account, the app reports its presence while it runs, even if you don’t open the community. The signal contains your account identity, an instance ID and its timestamp, not your activity in conversations or files. Members only see how many people are online; only admins see their names. Several instances of one account count as one person. With no signal for two minutes, the account no longer counts as online. Signing out of DevOne stops this signal. The web admin doesn’t report presence.

Replies, mentions and changes to requests you follow trigger targeted notifications. Announcement notifications are sent only if you turn on “Receive announcements” in your profile.

A screenshot or video attached to a message is sent only when you ask. The selection and its markers stay local until you send: check the proof and remove anything you don’t want to share. The community doesn’t record your usage, and uses no session replay or tools like PostHog. Replays from the agent’s browser stay on your computer, unless you choose to share a clip.

Polar Software, Inc. sells you the Plans as a reseller (“merchant of record”): it collects payment, issues the invoice and applies VAT, under its own terms and privacy policy, and under its own responsibility. The community service keeps the customer ID and payment entitlements received from Polar to link them to your account, not your card details. Managing this data requires a role verified by the server.

At your first authenticated access check, the service records the start and end dates of your free trial month. These dates are tied to your account, not to your conversations or files. The trial requires no card and starts no subscription or charge when it ends.

Your phone

If you pair a phone, the PC and the phone communicate through a relay: my.omp.sh, run by Stencil Labs, the publisher of the OMP engine.

• Content is end-to-end encrypted. The relay can’t read your conversations.
• The relay sees the IP address of the PC and the phone, a room ID, a device ID, and the size and time of exchanges.
• The phone app is served by Vercel when you open it in a browser.

A paired phone can do everything the PC does: read your conversations, run commands, read your secrets. If you lose a phone, revoke it in the Devices panel.

Images and pages cited by the AI

• An image or video from the web in a reply doesn’t load on its own. It loads only when you click “Load image” or “Load video”. The site then receives your IP address and the image address, without the address of the DevOne page the request comes from.
• To illustrate a cited page, DevOne downloads it itself, without cookies. If the page has no image, DevOne takes a screenshot of it in an empty browser profile, without your accounts, deleted after the capture.
• The title of a mentioned page is read the same way, without cookies.
• DevOne never downloads a page on your local network or your computer cited by the AI.

Site icons

DevOne downloads a site’s icon directly from that site, then keeps it on your computer. No third-party service receives the list of sites you open. For a site on your local network or your computer, the icon is read directly from that site.

The built-in browser

Sites you open in DevOne’s browser receive what any browser sends. A search typed in the address bar goes to Google. The agent can use the sites you’re signed in to in this browser.

Chromium, the engine behind the browser and the interface, also contacts Google on its own at launch, even before the consent screen, without anything from your conversations. It checks its security data (revoked certificates, certificate transparency, download rules) and updates it from update.googleapis.com, and asks accounts.google.com for the list of Google accounts signed in to its browser. Google receives your IP address. DevOne blocks Chromium’s other background requests to Google: the address bar AI mode check and the translation model. Extensions that other software on your computer registers for Google Chrome (Windows registry, External Extensions files) are never installed in DevOne’s browser; the ones you install yourself from the Chrome Web Store work.

Updates

DevOne checks for an update 30 seconds after launch, then every 6 hours. You can turn this check off. It queries GitHub, which receives your IP address, your DevOne version, your operating system and your processor type. An update installs only when you click “Restart”.

Updates are signed: DevOne rejects an update whose signature doesn’t match. Linux .deb and .rpm packages don’t update on their own.

On your computer, DevOne keeps its update log for 90 days, with at least the last 5 updates. The previously installed version is deleted after 7 days.

Tech watch

When the tech watch refreshes, DevOne reads public release notes from GitHub, docs.claude.com and platform.openai.com. These sites receive your IP address. No GitHub token is sent, unless you deliberately provide one in the DEVONE_NEWS_GITHUB_TOKEN variable: it’s then used only if GitHub refuses anonymous access. The tech watch summary is written by your AI provider.

Model and tool downloads

After you agree at first launch, DevOne downloads its small local model in the background (llama.cpp from GitHub, Gemma 3 1B from Hugging Face, about 800 MB), unless you’ve turned it off. When you install another local model or a tool, DevOne downloads it from Hugging Face, GitHub or the npm registry. These sites receive your IP address.

Your connections

• Calendar: DevOne reads the iCal address you give it.
• Slack: DevOne uses your Slack token to read and send your messages.
• Command-line tools (GitHub, Vercel…): DevOne runs them with the credentials they already have on your computer.
• MCP servers: the servers you add receive what the agent sends them.

Engine telemetry

If your environment sets OTEL_EXPORTER_OTLP_* variables, the engine sends its traces to the given address. Conversation content is included only if you asked for it with OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT.

What stays on your computer

• Local models. Searches in your sessions and small local tasks run on llama.cpp (Gemma 3 1B). Meeting and voice transcription runs on sherpa-onnx. These models run on your processor and only listen on your computer. If a local model fails, the task goes to your AI provider.
• DevOne’s journal and the crash log. They are never sent.

What the publisher processes, and why

The publisher receives neither your conversations, nor your files, nor the content of your meetings. It processes only the following data:

An email address or a Google or GitHub account is required to create a DevOne Account; without an account, no agent can start. The publisher makes no decisions based solely on automated processing and does no profiling.

Recipients and service providers

The publisher doesn’t sell or rent your data. It is accessible to the publisher and to the service providers that help it run DevOne, each for its own task only:

Transfers outside the European Union

The DevOne Account database stays in the European Union. Some providers, or their own subprocessors, are established outside the Union, notably in the United States. These transfers are safeguarded, provider by provider, as follows:

• The publisher, in Israel : European Commission adequacy decision (2011/61/EU);
• Vercel, Google, GitHub and Resend : certified under the EU–U.S. Data Privacy Framework, recognized by the European Commission adequacy decision of July 10, 2023;
• Polar, Supabase and Stencil Labs : standard contractual clauses adopted by the European Commission (Decision 2021/914).

You can get a copy of these safeguards by writing to the publisher.

How long DevOne keeps your data

• Browser replays, closed side chats, log of your actions, Briefing history, browser tab registry: 90 days, then deleted automatically. The replay of a conversation active within the last 90 days is kept.
• DevOne’s journal: what DevOne has learned stays; the details of your conversations it indexes are forgotten about 4 months after their last message (sooner if the journal exceeds 512 MB, never before 30 days).
• Images in your notes and files sent from your phone: deleted as soon as nothing uses them anymore (note deleted, file never sent, conversation deleted or forgotten by the journal).
• DevOne test instances: deleted after 14 days without use.
• Raw meeting audio: 30 days after the meeting ends. The transcript, images and notes stay.
• Usage tracking: 8 days.
• Agent conversations: kept in ~/.omp/agent/sessions until you delete them.
• Icons and images of cited pages: kept in DevOne’s data folder, with no time limit. An icon is downloaded again after 30 days.
• Community: published messages, requests, votes and proofs stay on the shared service until they are deleted. Quitting or uninstalling DevOne doesn’t delete these posts. To delete your account or your shared content, contact the publisher.

At the publisher

• DevOne Account and trial dates: as long as the account exists. An account with no sign-in for two years is deleted, in line with the recommendations of the CNIL (French data protection authority).
• Billing data: invoices are issued and kept by Polar, the reseller. The publisher keeps the customer ID and entitlements received from Polar as long as the account exists, and its own accounting records for the period required by Israeli accounting and tax rules.
• Support exchanges: three years after the last exchange.

Deleting your data

• A conversation: delete it in DevOne. DevOne then erases its history and backups, its working files (subagents, tool results), its side chats, its replays, its browser screenshots, its title, its icon, its summary and every trace of it in the journal, search included.
• All data on Windows: when uninstalling, check “Delete app data”. DevOne erases %APPDATA%\app.dev-one.desktop and %LOCALAPPDATA%\app.dev-one.desktop (with the working copies in the default folder), the folders under the old name, %TEMP%\devone and its session files in ~/.omp/agent. Without the checkbox, everything stays.
• All data on macOS or Linux: quit DevOne, then delete the app.dev-one.desktop folders. On macOS, they’re in ~/Library/Application Support and ~/Library/Caches ; on Linux, in ~/.local/share and ~/.cache.
• Engine history: the ~/.omp/agent folder is shared with the command-line engine, so DevOne keeps it. Delete your history manually in ~/.omp/agent/sessions.
• Exported videos: they stay in your Videos\DevOne.
• Phones: revoke them in the Devices panel.
• Data held by your AI provider: follow its terms and settings.
• Account and community content: contact the publisher via dev-one.app; deleting local data or revoking your sign-in doesn’t delete what has already been published.

Your rights

You can view, correct or delete your data on your computer at any time. For data sent to your AI provider, Vercel, GitHub or the my.omp.sh relay, contact each of them. For any question about DevOne, write to the publisher via the dev-one.app website.

For the data the publisher processes, you have the rights of access, rectification, erasure, restriction, portability and objection, the right to withdraw your consent at any time and the right to set instructions on what happens to your data after your death.

Write to contact@dev-one.app. The publisher replies within one month, which may be extended by two months for a complex request; you may be asked for proof of identity if there is doubt.

If you believe your rights are not being respected, you can lodge a complaint with the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or at cnil.fr.

The dev-one.app website

When you visit this website, its host records technical logs (IP address, requested page, browser, date) to serve and protect it. Vercel keeps them under its own privacy policy and legal obligations; the publisher consults them only to diagnose an incident.

The website sets no audience measurement or advertising cookies, and uses no trackers that require your consent (Article 82 of the French Data Protection Act).

Minimum age

A DevOne Account can be created from age 15. Below that age, consent from a holder of parental authority is required (Article 45 of the French Data Protection Act). Buying a Plan is reserved for adults or people authorized by their legal guardian.

Changes

This policy may change as DevOne evolves. The last updated date is shown at the top of the page. If there is a significant change, you’ll be notified by email, at your DevOne Account address, before it applies. If the change concerns what DevOne sends to your AI provider, the app asks for your consent again at the next launch.