Privacy policy
Link Jar saves your links in your own AT Protocol account. Private links are encrypted on your device before they leave it. This page explains what Link Jar handles, when and why, and what you control.
The short version
- Public links are public. Public links, boards, comments, reactions and follows are records on the open AT Protocol network. Anyone can read them, including other apps.
- Private links are encrypted on your device. Their addresses, titles, notes and tags are encrypted before upload. Your settings, reading progress and highlights are always encrypted. Link Jar and your account host store this data but cannot read it.
- Some features send data when you use them. Link previews, snapshots and AI features send a link or article text to a Link Jar service. For private links, these features are off by default or ask each time. On iPhone, some of them start on; see Features that use our servers.
- No ads, no selling. We don't sell personal data, show ads, or track you across other apps and websites.
- Limited analytics. The web app and website use analytics that never include your links. The browser extension and the iPhone and Mac apps have none.
- Who runs Link Jar
- Your account
- Public and private links
- Your Private Jar keys
- Features that use our servers
- Sync and notifications
- The public index
- Link Jar accounts
- Website and waitlist
- Analytics
- Data on your devices
- Service providers
- How long we keep data
- Your choices and rights
- Changes and contact
Who runs Link Jar
Link Jar is operated by Uros Karic, Mise Vujica 1, Belgrade, Serbia, the controller of the personal data described here. Email hello@linkjar.io with any privacy question or request.
Your account
Link Jar runs on AT Protocol, the open network that Bluesky also uses. Your links are records in your AT Protocol account, also called your repository. An account host stores it:
- If you sign in with Bluesky or another provider, that provider hosts your account, and its privacy policy covers the account itself. Link Jar signs in through OAuth. Your sign-in session stays on your device; Link Jar's servers never receive your password or your session.
- If you create a Link Jar account, we host it. See Link Jar accounts.
When an app uses a Link Jar service, your host issues it a short-lived token that proves which account is asking. The token identifies your account by its DID, the permanent identifier every AT Protocol account has.
Public and private links
Public
A public link's address, title, note, tags and summary are published with your account, and so are the times you saved it: when you save a link that is already in your Jar, Link Jar adds that time to the link. Public boards and their items, comments, reactions and follows are published too. Anyone can read them. Other services on the network, such as relays and apps, can keep copies. When you delete a public record, it leaves your repository and Link Jar's index; we can't remove copies that others hold.
Private
For a private link, the address, title, note, tags and boards are encrypted on your device. Settings, reading progress, highlights and saved summaries are always encrypted, whatever the link's visibility. Snapshots (offline copies of articles) are encrypted before upload.
Encryption doesn't hide everything. For private records, your host and the network can still see when each record was created, its approximate size, that it is private, how many images a snapshot has and their sizes, and a keyed marker that shows whether two of your private links point to the same address. Encrypted records travel through the network like public ones, so others can hold copies of the encrypted data.
Your Private Jar keys
- Private data is encrypted with keys derived from your Recovery Seed, which your device creates. The seed never goes to Link Jar in readable form.
- Your Recovery Kit (a code or 24 words) restores access. We can't reset it or recover your private data without it. Anyone who has it can read your private data, so keep it safe.
- With a passkey, your repository keeps a copy of the seed that only that passkey can unlock.
- The iPhone and Mac apps can keep a copy of the seed in iCloud Keychain so your other Apple devices can unlock. This is on by default. Turn it off in Settings: Sync with iCloud Keychain on iPhone, or Keep a copy in iCloud Keychain on Mac. Apple encrypts iCloud Keychain end to end.
- In the web app, your Recovery Kit stays in memory and is gone when you reload or close the page. With a passkey, the browser also keeps a copy of the seed that the passkey unlocks. After you unlock, the browser can reopen your Private Jar without asking for the passkey again until you have been away for 15 minutes. In Settings, use Require biometric to change that time, or choose Every time to turn this off.
Features that use our servers
These features send data to a Link Jar service when you use them. The service uses it for that one request unless the table says otherwise. Where a feature would send a private link's content, it is off by default or asks you first, except where the iPhone row says otherwise.
| Feature | What is sent | Default | Kept |
|---|---|---|---|
| Link previews (web app) | The link's address. Our server loads the page to read its title, description and image, so the website sees a request from Link Jar. For a Bluesky post, an X post or a Hacker News item, our server instead asks that service's public API for the post. | Off. In Settings, Ask turns previews on for public links, and Always turns them on for private links too. For a private link you can also choose Fetch preview, which loads one preview after you confirm. | Public links: the preview, by address, for up to 1 hour. Private links: not kept. |
| Link previews (iPhone) | Nothing to Link Jar. Your phone loads the page and its images directly. | On, including Previews for private links. | On your phone. |
| Snapshots | The browser extension copies the page you have open, with no server involved. The web app can ask our server to load the page; the server sees the article text while it prepares the copy. Your device then encrypts the copy and stores it in your repository. | Private links: asks every time. On iPhone, your phone loads pages itself, and Snapshot when saving and Snapshot for Read Later are on. | The snapshot is not kept on our servers. We keep a count of your snapshot requests in the last minute, for rate limits. |
| AI suggestions (tags, summary, board) | Title, description, site and language. For public links, also the address. Processed by Cloudflare Workers AI (currently Llama 3.3). | Off. For private links, asks every time. | Public-link results for 30 days, without your identity. Private: not kept. A count of your requests, for usage limits. |
| Cloud summaries | The article's title and text, up to about 48 KB per request. Processed by Cloudflare Workers AI (currently Mistral Small 3.1), with request logging off. | Off. Asks for each article. | Not kept. A count of your requests, for usage limits. |
| Invitations | When you create or share your invitation link: your DID, handle and display name, and how you shared the link. When someone opens your link: only its code. When someone joins through your link: their DID, handle and display name. Your link is a public address. Anyone who has it can open it and see your handle and display name. | Only when you create or share an invitation link, or join through one. | Who invited whom, and when. How often your link was opened and shared. Your founding number, if you were among the first 500 to join through an invitation. Kept until you delete your account or ask us. We store no IP address or email address for invitations. |
| Share links (jar.ink) | When you share a link: the share record from your repository (the link without its tracking parameters, its preview card and your optional note) and your DID. The page shows your public Bluesky name and picture. When someone opens your link: we count the visit, and use their IP address and browser type only to count each visitor once a day, as a keyed hash. We note the site that sent them, as a host name. The page loads images through jar.ink, so the original sites don't see visitors until they open the original. We check the link's host name against Cloudflare's list of malware and phishing sites. When someone reports a link: the reason and any text they add, and the same daily keyed hash, so one person counts once a day. | Only when you share a link with jar.ink. Sharing a private link publishes its address, and the app asks first. Its title, note and tags stay encrypted. | Your share and its daily counts until you stop sharing it or delete the share record. Visitor hashes until the end of that day (UTC). Reports until we have reviewed them. We store no IP address or browser type for share links. |
Some features run on your device: summaries from Apple Intelligence on iPhone, on-device summaries in the web app, Abridged reading in Enhance for listening on Mac, and Labs search. Some of them download files the first time you use them. The listening voice pack (about 116 MB), the web app's Labs search model and the web app's summary model (about 320 MB) come from Hugging Face. The summary model's runtime comes from GitHub (raw.githubusercontent.com). Both services see your IP address. In Chrome, the web app uses Chrome's built-in summarizer when it is available, and Chrome may download its model from Google.
Images and site icons shown with your saved links load directly from the websites that host them, so those websites see your IP address.
Sync and notifications
- Live sync. While an app is open, our events service relays changes in your repository to your other devices. It holds up to your last 1,000 changes (public content, and private records still encrypted). It also counts your changes and notes when it relayed the last one. It deletes the changes, the count and that time within 10 minutes after your last device disconnects. It keeps one marker of your most recent change, with your DID: the time of the change, its type (create, update or delete) and a reference to the record that changed. For a LinkJar account, the marker can also hold the revision of your repository at that change. The marker holds none of the record's content. A returning device uses the marker to resume. To receive changes quickly, it tells Bluesky's Jetstream service which accounts are connected, by DID.
- iPhone background sync and notifications. When you sign in, the iPhone app registers its push token with our events service, so that a change on another device can wake the phone. This is on by default and needs no notification permission. With your account, we store the token, a random tag for this copy of the app, its build type, whether Background sync and activity alerts are on, the times of the last registration and the last sync notification, and any sync notification or alert that is waiting to be sent. We delete them when you sign out, when Background sync (in Settings) and activity alerts (Settings › Notifications › Activity) are both off, or when Apple reports the token as invalid. If the request at sign-out fails, they stay until Apple reports the token as invalid. Sync notifications contain no content. Activity alerts contain the type of activity, counts, the DIDs of up to eight people involved and a reference to the link. Apple delivers them.
- Web reminders. When you turn on reminder notifications in a browser, we store that browser's push subscription and your reminder times with your account. Each browser's subscription is filed under a random tag. Each reminder is named by a keyed hash of the link, so we can't tell which link it belongs to, and a reminder notification carries only that hash. Your browser's push service delivers the notification, encrypted. We remember sent reminders for 7 days. We delete a browser's subscription when you sign out or turn reminder notifications off in that browser, or when its push service reports the subscription as expired. If the browser's request to delete it fails, the subscription stays until its push service reports it as expired. When no subscription is left, we delete your reminder times and the record of sent reminders too.
The public index
Link Jar's index (indexer.linkjar.io) reads public Link Jar records from the network. It powers Following, Discover, public jar pages, people search, comments and notifications. It stores public links (address, title, note, site, tags and summary), boards, follows, comments and reactions, the notifications derived from them, and a cache of account handles. It never stores private records.
Your notifications are visible only to you: the index answers only the account they belong to. When you delete a public record or make it private, we remove it from the index. When your host reports that your account was deleted, suspended or deactivated, we remove what it published. If anything remains, email us and we'll remove it. The index also checks whether saved public links still load, which contacts those websites.
Link Jar accounts
Link Jar accounts open during the private alpha. This section describes how they work; we'll update it if anything changes when they open. When you create a Link Jar account on our account server (pds.linkjar.social), we store:
- Your email address and whether you've verified it.
- Your password as a hash. If you sign in with Apple, Google or GitHub instead, we store the link to that account.
- Your handle and DID.
- Your devices' sessions and the apps you've connected.
- IP addresses and times of sign-ins and sign-ups, for security and to prevent abuse.
- Your repository and files: records on our server in Nuremberg, Germany (Hetzner), and files in Cloudflare R2.
Sign-up is protected by hCaptcha, which receives your IP address and browser details. We send account emails through Cloudflare Email Service, from accounts@linkjar.io. From the day accounts open, backups of account databases are kept for 7 days, and daily snapshots of encryption keys and server configuration for 30 days.
You can manage or delete your account on your account page (in Settings, open Sign-in methods), or email us. Deleting the account removes your repository from our server. Public records that others copied before you deleted them remain with them.
Website and waitlist
- Waitlist. We store your email address, the time you joined and whether our email reached you. We send the email through Resend. We keep your entry until you ask us to delete it. To limit repeated sign-ups, we store a keyed hash of your IP address and the current hour. The key is not stored with the hash. We delete the hash with the next sign-up after that hour.
- Extension uninstall form. If you fill it in, we store your reason, any comment, the extension version, your browser and the time you sent it. We delete answers older than 12 months. To limit repeated submissions, we separately store a keyed hash of your IP address and the current hour, and delete it with the next submission after that hour.
- Fonts. The website and web app load fonts from Google Fonts, which receives your IP address.
Analytics
We use PostHog, hosted in the EU, to understand how Link Jar is used.
- Web app. We record which screen you open (as a route, such as the Read Later screen, never the link itself) and events such as "link saved", "highlight created" or "AI suggestion accepted". Events never include addresses, titles, notes or article text. They are linked to your account's DID, not your handle. There is no automatic click tracking and no session recording. Analytics stays off when your browser sends Do Not Track or Global Privacy Control, and uses local storage rather than cookies.
- Website. We record page views and clicks, without session recordings, and honor Do Not Track. Nothing is stored in your browser, so we can't recognize repeat visits. Cloudflare Web Analytics also counts visits, without cookies.
- Browser extension, iPhone and Mac apps. No analytics. No Link Jar app uses crash reporting.
Data on your devices
- Web app. Your records are cached in the browser, encrypted with a key derived from your seed. Your handle and some preferences sit in local storage. Signing out removes your keys, the decrypted data and the local database.
- Browser extension. To show that a page is already in your Jar without asking a server, the extension keeps an index of your saved links. Public links are stored as they are. Private links are stored encrypted, with only a keyed hash of each address, so the index reveals nothing about them without your keys. Your seed stays in memory for the browser session.
- iPhone. The app stores your records decrypted in its own storage, protected by your device's data protection. Saves waiting to sync, including page content from the share sheet, are stored the same way until they sync.
- Mac. In the app's local database, private records and always-encrypted data, such as settings and highlights, stay encrypted with keys derived from your seed. Public records are stored as they are.
Service providers
We share data only as this policy describes, with these providers:
- Cloudflare: hosts Link Jar's services and website, runs the AI features, sends Link Jar account email, resolves handles over DNS, and provides web analytics.
- PostHog (EU): analytics.
- Resend: waitlist email.
- Apple: push notifications, iCloud Keychain and Sign in with Apple.
- Google: fonts, and Google sign-in for Link Jar accounts.
- GitHub: GitHub sign-in for Link Jar accounts, and the runtime download for on-device summaries in the web app.
- hCaptcha: sign-up protection for Link Jar accounts.
- Hetzner: the Link Jar account server.
- Hugging Face: downloads you request.
- Bluesky: Jetstream (sync), its AppView (profiles and people search) and, by default, handle lookups through bsky.social.
- PLC directory (plc.directory): account identity lookups.
We don't sell personal data or share it for advertising. We disclose data when the law requires it.
How long we keep data
| Data | Kept |
|---|---|
| Link previews of public links | Up to 1 hour |
| AI results for public links | 30 days |
| AI usage counts (requests per day and month, for usage limits) | Until the end of the month they count toward |
| Live sync buffer | Up to 10 minutes after your last device disconnects |
| Live sync activity counts (number of changes and the time the last one was relayed) | Up to 10 minutes after your last device disconnects |
| Live sync position marker (time, type and record reference of your most recent change) | Until a newer change replaces it, or until you ask us to delete it |
| iPhone push registration | Until you sign out, Background sync and activity alerts are both off, or Apple reports the token as invalid |
| Web reminder subscription | Until you sign out or turn reminder notifications off in that browser, or its push service reports it as expired |
| Web reminder times | Until the reminder is sent, or until no browser is subscribed |
| Sent web reminders | 7 days |
| Public index entries | Until you delete the record, make it private or ask us to remove it |
| Link Jar account | Until you delete it |
| Link Jar account backups | Databases 7 days; key and configuration snapshots 30 days (from the day accounts open) |
| Invitation record (who invited whom and when, the open and share counts of your link, your founding number) | Until you delete your account or ask us |
| Share link (the copy of your share record, daily view, visitor and preview counts, referring sites) | Until you stop sharing, delete the share record or ask us |
| Share link visitor hashes and the daily key behind them | Until the end of that day (UTC) |
| Reports on a share link (the reason and any text the reporter adds) | Until we have reviewed them. The reporter's daily hash until the end of that day (UTC) |
| Waitlist entry | Until you ask us to delete it |
| Waitlist sign-up limit (keyed IP hash and hour) | Until the next sign-up after that hour |
| Extension uninstall feedback | 12 months, then deleted with the next submission |
| Uninstall form limit (keyed IP hash and hour) | Until the next submission after that hour |
| Service logs (services on Cloudflare) | Up to 7 days. Logs record event names, not your content. Some entries, including account removals and errors, include your DID. An error entry can include the address of the request that failed, without its query string. In the web app, that address can contain the name of a tag you opened. For an invitation, it can contain the invitation code, and for a share link, the share code. The link checker records the host name of each public link it checks. |
Your choices and rights
- Settings. Choose each link's visibility, and turn previews, snapshots, AI features and notifications on or off.
- Export. In Settings, use Your data on the web or Export links on iPhone. The export file is created on your device and not sent to Link Jar.
- Delete. Deleting a link removes it from your repository and from our index. In the web and Mac apps, its snapshots and board entries go with it. Its highlights are marked deleted and their notes are removed. An encrypted marker with the highlighted text stays in your repository for 30 days. After that, Link Jar removes it when one of your unlocked apps syncs. A saved article summary stays in your repository, encrypted. Your host may keep a deleted snapshot's encrypted file until it cleans up unused files.
- Your rights. Depending on where you live, you can ask to access, correct, delete, restrict or transfer your data, or object to how we use it. Email hello@linkjar.io; we reply within one month. You can also complain to your data protection authority.
- Legal bases. We process data to provide the features you use, with your consent for features that ask first, and for our legitimate interests in security, abuse prevention and limited analytics.
- Children. Link Jar is not for children under 16.
Changes and contact
When this policy changes, we update the date at the top. We announce significant changes in the app or by email. Questions and requests: hello@linkjar.io.