1. Introduction
This Cookie Policy explains how HabeshaDrive (“we,” “our,” or “us”) uses cookies and similar technologies to recognise you when you visit our driving theory test preparation platform. It explains what these technologies are and why we use them, as well as your rights to control our use of them.
By using HabeshaDrive, you consent to the use of cookies and similar technologies as described in this policy.
2. What Are Cookies?
Cookies are small text files that are stored on your device (computer, tablet, or mobile) when you visit a website. They are widely used to make websites work more efficiently and provide information to website owners.
We use both session cookies (which expire when you close your browser) and persistent cookies (which remain on your device until deleted or expired).
3. Technologies We Use
HabeshaDrive uses the following storage technologies and mechanisms:
3.1 Local Storage
We use browser Local Storage to store data locally on your device. This technology is similar to cookies but can store larger amounts of data.
Authentication Tokens
- Purpose: Store your access and refresh tokens to keep you logged in
- Data Stored: JWT access token, JWT refresh token
- Duration: Until you log out or tokens expire
- Essential: Yes - Required for authentication
User State (Zustand Persist)
- Purpose: Persist your application state across sessions
- Data Stored: User profile, selected license category, authentication status, content language preferences
- Duration: Persistent until cleared
- Essential: Yes - Required for app functionality
Test Progress Data
- Purpose: Save your progress in mock tests and revision sessions
- Data Stored: Current question index, selected answers, test session data, timer state
- Duration: Until test completion or manual clearing
- Essential: Yes - Required to resume tests
3.2 Theme Preferences (next-themes)
We use the next-themes library to manage your dark/light mode preference.
Theme Cookie
- Purpose: Remember your theme preference (dark, light, or system)
- Data Stored: Theme selection (“dark”, “light”, or “system”)
- Duration: 1 year
- Essential: No - Functional/Preference cookie
3.3 Internationalization (next-intl)
We use next-intl to provide content in multiple languages (English, Amharic, Tigrinya, Somali, and Arabic).
Locale Preference
- Purpose: Remember your language preference
- Data Stored: Selected locale code (“en”, “am”, “ti”, “so”, or “ar”)
- Duration: Session or persistent based on implementation
- Essential: Yes - Required for proper content display
3.4 Progressive Web App (PWA)
Our platform is a Progressive Web App that can be installed on your device.
Service Worker & Cache Storage
- Purpose: Enable offline functionality and faster loading
- Data Stored: Cached pages, assets, and API responses
- Duration: Until cache is cleared or updated
- Essential: No - Performance enhancement
PWA Install Prompt State
- Purpose: Remember if you've dismissed the install prompt
- Data Stored: Install prompt interaction state
- Duration: Session-based
- Essential: No - User experience enhancement
3.5 Payment Processing (Stripe)
When you make a payment, Stripe (our payment processor) may set cookies for fraud prevention and payment processing.
Stripe Cookies
- Purpose: Fraud detection and secure payment processing
- Data Stored: Payment session data, fraud prevention tokens
- Duration: Varies by cookie type
- Essential: Yes - Required for payment processing
- Third Party: Stripe (see Stripe Privacy Policy)
4. Cookie Categories
We categorize our cookies and similar technologies as follows:
Strictly Necessary
These are essential for the website to function properly. They enable core functionality such as security, authentication, and accessibility.
Examples: Authentication tokens, session management, locale preferences
Functional
These enhance functionality and personalization, such as remembering your preferences and settings.
Examples: Theme preference, language selection, test progress
Performance
These help us understand how visitors interact with our platform by collecting and reporting information anonymously.
Examples: PWA cache, service worker storage
5. Why We Use These Technologies
We use cookies and similar storage technologies for the following purposes:
- Authentication: To keep you logged in and verify your identity
- Security: To protect your account and prevent unauthorized access
- Functionality: To remember your preferences and settings
- Performance: To improve loading times and enable offline access
- User Experience: To provide a personalized learning experience
- Progress Tracking: To save your test progress and learning history
- Payment Processing: To securely process subscription payments
6. Third-Party Cookies
We use limited third-party services that may set their own cookies:
- Stripe: For payment processing and fraud prevention
These third parties have their own privacy policies and cookie policies. We recommend reviewing them:
7. How to Control Cookies
You have the right to decide whether to accept or reject cookies. Here are your options:
7.1 Browser Settings
Most web browsers allow you to control cookies through their settings. You can:
- View what cookies are stored and delete them individually
- Block third-party cookies
- Block cookies from specific websites
- Block all cookies from being set
- Delete all cookies when you close your browser
7.2 Browser-Specific Instructions
7.3 Local Storage
To clear Local Storage data:
- Open your browser's Developer Tools (usually F12)
- Go to the Application or Storage tab
- Select Local Storage and clear the data for habeshadrive.com
- Alternatively, use your browser's "Clear browsing data" feature
7.4 Impact of Disabling Cookies
Please note that if you disable or refuse cookies:
- You will not be able to log in or use authenticated features
- Your preferences and settings will not be saved
- Test progress will not be saved between sessions
- Some features of the platform may not function properly
- You may need to manually adjust settings each visit
8. Data Retention
The data stored in cookies and local storage is retained as follows:
- Session data: Cleared when you close your browser
- Authentication tokens: Valid until expiration or logout
- Persistent preferences: Stored until manually cleared or account deletion
- Test progress: Stored until test completion or manual clearing
- PWA cache: Updated periodically or cleared manually
9. Updates to This Policy
We may update this Cookie Policy from time to time to reflect changes in our practices or for legal, regulatory, or operational reasons. We will notify you of any material changes by posting the new Cookie Policy on this page and updating the “Last updated” date.
10. Contact Us
If you have any questions about our use of cookies or this Cookie Policy, please contact us:
11. Related Policies
For more information about how we handle your data, please review: