Privacy policy
What Bunfolio collects, why we collect it, who else sees it, and how to get it deleted. In plain language, with no clauses we cannot back up in the product.
Last updated [[EFFECTIVE DATE]]
The short version
Bunfolio builds a public portfolio site out of information you deliberately give us. We keep your account details from Google sign-in, the content you write for your site, and a count of how many people visit it. We send the text you write to Google Gemini so it can draft and edit your site copy. We do not run advertising, we do not sell anything to data brokers, and we do not load third-party tracking scripts.
Almost everything you type is meant to be published. Once your site is live, anyone on the internet can read it — including the contact email address you put on it.
Who we are
Bunfolio is operated by [[COMPANY LEGAL NAME]], registered at [[REGISTERED ADDRESS]]. We are the party responsible for the personal data described in this policy. You can reach us about anything on this page at [[CONTACT EMAIL]].
One exception matters: messages that visitors send through the contact form on your published site are collected for you, not for us. We store them so you can read them; what happens with them afterwards is your decision. See “Messages sent to your site” below.
Your account
You sign in with Google. When you do, we receive your name, your email address, your Google account identifier and the URL of your Google profile picture, and we store those on your account record so we can recognise you next time and show you who is signed in. We also mark the account as email-verified, because Google has already verified it, and we record whether the account has staff access to our admin panel.
Our database has a password column, inherited from the framework starter kit we built on. The product only offers Google sign-in, so for accounts created that way the column is empty. If a password is ever set, it is stored as a one-way hash. We never store or transmit a password in readable form, and nobody at Bunfolio can read one.
While you are signed in, your login session is stored server-side. That session record includes your IP address and browser user-agent string, which is how the framework detects a hijacked session. It is deleted when the session expires or you sign out.
The content you write for your site
Everything you enter in the setup wizard or later edit is stored against your account so we can render your site:
- Your display name, brand name, headline and subheadline.
- Your about text, statistics, services and the bullet points under them.
- Your skills and the tools you work with.
- Your contact email address, location, and any social or profile links you add — LinkedIn, GitHub, your own website, freelance platform profiles.
- Your username, which becomes your web address, and whether the site is currently published. We pick a username for you from your name when you first sign in, so you always have a working address; you can change it later.
- The domain of your own you connect, if you connect one. We store the domain name and the date we confirmed its DNS points at us.
- Your projects: title, description, image, the services each one involved, an optional link, and an optional client quote with the name of the person who gave it.
- Images you upload for your logo or photo, up to 2 MB each. These are stored as ordinary files on our public file storage and served from a public URL, so treat an uploaded image as published the moment you upload it.
We use this content for one purpose: to build and serve the site you asked us to build. It is the substance of the service you signed up for, so we process it to perform our agreement with you.
Importing from LinkedIn
The wizard offers to save you typing: paste the address of a public LinkedIn profile and our server fetches that page and reads what it can from it — name, headline, about text, profile photo URL, location and listed skills — then drops the result into the wizard fields for you to check and change.
This is optional and it is never a requirement. The manual form works completely on its own, and nothing imported is saved to your site until you finish the wizard. The fetch happens from our server, so LinkedIn sees a request from us rather than from your browser. Depending on how the platform is configured, the same lookup may go through a third-party profile-data provider or through a Google Search query made by our AI provider; both are described below.
Please only import a profile that is yours, or one you have clear permission to copy from.
AI drafting, and what we send to Google Gemini
Bunfolio writes the first draft of your site with an AI model. That model is not ours: it is the Gemini API, run by Google. When you finish the wizard, ask for a suggested about section or skill list, generate a project description, or edit your site through the chat box, we send the relevant material to Google over an encrypted connection and use the reply as your site copy.
What we send is the wizard answers and site text involved in that particular request, plus your name where the prompt needs it — for example to write about you in the first person. For a LinkedIn import it can also include text read off the profile page you pasted. We do not send your Google account identifier, your session, or the messages visitors send you.
Some of these requests let the model run a Google Search to check facts, which means the search terms derived from your content reach Google Search as well. Google processes this data as an independent provider under its own terms; we have no control over how it operates its models.
If the platform is running without an AI key configured, the wizard falls back to assembling your site from your answers alone, and nothing goes to Google Gemini.
What a published site makes public
When you publish, your site is served to anyone who asks for it, at your subdomain and at the equivalent path on our main domain. If you have connected a domain of your own and we have confirmed it points at us, the same site is served there too. There is no password on any of those addresses and no way to make the site visible to only some people.
Everything in your site content becomes public at that point, including the contact email address you chose to display, your photo, your links and your project descriptions. Your site also publishes a sitemap, so search engines can find and index it, and search engines keep their own copies that we cannot delete for you.
Unpublishing takes the public pages down immediately — requests for them return “not found” — but it does not remove pages already cached or archived elsewhere on the internet. If you would rather something was never public, do not put it on the site.
Visitor counting
Your dashboard shows how many unique people visited your site each day. We collect that ourselves, and we designed it so it cannot be turned back into a person or into a trail.
When a published page is rendered, we combine the visitor’s IP address, their browser user-agent string and today’s date, run the three through a SHA-256 hash, and store only the resulting 64-character string alongside your site’s id and the date. The raw IP address and user-agent are never written down; the hash cannot be reversed to recover them.
Because the date is part of what gets hashed, the same visitor produces a different hash tomorrow. That is deliberate: the record can tell you “two people came today” but it cannot follow anyone from one day to the next, and it cannot connect a visitor to a visit on someone else’s Bunfolio site. We count only real public page views — previewing your own site does not add to the count.
Messages sent to your site
Your published site has a contact form. When a visitor uses it, we store the name, email address and message they typed against your site, and show them to you on your leads page. We hold them for you; we do not use them for our own purposes, and we do not email them anywhere.
If you are the site owner, those messages are yours to look after. You decide what to do with them and how long to keep them, and you are the person the sender is really contacting.
If you sent a message through someone’s Bunfolio site and you want it removed, the quickest route is to ask the site owner. You can also write to us at [[CONTACT EMAIL]] and we will act on it.
Who else processes your data
We keep this list short on purpose. Today it is:
- Google, for sign-in. When you choose “Sign in with Google”, Google authenticates you and tells us your name, email address, account id and profile picture URL.
- Google, for the Gemini API. It receives the site content described in the AI section above, and may run a Google Search on material derived from it.
- LinkedIn, if you use the import. Our server requests the public profile page you pasted.
- A third-party profile-data provider, only if the platform has been configured with a key for one, and only for a LinkedIn import you started.
- [[HOSTING PROVIDER]], which runs the servers and storage this application and its database live on.
We do not sell personal data, we do not share it for advertising, and we do not hand it to anyone else except where the law obliges us to. If we add a processor that changes this picture, we will update this page.
How long we keep things
Your account and site content stay until you or we delete them, because a portfolio is only useful while it is up. Login sessions expire on their own. Visit records are kept as daily counts for as long as your site exists.
Deleting an account removes it all together: the database is set up so that deleting a user also deletes their portfolio, their projects, their visit records and the contact messages their site received. Deletion is immediate and permanent — we do not keep a copy for you, so export anything you want to keep first. Ordinary infrastructure backups may hold data a while longer before they age out.
Your rights
You can ask us to:
- show you what we hold about you;
- give you a copy of your site content in a portable form;
- correct anything that is wrong — most of it you can edit yourself in the app;
- delete your account and everything attached to it;
- stop processing your data in a particular way, where the law gives you that right.
Write to [[CONTACT EMAIL]] from the address you signed up with and we will handle it. We may need to ask a question to be sure it is really you. Depending on where you live you may also have the right to complain to your national data protection authority.
Security
Traffic to Bunfolio is served over HTTPS. Requests to Google and to any other provider are made over encrypted connections. Passwords, where they exist at all, are stored only as hashes. Access to the admin panel is restricted to staff accounts flagged for it.
No service can promise perfect security, and we are not going to pretend otherwise. What we can promise is that we keep the amount of personal data in the system small, which is the most reliable protection there is.
Children
Bunfolio is built for working freelancers and is not intended for children. You need to be at least [[MINIMUM AGE]] to have an account. We do not knowingly collect data from anyone younger; if you believe a child has an account, tell us at [[CONTACT EMAIL]] and we will delete it.
Changes to this policy
When the product changes, this page changes with it. The date at the top always reflects the current version. If a change materially affects how we handle your data, we will make a point of telling account holders rather than quietly editing the text.
Contact
Questions, corrections, deletion requests and complaints all go to [[CONTACT EMAIL]], or by post to [[COMPANY LEGAL NAME]], [[REGISTERED ADDRESS]].