Authentication Required

To obtain a feed of documents you will need to grant access for us to fetch it on your behalf.

Only do this if you trust us to have access to your document feed.

Authenticate with Google »

What's happening?

If you choose to auth we'll send you off to Google where you'll sign into your account and be asked whether you trust us.

If you agree that you do Google will send you back here to this page. In the address bar will be a little token which we then store in your browser as a cookie.

Whenever your Google Toolbar wants to build the dropdown list of documents it will come here to this page. We will ask your browse for the token stored in our cookie. We then ask Google Docs for the list of documents - giving the token to Google Docs as proof that you trust us to have the list.

Authenticate with Google »

Who are we and should we trust you.

We are Isotope Communications Ltd, a digital agency in Bath, UK.

Whether you trust us with access to you really! For the techies amongst you here's exactly what happens with your authentication 'tokens'. You follow the link above and Google sends you back to us with a token which can be used only once. This token is visible in your browser address bar - and as a consequence will end up in our access logs on the server. However, it's a single-use token. We use it to grab a more permenant token (so you don't have to auth every five minutes) and we store this second 'session' token in your browser. We do not store your session token anywhere within our own infrastructure. When your toolbar requests the feed we pick up the token, use it to grab the feed and again, do not store it.

Want to know more or how we do this?

Have a look at the Google Docs API

Want to get in touch?

Please do: opensource@icommunicate.co.uk