Third-Party Service Providers
At Leoblocks, we are committed to transparency about the services and technologies we use to operate our platform. This page outlines the third-party service providers that may process user data—including Student Data—to support core functionality, performance, and reliability.
We review each provider to ensure they comply with privacy regulations such as FERPA, COPPA, and GDPR, and we require strong data protection standards in all vendor relationships.
Student and user-generated files remain strictly private and are only accessible by the user or authorized personnel for educational or support purposes.
If you have any questions about the tools we use, please contact us at support@leoblocks.com.
🔒 Core Infrastructure & Hosting
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Google Cloud | Hosting, file storage, backups | App data, user files (private) | Google Privacy |
| MySQL (via GCP) | Relational database for platform | Student and user data | Managed by GCP |
👥 Authentication
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Google OAuth | Google Single Sign-On | Name, email | Google Privacy |
| Microsoft Azure OAuth | Microsoft Single Sign-On | Name, email | Microsoft Privacy |
| Laravel Sanctum | Session authentication | User ID, session token | Laravel Sanctum |
📬 Email & Communication
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Mailgun | Transactional emails | Email addresses | Mailgun Privacy |
🛡 Monitoring & Security
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Sentry | Error monitoring | Anonymized logs | Sentry Privacy |
| GitHub | CI/CD and dependency monitoring | Build metadata | GitHub Privacy |
🧪 Development & Deployment
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Laravel Forge | Server provisioning & deploys | Deployment metadata | Forge Privacy |
| GitHub Actions | Continuous Integration | Build metadata | GitHub Privacy |
📊 Analytics
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Google Analytics | Platform usage analytics | IP, device, usage data | Google Analytics Privacy |
| Google Tag Manager | Managing analytics and tags | Limited metadata | Google Privacy |
Analytics are used solely for performance, usability insights, and improving the product experience. No advertising or marketing tracking is in place, and IP anonymization is enabled where applicable.
💳 Payments
| Provider | Purpose | Data Shared | Privacy Policy |
|---|
| Stripe | Payment processing for subscriptions and license purchases | Billing details, email address | Stripe Privacy |
Leoblocks uses Stripe to securely handle payments for both individual Pro subscriptions and bulk license purchases for schools. All payment data is processed by Stripe and never stored on Leoblocks servers.
⚠️ Additional Notes
- We do not sell or share Student Data with advertisers.
- Students’ and users’ files remain strictly private unless explicitly shared by the user.
- We keep this list up-to-date as our systems evolve. Updates will be reflected on this page.
