dzimplei › Privacy Policy
Privacy Policy
How dzimplei handles your data across the desktop application, the website, and the Chrome extension. Honest, plain-spoken, and governed by European data protection law.
Last updated: 15 November 2026 · Controller: Dzimplei Limited, Ireland.
Overview & Core Principles
dzimplei is an AI workspace and agent coordination environment. We believe software handling your work, code, and browser sessions should be transparent, respectful, and strictly under your control.
- We do not sell your data. We never sell, rent, monetize, or broker personal data, browsing history, or workspace content to third parties.
- We do not run behavioral advertising. There are no ad networks, behavioral tracking pixels, or cross-site fingerprinting scripts in our apps or browser extensions.
- You choose where work runs. A local desktop workspace can stay on your computer. Hosted workspaces, server connections and AI requests send the data needed for those features to the selected server or provider.
- Controller. Dzimplei Limited, Trinity Hall, Dartry Road, Dublin 6, Ireland, operates the hosted service. Contact [email protected] about your data. EU hosting does not mean that every connected service or AI provider processes data only in the EU.
Purposes, Legal Bases & Retention
- Accounts and requested work: email, identity-provider information, passkey public keys, device credentials, preferences, chats, files, tool results and agent memory are processed to provide the service you request (Art. 6(1)(b)). Account and workspace content remains while you use the service or until you remove it or request erasure, subject to recovery archives and legal exceptions described below. Authentication requires the corresponding identifier; without it we cannot sign you in.
- Security and reliability: connection information, temporary network-address rate limits and technical/error records protect accounts, investigate failures and prevent abuse (Art. 6(1)(f), our legitimate interests in operating a secure service). Technical records are assessed for how long they are needed for the incident or security purpose; a universal automatic log-expiry period has not been verified.
- Optional measurement: approved event labels, page variant and rotating pseudonyms are processed only after consent (Art. 6(1)(a)). The local collector’s event window is 30 days and consent/preference window is 180 days. Withdrawal stops further optional collection.
- Privacy requests and legal duties: contact and verification details and the request/outcome record are processed to meet applicable obligations (Art. 6(1)(c)). Necessary legal-claims records may be retained under Art. 6(1)(f). The applicable duty or claim, rather than a blanket period for all records, determines retention.
Connector access and device permissions are optional. Turning on a connector grants technical access; it does not by itself establish a legal basis for every use of another person’s data. Do not provide health or other special-category data unless an applicable Art. 9 condition and appropriate safeguards have been established.
Service Providers & International Processing
Oracle Cloud supplies hosting infrastructure. Cloudflare delivers and protects websites and tunnels and can process network addresses, request metadata and traffic needed to provide those services. Resend is used for sign-in and service emails and receives the destination address and message content. Connected identity, communication and workspace services receive the data necessary for the feature you choose; AI and gateway recipients are described in the model section.
EU-hosted workspace storage does not prevent processing or support access outside the EEA by a provider or its subprocessors. The applicable contract must identify the recipient, locations and transfer mechanism, such as a relevant adequacy decision or Standard Contractual Clauses and necessary supplementary measures. We have not yet verified a complete agreement and transfer-safeguard record for every enabled route. This notice does not assert that all provider agreements are in place; contact us for the current route-specific information before sending sensitive content.
Provider notices and contract resources: Oracle Cloud, Cloudflare and Resend. A publicly available DPA is not evidence that it applies to our particular account or processing.
The dzimplei Chrome Extension
This section provides specific disclosures required for the dzimplei Chrome extension in accordance with Google's Chrome Web Store User Data Policy.
Single Purpose
The single purpose of the dzimplei extension is to enable the user's dzimplei desktop assistant or connected workspace to interact with their active browser session via a secure local bridge, and to provide access to the Jim assistant in a side panel.
What Data the Extension Handles
- Authentication Information: If you sign in to a remote dzimplei server or dzimplei.app from the extension's side panel, the extension stores a random device authentication token in Chrome's local storage (
chrome.storage.local). This token authenticates the browser instance to your authorized server; keep it private and revoke it when that connection is no longer wanted. - Tab Metadata (URLs and Titles): When connected, the extension enumerates open browser tabs (excluding internal
chrome://and Web Store URLs) to let the local dzimplei bridge route commands to the target tab. - Page Content & Screenshots: When an AI agent in your workspace is explicitly instructed to inspect or interact with a webpage (for example, reading text, finding buttons, clicking elements, or taking an accessibility snapshot), the extension reads the page DOM or captures a viewport screenshot and returns it to your local dzimplei instance.
- Synthetic Input: Clicks, keystrokes, and scroll actions requested by your agent are dispatched directly to the active tab via the Chrome DevTools Protocol.
Where Data Goes
The extension connects to the dzimplei instance you pair with. That instance may then use the content with its configured AI and tool services:
- With the dzimplei desktop app on the same computer, communication occurs over a loopback connection (
127.0.0.1) via WebSocket. The bridge connection stays on that computer; content returned to an agent can still be sent to its configured model or gateway. - If you sign in to dzimplei.app from the side panel (an emailed six-digit code), the extension connects your browser to that account on dzimplei's server over an encrypted WebSocket (WSS). From then on, the tab list and whatever the agents of that account ask the browser to read, click or capture is sent to dzimplei's server, which is operated by us. It is used only to carry out the task you gave the agent.
- If you add a different (self-hosted) dzimplei server in the panel, the same data goes to that server instead.
- The email address you type to sign in is sent to dzimplei.app to receive the code.
- The extension does not send browsing data to advertisers. Content returned to your agent may be sent onward by the configured server to its AI provider or gateway as part of your task, as explained below.
Permissions Justification
debugger: Required to relay Chrome DevTools Protocol (CDP) commands between your local dzimplei agent and Chrome tabs. This allows synthetic input (clicks, typing, scrolling) and tab screenshots without requiring an insecure remote debugging port.tabs: Required to list open tabs, detect active tab changes, open new tabs requested by your agent, and close tabs when completed.storage: Required to persist pairing tokens, configured server endpoints, and your browser instance label locally on your device.scripting: Required to inject lightweight accessibility inspection helpers into page frames to locate buttons and form controls by reference.sidePanel: Required to host the Jim chat interface and workspace switcher in Chrome's native side panel.declarativeNetRequestWithHostAccess: Required to removeX-Frame-Optionsrestrictions when embedding your authorized dzimplei workspace inside the extension's own side panel.http://*/*andhttps://*/*(Host Permissions): Required to allow the debugger and scripting APIs to inspect and automate pages on arbitrary websites you instruct your agent to navigate.
Data Retention & Deletion
The extension stores no persistent browsing history. Pairing tokens and configuration stored in chrome.storage.local can be deleted at any time by right-clicking the extension icon, selecting Remove from Chrome, or clearing extension data in chrome://settings/clearBrowserData. If you signed in to dzimplei.app from the extension, the key it was given stays valid on the server until you revoke it in dzimplei's Settings, where it is listed as "Chrome extension".
Desktop & Web Applications
The desktop app supports local workspaces and connections to hosted servers. Local files stay on your computer unless you sync, share, attach them to a task, connect a remote workspace, or ask an agent to use them with an external service. The hosted app stores account information, workspaces, chats, uploads and agent memory on our server infrastructure.
Account data includes your email address, display name, authentication records such as passkey public keys and device-key hashes, preferences and the content you or your agents save. Email codes, passkeys and available identity-provider sign-ins are supported. Provider sign-in can supply a verified email and profile information; it does not automatically connect your mailbox or grant every connector permission.
Shared workspaces and Teams make selected content available to the people you grant access to. A browser extension or connected computer can send tab information, screenshots and page content to the server and AI route used for your task. Review what a workspace, agent and connector can access before enabling it.
AI Models & Third-Party Providers
Agents send prompts, relevant conversation history, tool results, workspace excerpts and requested images or browser content to the model and gateway selected for the task. This may use your own provider connection or dzimplei-provided access. A fallback can use a different provider. Local model use differs from a hosted API or provider-login route. Voice audio or text you ask the app to transcribe or speak may be sent to the configured speech service or gateway; check that route before supplying sensitive content.
Available routes include services from OpenAI, Anthropic, Google, Microsoft/GitHub, OpenRouter, xAI, Moonshot/Kimi, Alibaba/Qwen and Cursor. OpenRouter can forward a request to another model provider. The selected model alone does not establish the legal recipient, processing region or retention settings. Connected-service content can become part of saved chat history.
Provider terms do not replace our obligations for the hosted service. Provider retention, training use and international processing depend on the particular product, connection and account terms; we do not promise zero retention, EU-only processing or no training across every route. Ask us about the route before sending confidential or special-category data. Consumer subscriptions and paid APIs must be assessed separately.
Provider information: OpenAI, Anthropic, Google, Microsoft and OpenRouter.
Google User Data (Gmail, Calendar, Drive)
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
This section applies when you connect a Google account to dzimplei (Settings › Plugins › Google), or sign in with Google. Connecting is optional; dzimplei works without it.
- What we ask Google for: your email address and sign-in identity (
openid email); read, search and send access to Gmail (gmail.modify); read and create events in Google Calendar (calendar); and access to the files dzimplei itself creates in your Google Drive (drive.file).drive.filecannot see any other file in your Drive. Google account sign-in uses identity scopes only. Connecting Google Workspace separately requests the mail, calendar and Drive permissions described here; the consent screen shows the permissions being requested. - What we do with it, and only on your behalf:
- Gmail: when you or your agents ask, dzimplei lists, searches and reads messages and sends a message from the account you name. Nothing is deleted or moved to the trash by dzimplei. If you switch on “When important mail arrives” or “When anything arrives that makes work” (Settings › Jim), dzimplei checks your unread mail about once a minute, skips promotions and forums, and reads the sender, subject, labels and a short snippet of up to 20 new messages to decide whether Jim should wake.
- Calendar: agents can list your calendars and events and add an event. An invitation is sent to other people only if the agent is asked to add attendees. When a to-do you create names a day, dzimplei adds an event for it to your primary calendar.
- Drive: when you choose “Open in Google Slides, Docs or Sheets”, dzimplei uploads that one presentation, document or spreadsheet to your Drive and opens it.
- Where Google data goes:
- The AI model you use. When an agent reads your mail or calendar to do what you asked, the content it reads becomes part of that conversation and is sent to the AI model provider configured for that chat (see “AI Models & Third-Party Providers”). That is the feature you asked for, and it is the only reason it is sent.
- The triage model. If you switch on “When anything arrives that makes work”, the sender, subject and a snippet of about 700 characters of each new message are sent to a free third-party language model (served through OpenRouter) that decides whether the message needs action. This is off unless you switch it on, and you can switch it off at any time.
- We do not send Google user data anywhere else, and we do not give it to advertisers, data brokers or resellers.
- What we store: to stay connected, dzimplei keeps your Google email address and the access and refresh tokens Google issues, in a file readable only by the dzimplei service (on the desktop app, on your computer; on dzimplei.app, on our server in the EU). Message and event content is not copied into a database of ours; it exists only in the conversations, notes and to-dos you and your agents create from it, stored as described under “Desktop & Web Applications”. Items detected by the triage switch are held in memory only.
- The sign-in broker: installs without their own Google app connect through dzimplei.app. Our server exchanges Google’s one-time code and passes the tokens once to the app that started the sign-in; they wait in memory for at most ten minutes and are not kept. To refresh access later, the app sends only its refresh token to our server, which adds its client secret and asks Google for a new access token; we do not keep it.
- What we never do with it: we do not sell it; we do not use it for advertising, retargeting or interest-based ads; we do not use it to judge credit-worthiness; and we do not use it to develop, improve or train generalised AI or machine-learning models. We use it only to provide the features you asked for that are visible in dzimplei.
- Who can read it: no one at dzimplei reads your Google data, unless you ask us to look at a specific item, it is necessary to investigate abuse or a security problem, it is required by law, or the data is aggregated and anonymous.
- Revoking access: disconnect Google in Settings › Plugins › Google, which deletes the stored tokens and asks Google to revoke them. You can also remove dzimplei at any time at myaccount.google.com/permissions.
- Deleting it: account removal disables the login and can retain workspace and profile content in a recovery archive; it is not a complete erasure request. See Delete Your Account. Disconnect Google first if you also want Google to revoke the access, or remove it at the link above. To delete conversations or notes that contain Google content, delete them in the app or write to [email protected].
Website & Optional Measurement
The public site serves its animation code, fonts and company marks from this site. It does not need a third-party animation CDN. Cloudflare still handles delivery and connection/security information as described below.
Optional measurement is currently disabled on the marketing website. Its Privacy settings control clears saved browser choices without requiring sign-in. On an installation with a configured collector, optional onboarding measurement and page-experiment events are off unless you opt in to the relevant purpose through Privacy settings and the consent service acknowledges the choice. The landing page may show different layouts without measuring you. Without experiment consent it sends no experiment beacon and adds no experiment attribution to links. Forced preview links are not measured.
The consent helper does not load a PostHog SDK. Optional collection, where enabled, uses a first-party collector with rotating pseudonyms; pseudonymous records are personal data, not automatically anonymous. PostHog forwarding is not implemented by this collector. The marketing site can refuse an opt-in when its collector is unavailable; that keeps optional tracking off.
Ignoring or refusing optional measurement does not restrict sign-in or product use. Use the same Privacy settings control to reject or withdraw all, without a floating overlay button. The preference is kept in browser storage for up to 180 days; acknowledged consent can also use a first-party receipt cookie. Optional event records in the collector expire after 30 days. An offline withdrawal stops local tracking immediately and reports any pending server operation; contact us if it remains pending. Clearing browser storage alone does not establish deletion of server records.
Authentication and device keys, account/workspace preferences and security controls are separate from optional analytics. Necessary connection information is processed to deliver requests and prevent abuse. Invitation and reset tokens are removed from the address bar by the consent helper; avoid sharing sign-in URLs.
Read the analytics impact-assessment working draft. It records unresolved review items and is not a certification.
Phone Numbers & Text-Message Codes
Where text-message sign-in is switched on, you can sign in to dzimplei.app with a phone number instead of (or as well as) an email address. It is optional; email and passkeys work without it.
- What we send: your number and a six-digit code go to our text-message provider, which delivers the message. The provider is named here once the service is switched on, and processes the number only to send and check that code.
- What we keep: after you sign in or add a number, dzimplei stores a keyed hash of the number (so the next sign-in can find your account) and its last four digits (so you can tell your numbers apart in Settings). The number itself is not stored on our servers. While a code is outstanding, the number is held in memory for at most ten minutes.
- What we do not do: we do not use the number for marketing, and we do not sell or share it. A number can belong to one account only.
- Removing it: you can remove a number in Settings at any time; the hash and the last four digits are deleted with it, or with your account.
- Limits: codes are sent only to numbers in countries we have enabled, and the number of texts per number, per device and per day is limited to prevent abuse. Your carrier may charge for receiving a message.
Former Waitlist
The public waitlist has been retired; new visitors use sign-in. Existing waitlist records may contain a contact address or number, joining/acceptance times and a referral code. Older versions also collected device and referral context. The current collector no longer adds that context.
Historical list data is not repurposed as product analytics. The original purpose was to notify you about access, based on your consent. You can withdraw or ask for deletion at [email protected]. Existing historical copies and their final cleanup must be included when handling that request; retirement of the screen is not proof they were erased.
The Android App
The dzimplei app for Android opens dzimplei.app, the same web app you can use in a browser, in full screen. It is a Trusted Web Activity: the app itself contains no tracking code and collects nothing of its own. Everything this policy says about the web application applies to it.
- Internet (
INTERNET): required, because your workspaces and chats are loaded from the dzimplei server. - Notifications (
POST_NOTIFICATIONS): only if you turn them on. We use them to tell you that an agent has finished or that Jim has an answer. You can switch them off at any time in Android's app settings. - Microphone: only if you choose a voice input and allow it in the permission prompt. The microphone is used while the app is open and in front, never in the background, and it is not used to listen for a wake word on Android.
- Location: the app does not request or collect your location.
- Contacts, camera and files: the app does not request access to your contacts or camera. If you attach a file, Android's own file picker hands us only the file you picked.
- No advertising, no selling: there is no advertising identifier, no ad network and no sale or sharing of your data for marketing.
You can delete your account and its data as described in Delete Your Account, without installing the app.
Delete Your Account
To request erasure, email [email protected] from your account address with the subject “Delete my dzimplei account”. State which hosted server or connected installation you used. We may ask for proportionate information to verify the request.
Removing an account in Settings is not the same as complete erasure. The application can disable the login and set aside owned workspaces and profiles in a recovery archive. A full request must also address that archive, account-level memory and notes, uploaded files, connector credentials, relevant processor copies and backups. We do not describe a disabled login or archived workspace as permanently erased.
We respond without undue delay and normally within one month. Where GDPR permits an extension because a request is complex or numerous, we explain the reason within that month. Erasure is subject to applicable exceptions, such as records necessary for a legal obligation or legal claims; we explain any retained categories and basis.
A fixed 30-day expiry and encryption of every backup have not yet been verified. We therefore do not promise that all copies disappear automatically within 30 days. Ask us to confirm the scope and outcome of your request, including recovery archives and provider copies. Deleting the Android app, clearing a browser or disconnecting a provider does not by itself delete your hosted account.
Data Security & Storage
Public endpoints use HTTPS/WSS. Account separation, authenticated requests and restricted filesystem permissions protect access. Local browser bridges bind to loopback where supported. Application-level encryption exists for some credential and analytics stores; that is not a claim that every workspace, log or backup has separate application encryption.
Cloud infrastructure encryption, backup coverage, expiry and restore handling require operational verification. We do not claim healthcare certification or a guarantee against every security risk. Please report a suspected security or privacy problem to [email protected].
Your Data Protection Rights
Where GDPR applies, you can request access, correction, erasure, restriction of processing and, where applicable, a portable copy of your data. You can object to processing based on legitimate interests and withdraw consent at any time without affecting processing that was lawful before withdrawal. Exporting one workspace is not necessarily a complete copy of all personal data held about you.
Contact [email protected] to exercise these rights. Optional measurement choices can also be changed through Privacy settings. We may verify your identity proportionately before releasing data.
You may complain to the Irish Data Protection Commission or another competent supervisory authority, including where you live or work. Optional analytics is not used to make decisions producing legal or similarly significant effects about you. AI output and automated agent actions should be reviewed in light of the permissions and task you supplied.
Controller & Contact
Dzimplei Limited
Trinity Hall, Dartry Road
Dublin 6, Ireland
[email protected]
This notice covers dzimplei-operated websites and hosted services. When you choose an independently operated server, that operator is responsible for its processing. An organisation using dzimplei for other people’s data must also establish its own lawful basis and any required processing agreement.
Next
Personalized landing demo
When you ask Jim to show your day, your description and optional follow-up are sent to our AI service to generate an illustrative demo. Please leave out private details and passwords. No social accounts are connected, and no messages or tasks are actually executed.
Your answers are not added to an account, retained as chat history, or included in analytics. The model provider processes the request to generate a response. We keep temporary request counts by network address to limit abuse. The demo uses sample stats, accounts and activity.