Bizzit

Getting live

The site hangs on an account, not on a tab you will close.

By Bizzit � � Updated

Why Bizzit uses Google sign-in to build | Bizzit guide

You cannot publish a live Bizzit address as a ghost. Google sign-in attaches the brief, the generated site, and the hostname to an account. That is how you get back to the studio tomorrow without emailing a screenshot to yourself. It is also how Pro, domains, and a Stripe key stay with the same login. Sign-in is not a Google ranking boost, not a review widget, and not a Workspace mail setup. Privacy details live on the privacy page; this page is why the button is there before Cipher works.

Google sign-in owns the project: brief, preview, slug, and later Pro features. It is not anonymous hosting. It is not Google Business and not Workspace email. We store the account id, name, email, the brief, and the generated site as the privacy page describes.

What sign-in unlocks

Create, preview, publish free, dashboard. Turns counted on that account's project. Later: domain, checkout key, overnight tab. Without it, there is no you.bizzit.io that you can reclaim.

What we are not doing with Google

We are not posting to your Business Profile. We are not reading Gmail. We are not selling a Workspace bundle as a Bizzit SKU. CNAME plus Workspace MX is a DNS essay, not this button.

Why not a password form

Google sign-in is the shipped auth. We are not documenting a second identity SKU here. Use an account you will still have next year. A throwaway login is how people lose shops.

Shared shops and sign-in

There is no seats product on pricing. Two owners should not share a password folklore. Sit together, or pick the person who will pay Pro. Do not mint a second fifty turns with a second Google user as a plan.

Not a ranking factor

Not GBP

Not Workspace

Not anonymous hosting

If sign-in fails

Pop-up blockers, third-party cookie theater, and the wrong Google user in the chooser are the usual villains. Try a browser that is not blocking the OAuth redirect. Confirm you finished the Google screen. We cannot complete sign-in from a blog paragraph.

After you are in

Write the brief. Preview. Publish when facts are true. The account is the string that ties those together.

  1. Choose the Google user you will keep
  2. Finish sign-in on Create
  3. Build the preview
  4. Do not switch users mid-project without expecting a different account's dashboard

Limits and caveats

This is not the privacy policy. It is not legal advice. If you need to know what is stored, read /privacy.

If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.

What to do after you read this

If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Getting live. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.

Tools that actually do this job

These are public pages. Use them when the job is this job. They are not a second product you have to buy.

Questions people actually ask

Can I use an Apple or email login instead?

Pricing and Create document Google sign-in. We do not list other identity SKUs here.

Does signing in publish the site?

No. Sign-in opens the studio. Publish is a later explicit action.

Will Google see my unpublished brief?

Create is noindex. Sign-in is auth with Google. The brief lives on our project record as privacy describes. Do not put secrets in a brief you might publish.

Can I transfer a site to another Google user?

We do not document a transfer SKU on this page. Build on the account that should own it.

Start free