Privacy · last updated 4 October 2026

What StaFeb knows about you

Founders put unfinished ideas into StaFeb, and that deserves a straight answer about where they go. Here it is.

The short version

No account? Nothing leaves your browser.Your startups stay on your own device.

Signed in? Only your team sees it.Enforced by the database, not just the website.

Nothing is sold, ever.No ads, no data brokers, no analytics companies.

You are not tracked.No analytics and no tracking cookies.

The founder can see the database.He runs it. Said plainly rather than buried.

Ask, and it is deleted.All of it, with nothing kept back.

Without an account

You can use the whole workspace without signing in. Your startups are then saved in your browser's own storage on this device. They are not sent to StaFeb or anyone else, and clearing your browser's site data deletes them — which is why Settings has an Export button.

The browser also keeps a few small notes for the app's own use: whether you have seen the walkthrough, and, while you are signing in, the page to bring you back to. They stay on your device.

Two things do reach a server even without an account: the Feedback button, which sends your message (and which page you were on) to StaFeb, and the public board, which is read from StaFeb's database when you open it.

With an account: what is collected

Only what the features you use actually need.

Your email address: To sign you in. If you use an email link, the link is sent to it. Nothing else is ever sent to it: no newsletter, no marketing.
Your name: Only if you sign in with Google, which passes on the name on your Google account. If you use an email link instead, StaFeb uses the part of your email before the @.
Startups you save to your account: Everything in that workspace — problem, assumptions, evidence, decisions, features, tasks, people, metrics, listings — stored as one record so it syncs across your devices and your team.
Team membership: Which startups you belong to, as owner or editor, with your email address.
Invites: The email address you invite, which startup it is for, and who sent it.
Board listings: When you publish a listing: its title, description, skills, commitment and location, plus your startup's name and one-line description. These are public — anyone can read them without an account.
Applications: When you apply to a listing: the name you give, your email address, your message and any link you add.
Feedback and reports: What you write, which page you were on, and — if you are signed in — your account and email, so a reply is possible.
A sign-in session: A token kept in your own browser so you stay signed in between visits. Signing out removes it.

There is no age, phone number, location, gender or college field. None of it is needed, so none of it is asked for.

Who can see what

The whole policy in one table. Everything not ticked is closed to that person.

Your…	Anyone	Your team	A startup you apply to	The founder
Startups (signed out)	— No	— No	— No	— No
Startups (saved to your account)	— No	Yes	— No	Yes
Email address	— No	Yes	If you apply	Yes
Published board listings	Yes	Yes	Yes	Yes
Applications you send	— No	— No	Yes	Yes
Feedback and reports	— No	— No	— No	Yes

In detail:

Anyone at all: Only the open listings on the public board. A visitor with no account can read those and nothing else in the database.
Your team: Everyone you invite into a startup can read and edit all of it, and can see the email address of everyone else on that team. The owner can see pending invites.
A startup you apply to: Its team sees your name, email, message and link, so they can get in touch. You can see your own applications and their status. Nobody else can.
Other members: Nothing of yours, beyond any listings you have published. This is enforced by rules inside the database, so it holds even if the website itself were broken.
Whoever runs the database: Everything in it. StaFeb is run by its founder, Vishveshwar Raj Soni, who can read the database directly; anyone who runs a service and tells you otherwise is not being straight with you. He reads feedback and reports because that is how StaFeb gets better. He has no interest in your startup's ideas, and they will not be used, shared or published.

Companies involved

StaFeb has no servers of its own. These services make it work, and each is listed because each touches something of yours.

Supabase: Holds the database and handles sign-in. Everything listed under “with an account” lives here. It also sends the email sign-in links.
Netlify: Serves the website. Like any web server it keeps routine request logs, which include visitors' network addresses.
Google: If you choose to sign in with Google, Google tells StaFeb your name and email address, and nothing else. Separately, the site's fonts are loaded from Google Fonts, so Google sees that a browser at your network address loaded them.
jsDelivr: Delivers the code library the workspace uses to talk to Supabase. Like Google Fonts, it sees your network address when the page loads.

There is no analytics service, no advertising network and no tracker. If that ever changes, it will be written here first.

What will never happen

Your data will never be sold. StaFeb is non-profit, and your startup is not the product.
Your ideas will never be used to build a competing product or handed to anyone who would.
You will never be emailed things you did not ask for. Sign-in emails only.
Your data will never be handed over quietly. If a law ever required disclosure, you would be told, unless telling you were itself unlawful.

Your data is yours

Change it: Anything in a workspace can be edited or deleted from inside the app, at any time.
Get a copy: Settings → Export this startup or Export all startups downloads everything as a file, whenever you like.
Delete it: As owner, Settings → Delete removes a startup from the database for everyone, along with its board listings, the applications to them and its invites. As a team member, Leave removes you. To delete your whole account, send a message with the Feedback button while signed in, saying “delete my account”; it will be done and confirmed to your email. Nothing is kept back.

Honest caveats

StaFeb is in beta and run by one person, not a company with a security team. Everything above is true, and the protections described are real and enforced by the database. But it is a small project, and treating it as though it had the resilience of a large organisation would be a mistake.

Practical advice: sign in with Google, so there is no password here at all, and don't put anything in a workspace that would genuinely harm you if it were exposed. That is good advice for any young platform, this one included.

If you are under 18, please use StaFeb with a parent's or guardian's knowledge.

If this policy changes in a way that affects you, the change and its date will be shown here. It will not be altered quietly.