Skip to content
Tabsend
Privacy policy Terms of service Support Delete your data
Back to tabsend.org

Last updated November 13, 2026

Privacy policy

What Tabsend handles when you send a link, who else gets it, and how long it stays.

The short version

  • Tabsend moves a link from one of your devices to another. To do that, it handles the web address, the title and the icon of the page you choose to send.
  • Those three are locked (encrypted) on your device before they leave it. The server only passes the locked version along. We don't read your links.
  • No ads, no trackers, no cookies. This website counts its visits, without cookies (section 2). The extension and the apps count nothing. We don't sell your data and we don't share it for advertising.
  • The browser extension talks to your Tabsend server and your browser's push service. Website images in History load from linked websites and their image hosts.
  • One honest limit: the server keeps your list of devices, and nothing signs that list. Someone who broke into the server could add a device to your group. That device could read the links your devices send while it is there, plus the last 30 days of history. It would show up in your device list, and your other devices would tell you a new device joined. More in section 6.
  • If you run your own server, the browser extension sends us nothing. Phones are the one exception, because of Apple and Google rules. See section 5.

On this page

  1. 1. Who this covers
  2. 2. What Tabsend handles
  3. 3. What the extension can reach
  4. 4. How we use it
  5. 5. Who else gets it
  6. 6. Security and its limits
  7. 7. Keeping and deleting
  8. 8. Your rights
  9. 9. Children
  10. 10. Where data lives
  11. 11. Changes
  12. 12. Contact

1. Who this covers

This policy covers the Tabsend browser extension (Chrome, Edge, Brave and other Chromium browsers, and Firefox), the Tabsend apps for Android and iPhone, the web console, this website, and the hosted Tabsend service. Tabsend is made and run by Zinnia Drive LLC, in the United States. In this policy, "we" means Zinnia Drive LLC.

Tabsend needs a server to pass links along. We call it the relay. There are three ways to use one:

  • Your own server. You, or someone you trust, run the relay. We never receive what is on it. This policy then covers only what the Tabsend apps do. Whoever runs the server is responsible for what it keeps. If someone else runs yours, ask them for their policy.
  • The hosted service we run. Everything here about "our server" applies. Parts of this policy that apply only to it are marked "hosted service".
  • A server run by someone else. Their policy applies to that server. This one still covers the Tabsend apps.

2. What Tabsend handles

This is the full list. In the table, "your server" means whichever relay your devices are paired with.

Data that leaves your device
WhatWhyWhere it goesHow long
The links you sendThe web address, page title and page icon of each tab you choose to send It is the thing you asked Tabsend to deliver. Locked on your device first. The locked copy goes to your server and on to the device you picked. A second locked copy, for your history, can be opened by your own devices. A waiting link is erased when the other device confirms it arrived, or after 7 days. The history copy is erased after 30 days. Whoever runs a server can change these numbers on it.
History picture requestsThe address of a linked page or its preview picture To show pictures while viewing history. "Don't load website images" in Settings turns this off. Directly from your device to the website and its image host. They see your IP address and the request time. No copy goes to Tabsend or your relay. Pictures stay temporarily on your device. Each website decides how long to retain its request logs.
Your devicesThe name you give each one, its type (for example Chrome on Windows), its public encryption key, and a fingerprint of its secret device token To show your device list, send to the right device, and recognize each device. Your devices and your server. The server can read these; they are not locked. Until you remove the device or the group is deleted.
Delivery recordsWhich device sent to which, when, and whether it arrived To deliver the link and to show your history. Your server. While it holds a locked message, it also sees how big it is. Up to 30 days.
Wake-up addressesAn address your browser's push service or your phone's system gives Tabsend So a link opens right away, instead of when the device next checks in. Your server. For iPhones, and for Android phones that use Google push, also our wake-up service (section 5). The wake-up message carries no link. On an iPhone it is a notification that says only “New link”, the same words every time, and your phone fills in the link itself. Until you remove the device or the address stops working.
Network detailsThe IP address your devices connect from, the time, and the address requested To deliver links, limit abuse and fix problems. Your server's request logs and short rate-limit counters. Hosted service: logs for 30 days. Counters are dropped when their time window ends, which is minutes. On your own server, whoever runs it decides.
Your account (hosted service only)Your email address, when your trial or subscription starts and ends, and a Stripe customer number To send sign-in links and notices, start your trial and bill you. Our account system, our email delivery service and Stripe. We never see your card number, and the free trial doesn't ask for a card. While your account exists. Then it is deleted (section 7).
The "links still waiting" email (hosted service only)The names of the sending and receiving devices, and when the link was sent. Never the link itself To tell you when a link has waited more than a day and a half for its device, at most once a day. You can turn it off on your account page. From your server to our account system, which writes the email, and to our email delivery service. Not kept. Our account system only remembers when it last emailed you.
Visits to this websiteThe page you open, the site you came from, your country, and your browser and device type. If the link you followed carried a campaign tag (such as utm_source=reddit), that tag, the page and the date To see how many people visit and how they find Tabsend. Cloudflare Web Analytics, which counts visits without cookies and doesn't follow you to other sites. Campaign tags go to a list kept with Cloudflare, with no IP address and nothing else about you. Cloudflare keeps visit counts for six months. Campaign tags say nothing about who you are, so we keep them.
How you arrived (hosted service only)The campaign tag on the link you followed (for example reddit), the page of this website you pressed Start free trial on, and, if you tap it, how you say you heard about us. Nothing about you. To see which channels and pages bring customers. Our account records. Kept in our log after your account is deleted, because it says nothing about a person.
Your answers to our questions (hosted service only)A reason you tap when a trial or a paid year ends, or when you turn renewal off or delete your account, and anything you choose to write, including suggestions To learn why people leave and what is missing. Our account records. When you delete your account, what you wrote and the link to your account are deleted. The reason you tapped stays as a count with no name.
Your personal link and friends who join through it (hosted service only)A random code that is your link, which friend's code a new account came through, and, once that friend pays, a count and a $5 credit. You see only a number, never who. To give a thank-you and to see whether sharing works. Our account records. When you delete your account, your link and the link to whoever referred you are deleted. Our log keeps counts with no name.
The "A friend subscribed" email (hosted service only)Your email address, once, when a friend you referred pays. No open or click tracking. To thank you and tell you about the credit. Our email delivery service. One email per paying friend. Stop these with the link in the email; account emails still come.
Messages you send usSupport emails, and anything you put in them To answer you. Our email inbox. Until you ask us to delete them.

What stays on your device

The extension and the apps keep some things on your device only: your encryption keys, your pairing details, your settings, a list of links you recently sent and received (readable, with their addresses and titles), and links waiting to be sent while your server is offline. In a browser, this lives in the extension's own storage. Tabsend adds no encryption of its own there, so it has the same protection as the rest of your browser profile. Removing the extension deletes it.

What Tabsend does not collect

No names, passwords, contacts or location. No cookies, form entries or saved logins. To show pictures in History, the device that sends a tab finds the page's preview picture and passes its address to your other devices, encrypted so your relay cannot read it. The pictures stay on your devices. The extension does not read your browsing history; it reads only the tabs you choose to send. There are no analytics, no advertising identifiers, no crash reports and no fingerprinting in the extension or the apps. This website has no advertising identifiers or fingerprinting either, and sets no cookies. It counts visits as the table above says. The counter is a small script from Cloudflare, the only thing this site loads from another site. Like any website, it notes the address, time and IP address of each request. Cloudflare, which serves the site, does this for us.

3. What the extension can reach

Browsers make an extension ask for permissions up front. These are Tabsend's, and what each is for.

Permissions the extension asks for
PermissionWhat it is for
TabsReads the address, title and icon of the tab you choose to send, and opens tabs that arrive from your other devices.
StorageKeeps your pairing, keys, settings and tabs waiting to be sent.
Context menusAdds "Send tab to" and "Send link to" to the right-click menu.
AlarmsChecks your server for arriving tabs on a schedule, and retries sends that were waiting on an offline server.
Offscreen documentsHolds the live connection to your server, so arriving tabs open right away.
ScriptingShows a short "Sent to" note on the page you sent from. It runs only after you send, only on that tab. It also reads one thing from the page you send: the address of its preview picture.
NotificationsShows a notice when a tab arrives from another device. It is on by default and you can switch it off in settings. The notice appears on your own screen only.
Access to websites (http and https)You type the address of your own Tabsend server, and it can be any address, including one on your home network. The extension contacts that address. The same access lets the "Sent to" note appear on whichever page you sent from. If you turn on "A picture for every link" (in History or Settings), the extension asks your browser for access to all https websites and uses it for one thing: to look up the preview picture of a page in your History that arrived without one. It asks without your cookies or saved logins, never asks a page whose address has a "?" or "#" in it, and reads only the picture's address from the page. You can turn it off in Settings.

The extension runs no remote code. Everything it runs is in the package you installed from the store. It loads no scripts or fonts from other sites. When you receive a page, your browser may load that page's icon from the page's own website, as it does when you visit the site.

4. How we use it

We use what is listed in section 2 to move your links between your devices and to run the service that does it. In detail:

  • delivering links and showing your history
  • keeping the service secure and stopping abuse
  • billing you and sending account notices (hosted service)
  • answering you when you write to us
  • counting visits to this website, to see how people find Tabsend

We don't use it for advertising, profiling, or credit or lending decisions, and we don't use it to train AI models. We don't sell it. We hold no key to read your links. A person looks at device lists, delivery records or logs only to fix a problem you report, to look into abuse or a security issue, or when the law requires it.

Tabsend's use and transfer of information received through browser extension APIs follows the Chrome Web Store User Data Policy, including the Limited Use requirements.

5. Who else gets it

We don't sell or rent your data, and we don't share it for advertising. These are the only others who touch it:

  • The operator of your server. That is you if you run it yourself, and us for the hosted service.
  • Your browser's push service. To wake the extension, Tabsend signs your browser up with the push service of the company behind it, such as Google for Chrome or Mozilla for Firefox. The wake-up message is empty. That service sees that your browser got a wake-up, and when. It never gets a link.
  • Our wake-up service, plus Apple and Google, for phones. A phone can't be woken without Apple's or Google's push service, and those accept requests only from a key we hold. So your server tells our wake-up service to ring your phone, and it asks Apple or Google. This applies to iPhones and to Android phones that use Google push, even when you run your own server. The wake-up service learns that a device got something, and when. It does not learn what, or who sent it. On an iPhone with notifications allowed, the wake-up is a notification that says only “New link”, so Apple can see that a notification was sent. Your phone then fetches the link from your server and shows it. The link never passes through us or Apple. It keeps, for each phone, Apple's or Google's address for it (encrypted), a fingerprint of the phone's token, when it was last rung and how many times. It keeps no record of individual messages.
  • The websites you send. When a link opens, your browser loads the page from its site as usual. Viewing history also requests pictures, and on phones page details, directly from linked websites and their image hosts. So does sending a tab from a phone, which asks the page for its picture. Those sites see your IP address, the requested address and the request time. Phone requests, and a browser's page lookups when you turn on "A picture for every link", send no cookies or saved logins. In a browser a picture loads like any image on a web page, under your browser's usual cookie rules. No website scripts run. You can turn this off with "Don't load website images" in Settings. Pictures are kept temporarily on your device; the websites decide how long to keep their request logs.
  • Cloudflare, for this website. Cloudflare serves tabsend.org and counts its visits. It sees the IP address and request of everyone who visits the site.
  • Service providers, hosted service. Google Cloud hosts our servers in South Carolina, US. Stripe takes payments through its Link service, which sells the hosted service for us, works out the sales tax and sends receipts; for that, Link handles your payment details and billing address under its own privacy policy. An email delivery service sends sign-in links and notices. Each handles your data only to do that job for us.
  • Legal demands. If a valid legal demand arrives, we give only what we hold, which is the list in section 2, and we tell you when we can, unless the law forbids it.
  • A sale or handover. If Tabsend is ever sold or handed to someone else, your data moves only if you agree first.

6. Security and its limits

  • Links are locked on your device. We use libsodium: X25519 key exchange and XSalsa20-Poly1305 encryption. Each link is locked once for each device that receives it, plus one history copy for your group's devices.
  • The hosted service uses HTTPS only. The extension also accepts plain http addresses, so people can use a server on their home network. Links stay locked either way, but device names and delivery details cross a plain http connection in the open. Use https unless the server is on a network you trust.
  • The server keeps your device list, and nothing signs it. Someone who broke into the server could add a device to your group. That device could read the links your devices send while it is there, and the last 30 days of history. It would show up in your device list, and each of your other devices checks the list against the one it last saw and shows a notice when a new device appears. We don't read your links, but we can't promise nobody ever could.
  • No independent audit. Nobody outside the project has audited Tabsend's security.
  • Your devices matter. Anyone who can use your unlocked browser or phone can see its recent links and send from it.

If you find a security problem, please email contact@tabsend.org with "Tabsend security" in the subject line.

7. Keeping and deleting

  • How long things stay is in the table in section 2. Backups of the hosted database roll off after 30 days.
  • Remove one device from the device list in any Tabsend app. That removes it from your group, and its wake-up address with it.
  • Remove the extension and the browser deletes everything the extension kept. Your server still lists the device until you remove it from the device list.
  • Delete your hosted account from your account page, or by email. We then remove your account, your group and everything on the server, except a few counts that name no one (section 2: how you arrived, and the reasons you tapped). Backups roll off within 30 days. Stripe keeps payment records as the law requires.
  • If a trial or subscription ends unpaid, the account pauses. Nothing is deleted at first, and your devices stay paired. We email you, and if there is still no payment 90 days later, we delete the account.
  • On your own server, you hold everything and you delete it.

8. Your rights

Wherever you live, you can ask us to tell you what we hold about you, correct it, delete it, or send you a copy. Email us. We answer within 30 days. We may ask you to write from your account's email address, so we know the request is yours.

Laws in California and some other US states give these rights too; we apply them to everyone. We don't sell or share personal information as those laws define it. We don't track you across sites, so a "Do Not Track" signal changes nothing. If you think we handled your data wrongly, you can also complain to your local data protection authority.

9. Children

Tabsend is not for children under 13, and we don't knowingly collect their data. A hosted account needs you to be 13 or older. If a child's data reached us, email us and we will delete it.

10. Where data lives

On the hosted service, in the United States, on servers in South Carolina. If you use it from another country, your data goes to the US. On your own server, it lives wherever you run it. This website and its visit counts run on Cloudflare's network, which spreads copies across many countries.

11. Changes

When this policy changes, we change the date at the top. If a change matters, we email hosted-service users first. If a change would alter what the extension handles, we update the store listing before the new version ships.

12. Contact

Zinnia Drive LLC. Questions, requests, or a complaint: contact@tabsend.org. One person reads it, so replies can take a few days. See also the terms of service, support, and how to delete your Tabsend data.

Tabsend

Send a link to your phone, or to any other browser, in one click.

Pages

  • Home
  • Privacy policy
  • Terms of service
  • Support
  • Delete your data
  • Deutsch

License

The apps are open source under Apache-2.0. The server code is public under FSL-1.1-ALv2: free to run yourself, not to resell as a competing service, and it becomes Apache-2.0 two years after each release.

© 2026 Zinnia Drive LLC. Made by one person. Bug reports welcome.