Privacy
Last updated 10 October 2026
SoloPlus.ai is a community where people building products share what they made and what they learned. This page says what we hold about you, why we hold it, and how to get rid of it. It is written to be read rather than to be survived.
What we collect
Five things, and nothing else.
Your account
Your name and email address. If you join with an email and password, the password is handled by Google's Firebase Authentication and is never seen or stored by us. If you join with Google, we receive your name and email address from your Google account — nothing else, and no access to anything in it.
What you put on your board
The products you add, their names and descriptions, which stage they are at, and who you have chosen can see them. Along with them, whatever you attach: links to videos, written lessons, and documents you upload. You decide who can see each product, and you can change that or delete it at any time.
Your connected machines
If you connect Claude Code or Codex to your account to receive the skills, we hold a record of each connection: when it was made, which tool it is for, and when it last asked for the skills. The machine keeps a private token in your home folder; we keep only a fingerprint of it, so nobody can read it back from us. You can disconnect every machine at once from the Connect page.
Field reports
When one of the skills finishes, it writes a short field report on your machine. If you have said yes to field reports, the report is also sent to us, automatically. It holds the facts of the run — which skill, which version of it, which tool, the questions it asked you, and whether the document got written — and short notes written by the skill: what was unclear in its instructions, where you got stuck, and what it had to do that the skill didn't say, with your one-line verdict if you gave one. The notes may mention what you are building in passing. They are summaries: never your code, your files, or the conversation itself.
We keep reports with your account. We read them to improve the skills, and the facts in them will help us guide you through the method later. Nothing is sent unless you say yes — for one report, or for all of them — and you can switch reports on or off at any time on the Connect page. A report written while they are off stays on your machine.
In Claude Code, the SoloPlus.ai bar has a Send feedback button. When you press it, Claude asks what you'd like to tell us, and sends just the words you type — whether field reports are on or off, because you chose to send them. Nothing else goes with them: not your code, your files, or the conversation. We read feedback the way we read reports.
A note of each email we send you
When we email you — a sign-up code, a welcome — we keep a short note that we did: which kind of email it was, the address it went to, when, and whether it was delivered. The note holds nothing of the email itself: not the subject, not the text, and never a sign-up code.
A count that stops the forms being used to send email in bulk
Anyone can type any address into the sign-up and password-reset forms, so we count how many emails they send in an hour: for the site as a whole, and for each network address that asks. The network address is scrambled before it is stored, so the count holds no address anyone could read, and nothing joins it to an account. Each count is deleted within about a day.
Two cookies, and what each one is for
The first is named __session. It exists so you stay signed in between visits and it cannot be read by scripts in the page. It is not used to follow you anywhere, and it is cleared when you sign out.
The second is named sp_seen, and it is how we count how many people reach our front page. All it holds is the number 1 — the fact that this browser has been here before, so a first visit can be told apart from someone coming back. It is not an identifier: it contains nothing about you, nothing that could be linked to you or to your account, and every visitor's copy of it is identical to every other visitor's. On a browser whose owner asked for it not to be counted — something only the people who run this site can do, for their own browsers — it holds the number 0 instead. It cannot be read by scripts in the page, and it lasts a year.
What we count, and what we don't
We count how many people arrive at our front page, and whether each visit is a first one. Each visit also adds one to a few daily tallies: which site it came from (only from a short list of sites, such as LinkedIn or a search engine, or a tag on a link we posted ourselves, and otherwise just “somewhere else”), whether it was on a phone or a computer, and the browser's language. Bots are counted on their own. We also count how many times the sign-up page is opened and how many sign-ups are finished each day. Visits from anyone signed in are not counted. So that automated scripts can't inflate these numbers, the server briefly remembers how often an address has loaded the front page or the sign-up page in the last hour, and stops counting after a few. That tally is kept only in the server's memory, scrambled, is never saved anywhere, and is forgotten within the hour.
That is the whole of it: running totals for each day, with nothing recorded about who any of those people are — no email addresses, no IP addresses, no device fingerprints, no record of a visit that could be traced to a person or joined up with an account.
There is no advertising here, no third-party trackers embedded in these pages, and no analytics service watching what you do — no Google Analytics, nothing of that kind. We do not buy or sell data about you. If you pay for a plan, your card details go to Polar, not to us, so we hold no card or payment details at all.
Who else touches it
Google, for running the site. It runs on Google Cloud — Firebase Authentication for signing in, Cloud Firestore for the boards, Cloud Storage for uploaded documents, and Cloud Run for the site itself. Data is stored in Google's United States region. Google processes it on our behalf, under their terms, and for no purpose of their own. Like any web host, Google Cloud keeps standard request logs — the network address a request came from, the browser, and the page asked for — for about 30 days, so that problems with the site can be looked into.
Polar (polar.sh), if you choose a plan. Polar is the seller of every plan, so when you go to checkout we send it your email address and an account number that links the purchase back to your account. Your card details go to Polar directly and never reach us; Polar tells us only which plan you have and whether it is active. Its own privacy policy covers what it does with them.
Resend (resend.com), for sending email. When we email you, Resend receives your email address and the email itself — which may include your name in the greeting, or a sign-up code — and delivers it. It handles them on our behalf, only to deliver that email and report whether it arrived, and its own privacy policy covers how.
What other people can see
Every product you add starts Private, visible only to you. You can change any product to Members, which makes it readable by people signed in to SoloPlus.ai, or Public, which means anyone with the link can read it without signing in. Public is genuinely public: treat it as publishing. Your name appears alongside anything you share, which is the point — the community is people, not anonymous posts.
How long we keep it
Until you remove it. Deleting a product deletes everything attached to it, including the files you uploaded. If you want your whole account and everything in it deleted, email inbar@soloplus.ai and we will do it.
Your rights over it
You can ask us what we hold about you, ask us to correct it, ask for a copy, or ask us to delete it. Email inbar@soloplus.ai. There is one person answering that address, so expect a human reply rather than an instant one.
Children
SoloPlus.ai is not intended for people under 16, and we do not knowingly hold information about them. If you believe a child has an account here, email us and we will remove it.
Changes
If this page changes in a way that affects what we do with your information, we will say so here and change the date at the top. The site is early and being built in the open, so it will change.