When it comes to a user connecting a third-party service, there are two main forks in the road a user must choose between in terms of the future of their data. The first, is what to do about all existing, previously-collected data? And second, how to manage data going forward.

1. Previously-existed data

If a user decides to keep all of their data in previous third-party services, then Circaevum will not create duplicates this data, but rather feed it in only for the purpose of visualization. To help clarify this, a core functionality of Circaevum will be to visualize the source of each dataset being rendered into the environment. For example, there might be a satellite, or cube floating above the Earth, that represents data from Google’s servers. When the player loads their calendar, if they have an account setup to load data from Google, then the API’s will do their thing, and feed the data in to be visualized in Circaevum. Some sort of glowy connections will show up between those events and the respective floating cube thingies (this is a very technical paper - clearly). IF however, the user has decided to use Circaevum’s internal storage for event management, then that data will show links to a separate cube or region that represents Circaevum servers.

1. Data Going Forward

2. Keep their data only in the connected third-party service

3. Create a clone of the data in Circaevum

4. Migrate the data into Circaevum and delete it from the original source

There are a myriad of reasons why somebody might want to keep their data in the original third-party service, and not have a copy of it in Circaevum. Just as well, we also don’t want to require users to start additional third-party services in order to use our app, so we offer the ability to create and store data purely in Circaevum. Thus we will operate with a hybrid data model, where the user is given the decision of where they want to store their data.

To help drive the clarity around data terms, the “March” room of the Whitepaper Palace will be dedicated to making our terms and conditions, and data policy in general, visually appealing and easy to understand. This will help ensure that users are fully informed about their options and can make an informed decision about where to store their data going forward. Additionally, we will provide clear documentation and support to help users with the migration process if they choose to move their data from a third-party service into Circaevum. Ultimately, our goal is to provide users with the flexibility and control they need to manage their data in a way that works best for them.