Data synchronization

This page describes how your data is automatically synchronized across your devices via our backend servers.

General principles

Our aim with Aviator Logbook was to replace manual sync and backups used by other logbook software, and make synchronization something you never even think about. After all, this is what you would expect from any modern mobile app!

All of your data is connected to your individual Aviator Logbook account, and a copy is stored automatically on our backend servers. Every time you create, edit or delete an item, this changed is synchronized straight away in the background if you are online, or when a connection becomes available again.

When you start the app, a check is made for any new data on the server. This is then synchronized (you'll see this screen every time you start the app). The same thing happens if the app's aerodrome library gets updated. Don't worry if you're on a slow connection, after a short time this screen will 'time-out' and sync will continue in the background.

Finally, whenever you sign in to the app on a new device, your data will be synced and should be available straight away! We'll also sync the aerodrome library from the server.

Offline editing

Logging a flight offline, for example in the cruise or whilst deadheading somewhere? You'll be able to use the app as usual, with the following differences:

• No initial sync will be performed, meaning changes you made on other devices will not be visible.

• Any data you create, edit or delete will be stored and synced next time the app has an internet connection.

This could lead to conflicting edits, for example editing a flight on one device offline and editing the same flight on a different offline devices. When internet connectivity is restored and a sync is performed, any conflicting changes are resolved based on the time they were made, i.e. the last made edit is the one that will be kept.

It is generally good practice, but not enforced, that the app should be allowed to sync on a regular basis with the backend servers.

Data storage and backup

We want your data to be safe in our hands. All logbook data is stored on a main server, with live copies across two other servers. Furthermore a hard backup of all data is made every 24 hours that can be restored in the worst case scenario.