StudyulaSubprocessors and Service Providers
This page explains the third-party service categories Studyula may use to deliver the service and our approach to data sharing.
Last updated: 4 September 2026
Only data needed for the relevant feature is shared. Support for an integration in the codebase does not mean that provider is active for every customer or country.
1. Core service categories
Studyula may use hosting/infrastructure, database/security, AI/model, transactional email/notification and, when needed, payment services in production.
- Hosting / server infrastructure — running application and database services
- AI / model provider — prompt and context required for the requested AI feature
- Email / notification infrastructure — verification, password reset and service messages
- Payment provider — only where paid-plan or institution payment flow is enabled
- Browser Web Push infrastructure — when the user grants notification permission
2. Optional payment and integration providers
The Studyula codebase can support payment bridges such as Stripe, PayTR, iyzico and bank virtual POS. Only a provider configured and enabled for the relevant market/institution processes data. Email or infrastructure bridges can similarly vary by deployment.
3. Data minimization
We aim to send a provider only what is needed for its task: the relevant prompt/context for AI, customer/transaction data needed for payment, or recipient/message information for transactional email.
4. Changes
This page is updated as providers, regions or service architecture change. Institution customers may request that active subprocessors and transfer terms be identified in their executed DPA.
5. Analytics and advertising
Under the current Cookie Policy, the Studyula web app does not have Google Analytics, Meta Pixel, Hotjar or similar behavioral advertising trackers active. If this changes, policies and consent controls will be updated.