Accounts and privacy
Local and connected accounts, signing in and out, where your saved work is kept, and every case in which something leaves your browser.
You need an account only for Contract Graph and the Postman companion. Everything else works signed out. An account is free, and nothing asks for a card.
Two kinds of account
Which kind you get depends on how the site you are using was set up. You don't choose it.
| Local account | Connected account | |
|---|---|---|
| Where it lives | In this browser only | With the site's sign-in service |
| How to tell | The sign-in page says accounts are stored in this browser only, and the account menu says "Local account" | No such notice. Google and GitHub buttons may appear |
| Use it on another device | No | Yes, you can sign in anywhere |
| Sign in with Google or GitHub | Not offered | Offered if the site has switched them on |
| Lost if you clear site data | Yes | The account is not, but your saved work is |
A local account is still useful. It keeps your workspaces apart from those of other people who use the same computer.
Signing up and signing in
To create an account, give a name, an email address and a password. The password needs at least 8 characters, with at least one letter and one number. If the site asks you to confirm your email, the page says "Check your email" and waits until you click the link.
Keep me signed in is ticked by default. Untick it on a shared computer, and you are signed out when you close the tab.
A wrong email or password always gives the same message, "Email or password is incorrect". That is deliberate, so the form can't be used to find out which addresses have accounts.
Continue without an account takes you to the Home page, with everything except Contract Graph and the Postman companion.
After signing in you go back to the page that asked you to. A shared Contract Graph link survives the trip, except through Google or GitHub sign-in, which leaves the site and comes back. Open the link again in that case.
Signing out
Click your avatar at the top right and choose Sign out.
Where your saved work lives
Everything you save is kept in this browser, whichever kind of account you have. A connected account lets you sign in from anywhere, but your saved work does not travel with it.
| What | Tied to your account? |
|---|---|
| Contract Graph workspaces | Yes. Each account on the browser sees its own |
| Recent APIs, the last eight | No. Everyone who uses the browser sees the same list |
| Collections, up to 20 | No |
| Environments | No |
| Postman API key | No. Signing out does not remove it |
| OpenRouter key for the AI assistant, if you pasted one | No |
To move a Contract Graph workspace to another browser, use Download workspace file on one side and Import workspace file on the other. Clearing this site's data in your browser removes everything in the table, and a local account with it.
What leaves your browser
Vizroute has no server of its own that receives your specifications. These are the only times anything goes out, and each one starts with something you do:
| When | What is sent | Sent to |
|---|---|---|
| You send a request from the playground, or run a live check | That request | The API you are testing |
| You load a specification from a URL | A request for that file | That address |
| You use the AI assistant | The loaded specification or workspace, with credential-like values hidden | OpenRouter |
| You use the Postman companion | Your API key, and any collection you push | Postman |
| You sign in with a connected account | Your email address and password | The site's sign-in service |
A share link is different: it sends nothing anywhere. The specification travels inside the link, after the #, and browsers never send that part to a server. But anyone you give the link to can read the specification.
One more case applies only where the SOAP Workbench is switched on. While it serves a REST bridge, your design goes to a server run by the site: the routes, the schemas and the SOAP endpoint's address.