Privacy

Effective 26 September 2026. Plain English, and specific — a privacy page that keeps its options open is telling you something.

The short version

1. The browser tools

Every tool on this site runs on your own device. Links you paste are processed there and never sent anywhere, so we have nothing to store or log.

Share links keep your input in the part of the link after the #. Browsers never send that part to a server, so even a link you share does not reveal its contents to us.

The UTM builder saves presets in your browser's local storage so they are there next time. That stays on your machine. Clearing your browser data removes it.

2. Site analytics

We use Cloudflare Web Analytics. It uses no cookies and does not try to identify you. It only counts page views and which sites people came from, in total. That is why there is no cookie banner.

3. Your account

An account is needed for short links, file delivery and paid plans, and for nothing else. You create one by signing in with Google, or with a code we email you.

With Google, we receive from them: your email address, your display name if they send one, the ID number Google uses for your account, and whether they have confirmed the address is yours.

With an emailed code, we send a six-digit code to the address you type, and store a scrambled (hashed) copy of the code, the address, and a hashed form of your IP address. The hashed IP is how we stop one network asking for codes to many addresses. The code works once, for ten minutes, and these records are deleted after a day.

We never hold a password. There is no password field in our database and there never will be. Google holds that credential, and an emailed code is only ever stored hashed and only until it is used or expires.

Signing in sets one cookie that keeps you signed in. It lasts twelve hours. If you tick "keep me signed in", it lasts until you have not used the site for 14 days, and never longer than 90 days. For each signed-in device we store a short name for it taken from your browser (such as "Chrome on macOS"), so the account page can list your devices and let you sign any of them out. A second, shorter cookie exists for ten minutes while you sign in, to stop anyone faking that step. Both cookies are needed for the service to work, and neither is used to track you on other sites.

4. Links, files and their recipients

When you create a link we store what you gave us: the destination, the short slug, any title, expiry, open limit, and — if you set one — a hash of the link password, never the password itself. If you restrict a link to named recipients, the email addresses you list are stored so the link can enforce that.

Links made without an account. You can make a few short links on the homepage without signing up. For each one we store the destination and the short slug, plus your IP address scrambled with a secret key that changes every day — used only to hold everyone to a few links a day. We also set one cookie in your browser, holding a random code, so that if you sign up later the links you made move into your account. We store only a scrambled copy of that code, which cannot be turned back into it. Opens of these links are counted like any other link's, as described in section 5, and shown only to whoever signs up with that browser. These links stop working after 30 days unless you sign up.

When someone claims a recipient-restricted link we record their email address, the time, and a hashed form of their IP address. That record is how the delivery proof works, and it is visible to the person who created the link. After 18 months the recipient's details are removed from it automatically and only the fact of the delivery remains.

For file delivery we store the file, its name, size, type and checksum. Files expire automatically and are then deleted from storage. Where a transfer is end-to-end encrypted, the decryption key lives only in the link fragment and never reaches us — we cannot read those files, which also means we cannot scan them or recover them for you.

Destination URLs are sent to a Google link-safety service to be checked against known phishing and malware lists — when a link is made, and again at most once a day while it is being opened. This is what stops the service becoming a laundering service for hostile links.

5. Click counts, and what we do not keep

When someone opens one of your links we record the event so you can see your click counts: which link, what happened, whether the visitor looked like a person or a bot, their country, the site they came from, their browser and device type, and the time.

The IP address is not stored. We scramble it with a secret key that changes every day, and store only the scrambled result. This means nobody can follow a visitor from one day to the next. The downside is that visitor counts across several days are only approximate, and we think that is worth it.

Click events are held for 90 days and then expire automatically.

Before they expire, we keep one number per link per day: how many times it was opened, and how many of those looked like people. Nothing about who opened it — no IP, country, referrer or browser. These daily counts are kept for two years, so paid plans can show older history, and are deleted with your account.

6. The audit log

Actions on an account, such as creating, editing or revoking a link, setting a password, or adding a domain, are written to a log (the audit log). Each entry has the time, the email address of who did it, a scrambled IP address and their browser and device type.

Customers use this log to show their own auditors what happened. We also need it by law, to show what we did about a complaint and when.

The record is kept for as long as the account exists, but the parts that identify a person are not. After 18 months, the email address, scrambled IP address and browser details are removed automatically. What happened, when, and to which link stays. We never delete entries, because a log that can be changed cannot be trusted as proof.

7. The newsletter

If you enter an email address it is stored so we can email you when there are new tools. It is not sold, not shared, and not used for anything else. Every email has a one-click unsubscribe link. If you unsubscribe, we keep a note of that, so we do not email you again.

8. Payments

Paid plans are sold through a payment company, which is the legal seller and handles the payment. We never see your card details. We store a copy of your subscription details: the payment company's IDs for you and your subscription, the plan, its status, and when the current period ends. We also keep the provider's notifications about your subscription, which can include your name and billing address, for 18 months in case a charge is disputed; after that only the fact and time of each notification remain. Your payment provider keeps its own records under its own privacy policy and its own tax obligations.

9. Abuse reports

Anyone can report a link. If they give an email address we store it so we can reply, and we store a scrambled IP address to spot floods of reports meant to harass someone.A report is never shown to the account it is about.

10. Who else sees your data

There are no advertising networks, no trackers and no data brokers. The companies that process data on our behalf, and the reason for each:

WhoWhat for
CloudflareHosting, the database, file storage and analytics — all of it runs there
GoogleSign-in, if you use it; and safety checks on link destinations
ZohoSending our emails, such as sign-in codes; and hosting our support inbox, where reports and complaints you send us are kept
Our payment providerTaking payment as the legal seller, on paid plans only

We will also disclose data where a valid court order or a lawful demand from an authorised government agency requires it, and where it is necessary to report material involving the abuse of a minor, which we are obliged to do and which is described in section 10 of the terms.

11. Where your data is

The service runs on Cloudflare's global network, so your data is processed and stored outside the country you are in, including outside the European Economic Area. Transfers are covered by Cloudflare's data processing terms and the Standard Contractual Clauses approved by the European Commission.

We cannot currently keep your data in one specific country or region. If your contract requires that, write to us before you sign up.

12. How long we keep things

13. Deleting your account

In the dashboard, under Account. You confirm by typing your own email address, and then:

The seven days are not us dragging our feet. If someone else got into your account, instant deletion would mean a single click destroyed everything you had. Instead the request does nothing that a cancel cannot undo, and you have a week to notice. That is a far more likely way to lose your data than us taking a week over it.

Two things survive an erasure, and both are deliberate:

Everything else goes. Where a record has to survive for one of the reasons above — the audit log is the main one — the fields that identify you are removed and only the bare fact of what happened remains. Signing up again later starts an empty account: there is nothing left to restore it from.

14. Your rights

If you are in the UK, the EU or another place with comparable law, you have the right to see what we hold about you, to have it corrected, to have it deleted, to object to how we use it, and to get a copy in a portable form. You also have the right to complain to your data protection authority.

Deletion and a link export you can do yourself from the dashboard, immediately, with no request to us. For anything else write to support@vololink.com and we will answer within 30 days. We do not charge for this and we will not ask you why.

15. Children

The service is not for children. Do not create an account if you are under 16, or under the age of digital consent where you live if that is higher. If we learn that an account belongs to a child we will delete it.

16. Changes, and how to reach us

If what we collect, why, or who we share it with changes, this page changes and the effective date at the top moves with it. Material changes to an account holder's data will also be announced in the dashboard.

VoloLink is operated from India. Every privacy question, request and complaint goes to one address that is read:support@vololink.com.