Privacy Policy

Local-first makes this page short.

Your conversations, your agents’ memory and your keys live in a folder on your own Mac, and we cannot see them. What follows is every place data does move, and what happens to it there.

Last updated October 28, 2026

What stays on your machine

  • Conversations and transcripts. Stored in ~/.bloks on your computer. Never sent to us.
  • API keys and secrets. Stored in a file only your user account can read, with file permissions to match. Never sent to us, and never echoed back to any interface once saved; even the settings screen only ever says whether a key exists.
  • Agent memory and working files. Plain files on your disk, readable, editable and deletable by you.
  • Voice. Calls are recognized on the device you speak into; replies are synthesized through the voice vendor you configured, with your key.
  • The app’s log and crash reports. The desktop app keeps a small log of its own about its window and processes, in its logs folder (on a Mac, ~/Library/Logs/bloks), and a crash leaves a report in your computer’s own crash folder. Neither is ever uploaded: there is no server to send them to. Copy diagnostics, in Settings, About and updates, puts a short report on your clipboard, with which keys are set but never the keys, for you to paste wherever you choose.

Deleting ~/.bloks removes everything Bloks knows. That is the design, not a limitation.

Between your computer and your own devices

A phone or a browser you pair talks to your own computer: on your network directly, or from anywhere through Bloks Cloud, where everything it carries is sealed end to end for the two of them, so we cannot read it. A few things travel this way that are worth naming.

  • Where you are, only if you turn it on. Location is off in the iPhone and Android apps until you switch it on there. Then the phone tells one workspace of your own, on your own computer, the city you are in, and the neighbourhood when the phone gives Bloks a precise fix; your coordinates only if you also choose Exact position. Your computer keeps the last reading and nothing before it: no history, and never in a backup. Pause keeps it from your agents and watchers, and turning it off on the phone, or Forget on the computer, drops it. It is never sent to people you invite into a workspace or a room, or to a workspace you joined, and through Bloks Cloud it is sealed, so we cannot read it.
  • Pictures of an agent’s screen. When you watch an agent work from your iPhone, your computer sends your own paired phone pictures of that agent’s browser, its cloud computer or Local VM, or your Mac’s screen while an agent is working on it. Through Bloks Cloud they are sealed like everything else, so we cannot see them. People you invite into a workspace or a room never receive them, and a picture of your Mac’s screen is never handed to an agent this way.
  • Your other workspaces. A phone paired with one of your workspaces can ask it which other workspaces of yours are on the same computer, by name and mark, and pair with one of them. Only your own paired devices can ask, never a member’s; only workspaces of your own are listed, never one you joined; the other workspace has to have phone access on already; each pairing made this way works once, lasts a few minutes and travels over the connection the phone already uses; and your computer tells you each time one is made.
  • Saying where Bloks is on your network. While phone access is on, Bloks on a Mac announces itself on your local network (Bonjour), so a paired phone can find it again when its address or port changes. The announcement holds your computer’s name, the port, and a random tag that tells your workspaces apart and says nothing else about them. Nothing private is in it: no conversations, keys or account details. Hearing it lets nobody in: a phone still needs its pairing or a code to do anything, and a paired phone only moves to a Bloks that proves it holds that pairing. Turning phone access off ends the announcement.

What reaches third parties, at your direction

  • AI providers. When an agent takes a turn on your own keys or sign-in, the message and relevant context go to the provider you configured, using your credentials, directly. Their privacy policies govern that data. We are not in that path and cannot read it.
  • Bloks AI, when you use it. An agent that runs on Bloks AI sends its requests through Bloks and our AI gateway to the model provider, so each request can be counted against your balance. Bloks keeps the counts, not the contents. The gateway is Vercel AI Gateway, and every request is held to zero data retention there and at the model provider, with no training on it. Bloks AI names each company and what it keeps.
  • Notifications on your phone. When your computer has something for your phone, such as an approval waiting or an answer ready, the relay asks Apple (on an iPhone) or Google’s Firebase Cloud Messaging (on Android) to wake the app. What they carry is your phone’s push token, a fixed line like “An agent is waiting for your approval.”, and a preview your computer sealed for that one phone, which we, Apple and Google cannot open. The relay keeps the token so it can reach the phone, and drops it when Apple or Google say it no longer works. Turning notifications off on the phone stops all of it.
  • Connected services. Apps you connect, whether through connector cards, your own MCP servers, or an API key you saved, are used by your agents under the access you granted, and those services’ policies apply.

What reaches us

  • A Teams enquiry, if you send one. One address and a timestamp, stored so we can tell you when Bloks Teams is ready, used for nothing else, never shared or sold. Email privacy@bloks.dev and it is deleted.
  • Ordinary server logs. This site is served by Cloudflare, which processes IP addresses and request metadata to deliver pages, as every host does. Two things on this site transmit anything you type: the Teams enquiry form, when you send one, and the checkout page at /cloud, which loads Stripe’s own script so that your card details travel straight to Stripe and never pass through us. Every other page here is a static file.
  • Visits to this site, through Google Analytics. Since October 27, 2026, the pages of bloks.dev count visits with Google Analytics 4: the pages you open, the page that sent you here, and your browser, device and approximate location, as Google reports them. It sets Google’s cookies (_ga and _ga_<id>) to tell a return visit from a first one, and Google, a US company, may process this in the United States. It never receives anything you type into a form, and it never runs on the pages that hold your keys (/app and /web). If your browser is set to a time zone in Europe or the UK, you are asked first and nothing of Google’s loads unless you allow it. Anywhere, the Analytics switch at the foot of a page, or this one: , turns it off in your browser and clears its cookies.
  • Visits to this site, by our own count. Beside Analytics, bloks.dev keeps a count of its own, on Cloudflare, which sets no cookie and keeps no IP address. Each page you open sends us its address, without anything after a ? or #, and the site that sent you, cut down to its name (google.com, never the page you were on there). To that we add what Cloudflare already knows about the request: your city, region and country as Cloudflare places them, and whether you are on a computer, a phone or a tablet, with its operating system and browser as a word each. To count people as well as pages, your IP address and browser are mixed with a secret of ours and the day’s date into a short code that cannot be turned back into either. You are the same visitor for one day and a new one the next, so we cannot follow you from one day to another or recognise you later. The IP address itself is never written down. Each record is deleted after 400 days. It never runs on /app or /web, and if your browser sends Global Privacy Control, it sends nothing at all.
  • Relay traffic, when you use it. Pairing your phone on your own network never touches us. If you use the relay to reach your Mac across the internet, the relay forwards traffic between your devices and keeps only the operational logs needed to run it. It exists to deliver bytes, not to read them.
  • Bloks Cloud billing, if you subscribe. Payments run through Stripe, who handle the card and hold the billing details; we never see a card number. What reaches us is the email you paid with, Stripe’s customer and subscription identifiers, whether the subscription is active and when the paid period ends, and the licence key issued against it. That is what the relay checks before it will carry anything for you, and it is deleted when the subscription ends and you ask.

What we do not do

  • No analytics and no tracking cookies in the builds we ship: the desktop app, the phone app and Bloks in a browser report nothing. The desktop app carries no analytics token; build it yourself with one and only the named counters in src/lib/analytics.ts are sent, never your content. The only analytics anywhere are the two visit counts on these web pages, described above: Google Analytics, which you can switch off, and our own, which Global Privacy Control stops.
  • No advertising, no data brokers, no sale of personal data, ever.
  • No account required to download or use the desktop app.
  • No telemetry in the desktop app that sends your content anywhere.

Retention

Data on your machine is yours and follows your own retention, which is to say: it stays until you delete it. A Teams enquiry stays until Bloks Teams is ready or you ask for deletion, whichever comes first. A Bloks Cloud licence and the details attached to it stay while the subscription runs, and are deleted on request once it has ended. Host and relay logs rotate on the short schedules typical of operations, measured in days and weeks, not years.

Security

The config file that holds keys is created with owner‑only permissions. The webhook receiver and the pairing system use long random tokens, compared in constant time, revocable individually. The harness answers only your own origin. Security reports go to security@bloks.dev and are read the same day.

Your rights

Depending on where you live, including under the GDPR and the CCPA, you may have the right to access, correct, delete, export or restrict the personal data we hold about you, and to complain to your local authority. Since the most we ever hold is an email address, and the billing details listed above if you subscribe to Cloud, exercising these rights is usually one message to privacy@bloks.dev, answered within thirty days. We do not discriminate against anyone for exercising them.

Children

Bloks is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us data, write to us and it will be removed.

Changes

If a future feature changes what reaches us, this page will say so before the feature ships, with an updated date at the top. A privacy policy that changes quietly is not one.

Meet your team.

Free for Mac, Windows and Linux. Bring the AI you already have.

View on GitHub