API Terms of Service and Storing Data/Editing Transactions
With all these parameters set in place, does this app sound like it would be in good standing with YNAB's API Terms of Service, or would it be in violation of 4?
Also, does allowing for the editing of transactions, in the same vein as YNAB's interface, within the app constitute a violation of 6?
Hey there! Thanks for checking in with us about this! Based on what you've described, that functionality sounds entirely within the Terms of Service! As long as you specify which information you're collecting and how it will be stored, and that it won't be passed on to any 3rd parties, that should be fine. I also don't see any issues with allowing users to edit transactions within the app especially if there's app-specific info attached to those transactions. We're big on "good faith" so as long as the app is intended as a supplement to YNAB and not a replacement, you should be good to go. I hope that helps and we're excited to see what you build!