Privacy Policy
This policy explains what personal data we process when you use SHIPIT by Dzhura ("SHIPIT"), our macOS app, together with the Dzhura account you may sign in with. It is short because SHIPIT sends very little to us. "Very little" is not the same as "nothing", so this policy lists every item that does reach us. It is information for you, not a contract you agree to; the contract is in our Terms of Use.
01Summary
- Your work stays on your Mac. SHIPIT does not upload your files, prompts, agent conversations, terminal output or code to us. The one exception: if you turn on crash and error reports, or send a problem report, a filtered error message can occasionally contain a short fragment of text from your work (see 3.2).
- We do receive a small amount of data:
- update checks: your IP address and the SHIPIT version (you can turn automatic checks off);
- crash and error reports, only if you turn them on;
- problem reports, only when you send one;
- your email address and plan, only if you sign in to a Dzhura account;
- payment records, only if you pay for a subscription.
- Your agents are yours. The AI agents and command-line tools you run in SHIPIT (Claude Code, Codex, Gemini and others) connect to their providers under your own accounts. That traffic does not pass through us, and the providers' own policies apply to it.
- No analytics, no advertising, no tracking SDKs. We do not sell or share your personal information.
02Who we are
The controller of the data described here is Maksym Zhuk, an individual trading as Dzhura ("we", "us").
Address: Shypit Waterfall, Pylypets, Zakarpattia Oblast, 90011, Ukraine
Privacy contact: [email protected]
03What we collect, why, and on what legal basis
3.1Update checks (automatic, can be turned off)
SHIPIT checks for updates with the Sparkle framework about once an hour, and again when you choose Check for Updates…. Each check downloads our update feed from homin.app; installing an update also downloads the new version from there.
- What reaches us: your IP address, the time, the requested file, and the app name and version (sent in the User-Agent header). SHIPIT does not send a system profile, an account identifier or an install ID with update checks.
- Why: to deliver security fixes and new versions, and to protect the server from abuse.
- Legal basis: our legitimate interest in keeping the software secure and up to date (GDPR Art. 6(1)(f)).
- Retention: web-server access logs are rotated daily and kept for 14 days.
- Turning it off: automatic checks are on by default. Turn off Check for updates automatically in Settings. If you do, you will not receive security updates automatically.
3.2Crash and error reports (off unless you turn them on)
SHIPIT asks once whether to send crash and error reports. They are off until you turn them on, in setup or in Settings › Behavior, and you can turn them off there at any time. Only errors recorded after you turn reports on are sent; errors from before stay on your Mac.
When reports are on, SHIPIT sends:
- the error or crash type, a filtered error message and a stack trace;
- the SHIPIT version and build, your macOS version and your Mac's model identifier (for example
Mac15,3); - a random install ID. It is generated on your Mac, is not linked to your account, and lets us count how many installations a problem affects.
Before sending, SHIPIT removes fenced code blocks, quoted text of 60 characters or more, API keys and tokens it recognises, email addresses, your user name in /Users/<name> paths, file paths under your home folder, /Volumes, /private, /tmp and /var, and long hex or encoded strings. It also shortens long fields. This filter is automatic and can miss things, which is one reason reports are off by default.
- Why: to find and fix bugs.
- Legal basis: your consent (Art. 6(1)(a)). You can withdraw it at any time; withdrawal does not affect reports already sent.
- Retention:
- Individual reports are deleted automatically after 90 days.
- We keep a summary per problem: the error signature, a filtered message, counts, the first and last time it was seen, the builds affected, and the install IDs that reported it. There is no fixed time limit for these summaries. We delete them when we no longer need them, and when you ask (see section 7).
- For rate-limiting, we keep a truncated hash of your IP address combined with the date, for 3 days. The raw IP address is not stored.
- Team alerts: when a new problem appears, or an old one comes back, a short summary is sent to our team's Telegram chat: the error message or signature, the build, the SHIPIT and macOS versions and the Mac model. It contains no install ID, no account data and no problem-report text.
3.3Problem reports (only when you send one)
Help › Report a Problem… shows you what it will send before you send it. It sends the text you type (filtered as in 3.2, up to 2,000 characters). If you leave Attach recent errors ticked, it also sends your most recent filtered errors. It sends the same version, macOS version, Mac model and install ID as a crash report. A problem report is sent even if automatic crash reports are off, because you asked for it to be sent.
- Legal basis: your consent, and our legitimate interest in answering support requests (Art. 6(1)(a) and (f)).
- Retention: as for crash reports (3.2). The text you type is not sent to Telegram.
- Please do not paste secrets or other people's personal data into the report.
3.4Dzhura account (only if you sign in)
You do not need an account to use SHIPIT. If you sign in to a Dzhura account, SHIPIT sends your email address and password to sign in, then uses session tokens to show your profile and plan. When you sign out, SHIPIT tells our server to end the session.
Our account server holds the following data about you:
- your email address;
- a password hash (we never store your password itself);
- your plan and its expiry date;
- session records, which store a hash of each session token, its expiry, and which app created it;
- referral and promo-code records, if you use them;
- if you signed up on dzhura.app with Google or Apple, the provider's account identifier and the email it reported;
- a record of each download you make while signed in: the file, the time, your country, your browser's User-Agent, and a salted hash of your IP address (not the raw IP).
Our server also logs requests and errors so that we can fix problems. These logs mask passwords, tokens and authorisation headers, but can contain your IP address or account identifier. We keep them only as long as we need them to fix problems.
- Why: to provide the account, check which plan you have, keep the account secure, and handle downloads.
- Legal basis: performance of our contract with you (Art. 6(1)(b)), and our legitimate interest in security and fraud prevention (Art. 6(1)(f)).
- Retention: for as long as the account exists. See section 7 for deletion.
We send account emails such as email verification and password reset. We may also occasionally send product announcements to account holders (legal basis: Art. 6(1)(f), or your consent where the law requires it). To stop announcements, write to [email protected].
3.5Payments (only if you pay)
- The Dzhura subscription is paid in crypto (USDT on TRON). We issue an invoice with a unique amount. We confirm payment by reading the public TRON blockchain through TronGrid and then store:
- the invoice: plan, amount, status and dates;
- the transaction ID.
A blockchain transaction is public by design and shows the sending wallet address. We cannot change or delete anything on the blockchain.
- Card payments: the Dzhura subscription cannot currently be paid by card. If you pay for a separate Homin plan by card, Stripe handles that payment on its own hosted page; we store only your Stripe customer and subscription identifiers and the subscription status. If we later offer card payments for the Dzhura subscription, Stripe will handle them in the same way and we will update this policy.
- Legal basis: performance of the contract (Art. 6(1)(b)) and our legal obligation to keep accounting records (Art. 6(1)(c)).
- Retention: payment and invoice records are kept as bookkeeping records for as long as tax and accounting law requires, even after you delete your account; at that point they are no longer linked to your email.
3.6Public revenue page
Our revenue page (dzhura.app/revenue) shows totals only. It does not list individual payments, names, emails, wallet addresses or transaction hashes.
3.7Waitlists on dzhura.app
If you join a waitlist on dzhura.app, we store your email address, the page you signed up from and your language, and send a notice of the sign-up to our team's Telegram chat. Legal basis: your consent, given when you sign up (Art. 6(1)(a)). Retention: until we contact you about it or you ask us to remove you. Daily download counts from dzhura.app go to the same chat; they contain no personal data.
04What we do not collect
SHIPIT does not send us:
- your files or the contents of the folders you open;
- your prompts, your agents' answers, conversation transcripts, or terminal input and output (except a filtered fragment in a report, as described in 3.2 and 3.3);
- your code, repositories or git history;
- your API keys, or the credentials of your agent accounts (Anthropic, OpenAI, GitHub and others);
- your contacts, calendars, reminders, messages, location, microphone, camera or screen (agents you allow can read some of these; see section 5);
- usage analytics, telemetry, advertising identifiers or tracking cookies.
SHIPIT contains no third-party analytics, advertising or tracking SDKs.
05Your agents and third-party services
SHIPIT is a workspace for AI agents and developer tools that run on your Mac under your own accounts. When you use them, data goes directly from your Mac to the service you chose, under that service's terms and privacy policy. We and our servers are not a party to it. This includes:
- Agent command-line tools such as Claude Code (Anthropic), Codex (OpenAI), Gemini (Google), Grok (xAI), OpenCode, Cursor, Aider and others. These send your prompts and the files they read to their providers.
- Account allowance display. To show how much of your plan's allowance is left, SHIPIT itself uses your locally stored Anthropic or OpenAI sign-in to ask that provider for your usage figures (and, for Anthropic, your profile). It does this at most once a minute, while a conversation or the Accounts settings are on screen. Only your existing sign-in token is sent, and only to the provider that issued it.
- Personal plugin (if you turn it on). Agents can read your contacts, calendars and reminders and, with your approval, send iMessages. What they read goes to the agent's provider.
- Developer services you connect, such as GitHub, Vercel, Supabase, Stripe, Shopify, Cloudflare and Linear. Integrations ("plugins") use keys you enter, which are stored in your macOS Keychain.
- Web research by agents.
- When an agent searches the web, SHIPIT loads public search pages (DuckDuckGo, Google or Bing) and the pages the agent opens, using a hidden built-in browser on your Mac.
- If you connect SerpApi, searches go to SerpApi under your own key.
- When an agent shows a result card with images, SHIPIT downloads those images from the public sites where they are hosted.
- Those sites receive your IP address, as with any browser.
- Tool installation. When you choose to install an agent CLI, Git, the GitHub CLI or Node.js, SHIPIT downloads the installer from its official source, for example
claude.ai,github.com,api.github.comornodejs.org. - The built-in browser pane, which loads the sites you open in it.
Agents started by SHIPIT act on your behalf and may change files, run commands, push code and publish sites. What they send, and to whom, depends on how you instruct and configure them. See Agent Risk & Acceptable Use.
06Data stored only on your Mac
The following stays on your Mac and is not sent to us:
- App folders. SHIPIT keeps its data in
~/Library/Application Support/, in the foldersDzhura SHIPIT,Dzhura SHIPIT Accounts,SHIPITandSHIPIT Session Resume. This includes:- workspace, conversation and session state;
- the separate configuration folders of agent accounts you add;
- a local error journal of the last 500 filtered errors.
- Preferences. Your settings, the random install ID and a cached copy of your Dzhura profile (email and plan) are kept in SHIPIT's preferences.
- Your acceptance and access-mode record. The version of the Terms of Use you accepted, when you accepted it, the access mode you were using (Ask before acting or Full access), and later changes of mode. SHIPIT keeps it to show what was agreed and which mode you chose. We see it only if you send it to us.
- Keychain. Your Dzhura session token and any keys you enter for integrations are stored in the macOS Keychain.
- Local API. SHIPIT has an optional local API (off by default). When you enable it, it listens only on your Mac. You may separately allow it on your local network, in which case it is reachable only by devices you authorise with a token. Traffic stays between your own devices and does not pass through our servers.
You can delete this data by deleting the folders above, SHIPIT's preferences (app.dzhura.shipit.superapp) and the related Keychain items.
07Your rights
Depending on where you live, you have rights over your personal data. They include the rights to:
- access it and receive a copy (portability);
- have it corrected or deleted;
- restrict or object to its processing;
- withdraw consent at any time.
Account deletion: email [email protected] from the address on your account. We will delete your account within 30 days, and usually within 72 hours. When we delete your account, we remove your sessions, your profile, your sign-in links (Google or Apple) and your personal records. We keep only the payment records described in section 3.5, no longer linked to you.
Crash and problem reports are not linked to your account. To have the reports and summaries linked to your install ID deleted, email [email protected] with your install ID. You can find it in Terminal with defaults read app.dzhura.shipit.superapp shipit.reports.installID.
EU/EEA and UK: you may complain to your local data protection authority. We would appreciate the chance to resolve your concern first.
California: we are not currently required to comply with the CCPA, but we honour these rights for everyone.
- In the last 12 months we collected these categories of personal information, for the purposes and from the sources described above:
- identifiers: email, IP address, install ID;
- commercial information: plan and payments;
- internet activity: server logs;
- device information: macOS version and Mac model.
- Your account password is used only to sign you in.
- We do not sell or share personal information (including for cross-context behavioural advertising), and we have not done so.
- You have the right to know, delete and correct your information, and we will not discriminate against you for exercising these rights.
We answer requests within 30 days (45 for California requests). We may need to verify your identity first.
08Service providers
| Provider | Role | Data | Location |
|---|---|---|---|
| The Constant Company, LLC (Vultr) | Hosts our account server, database, update feed and downloads | Account and payment data, IP addresses in server logs | Server in Warsaw, Poland; company in the USA |
| Cloudflare, Inc. | Runs dzhura.app (which forwards account requests to our server) and the crash-report service (Workers and D1 database) | IP addresses in transit, account requests, crash and problem reports, waitlist sign-ups | Global network; company in the USA |
| Resend | Sends account emails | Email address, email content | USA |
| Telegram | Internal alerts to our team | Crash summaries as described in 3.2; waitlist sign-ups as described in 3.7 | Outside the EU |
| TronGrid (TRON network API) | Reads the public blockchain to confirm crypto payments | Our receiving wallet and public transaction data | Outside the EU |
| Stripe | Card payments for separate Homin plans only (Stripe acts as an independent controller for payment data) | Payment and card details, email | USA / Ireland |
If you choose to sign in on dzhura.app with Google or Apple, those companies process your sign-in as independent controllers.
09International transfers
Our account server is in the EU (Warsaw, Poland). Some providers listed in section 8 are based in the USA or operate globally, and we may access personal data from outside the EU/EEA and the UK to run the service. Where personal data is transferred outside the EU/EEA or the UK, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum), or on the provider's certification under the EU-U.S. Data Privacy Framework, as offered in each provider's data processing terms.
10Security
- All connections from SHIPIT to us use HTTPS.
- Updates are verified with an Ed25519 signature before they install.
- Passwords are stored only as hashes, and session tokens only as hashes on the server.
- Server logs mask authorisation headers, passwords and tokens.
- SHIPIT's network session for your account keeps no cookies or cache.
No system is perfectly secure. If a breach affects your personal data, we will notify you and the authorities as the law requires. To report a security problem, write to [email protected] with "Security" in the subject.
11Children
SHIPIT is intended for people aged 18 and over. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.
12Changes
We will publish any change on this page with a new version number and effective date, and keep earlier versions available on dzhura.app. If a change materially affects how we use data you have already given us, we will tell you in the app or by email before it takes effect.
13Contact
Maksym Zhuk (Dzhura)
Shypit Waterfall, Pylypets, Zakarpattia Oblast, 90011, Ukraine
Email: [email protected]