User Profile

Hi everyone,I'm planning my very first app submission.It's a generic font installer and updater, meaning that users will be able to load their purchased or free fonts from font publishers as subscriptions into the app, keep them in user accounts, automatically receive updates of the fonts etc.Imagine you're a commercial font user, so you've just purchased a couple of fonts from a font maker. The old way is that you get offered to download a zip file containing the fonts, and then you are responsible to install them in the correct place and also responsible for keeping the file for when you next need them.With my app, the font maker will offer a "Install in Type.World App" button after purchase. Once the app is installed, it will come open and offer to install the new fonts for you with another click. Later, after you've lost or crashed your computer, you can easily restore all your font subscriptions by just logging into the user account with the app instead of manually digging up all the fonts.Also, the app will inform you of available updates to the available fonts.Each font maker will provide the necessary data to install the fonts under individual API endpoints on their servers.Here's my question: Does this behaviour collide with the "loading resources" section of the App Store Review Guidelines (2.4.5 (ii))?It reads:(ii) They must be packaged and submitted using technologies provided in Xcode; no third-party installers allowed. They must also be self-contained, single application installation bundles and cannot install code or resources in shared locations.Fonts are not code, but they are surely resources. But that's kind of the point of the app, not some shady feature.Any experiences?Thank you.