Quizglish

Legal and support

Service Providers and Subprocessors

Effective August 14, 2026
Privacy PolicyTerms of UseSupportSubprocessors

Current Quizglish service providers and subprocessors for hosting, authentication, AI generation, analytics, notifications, app distribution, and support.

This page identifies third parties that currently process data to provide Quizglish. Depending on the legal context, a company listed here may act as a processor, subprocessor, or independent service provider.

Quizglish does not list hypothetical or unused vendors. The list will be updated before or when a new provider materially changes personal-data processing.

1. Contabo GmbH — hosting

Purpose: VPS infrastructure for the Quizglish website, API, self-hosted MongoDB database, routing, and operational logs.

Data: all account, quiz, participant-response, AI-operation, moderation, support-routing, and technical data stored on or transmitted through the VPS.

Location: the selected Contabo European Union region. The current public IP is registered to Contabo in Germany. Quizglish does not currently operate a separate external backup service.

2. Google LLC / Firebase — authentication

Purpose: Firebase Authentication for Apple and Google identities, authentication security, and account deletion.

Data: provider identifier, email when supplied, IP address, user agent, authentication and security metadata.

Location: Firebase Authentication is operated from United States data centers under Google/Firebase terms.

3. X.AI LLC — AI generation

Purpose: standard Grok API processing when an account holder requests quiz generation or regeneration.

Data: source text, prompt instructions, selected settings, relevant quiz context, generated output, and request metadata.

Location and retention: United States. Under xAI published standard API terms, input and output may be retained for up to 30 days and is not used to train xAI models. A separate Zero Data Retention mode is not currently enabled.

4. 650 Industries, Inc. (Expo) — mobile infrastructure and notifications

Purpose: EAS mobile build infrastructure and Expo Push Service delivery.

Data: build and application metadata, Expo push token, notification payload, participant display name, quiz title, and internal quiz/response route identifiers.

Location: United States and infrastructure locations used by Expo and its providers.

5. Apple — sign-in, notifications, and distribution

Purpose: Sign in with Apple, Apple Push Notification Service, App Store distribution, app review, and platform security.

Data: Apple account identifier, email or private relay address when supplied, authentication metadata, push token and payload, device and store metadata.

Location: international Apple infrastructure under Apple terms and privacy notices.

6. Google — sign-in, distribution, and support email

Purpose: Google Sign-In, Google Play distribution and app review, and the Gmail inbox used for support, privacy, deletion, copyright, abuse, and security requests.

Data: Google authentication metadata, store and device metadata, sender email, support message, attachments, and request-handling records.

Location: international Google infrastructure under Google terms and privacy notices.

7. Amplitude, Inc. — mobile-app analytics

Purpose: privacy-limited product and UX analytics for screens, actions, and request outcomes in the quiz-creator mobile app. Amplitude is not used on public web participant pages.

Data: event names, app version, platform, environment, bounded counts and length buckets, opaque internal account, quiz, question, response, and answer identifiers, and a random device identifier that is not persisted across app restarts. Amplitude does not receive prompts, raw quiz text, generated content, names, email addresses, authentication tokens, answers, or other personal content.

Location: United States infrastructure under Amplitude terms and privacy notices.

8. Services not currently used

Quizglish does not currently use a payment processor, advertising network, external crash-reporting provider, managed cloud database provider, CDN proxy, transactional-email provider, or external backup provider for production user data.

9. International transfers and safeguards

Some providers process data outside Ukraine and the European Union. Where applicable law requires a transfer mechanism, Quizglish assesses and uses available provider data-processing terms, standard contractual clauses, adequacy mechanisms, or other recognized safeguards.

10. Changes to this list

Quizglish will update this page before or at the same time as adding a provider that materially changes personal-data processing. The effective date will be updated, and a material notice will be published on the site or in the app when appropriate.

Quizglish does not currently operate an email notification list for provider changes.

11. Contact

Questions about providers, transfers, or data processing may be sent to Alekseev Aleksandr at ventarichannel@gmail.com.