This is a draft. It is not in force yet.

Privacy policy

Draft for legal review. Not in force until reviewed.

Effective date: [effective to be added]

This policy explains what personal data bio.bid collects, why, who receives it and how long we keep it. It also explains your rights under the General Data Protection Regulation (GDPR).

It applies to three groups of people:

Who is responsible for your data

The operator of bio.bid, named below, is the controller of your personal data.

The name and postal address of the operator of bio.bid

Write to us about privacy at info@bio.bid.

Creators decide what they publish on their pages. If a page shows your personal data without your permission, report the page.

Data about creators

Sign-in

We do not use passwords. When you ask to sign in, we email you a 6-digit code and a link. Either one signs you in. To do this, we store:

Building a page before you sign up

You can build a page in the editor at app.bio.bid before you have an account. Your browser keeps the page on your device for 7 days after your last change, and each picture that you add for 90 days. We do not receive the page until you claim a handle or sign in. The pictures upload to us when you sign in in the same browser.

While you build, our server checks whether the handles that you type are free and suggests other handles. If you import a page, our server reads it and the start of each picture on it to show you a preview. Your browser then loads the pictures from the site they came from. We do not store these checks or previews.

Handle claims

When you claim a handle, we email you a link that signs you in. If you claim with a page that you built, the email also has a 6-digit code. We store hashes of the link's token and the code, as for sign-in. The link and the code work for 24 hours. After 5 wrong tries, the code stops working.

For each claim, we store:

When you sign in, we make your page from the claim. We keep the claim with your handle until you delete your account.

Names kept for well-known accounts

We keep some handles for well-known accounts. To claim one, you prove that the account is yours in one of these ways:

Your page

We store what you add to your page: your name, photo, bio, links, images, videos, embeds, contact details, products, social links, theme and the 18+ setting. We keep the last 30 published versions of your page.

We store the images and videos that you upload in Cloudflare R2. We make large images smaller before we store them.

When you add a link, we send its web address to Google Web Risk to check it for malware, phishing and unwanted software. While the link is on your page, we check it again from time to time. Our server also fetches the icon of the linked site. For music and video links, our server asks the provider, such as Spotify or YouTube, for the artwork, title and artist, and stores the artwork.

If you ask us to import a page from another service, such as Linktree or Stan, our server reads that public page. If the site refuses our request, or builds its links with scripts, we load the page in a browser that Cloudflare runs for us (Cloudflare Browser Rendering). For some services, such as Komi, we get the same public data directly from the service. After you sign in, an import copies up to 40 of the page's images and videos into your media. Each image can be up to 5 MB, and each video up to 20 MB. An import can also get the artwork of music and video links from their providers.

Data about visitors

Creators' public pages load no analytics script. They set no cookies, except the 18+ cookie that "Cookies" explains. We do not show ads.

Views and clicks

We count page views and link clicks on our own server, without cookies. We store the counts in Cloudflare Workers Analytics Engine. For each view or click, we store:

We make the daily visitor hash from the IP address, the browser's user agent and a random value called a salt. We make a new salt for each day and delete it after two days. After that, nobody, including us, can trace the hash back to an IP address or link it to visits on other days. We do not store the IP address itself.

Creators see only totals for their own page, for up to the last 90 days. They do not see data about single visitors.

Our own website and editor

Our own pages and the editor at app.bio.bid use DataDad's app and web analytics to count visits and actions, such as a claimed handle or a published page. Our own pages are the home page, the import page, these legal pages, the pages that confirm a claim and show a claim (bio.bid/waitlist/{code}), and the "page not found" page. DataDad sets no cookies. It receives:

We never send DataDad your email address or text that you type. Creators' public pages, their 18+ warning, their link redirects and the report form do not load DataDad.

Delivery and security

Cloudflare handles every request to bio.bid. It processes the visitor's IP address and request details to deliver the page and to block attacks.

To stop abuse, we limit how many requests one IP address or account can send in a short time. Cloudflare keeps these counts only for that time.

Our code keeps logs of requests and errors in Cloudflare Workers Logs, so that we can find and fix faults. The logs hold details of each request, such as its address and result. Cloudflare deletes them after 7 days.

Embeds

Embedded content, such as a YouTube video or a Spotify player, shows a picture and a Play button. The player does not load until you tap it. When you tap it, your browser connects to the provider, and the provider's own terms and privacy policy apply. The provider can then receive your IP address and set its own cookies. For YouTube, we use youtube-nocookie.com.

We store most of these pictures on bio.bid. The picture of a YouTube Short, and of a YouTube video that we have no copy for, comes from YouTube's image server (i.ytimg.com). Your browser then asks YouTube for that picture before you tap.

A creator can choose to show a full player instead. A full player loads when it comes into view on the page, without a tap. The provider then receives data from your browser, as above.

Feeds and live status

A creator can show the newest entries of a podcast, blog or YouTube feed. Our server reads the feed every hour and stores its newest entries: their titles, links, dates and picture addresses. Your browser loads the entries' pictures from the sites they come from, which then receive your IP address.

A creator can show when they stream on Twitch or Kick. Every two minutes our server asks Twitch and Kick which of these channels are live, and stores the answer and the stream's title. We send Twitch and Kick only the channel names, never data about visitors.

Email sign-ups

A creator can add a form where you leave your email address to get their news. When you send the form, we store your email address, the page and the time, and we email you a link to confirm. The creator receives your address only after you confirm. If you do not confirm within 7 days, we delete it.

After you confirm, the creator can see your email address and the time you confirmed, and can download them to send you their news with their own tools. For these addresses, the creator decides why and how they use them, and their own privacy terms apply. bio.bid stores them for the creator and does not use them for anything else.

The confirmation email has a link that takes your address off the list at any time. The creator can also remove it. When the creator deletes their account or page, we delete the list.

Data from forms, reports and email

We use Cloudflare Turnstile on the handle claim, sign-in, ownership review and report forms to stop bots. The email sign-up forms on creators' pages use a hidden field and rate limits instead, so that the page needs no script. Turnstile runs a check in your browser and sends the result to Cloudflare. Our server then sends the result and your IP address to Cloudflare to verify it.

Anyone can report a page from the Report link at the bottom of the page. If you report a page, we store the page, the reason and the details that you give. We also email the report to the operator at abuse@bio.bid. The form does not ask for your name or email address, and we do not store your IP address.

If you email abuse@bio.bid, Cloudflare Email Routing forwards your message to us. We use your email address and message only to handle your request.

We send sign-in, confirmation, sign-up confirmation and report emails through Cloudflare Email Service. We do not send marketing email unless you agree to it.

Cookies

The editor at app.bio.bid sets one cookie, "sid", after you sign in, to keep you signed in. It is httpOnly and secure, and only app.bio.bid can read it. It lasts 30 days, or until you sign out. The editor cannot work without it, so we do not ask for consent.

Public pages on bio.bid set one cookie, "age_ok", and only when you confirm that you are 18 or older on a page or link with the 18+ warning. It holds no personal data. It saves your answer for 30 days, so that you do not see the warning again on each page. We do not use cookies for analytics or ads.

The editor also keeps data in your browser's storage on your device:

You can delete this data in your browser's settings.

Why we use your data

To provide the service

We use data to perform our contract with you, or to take steps that you ask for before it starts:

Legitimate interests

We use data where we have a legitimate interest that your rights do not override. This covers:

You can object to this use at any time, as "Your rights" explains.

Consent

Embedded content loads only after you tap it, except a full player that a creator chose (see "Embeds").

Legal obligations

We use data when the law requires it. For example, we report child sexual abuse material to the authorities, and we answer valid orders from courts and authorities.

Who receives your data

We do not sell personal data. We share it only with these recipients:

We host our fonts ourselves, so pages do not contact a font service.

International transfers

Cloudflare and Google are based in the United States. Cloudflare also processes data in data centers in many countries.

When personal data leaves the European Economic Area, we protect it in one of these ways:

You can ask for a copy of these safeguards at info@bio.bid.

How long we keep data

Your rights

Under the GDPR, you have the right to:

You can export your data as JSON and delete your account in Settings. For other requests, write to info@bio.bid. We may ask you to confirm the request from the email address on your account. We answer within one month.

We cannot link a daily visitor hash to a person, so we usually cannot find statistics about one visitor.

You also have the right to complain to a data protection supervisory authority. You can do this in the EU country where you live or work, or in Czechia.

Automated decisions

We do not make decisions about you that have legal or similar effects based only on automated processing.

Our link check blocks a link automatically when Google Web Risk marks it as unsafe. If you think we blocked a link by mistake, write to abuse@bio.bid and a person will review it.

Our check for names kept for well-known accounts compares the Instagram or TikTok username with the handle automatically. If they are not the same, you can ask for a review by a person.

Children

You must be at least 16 years old to claim a handle or create an account. If we learn that a creator is under 16, we delete the account.

Security

We protect your data in these ways:

If a breach puts your rights at risk, we tell you and the supervisory authority, as the law requires.

What you must give us

You must give an email address to claim a handle or create an account, because we send sign-in codes and links to it. Everything else is your choice.

Changes to this policy

We may update this policy. We post the new version on this page with a new effective date. For important changes, we email creators before the changes take effect.

Contact

The name and postal address of the operator of bio.bid