Builder Profile lets indie builders make a public profile of their projects, numbers, goals and updates. This policy explains what we store, why, who helps us run the service, and how to delete your data. Builder Profile is run by {OPERATOR_NAME} (“we”, “us”). Questions go to {CONTACT_EMAIL}.
The short version: we keep only what is needed to sign you in and show your profile. We don’t show ads, we don’t sell or rent your data, and we don’t use third-party trackers. Anything you publish is public on purpose.
Signing in
You can sign in with your email address, and with Google or X (Twitter) once those options are switched on. Sign-in is handled by Supabase Auth.
- Email: we send a one-time sign-in link and code to your address. There is no password.
- Google or X: the provider confirms who you are and shares basic account details with us: your email address (if the provider gives one), name, profile picture link and, for X, your username. We never see your Google or X password, and we don’t post anything on your behalf.
We keep your email address and these account details so you can sign in again and so we can contact you about your account.
What we store
- Your account: email address, sign-in method, account details from Google or X if you use them, and when the account was created and last signed in.
- Your handle: the name in your profile address, like
/alexbuilds. - Your profile: everything you put into the editor — name, bio, links, projects, numbers, goals, achievements, updates and style choices. We keep a private draft you are working on and, after you publish, the published version.
- Your photo: if you upload one, a 400×400 copy made in your browser. It is stored with Supabase and can be opened by anyone who has its link, because it is shown on your public profile. If you signed in with X, your profile can use your X picture instead, loaded from X.
- View counts: how many times your public profile was opened each day, and from which website (for example
x.com). We count views only as daily totals. We don’t record visitors’ IP addresses, browsers or devices, and we can’t tell who a visitor was. Your own visits while signed in aren’t counted. - Share counts: daily totals of how often the share buttons on your profile and share cards were used (Post on X, download, copy link), recorded the same way as views.
The editor may also keep a copy of your draft in your browser’s local storage, together with your light or dark theme choice. That copy stays on your device and is not sent to us until you save or publish.
What is public
Your published profile and handle are public: anyone with the link can see them, they can appear in search results, and sites like X show a preview card when the link is shared. Your draft, email address and view counts are private to you.
Numbers on a profile, such as revenue or user counts, are entered by the profile’s author and shown with a note saying so. We don’t check them. Only publish numbers you are comfortable sharing with the world.
Cookies
We use cookies only to keep you signed in. They are set by our sign-in system and are needed for the site to work. We don’t use advertising, analytics or tracking cookies, so there is nothing to opt out of. Site-wide visit statistics (below) work without cookies.
Who helps us run the service
We use a few providers to run Builder Profile. They process data only to provide their service to us.
- Supabase — database, sign-in and file storage. Our data is stored in the United States (US East).
- Vercel — hosts the website. Like any web host, Vercel handles technical request data such as IP addresses to deliver and protect the site. We don’t copy that data into our database or use it for analytics.
- Vercel Web Analytics — counts page visits across the site without cookies. It sees the page, the referring website, and the country and device type, and does not identify individual visitors.
- Sentry — receives error reports when something breaks: the page, the error, and the browser and system version. Reports don’t include your email, cookies or IP address.
- Cloudflare Turnstile — checks that the email sign-in form is used by a person, not a bot. Cloudflare looks at signals from your browser to do this and does not use them for advertising.
- Email delivery — sign-in emails are sent through an email provider (Resend, or Supabase’s built-in email while we test). It receives your email address and the message.
- Google and X — only if you choose to sign in with them, as described above.
If you live outside the United States, your data will be transferred to and stored in the United States. We share data with others only if the law requires it.
Stripe (planned)
We plan to let you connect Stripe so revenue numbers can come from your Stripe account instead of being typed in. This is not live yet. When it launches it will be optional and read-only: we will read only what is needed to calculate the numbers you choose to show, never move money, and you will be able to disconnect at any time. We will update this policy before it goes live.
How long we keep data
We keep your data while your account exists. When you delete your account, we delete your account, handle, draft, published profile, uploaded photos, view and share counts. Our own weekly database backups are encrypted and kept for up to 90 days; copies in our providers’ backups, if any, expire on their normal schedule. Links to your profile stop working, though search engines and sites that already showed a preview may keep a cached copy for a while.
Your choices and rights
- You can edit or unpublish your profile at any time.
- In Settings you can download a copy of your data and delete your account yourself. Deletion happens right away.
- You can also ask for a copy of your data, ask us to correct it, or ask us to delete your account by writing to {CONTACT_EMAIL}. We will answer within 30 days.
Children
Builder Profile is not meant for children. Don’t use it if you are under 16.
Changes to this policy
If we change this policy, we will update the date at the top. If a change affects how we use data you already gave us, we will tell you by email before it takes effect.
Contact
{OPERATOR_NAME}, {CONTACT_EMAIL}. See also our Terms of Service.