Security and privacy at RooQuiz
How we protect the quiz responses and leads you collect: where data is stored, who processes it, and the commitments we make in our Data Processing Agreement.
Based on our DPA · Last Updated: November 16, 2026
Where your data lives
The primary database holding quiz responses and leads is hosted in the United States (AWS us-west-2, Oregon). The application layer, object storage and caching run on Cloudflare's global network.
Encryption
Encryption in transit (TLS) for all connections to the platform, and encryption at rest for the primary database and object storage.
No selling, no AI training
We do not sell personal data, and we do not use your respondents' personal data for our own purposes — including advertising, profiling, or training AI models.
Deletion
On termination or expiry of your account, we will delete personal data processed on your behalf within 90 days, except where retention is required by applicable law. Backups are purged on their normal rotation cycle. If you need a final export, request it before your account closes.
Breach notification
We will notify you without undue delay after becoming aware of a personal data breach affecting personal data we process on your behalf, and in any event in time for you to meet your own notification obligations under Articles 33 and 34 GDPR.
Signed DPA on request
This DPA takes effect without signature. If your own compliance process requires a countersigned copy, or a version on your paper, email support@rooquiz.com and we will arrange it.
AI and your data
AI features run in two places. Scoring free-text answers against your reference answer, screening quizzes that are reported for abuse, and transcribing audio and video uploaded to AI quizzes run on Cloudflare Workers AI using models hosted by Cloudflare. Reports for AI quizzes are written by large language models that we reach through OpenRouter, which forwards each request to the model provider serving it: for that purpose only, the respondent's answers, any uploaded images, and text extracted or transcribed from uploaded files are sent to OpenRouter and that model provider. No other feature sends your content to an external AI provider, and we do not use your respondents' data to train AI models.
Security measures
- Encryption in transit (TLS) for all connections to the platform, and encryption at rest for the primary database and object storage.
- Credentials for connected destinations (such as Slack and Kit access tokens) stored encrypted at the application layer.
- Tenant isolation: every query is scoped to the team that owns the data, enforced in the application's access layer rather than by convention.
- Role-based access control within a team (owner, admin, member), with permission checks on both read and write paths.
- Personal data returned through the MCP interface to AI clients is masked before it leaves our systems.
- Bot and abuse protection on public quiz pages (Cloudflare Turnstile) and rate limiting on sensitive endpoints.
- An audit log of administrative actions, retained for 30 days on the Free plan and 365 days on Pro.
- Access to production systems limited to personnel who require it, protected by multi-factor authentication.
- Managed, redundant infrastructure with automated database backups.
- Security patches applied through regular dependency updates and automated vulnerability alerts.
These measures evolve as the service does. We may replace a measure with one that is at least equivalent in protection.
Sub-processors
The following sub-processors are engaged to deliver the service. "Account data" means data about you as a RooQuiz customer; "service data" means the responses and leads we process on your behalf.
| Sub-processor | Purpose | Data accessed | Processing location |
|---|---|---|---|
| Cloudflare, Inc. | Application hosting, object storage, caching, queues, CDN, bot protection (Turnstile), Workers AI for scoring free-text answers, screening reported quizzes and transcribing audio and video uploaded to AI quizzes, and delivery of account emails (sign-up verification, password resets, team invitations, and notifications) | Account data and service data | Global edge network |
| Supabase | Managed PostgreSQL database (primary data store) and file storage for respondent uploads | Account data and service data | AWS us-west-2 (Oregon, United States) |
| OpenRouter, Inc. | Writing AI quiz reports: routes each request to the large language model provider serving it | Service data: answers, uploaded images, and text extracted or transcribed from uploads to AI quizzes | United States; the model provider serving a request may process it in other regions |
| Resend | Delivery of emails to respondents (result emails and verification codes) | Names, email addresses, and the content of those emails | United States / European Union |
| Google Firebase Authentication | Sign-in for account holders and respondents | Email addresses and authentication identifiers | Google global infrastructure |
| Paddle.com Market Limited | Merchant of Record for payments, invoicing and tax | Account data only (billing details); no service data | United Kingdom / European Union |
| Sentry | Error and exception monitoring | Technical diagnostic data, which may incidentally include identifiers | United States / European Union |
| Axiom | Application logging and operational analysis | Technical log data, which may incidentally include identifiers | United States |
| Discord | Internal operational alerts to our team (for example, new sign-ups and abuse reports) | Account data (such as the email address used at sign-up); no respondent answers | United States |
| Crisp | In-app support chat, where enabled | Contact details and message content you provide in a support conversation | European Union |
| Google Analytics | Analytics on our own websites, loaded only where the visitor has consented | Usage data of visitors to our sites; no service data | Google global infrastructure |
Destinations you connect yourself — Slack, Zapier, Kit, webhooks, your own SMTP server or Gmail account, and any AI client you link over MCP — are not our sub-processors. When you enable one, you instruct us to transmit data to a third party of your choosing, and that provider processes it under your relationship with them.
Documents
- Data Processing Agreement — GDPR Article 28 terms, technical and organisational measures, and the full sub-processor list
- Privacy Policy — how we handle your account data and visitors to our sites
- Terms of Service
Report a security issue
Email support@rooquiz.com. Our contact details are also published at /.well-known/security.txt.