@slarti76current there is no plan to define what should and what should not be synced. But probably a good point. It should save us a few cents on the server and users may be happy not to sync some private data. Anyway in the first versions, it will for sure be "all or nothing".
And yes, it is correct, it is currently not available even to the rest of the Locus team

. And during August, it will be for sure ready for test for the brave one

.
@michaelbechtoldwe count with this. There is too many unknowns, so we are counting with the worst cases first. Currently, first initial sync of my 400 MB database took almost 2 hours, so 1 GB ... well, we will have to improve performance a little bit

.
Secondary database is a nice idea. It is not just about sync as you wrote slarti, it is also about performance. 1 GB database may suffer by slowness because table with points ... it really long, so simple load of track may be few times slower than from empty database.