Redundancy/Contingency plan for YNAW#324

Outline plans for what would happen due to changes in Google’s API or personal disaster, what would happen and what that would mean for customers.

Also potentially outline long term support details and metrics for support response times.

The short term response for this is that all data is saved in Drive. So a user will retain access to their data.

But it is worth noting that some of this data, like the positioning of documents in the sidebar and theming, is stored as metadata properties of the files. This data requires using the Drive API to access and is not accessible via the Drive UI.

The long term response will be adding a clause to continue to support the application or alternatively open source the code in case of personal disaster (to the business terms and my personal will).

It will also require adding a clause in the case of an API revoke from Google. Which would likely be either a) Selling it as self hosted software that can be installed or set up with your own API key or b) open sourcing.