Privacy Policy

ForQuiz ("we", "our", or "us") operates the website forquiz.fusebytes.in and the real-time quiz platform available at that domain. This policy explains what personal data we collect, why we collect it, and the choices available to you.

• Account information - email address and display name when you sign in via Google or email/password (stored in Firebase Authentication).
• Quiz content - quizzes you create are stored in Firebase Firestore under your account. The provided content and the generated response are stored in blob storage for debugging and improvement purposes which is linked to your user ID but not publicly accessible.
• Reference Quiz context - if you choose a Reference Quiz during AI quiz generation, we may send the selected quiz's question text, correct answer text, tags, and Did You Know text as prompt context so the generated quiz can avoid repeated learning points. We do not send Reference Quiz ID, title, owner, participant, player, result, or leaderboard data as part of that context.
• Game session data - player names, scores, and answers collected during live sessions. These are stored temporarily in server memory and optionally persisted to Firestore for result downloads. For signed-in non-host players, we may capture an internal Participant UID to match the player to an organizer-scoped Participant Directory record.
• Campaign/study setup data - campaign name, start and end times, access mode, restrictions or allowlists, result visibility settings, quiz versions, question tags, result file paths, and organizer dashboard metadata.
• Campaign/study participant data - player name and the identifier required for a campaign or study, such as an email address, phone number, or custom identifier configured by the organizer.
• Participant Directory and Segment data - organizers may store participant names, email addresses, phone numbers, custom identifiers, UID identifiers, Segment Categories, Segments, memberships, and import preview or commit records used to manage targeting and reporting.
• Campaign/study response data - selected answers, selected option text, correctness, score, points, answer timing, completion status, rank, percentile, and result metadata used for dashboards, exports, and participant result pages.
• Segment Snapshot and backfill data - completed results may store participant match status, participant display snapshots, Segment Snapshots, Segment Coverage, Segment Analytics, and Backfill preview or apply metadata so historical analytics and exports remain explainable.
• Insight Explorer data - study and live-session analytics subjects, read models, comparison metrics, shared-tag comparison, and Common-Participant Comparison data used by organizers to compare quiz experiences.
• Live-session result artifacts - live-session player results, participant match metadata, segment-enriched result artifacts, JSON companion files, and XLSX exports used for downloads, analytics, and backfill.
• Captcha and abuse-prevention data - for phone and custom identifier campaign flows, we use short-lived server-generated math captcha tokens and temporary IP/identifier failure counters to prevent automated or repeated invalid access attempts.
• Analytics data - only if you grant consent (see section 5), we collect anonymised usage events (page views, feature usage) via Firebase Analytics / Google Analytics.
• Browser storage - your browser may store your analytics consent choice and campaign resume tokens so you can continue an in-progress campaign attempt.
• Waitlist / contact submissions - email address and/or LinkedIn profile URL and optional message if you fill in a contact or waitlist form.

• Contract performance - processing necessary to provide the quiz service you signed up for.
• Legitimate interest - maintaining security, preventing abuse, and improving core product functionality.
• Consent - analytics tracking. You can withdraw this at any time (see section 5).

• To authenticate you and protect your account.
• To run live quiz sessions and display leaderboards.
• To create, operate, and manage campaigns/studies, including schedules, access controls, allowlists, quiz versions, organizer dashboards, and exports.
• To manage Participant Directory records and generate Segment-based campaign targeting lists.
• To validate campaign participant eligibility, enforce one-attempt rules, resume in-progress attempts, and prevent abuse.
• To match campaign and live-session players to organizer-scoped Participants, create Segment Snapshots, and keep unmatched players in overall results.
• To calculate campaign/study results, rankings, percentiles, question analytics, study comparisons, participant result pages, and downloadable JSON/XLSX result files.
• To generate Segment Coverage, Segment Analytics, Segment Backfill previews and apply results, owner-gated exports, and Insight Explorer comparisons.
• To improve AI quiz generation when you select a Reference Quiz by avoiding repeated learning points and keeping tags comparable.
• To understand how features are used and improve the platform (analytics, only with consent).
• To respond to support enquiries, privacy requests, and campaign response deletion requests.

We do not sell your personal data to third parties.

We use Firebase Analytics (Google) to collect anonymised behavioural data. This is loaded only after you explicitly click Accept Analytics in the cookie banner on your first visit. If you click Reject Analytics, no analytics cookies are set and the SDK is never loaded.

Your choice is stored in your browser's localStorage under the key analyticsConsent. You can change your preference at any time by clearing your browser's local storage for this domain and reloading the page - the consent banner will reappear.

• Firebase (Google) - Authentication, Firestore database, and (with consent) Analytics.
• S3-compatible blob/object storage - used for quiz-generation debug content, restrict lists, JSON campaign and live-session result exports, XLSX result downloads, and segment-enriched analytics artifacts.
• Google Tag Manager - loaded only in production for managing third-party tags.
• LLM Models - used server-side to generate AI quiz questions. Prompt context may include content pasted by users in the quiz creation form and, when selected, Reference Quiz question text, correct answer text, tags, and Did You Know text. Participant Directory data, player identifiers, result exports, Segment Snapshots, and UIDs are not intentionally sent to LLM providers.

Campaign captcha challenges are generated and verified by our own server; we do not use a third-party captcha provider for those flows.

Each provider has its own privacy policy. We encourage you to review Google's Privacy Policy.

• Account data - retained until you delete your account.
• Live session data - server-side game state is auto-deleted after 2 hours. Exported result files are retained until manually deleted or until a valid deletion request is processed.
• Campaign/study configuration - retained until the organizer or ForQuiz deletes the campaign/study.
• Participant Directory data - retained until the organizer or ForQuiz deletes the participant, identifier, Segment Category, Segment, or membership record.
• In-progress campaign attempts - retained in Firestore until completion, export, or deletion.
• Completed campaign/study and live-session results - retained in generated JSON/XLSX export files until manually deleted or until a valid deletion request is processed.
• Historical Participant and Segment Snapshots - completed results keep stored snapshots stable until explicit Backfill, deletion, or other authorized admin action updates them. Deleted Participants and identifiers stop future matching, but historical completed result snapshots may remain until such action is processed.
• Completed participant identifiers - may be retained to enforce one-attempt campaign rules.
• Analytics data - subject to Google Analytics retention settings (default 14 months).

If you are in the EEA or UK you have the right to access, correct, or erase your personal data, to restrict or object to processing, and to data portability. To exercise any right, email us at the address below and we will respond within 30 days. You may also request deletion of a campaign/study response tied to your email, phone number, custom identifier, or live-session identity where the result row is identifiable.

Deletion requests may include Participant Directory records, Segment data, campaign/study responses, and live-session result rows where identifiable. Some historical exports and stored snapshots require organizer or admin processing because they are stored in generated result artifacts.

We use industry-standard measures including HTTPS, Firebase security rules, and server-side authentication tokens. No method of transmission over the internet is 100% secure; we cannot guarantee absolute security.

ForQuiz is not directed at children under 13. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us so we can delete it. Parents, teachers, and educators should ensure that children use an appropriate parent or guardian account if sign-in is required and should obtain any required consent before using quizzes, campaigns, or studies with children or students.

We may update this policy from time to time. The "Last updated" date at the top of this page will reflect any changes. Continued use of the platform after changes constitutes acceptance of the revised policy.

For privacy-related questions or data requests, please email susmit.py@gmail.com.

If you wish to delete your account and all associated data, please email us at the address above with the subject "Delete Account". We will process your request within 30 days and confirm once completed. If you only want a specific campaign/study response deleted, include the campaign/study name or code and the email, phone number, or custom identifier used for that response. For Participant Directory, Segment, or live-session result deletion requests, include the organizer, campaign, quiz, live session, or participant details needed to locate the record.