👋 Hey Product Hunt! Sign up this week and get free Premium for life. Claim your link
Link.bio
AI builder MCP Features How it works Examples
Log in Claim your link
AI builder MCP Features How it works Examples Log in

Privacy Policy

Last updated November 17, 2026

This policy explains what Link.bio (“we”, “us”) collects when you visit link.bio or use your account, why we collect it, and the choices you have. We keep it short and only collect what we need to run the service.

What we collect

  • Account details. Your username and email address when you sign up, and your password if you choose to set one. We never store your password itself, only a one-way scrambled version (an Argon2id hash) that can’t be turned back into the password.
  • Signing in with Google. If you use “Continue with Google”, Google tells us your email address, your name and an ID for your Google account. We keep the ID and the email address to recognize you next time, and use your name as your page’s name when you sign up. We never see your Google password, and we don’t get your contacts or anything else from your Google account.
  • Your country. When you sign up (or, for older accounts, the next time you log in), we note the country you’re in, as provided by Cloudflare (just the country, not your address or city). For accounts from before we did this, we worked it out once from the IP address of your last login (or of your sign-up, from our server’s access logs), using an IP-to-country list stored on our own server (DB-IP); your IP address wasn’t sent anywhere. Only our team sees it, to understand where our users are and to help spot abuse.
  • How you found us. When you sign up, we note what brought you to Link.bio: the site you came from (for example Instagram, Google or ChatGPT), the name of a campaign link, or the Link.bio page whose “Made with Link.bio” badge you followed, and which page of our own site you saw first (for example our page for musicians). Until you sign up, this is kept only in that browser tab (session storage, not a cookie) and is gone when you close it. For accounts from before we did this, we worked it out once from our server’s access logs. Only our team sees it, to know which places bring new people.
  • Your language. We note the language of the site you sign up on (English, Spanish or Portuguese), and update it when you log in or reset your password on the Spanish or Portuguese site, so our emails reach you in that language.
  • Login sessions. When you log in, we create a session for that device. We store the date and time, your IP address and your browser’s user agent (for example “Chrome on Mac”), so you can see and log out of your devices on your dashboard and so we can spot suspicious activity.
  • Security counters. To stop password and code guessing and spam, we count recent login, signup and code attempts. These counters are stored in a scrambled form and deleted within an hour.
  • Server logs. Like most websites, our servers record basic request details (IP address, page requested, browser, time) to keep the site running and secure.
  • Your public page. Anything you add to your Link.bio page, such as your name, bio, photo, links, social icons, embedded videos or music, and your design, is public as soon as you save it (your page is live from the start unless you make it private). That’s the point of the page, so only add what you’re happy for anyone to see.
  • Pictures you upload. Profile pictures, link thumbnails, background and banner images and cutouts are resized and re-saved by us, which removes hidden information such as the location a photo was taken. They’re stored under random file names with Amazon Web Services and shown on your public page once you save your changes. When you make a cutout (your photo with the background removed), the background is removed on your own device: the original photo isn’t sent to us, only the finished cutout.
  • Background videos. A video you upload as your page’s background is stored the same way, with a still frame from it that your browser makes. We don’t re-encode videos, but we blank the information phones keep inside the file (such as where and when it was filmed and with which camera) before storing it.
  • Emails left in a signup block. If a page has an email signup block and you type your email address into it, we store that address with the date and the country you’re in (as provided by Cloudflare) for that page’s owner, who can see it, remove it and download it to use with their own email service. We don’t email the people on these lists, and we don’t use the addresses for anything else. To be taken off a list, ask the page’s owner or contact us. Page owners are responsible for how they use the emails they collect.
  • Building your page with AI. If you use “Build my page with AI” in your dashboard, we read the public pages at the links you paste (for example your website, Linktree or YouTube channel): their words, links and pictures. For a link to a profile on Instagram, TikTok, Facebook, X or Threads, our provider ScrapeCreators reads for us what that profile shows to anyone without logging in: its name, bio, profile picture, the links in its bio and, on Instagram, its latest pictures. We send what you typed, the public information we found and small previews of some of those pictures to OpenAI, which writes suggestions for your page. Pictures we suggest are copied and stored like your own uploads, and become part of your page only if you save. We keep a record of each build (when it happened, which kinds of links you pasted, such as a website or YouTube, how many were read, your language, the first theme suggested and what it cost us), never the addresses or what you typed.
  • AI agents you connect. If you connect an AI agent (such as Claude, ChatGPT or Cursor) to your account at link.bio/mcp and pick Allow, we store the agent’s name and the addresses it registered, when you connected it and when it last worked on your pages, plus scrambled versions of the keys it uses. The agent can then read and change your pages and see their stats for you; what you ask it and what it does with that is covered by the agent’s own privacy policy. Disconnect it any time in Settings; connections you don’t use end after 90 days.
  • Trying the AI builder before signing up. On our AI link in bio generator page you can build a page without an account. It works the same way as above. We keep the page it built, with its pictures, for one day so you can see it and claim it, and then delete it unless you signed up and claimed it. To limit how many tries each visitor gets, we count them by IP address for a day.
  • Visits to Link.bio pages. When someone visits a page or taps one of its links or social icons, we add one to that day’s totals: views, clicks per link and per social icon, the site the visitor came from (just its name, like “Instagram”), their country (provided by Cloudflare; counted for views and for clicks) and their type of device (mobile, tablet or desktop). We don’t store visitors’ IP addresses, set cookies on public pages, or keep anything that identifies a visitor in these statistics. Page owners see the totals in Insights. Visits by search engine bots and by the page owner aren’t counted.
  • Safety checks. To protect visitors from phishing, scams and malware, we automatically check the links, names and wording on pages for warning signs (for example a link to a site pretending to be a well-known brand, or a link that downloads a program). These checks only use what’s on the page: nothing is sent to other companies. Our team reviews flagged pages and visitor reports; nothing is taken down automatically. When we suspend an account, lift a suspension or mark a flagged page as fine, we record who did it, when and why. We can also block a website so that no page can link to it. When we suspend someone for abuse, we may keep their email address (in a form that also matches its variations, like added dots or “+” tags) so the same person can’t sign up again.
  • Messages you send us. When you use our contact form, we store your name, email address, the topic, your message, your IP address and browser, and your account if you’re logged in, so we can reply and prevent spam. We also email your name, email address, topic, message and account to our support inbox, so we can answer you from there. Messages you send from the Help & support window in your dashboard are handled the same way, along with your email address and the page you were working on.
  • Links and codes we email you. When we email you a link to confirm your email address or to reset your password, or a 6-digit code to log in, sign up or confirm a change in your settings, we store a scrambled version of the link or code, the address we sent it to, and when it expires. For a sign-up, we also keep the username you picked and how you found us until you enter the code.
  • Tips and trophy emails. We keep a record of which of these emails we’ve sent you and when, so you never get the same one twice, and a secret code for the one-click unsubscribe link in them. We also keep a list of email addresses that bounced or marked our emails as spam (we get it from SendGrid), so we stop emailing them.
  • Account milestones. We note when an account is created, when its page is first published (and published again), when its first link is added, and when the account is deleted, so we can count signups and cancellations over time. Each note holds only an internal account number, the type of event and the date.
  • Comments on our Instagram. If you comment on a post of Link.bio’s own Instagram account, we store your Instagram username, your comment and when you made it, through Instagram’s official API, so we can answer it. If your comment has a word we asked for (for example “Comment AI”), we send you one direct message with what you asked for and reply under your comment. We don’t message you otherwise.
  • Earlier username claims. If you claimed a username before accounts launched, we stored that username, your email address, your IP address and the time of the claim.

When you type a username and email into the claim form on our home page, they’re carried over to the signup form. Nothing is saved until you create your account.

How we use it

  • To create and run your account and your page, and to keep you logged in.
  • To show page owners how many people view their page and click their links (as totals only).
  • To protect your account and the service: detecting abuse, blocking repeated failed logins, and investigating problems.
  • To answer messages you send us.
  • To contact you about your account, for example about security or important changes to the service.
  • To send the emails your account needs: codes to log in or sign up, a link to confirm your email address, password reset links you ask for, and a notice when your email address or password changes. We don’t track whether you open our emails or click their links.
  • To send a few tips and trophy emails: help setting up your page in your first two weeks, a note when your page gets its first visitor, and when it earns a mystery box. At most one every 3 days. Every one has an unsubscribe link, and you can turn them off in Settings. We don’t send advertising.

We don’t sell your personal information, we don’t show ads, and we don’t use your data to build advertising profiles.

Cookies

We only use cookies that the site needs to work. There are no advertising or analytics cookies.

  • __Host-lb_session keeps you logged in. It contains only a random code, never your name or email. It lasts 30 days, and starts over each time you use the site, so you stay logged in while you keep using it.
  • __Host-lb_code is set when you ask for an email code, so the code only works in this browser and we can send you a new one. It holds a random code and the email or username you typed, and lasts a day.
  • __Host-lb_next is set only when you log in to connect an AI agent, so you come back to its Allow screen afterwards (10 minutes).
  • __Host-lb_oauth and __Host-lb_google are set only when you use “Continue with Google”: the first checks that the answer coming back from Google is for the sign-in you started (10 minutes), the second holds your Google email and name while you pick your page name (30 minutes).
  • __Host-lb_csrf protects our forms from being submitted by other websites. It lasts until you close your browser.
  • __Host-lb_own is set when you open your dashboard, so on Link.bio pages the Link.bio button and “Learn more” in the share window take you to your dashboard (or straight to your editor on your own pages) instead of telling you about Link.bio. It holds a scrambled short code for each of your page names (not the names, and nothing that logs you in), stays after you log out so these buttons can take you to the login page, lasts 400 days, and is removed when you delete your account.
  • __Host-lb_try is set when you build a page on our AI link in bio generator page without an account. It holds a random code for that page, so only your browser can claim it when you sign up, lasts one day, and is removed once the page is in your account.

Cloudflare, which protects our site, may set its own short-lived security cookies to tell people and bots apart.

Your dashboard also remembers three small settings in your browser’s local storage (not a cookie, and never sent to us): which of your pages you last picked (lb-page), the style you chose for your QR code (lb-qr-style) and, on phones, which corner you moved the mini preview to (lb-preview-side). Public Link.bio pages store nothing in visitors’ browsers. On our own site (link.bio), the tab you’re in remembers where you came from and the first page you saw until you sign up or close it (lb-src and lb-land, see “How you found us”), and if you pick a language in the footer, or answer our “see this in Spanish/Portuguese?” question, your browser remembers it (lb-lang) so we don’t ask again.

Because we only use what the site needs to work, there’s no cookie banner to accept. You can still block or delete cookies in your browser, but you won’t be able to log in without them.

Who else handles your data

We use a few service providers to run Link.bio. They only get what they need to provide their service to us:

  • Our hosting provider runs the servers where your account data is stored.
  • Cloudflare delivers and protects the website, so your requests (including your IP address) pass through it. If you aren’t logged in, our contact form also uses Cloudflare Turnstile, a check that tells people and bots apart: your browser loads it from Cloudflare, which receives your IP address and browser details.
  • Google Fonts serves the fonts on our pages and on public pages that use a custom font, so your browser contacts Google’s servers, which receive your IP address and browser details.
  • Product Hunt serves its badge on our own site and dashboard (not on public Link.bio pages), so your browser contacts its servers, which receive your IP address and browser details.
  • Amazon Web Services (Amazon S3 and CloudFront, in the United States) stores the pictures and videos you upload and delivers them to visitors of your page, so visitors’ browsers contact Amazon’s servers, which receive their IP address and browser details.
  • Google handles “Continue with Google” if you use it: you sign in on Google’s own page, and Google sends us the details listed above.
  • Twilio SendGrid (in the United States) delivers the emails we send you, so it receives your email address and the content of those emails. Open and click tracking are turned off.
  • Google Workspace hosts our own email inbox, so it receives the emails you send us and the messages from our contact form.
  • Metabase is the tool we use to look at how the service is doing (signups, pages, views and clicks). It can only read a limited copy of our data: usernames, page and link details and statistics, never email addresses, passwords, login sessions or IP addresses.
  • YouTube, Spotify and SoundCloud power the players that page owners can embed. A player only loads after a visitor taps play; from then on that provider receives the visitor’s IP address and browser details, and its own privacy policy applies. YouTube videos use its privacy-enhanced (no-cookie) mode.
  • ScrapeCreators (Web Scraping Guy LLC, in the United States) reads public Instagram, TikTok, Facebook, X and Threads profiles for “Build my page with AI” when you paste a link to one. It receives that profile’s address and returns what the profile shows publicly. It may keep copies of these public answers for a while, to answer the same request again faster.
  • OpenAI (in the United States) writes the suggestions for “Build my page with AI” when you use it. It receives what you typed, public information from the links you pasted and small previews of pictures from them. Under its terms for businesses it doesn’t use this to train its models; it may keep it for up to 30 days to detect abuse.
  • Meta (Instagram) runs our own Instagram account. We read the comments on our posts and answer them through its official API, so Meta handles those comments and messages under its own policies.
  • Calendly and Cal.com show the booking calendar when a page owner lets it open on their page. It only loads after a visitor taps that link; from then on that service receives the visitor’s IP address, browser details and anything they enter to book, and its own privacy policy applies.

We may also share information if the law requires it, or to protect the safety of our users or the public.

How long we keep it

  • Account details: for as long as you have an account.
  • Login sessions: deleted when you log out, when you log a device out from your dashboard, or when the session expires (30 days after you last used it). Expired sessions are cleaned up every hour.
  • Security counters: deleted within an hour.
  • Contact messages: kept for as long as we need them to help you, then deleted.
  • Links and codes we email you: codes work for 10 minutes, confirmation links for 7 days and password reset links for 1 hour; we delete them within a day after they’re used or expire.
  • Account milestones: kept after an account is deleted, so cancellations can still be counted. By then they can’t be linked to you: the account number belongs to nothing.
  • Emails left in a signup block: kept until the page’s owner removes them, or the page or account is deleted.
  • Records of AI page builds: kept so we can count what the service costs. After an account is deleted they hold only an internal account number.
  • Page statistics: daily totals are kept for 400 days, then deleted.
  • Comments on our Instagram posts: deleted from our records after 90 days.
  • Tips and trophy email records: deleted with your account. Addresses that bounced or marked our emails as spam stay on our do-not-email list.
  • Safety records (suspensions, reviews of flagged pages, blocked websites and the blocked email addresses of suspended people): kept as long as we need them to keep the service safe, also after an account is deleted. By then they hold only an internal account number, the reason, the date and, for someone we blocked from signing up again, their email address.
  • Deleted links: kept in the trash for 30 days so you can undo a mistake, then deleted with their thumbnails.
  • Pictures and videos you upload but don’t save: deleted within about a day, as are the pieces of a video upload that didn’t finish.
  • Backups: we keep daily backups of our database for 14 days, so deleted data disappears from backups within 14 days.
  • Server logs: kept for a limited time for security and troubleshooting, then deleted.

If you delete your account, we immediately delete your account details, your sessions, your pages, their statistics and your uploaded pictures and videos (and they leave our backups within 14 days). Your username becomes free for someone else to claim.

Your choices and rights

You can download a copy of your data and delete your account yourself, at any time, in your dashboard’s Settings. You can also ask us to show you the personal information we hold about you, correct it, give you a copy, or delete it along with your account. You can also object to how we use it. Email us at support@link.bio from the address on your account and we’ll respond within 30 days. Depending on where you live, you may also have the right to complain to your local data protection authority.

Security

The whole site uses HTTPS. Passwords are hashed with Argon2id, login cookies can’t be read by scripts on the page, only a scrambled version of your login code is stored on our side, and you can log out of every device at once from your dashboard. No system is perfectly secure, so if you set a password, please use one you don’t use anywhere else.

Children

Link.bio is not meant for children under 13, and we don’t knowingly collect their information. If you believe a child under 13 has created an account, please contact us and we’ll delete it.

Changes to this policy

If we change this policy, we’ll update the date at the top. If the changes are significant, we’ll let you know through the site or by email before they take effect.

Contact

Questions about privacy? Email support@link.bio.

Link.bio
AI builder MCP Features How it works Examples Link in bio For musicians For small businesses For athletes FAQ Contact Terms Privacy Cookies
Link.bio - Paste your link, we build your page that your AI runs | Product Hunt
English Español Português
© 2026 Link.bio. Made for people who make things.