Privacy Policy · Last updated:
Pulsar works without an account. If you use Pulsar Cloud to work as a team, we store only what’s needed for your teammates to see you and send each other files. It’s all here: what we store, why, where, for how long and how to delete it.
In short
Your profile (name, handle, photo and email), your teams and what you send to your teammates, only until it’s delivered: it’s deleted 24 h after everyone has received it, or after 30 days. If you share live with your team and include the snapshot, that still image, only while you share; and who shared and who watched, without the content, for 90 days.
The contents of your terminals, your agents’ prompts, your Claude Code and Codex sessions and the paths of your files.
Whether to use Pulsar without an account, what you send and to whom, and deleting your account whenever you want.
Pulsar is a macOS app created and run by its developer, Oliver, as an independent project (“Pulsar”, “we”). This policy explains what personal data we process in Pulsar Cloud —the app’s optional account, team and file-sharing features— and on this website.
Without an account, Pulsar works the same and sends nothing of yours to our servers. The app includes no analytics or usage tracking.
Claude Code, Codex and the other agents you run in Pulsar are third-party services: what you write to them goes straight from your Mac to their providers, under their own privacy policies, and never passes through us.
We only process your data to provide Pulsar Cloud —the service you turn on by signing in— and to keep it secure. There are no secondary uses: no advertising, no commercial profiling and no training of artificial intelligence models.
| Data | Why | For how long |
|---|---|---|
| Your GitHub or Google account profile: name, handle (username), photo, email and your ID with that provider | To create your account, sign you in and show you to the members of your teams | For as long as you have an account |
| Teams: name, members, each member’s role and join date | To make teams and their permissions work | For as long as you’re a member or the team exists |
| Invitations: code, team, role, who created it and who used it | So someone can join a team with a link | They expire after 7 days |
| Shares: the messages, files, texts and prompts you send, with their title, message, recipients, which share they reply to (with a short quote), the name, type and size of each file, and when each recipient downloaded and read them | To deliver them to the people you chose | Up to 24 h after every recipient and every device they use with Pulsar Cloud has saved them, or 30 days at most; files included |
| Your signed-in devices: a random identifier for each installation (it doesn’t identify your Mac or iPhone), its type (Mac, iPhone…), its name, when it last connected and which shares each one has already saved | So what you receive and what you send reaches all your devices before it’s deleted from the cloud | While you have an account; if you remove a device, it’s deleted right away. What each one saved is deleted along with the share |
| Project context, only if you include it: remote repository (without credentials), branch, commit, whether there are unsaved changes and the workspace name | So whoever receives it knows which version of the code it refers to | The same as the share |
| A snapshot of what you share live with your team, only if you choose to include it: a still image of the page (a JPEG of 30 KB at most), without the address bar | To show it on the chat card to the people on your team you picked | Until another snapshot replaces it, you stop sharing, you delete the chat message or the message expires |
| Live sharing: what you share (the port number and its title), with whom (your team, the people you picked, anyone with the Pulsar link or anyone at all, with the public link), its status and times, the public live-sharing key of each device with its fingerprint, and who joined to watch, from which device and when | So that only the people you choose can see what you share, to apply your plan’s limits and to show you who watched | For as long as the live share lasts and then up to 90 days. The public key, for as long as you use that device with Pulsar Cloud and up to 90 days after you remove it |
| Live sharing log: who shared which port and with whom, who joined to watch, who was admitted or removed, pauses, resumes and extensions, each day’s traffic and the time of each event. Never what’s on screen, the paths, the page addresses or the address of a public link | Security, preventing abuse and letting whoever shares see who watched | 90 days |
Public link: that you opened one, which port and its title, when it was opened, paused and ended, and how many people were watching (a number your Mac works out, without knowing who). Never its trycloudflare.com address, who opened it or their IP | To apply your plan’s limits, to be able to turn it off in case of abuse, and security | For as long as it lasts and then up to 90 days |
| Technical data from the relay (Cloudflare) when you share live, watch what someone else shares or connect your iPhone to your Mac away from home: your IP address, the live share or pairing identifier, the role (sharing or watching), the slot, the bytes, the duration and the time | To deliver the encrypted connection, prevent abuse and troubleshoot | A few days, according to Cloudflare’s retention periods |
| Presence: whether you’re online right now | So your team knows whether you’re available | We keep no history: it disappears when you disconnect |
| Technical connection data: IP address, client type and date, in our provider’s logs | Security, preventing abuse and troubleshooting | A few days, according to the provider’s retention periods |
Your handle is created from your GitHub username or from the part of your email before the “@”. Your teammates see your name, your handle, your photo and whether you’re online; your email is not shown.
Pulsar does not send to our servers:
The only thing that leaves is what you send to a teammate and, if you share live with your team and choose to include it, a still snapshot of the page you share. What’s seen when you share live with your devices, your team or a Pulsar link (the pages, their paths and headers) is end-to-end encrypted from your Mac to the viewer’s device: neither we nor the relay can read it, and we only keep the metadata in the table above. Not with the public link: it doesn’t go through our servers, but Cloudflare sees everything that’s transmitted. If an agent prepares a share from the command line, Pulsar asks you to confirm it —what is sent and to whom— before it goes out.
We don’t sell your data or share it with advertisers. We would only hand it over to an authority if the law required us to, and we would do so with the bare minimum.
With the public link, anyone with a browser sees a page from your Mac through TryCloudflare, a service from Cloudflare, Inc. that your Mac uses directly: it doesn’t go through our servers.
When you sign in with Google we only ask for the basic identity permissions (openid, email and profile): your name, your email and your photo. With GitHub, your public profile and your email. We don’t ask for access to your repositories, your Gmail, your Drive or any other data.
Pulsar’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can revoke access anytime from your Google account connections or your authorized GitHub applications. That stops you from signing in with that account again, but it doesn’t delete your Pulsar account: for that, see how to delete your account.
Pulsar Cloud data is hosted on Supabase, in data centers in the United States. If you live in another country, your data is transferred to and stored there.
Pulsar downloads what you receive and saves it on your Mac, in its data folder, so you keep it once it’s no longer in the cloud. Whoever sent it sees when your Mac saved it and when you read it. A copy of what you send is also kept on your Mac, so you can see your conversations. If someone who sent you something deletes it for everyone while it’s still in the cloud, Pulsar removes your copy; anything you’ve already opened, copied or passed to an agent can’t be taken back. What a teammate has already downloaded or passed to an agent stays on their Mac: we can’t delete it for you.
Each device you sign in to Pulsar Cloud with is registered to your account so shares reach all of them before they’re deleted from the cloud. Only you can see your devices, and you can remove them from the app’s Settings; a device you don’t use for 14 days stops being waited for on its own. Your teammates can’t see how many you have, but since they see how long a share will stay in the cloud, they can tell that some device of someone hasn’t saved it yet.
For now, to delete your account, write to us at oliver@olivermtz.com from the email you signed in with, with the subject “Delete my Pulsar account”. We’ll delete your profile, your team memberships, the invitations you created and the shares you sent or received. If you’re the only owner of a team with other members, we’ll ask you who to hand it over to.
Signing out of Pulsar does not delete your account.
You can also ask us at any time to access your data, correct it, delete it, take it with you in a readable format, object to a specific use or withdraw your consent. Write to the same address; we’ll reply within 20 business days at most. If you’re not satisfied, you can turn to the data protection authority in your country.
This website uses no cookies or analytics and loads nothing from third parties: even the fonts are served from the site itself.
The invitations page reads the code in the link in your browser and only hands it to the app; it never sends it to a server. Like any website, our hosting provider may log technical data about visits (IP and browser) to run and secure the service.
When you pay for a subscription, the charge is processed by Stripe. Stripe receives your payment and billing details (card, name, email, country and address) and also processes them under its own privacy policy. We never see or store your card number.
From Stripe we only keep what we need to give you access: the customer and subscription IDs, the plan, whether it’s monthly or yearly, its status and when it renews or ends.
For the free trial we store when it starts and ends, and an identifier derived from your Mac (a hash: it isn’t its serial number and can’t be used to tell which Mac it is) so the same machine doesn’t get two trials. We keep it for as long as your account exists; so that Mac doesn’t get another trial, its identifier is kept even if you delete your account, with nothing left linking it to you. We also store the names of your Macs (the one each computer has) so you can see and remove them in Settings, up to 3. The app keeps a signed license with your plan on your Mac so it can work offline for a few days.
We keep payment records for as long as tax law requires.
With Pulsar Business, whoever pays (the billing administrator) invites each person they offer a seat to by email. We store that email, when they were invited and whether they accepted, only to give them access. Before accepting, the person invited sees the name and username of whoever pays; the seat gives nothing until they accept it. The administrator sees the email they entered and whether the person accepted, declined or left the seat; they never see that person’s profile or their use of the app. If they remove the person or the person declines, we delete their email after 31 days; if the administrator deletes their account, right away. We don’t email these people: the administrator lets them know.
Pulsar Cloud is not directed at children under 16, and they can’t create an account. If you believe a minor has given us their data, write to us and we’ll delete it.
If we change anything important in this policy, we’ll announce it in the app or on this website before it takes effect, and we’ll update the date at the top.
For any question about your data, write to us at oliver@olivermtz.com.