Description of Service and Usage Limitation
Our service provides online voice lessons to individuals seeking to improve their vocal abilities. By using our service, you agree to use it only for personal, non-commercial purposes.
Description of Expected Procedures and Liability
While we strive to provide a reliable service, we cannot guarantee that our service will be uninterrupted or error-free. We are not responsible for any data loss, business interruption, or other damages that may result from the use of our service.
Description of Payment Policy
Our service requires payment for lessons. Payment is due at the time of booking and must be made through our online payment system. We reserve the right to cancel lessons for non-payment.
Our support team is available to assist you with any questions or issues you may have regarding our service. Our hours of operation are [insert hours of operation here]. We aim to respond to all support inquiries within [insert SLA here]. To create a support case, please visit [insert link to support page here]. You may also email us at [insert email address here] or call us at [insert phone number here].
Our documentation provides step-by-step instructions on how to use our service, including how to schedule and attend online voice lessons. To access our documentation, please visit [insert link to documentation here].
Deauthorization event URL for testing
In compliance with our commitment to security and the protection of user data, we provide a secure endpoint for receiving deauthorization notifications from our service. To remove or deauthorize our service, please visit [insert deauthorization event URL here].
Optimize app data fetching
To ensure optimal performance of our service, we adhere to optimal patterns of requesting and subscribing to data from our system. We subscribe to receive webhook event requests rather than long-polling the system API.
Remove unused scopes from development
To help ensure that our service only has access to the APIs necessary for its functioning, we only enable scopes that make functional, logical, and business sense for our service.
Optimize app authentication and refresh flows
To avoid making overly frequent requests for OAuth tokens, we request and store a token to allow our service to make API requests rather than generating a new token on each request. We cache data returned from our system’s authentication endpoints and reuse access tokens.