AspirantMitraa Cookie & Signals Policy

1. Why we use cookies & SDK signals

AspirantMitraa uses a minimal set of first-party cookies and mobile identifiers so that you can stay signed in, resume syllabus missions, and keep your progress synced across devices. Without these signals we would not be able to restore mock test attempts or show accurate leaderboards.

2. Types of storage we rely on

• Essential cookies: keep you logged in, remember exam selections, and secure your session.
• Performance analytics: first-party pixels and Mixpanel/Google Analytics events help us understand which question banks or features need improvement.
• Mobile app identifiers: Firebase analytics and push tokens are used to deliver exam alerts and crash reports on Android/iOS.

3. Third-party partners

We work with a short list of processors who handle infrastructure and analytics on our behalf. Each vendor signs data-processing agreements and only receives pseudonymous usage data necessary to operate the service. They are not permitted to re-sell or reuse your data.

• Google Analytics & Mixpanel – exam journey analytics and funnel optimisation
• Firebase Cloud Messaging – mobile notifications and crash diagnostics
• Razorpay/Stripe – payment checkout flows for premium mock packs

4. Your controls

• Use the in-app privacy settings to disable non-essential analytics at any time.
• Install the Google Analytics opt-out add-on if you prefer not to share usage stats.
• Clear cookies or local storage from your browser to sign out all devices instantly.
• On mobile, revoke analytics permissions from system settings or uninstall the app.

5. Changes & questions

We update this page whenever our analytics stack or regulatory guidance changes. Significant updates are announced in-product. For any questions, write to privacy@mocktest.com.