Privacy
Atlas is a free public map of UK accounting and bookkeeping events. You can use all of it without an account, without giving us an email address, and without connecting anything. This page says what happens if you do connect a calendar.
If you just browse
There is no account, no sign-up and no email capture. Your filters, any events you save, and anything you tell us in “Show events for me” (a goal, a role, a town) are kept in your own browser, not on our servers, which is why they do not follow you to another device.
We would like to count visits, and we ask first. Until you answer, and if you say no, nothing is loaded and no cookie is set — the counting code is not downloaded at all, so there is nothing to opt out of afterwards.
If you say yes, we use PostHog on its European servers to count page views and how many people come back. It stores a random identifier in your browser so a return visit is not counted as a new person. We do not ask it to record your screen, and we do not send it your name, your email, your saved events or anything you typed. If you arrived from a campaign link, the tag on that link is recorded so we know which one worked.
You can change your mind at any time, and this is the switch:
One caveat, stated because it would otherwise be a quiet exception: if you type a town we do not already cover, the name of that town — and nothing else — is looked up against postcodes.io, a free open service, to find its coordinates. The result stays in your browser.
If you connect a calendar
Connecting is optional and everything else keeps working without it. You can connect either Google Calendar or Microsoft Outlook. In both cases we ask for the narrowest permission the provider offers, and in neither case can we create, change or delete anything in your calendar.
Google Calendar
- Your availability (
calendar.freebusy). This returns blocks of time you are busy. It does not return event titles, guests, locations, descriptions or attachments. That is a limit of what Google will give us with this permission, not a promise we are asking you to take on trust. - The list of your calendars (
calendar.calendarlist.readonly). This is so we can check availability across the calendars you actually use rather than only your default one. It returns calendar names, never their contents.
Microsoft Outlook
Outlook uses Calendars.ReadBasic, the least-privileged permission Microsoft offers for reading availability, together with openid and email so we know which mailbox to ask about. We deliberately do not request User.Read, which would also give us your name, job title, photo and manager. It works with work or school accounts only, because Microsoft does not offer availability lookups for personal accounts.
One difference is worth stating plainly. Microsoft’s availability endpoint returns event subjects and locations alongside the busy times, whether or not an application wants them. Google’s does not. So with Outlook the guarantee is enforced by our code rather than by the permission: Atlas reads only the availability summary, a bare list of busy and free slots, and never reads the fields containing your event details. We would rather say that than imply the two providers give the same protection when they do not.
With either provider, holiday and birthday calendars are excluded, because otherwise every bank holiday would look like a commitment.
What we store, exactly
- A random identifier in a cookie, so your browser can be matched to your connection. It is not derived from anything about you and is not shared with anyone.
- The token your provider gives us to check your availability, encrypted at rest with AES-256-GCM. It is never written to our logs.
- Which provider you connected, so we know where to ask.
- The list of calendar identifiers to check, and the time you last used the connection.
Your busy times are not stored. They are fetched when the page loads, used to work out which events clash, and discarded. There is no copy of your diary on our servers.
Deleting it
Press Disconnect on the diary strip. That deletes the row and the token immediately and completely; there is no soft delete and no archived copy.
You can also revoke Atlas from the provider’s own side, which works even if you never come back here: Google account permissions or your Microsoft apps.
To clear saved events and filters, clear this site’s data in your browser. It never reached us in the first place.
Lawful basis
Under UK GDPR we rely on consent for calendar access. You give it by connecting and withdraw it by disconnecting, and withdrawing is as easy as giving it. There is no other processing of personal data to justify, because browsing Atlas involves none.
Event and organiser information
The events themselves come from public listings published by professional bodies, organisers and ticketing sites. Where an organiser is an individual rather than a company, their name and public contact details may appear as part of the listing, on the basis of our legitimate interest in running a public directory of these events. If you are an organiser and would like a listing corrected or removed, contact us and we will act on it.
Who else sees this
We do not sell, share or transfer any of it. Our hosting and database are run on Railway, and Google or Microsoft is the source of the availability data you asked us to read. There are no advertising networks and no data brokers involved.
The one exception is the visit counting described above, and only if you agreed to it: PostHog then sees that a browser loaded a page, and nothing about your calendar, your saved events or anything you told us. If you did not agree, PostHog receives nothing, because its code is never loaded.
Contact
Atlas is built by Reveal Technologies Ltd. For anything on this page, including a request to see or delete what we hold, email hello@revealos.com. You also have the right to complain to the Information Commissioner’s Office. Separately, our terms of use cover what Atlas is and is not responsible for.