Jix · Privacy Policy
Privacy Policy for Jix
Summary
Jix is a native macOS app that listens to your meeting, reads your own documents and answers questions from them. This addendum says exactly what stays on your Mac and what leaves it.
- DevX Group LLC runs no server that receives your call audio, transcripts, screen captures or documents. Jix still makes the network requests listed in section 4, such as the license check through our license server and the update check with our update server.
- Your microphone and the meeting audio are transcribed on your Mac. Jix does not write call audio to disk and never uploads it.
- Screen text is read on your Mac.
- Your document library is indexed on your Mac.
- Answers are different. Unless you use a local model, Jix sends your question and the context it needs (recent transcript lines, which can include other people’s words, library passages and any screenshot) to the AI provider you chose. That provider handles it under its own terms and your account settings. DevX Group LLC does not receive it. If the provider you picked is busy and “Switch to a backup” is on in Settings (it starts on), Jix can send the same question to another provider you connected, under that provider’s terms. If you picked a local model, the question never goes to the cloud.
- A few other requests leave the Mac, such as the license check, the update check and model downloads. Section 4 lists every one.
- The Jix app contains no analytics, telemetry, crash reporting or advertising code.
- The Jix website and checkout are different: section 8 lists what they record.
What Jix processes on your Mac
Jix needs the following data to do its job. None of it leaves your Mac on its own.
| Data | Purpose | Storage |
|---|---|---|
| Microphone audio | Transcribing your own speech during a meeting | Held in memory only while it is transcribed (at most about the last minute, which Jix uses to correct the line just spoken). Never written to disk |
| Meeting audio from the system | Transcribing the other side of the call | Held in memory only while it is transcribed (at most about the last minute, which Jix uses to correct the line just spoken). Never written to disk |
| Transcript text | Finding the question and showing you what was said | In memory during the session. Saved to disk only if you turn saved history on, except for the short-lived restart copy below, which Jix can write even when history is off |
| Screen frames and the text read from them | Answering a question shown on the screen, when you ask | Transient files, removed when the request finishes, fails or is cancelled |
| Documents you import | Answering from your own material | Extracted text in a local SQLite index at ~/Library/Application Support/Jix/Library, file permissions 0600 |
| Saved sessions | Reading a past meeting back | Text only, at ~/Library/Application Support/Jix/Sessions, and only when history is on |
| Restart copy of the current session | Picking the session back up when Jix restarts itself after an answer gets stuck | Text only, never audio, at ~/Library/Application Support/Jix/Recovery, readable only by you. Written whether or not history is on, deleted the next time Jix starts, and never added to history. A one-time key that signs it is kept in the Keychain and deleted at the same time |
| Recording notice record | Showing that you confirmed, in Settings, that you let people know when Jix is listening and get their OK where required | The time you ticked the Recording notice box and the Jix version, in macOS user defaults on this Mac. Unticking the box deletes it. Never sent to DevX Group LLC or anyone else |
| Keychain items | Your license, your Gemini key if you add one, and your Free plan listening total | The macOS Keychain on this Mac |
| App preferences | Restoring your settings between launches | macOS user defaults |
Permissions Jix requests
You can revoke any permission at any time in System Settings, under Privacy & Security. macOS permission prompts and recording indicators are left intact.
| Permission | Why |
|---|---|
| Microphone | Required to transcribe your own voice. |
| Screen & System Audio Recording | Required to hear the other side of the call, and to read the screen when you ask a question about it. |
| Speech Recognition | Required when Apple's on-device recogniser is in use, which covers languages other than English. |
| User-selected file read | Required to import the documents and folders you pick for your library. |
| Network (client) | Used for the answer model you chose, web search when you turn it on, the license check, the update check, model downloads, and websites you import. Section 4 lists each one. |
What leaves your Mac
This is every request Jix makes. None of them carries your audio, and none of them goes to DevX Group LLC except the update check.
- Your Gemini keyJix keeps it in the macOS Keychain on this Mac only and sends it only to Google.
| What leaves | When | To whom, under whose terms |
|---|---|---|
| Your question, recent transcript lines (which can include what other people on the call said), the library passages it needs, and any screenshot you attach or that a screen question needs | Only when Jix answers | The provider you chose. OpenAI, for ChatGPT through the Codex sign-in on your own account, under OpenAI’s privacy policy and your account’s data settings. Anthropic, for Claude through Claude Code on your own account, under Anthropic’s privacy policy. Google, for Gemini with your own API key, under the Gemini API terms; on Google’s free tier, Google may use prompts to improve its products, except in the EEA, the UK and Switzerland. Nobody, with a local Ollama model: Jix talks to Ollama only at 127.0.0.1 on this Mac and refuses Ollama cloud models, so the answer request stays on your Mac. The license check, update check, model downloads and website imports below still use the network. If the provider you picked is busy and “Switch to a backup” is on in Settings (it starts on), Jix can send the same question to another provider you connected, under that provider’s terms. If you picked a local model, the question never goes to the cloud. |
| A web search query | Only when “Search the web as a last resort” is on and neither your library nor the model knows the answer (Claude and Gemini) | The same provider, which sends it to its search engine, under that provider’s terms |
| Your license key, the label “Jix Mac”, the activation id for this Mac, and a one-way hash of this Mac’s hardware id (never the id itself) | When you activate or deactivate, when Jix opens, and about once an hour while it is open | Our license server, jix.devxgroup.io, hosted on Vercel. It checks the key with Lemon Squeezy, our merchant of record, under its privacy policy, and sends back a signed record that only unlocks Jix on this Mac. Lemon Squeezy keeps the label with the first 16 characters of the hash added, so the activation stays tied to this Mac. A Mac first activated by an older Jix also gets 12 characters of a one-way hash of its old activation id added, so a lost answer can be recovered. Our server stores none of it and does not log the key, the hash or the activation id. To stop abuse it counts requests per hour by a one-way hash of your IP address that changes every day. The count is kept in server memory only and cleared by the first request after its hour ends, or sooner if the server restarts. This policy applies |
| The app version, in a request for the update feed | When Jix checks for updates | Our update server, jix.devxgroup.io, hosted on Vercel, which sees your IP address like any web server. This policy applies |
| Requests for model files, with no audio and no text | The first time you turn on English speech, a word list or a local model | Hugging Face (speech models), the Ollama registry (local models you choose) and Apple (macOS language assets), under their terms |
| Requests for the pages of a website you add to your library | When you import or refresh it | That website, under its terms |
Jix never reads your ChatGPT login. It runs the Codex CLI against its own configuration directory under ~/Library/Application Support/Jix/Codex, which contains a symbolic link to the credential file macOS already holds. Jix creates that link and never opens it, so your own Codex configuration, servers and memories are never part of a Jix request.
What we do not do
- We do not run a Jix backend that receives your content.
- The app sends us no behavioural data. Our update server sees your IP address like any web server and uses it only to answer the request.
- Jix does not write call audio to disk. It is held in memory only while it is transcribed, then discarded.
- We do not sell, share or monetise your data.
- We do not use your meetings or your documents to train any model.
- We do not ship analytics, telemetry or crash-reporting code.
History, export and deletion
Saved history is off until you turn it on. When it is on, Jix stores the text of a session, never the audio and never the screenshots.
You can export a session as Markdown and you can delete any session from the History window. Turning history off stops new sessions being saved; it does not delete the ones already there, and it does not turn off the restart copy in section 2.
To remove what Jix keeps on this Mac, quit Jix, drag it to the Trash, and then:
- Library, sessions, restart copy and speech modelsdelete
~/Library/Application Support/Jix - Preferences and the recording notice recordrun
defaults delete io.devxgroup.jixin Terminal - Keychain itemsopen Keychain Access, search for “jix” and delete the items Jix created.
This does not remove sessions you exported, copies in Time Machine or other backups, your license activation and purchase records (ask us, section 13), or anything Jix already sent to an AI provider, which that provider’s own account controls handle.
Removing a document from your library removes its stored text. A session you saved earlier can still contain passages quoted from it, so delete the session too if you want the text gone.
Sharing your screen
Jix is a menu-bar app, so it does not appear in the Dock or the app switcher.
Jix can appear in a full-screen share or a recording. To keep it out of what others see, share a single window instead of the whole screen. We make no claim that Jix is hidden from any screen-sharing or recording app.
We make no claim about software auditing the machine itself. Jix runs under its own name and any tool that lists running applications can see it.
This website
Everything above is about the app. The Jix pages on jix.devxgroup.io and devxgroup.io, the installer download and the checkout record a little more, so we can see which pages help people and who bought.
- Until you choose Allow analytics, and after you choose Reject analytics, Google Analytics and Vercel Web Analytics do not run and our own page-visit records store no id in your browser, so your pages and visits are not linked together. To object to the remaining unlinked page counts, email support@devxgroup.io.
- We treat a Global Privacy Control signal as Reject analytics. Our own page-visit records then store no id, even if you chose Allow analytics before.
- When you click a Buy or download link, the link carries your visitor id (without Allow analytics, the id of that page only), so a purchase or download can be linked to that visit.
- Visitor ids and hashed network identifiers can still be personal data, and a visitor id attached to a purchase links that visit to the buyer. We treat them as personal data.
- We use your purchase email for your license and receipts. We do not send marketing to it unless you opt in.
- Service providers and other recipients: Vercel (hosting and aggregate visit counts), Supabase (databases) and Google Analytics (only with your consent) process data for us under their data processing terms. Lemon Squeezy runs checkout and license keys and is an independent controller for its own reseller, payment, tax, fraud-prevention and legal-compliance activities. To see or delete what we hold about you, write to support@devxgroup.io.
| What | What we record | Where it is kept |
|---|---|---|
| Page visits | Pages viewed, how far you scrolled, which buttons you clicked, the site that sent you and any campaign tag in the link, with a random visitor id and session id. Only after you choose Allow analytics are they kept in your browser’s storage (not a cookie); otherwise both are new on every page and never stored. No name and no email. Our server uses a one-way hash of your IP address that changes every day to limit abuse, never the address itself. Page visits are still counted without a stored id; see the notes below the table. | Our own analytics database (Supabase), up to 13 months |
| Visit and sales counts | Page views and four funnel steps: pricing seen, plan clicked, installer link clicked, and a completed or refunded purchase with only the plan name. The site steps also carry the campaign tag from the link you followed, if it had a short one; anything that looks like an email is dropped. No cookie, no name, no email, no order id. Vercel’s visitor hash changes every day, so it cannot follow you across days or sites. Counted until you choose Reject analytics, and skipped after that or whenever your browser sends Global Privacy Control. | Vercel Web Analytics, as aggregate counts |
| Installer downloads | Time, your country, browser family, the site that sent you, and a one-way hash of your IP address that changes every day. Never the address itself. | Our own analytics database (Supabase), up to 13 months |
| Purchases | Order id and number, your email and name, the plan, amount and currency, refund status, a one-way hash of your license key (never the key), and the visitor id from your visit if the checkout link carried one. When you tick the box asking for your license right away, the checkout link carries that choice and its time to Lemon Squeezy, and your license email confirms it. | Our own database (Supabase), 7 years for tax records. Lemon Squeezy, our merchant of record, holds the payment itself; we never see card details. |
| Google Analytics | Only if you choose Allow analytics in the cookie bar. Nothing loads from Google before that. | Google, under its own terms |
Who is responsible for your calls
The person or organization that decides how Jix is used is responsible for the call content. When you use Jix for your own work, that is you. When you use it for an employer or another organization, it is often that organization. The call content Jix handles (the audio, the transcript and what the other people say) stays on your Mac, except what Jix sends to the AI provider you chose (or a backup provider you connected, see section 1), which handles it under its agreement with you or your organization. DevX Group LLC supplies the software and does not receive that content.
Telling the people on your call and getting any permission you need is your responsibility, as section 9 of the License & Terms explains. Your acceptance of the Terms and of this policy does not give consent on behalf of anyone else on the call. Where data protection law applies to your use, the person or organization responsible for the call content needs a lawful basis for it, must give the people on the call the information the law requires (who is responsible, why, which AI provider, how long it is kept and their rights), and handles their requests. A link to this policy does not replace that notice.
The GDPR and the UK GDPR leave out purely personal or household activity, and that exception is narrow. Customer, sales, consulting, support, work and school calls are not purely personal, so data protection law applies when you use Jix on them.
Who we are
DevX Group LLC, San Diego, California, USA, support@devxgroup.io. We are the controller of account, purchase and billing data, your support emails, the license checks and the update check in section 4 and the website data in section 8. The Jix app sends us no diagnostics. Lemon Squeezy, our reseller and merchant of record, is an independent controller for its own payment, tax, fraud-prevention and legal-compliance activities.
Why we process data, and on what legal basis
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Delivering and checking your license, receipts, renewal notices and support | Purchase data, license key hash, your emails to us, and the license check in section 4 (key, activation id and hashed hardware id, passed to Lemon Squeezy and not kept) | Contract |
| Tax and accounting records | Purchase data | Legal obligation where EU or UK law requires the record; otherwise our legitimate interest in keeping the accounting records US law requires |
| Counting visits and the purchase funnel without cookies | Page visits, visit and sales counts, installer downloads and purchase attribution (section 8) | Legitimate interest in knowing which pages help people. You can object at any time by emailing support@devxgroup.io, and Reject analytics or Global Privacy Control stops the Vercel counts |
| Google Analytics | As described by Google | Your consent, which you can withdraw |
| Security and abuse prevention | Hosting and request logs | Legitimate interest |
How long we keep it
- Visit dataUp to 13 months.
- Purchase records7 years, for tax records.
- Support emailAs long as we need to answer you and keep a record of the conversation.
- Hosting logsKept by Vercel for a short period under its own retention settings.
Your rights
You can ask to see, correct, delete or export the data we hold about you, to restrict or object to its processing, or to withdraw a consent you gave, by emailing support@devxgroup.io. We respond without undue delay and within the time the law that applies to you sets. For GDPR and UK GDPR requests that is one month from receipt; where the law allows an extension, we tell you within that month and say why. If we decline a request, we explain why and how you can appeal or complain. If you are in the EU or the UK you may also complain to your data protection authority. California residents can use the same address for any request under California law.
If you were on a call where someone used Jix, contact that person or their organization about the transcript or anything they sent to their AI provider. DevX Group LLC cannot see, access or delete a Jix user’s local transcripts, library or saved sessions.
International transfers
We and our providers (Vercel, Supabase, Lemon Squeezy, Google) are in the United States or process data there. Where the law requires it, transfers rely on an adequacy decision, such as the EU-US Data Privacy Framework where a provider is certified under it, or on the provider’s standard contractual clauses. You can ask us about the safeguards for our transfers at support@devxgroup.io. If you choose a cloud AI provider, Jix sends call content to that provider under your own arrangement with it, which may involve its own transfers.
Do Not Track and Global Privacy Control
Our site treats Global Privacy Control as Reject analytics, as described in section 8. It does not change what it does in response to the older browser Do Not Track signal, because there is no common standard for it; you can choose Reject analytics in the cookie bar instead.
Age
Jix is for people 18 and older and is not directed to children, including children under 13. If we learn that we have collected personal data from a child under 13, or from anyone younger than 18, we stop that collection and delete the data. Concerns: support@devxgroup.io.
Changes to this policy
If we make a material change, we will update the "Last updated" date at the top of this page, note it in the app’s release notes, and email buyers when it affects them.
Contact
Questions about this policy or about your data: support@devxgroup.io. DevX Group LLC, San Diego, California, USA.