MEETHOUSE COOKIE POLICY
Effective Date: 19 September 2026
Last Updated: 19 September 2026
This Cookie Policy explains how Skyroket, the operator of Meethouse (“Meethouse,” “we,” “us,” or “our”), uses cookies and similar technologies on the Meethouse website and, where applicable, similar technologies within the Meethouse application.
This policy should be read together with our:
1. WHAT ARE COOKIES?
Cookies are small files or pieces of information that websites may store on your browser or device.
They can help websites:
- Remember settings
- Maintain sessions
- Authenticate users
- Protect accounts
- Improve performance
- Understand how a website is used
- Detect suspicious activity
- Provide requested functionality
Meethouse may also use technologies that perform functions similar to cookies, including:
- SDKs
- Local storage
- Device identifiers
- Pixels
- Tags
- Software development kits
- Log files
- Similar tracking or technical technologies
For convenience, this policy refers to these technologies collectively as “Cookies and Similar Technologies.”
2. WHERE WE USE THESE TECHNOLOGIES
Meethouse may use Cookies and Similar Technologies on:
- The Meethouse website
- Account and authentication pages
- Web-based services
- Payment-related web pages
- Support pages
- Other websites or web experiences operated by Skyroket in connection with Meethouse
Mobile applications may use SDKs, local storage, device identifiers, and similar technologies rather than traditional browser cookies.
3. TYPES OF TECHNOLOGIES WE MAY USE
3.1 Strictly Necessary Technologies
These technologies are necessary for the website or application to function.
They may be used for:
- Login sessions
- Authentication
- Account security
- Session management
- Fraud prevention
- Load balancing
- Security controls
- Remembering essential settings
- Delivering requested services
Because these technologies are necessary for the operation of the service, they may not always be optional.
4. Authentication Technologies
Meethouse uses Firebase Authentication for account authentication and OTP-based login functionality.
Authentication-related technologies may help us:
- Verify users
- Maintain login sessions
- Protect accounts
- Prevent unauthorized access
- Detect suspicious authentication activity
Information processed through authentication systems may include identifiers associated with your account, device, session, and authentication activity.
5. Website Hosting Technologies
The Meethouse website may be hosted using Vercel.
Website infrastructure may process technical information such as:
- IP address
- Browser information
- Device information
- Request information
- Connection information
- Security logs
- Technical diagnostics
These technologies help deliver website content and protect website infrastructure.
6. Security Technologies
Meethouse may use Cookies and Similar Technologies to protect users and our systems.
These technologies may help us:
- Detect suspicious activity
- Prevent fraud
- Detect automated abuse
- Protect accounts
- Identify unauthorized access attempts
- Enforce security controls
- Investigate security incidents
Security-related technologies may operate even when other optional technologies are disabled.
7. Preferences and Functionality
Where available, Meethouse may use technologies to remember preferences such as:
- Language
- Session preferences
- Website settings
- Interface preferences
- Consent preferences
- Other functionality settings
These technologies allow us to provide a more consistent experience.
8. Payment-Related Technologies
Meethouse may use third-party payment services including:
- Razorpay
- Google Play Billing
- Apple App Store / Apple payment systems
Payment providers may use cookies, SDKs, device identifiers, or similar technologies when processing transactions or providing payment-related functionality.
The exact technologies used may depend on:
- The payment method
- Device
- Operating system
- Payment provider
- Purchase location
- Applicable law
Payment providers may have their own privacy and cookie policies.
9. Firebase Cloud Messaging
Meethouse uses Firebase Cloud Messaging (FCM) for push notifications.
FCM may use technical identifiers and related information to deliver notifications to your device.
Push-notification functionality may involve:
- Device identifiers
- Application identifiers
- Notification tokens
- Technical information
- Delivery information
You can generally control push-notification permissions through your device settings.
10. Firebase Crashlytics
Meethouse uses Firebase Crashlytics to identify and diagnose application crashes and technical problems.
Crashlytics is not intended to function as a traditional browser-cookie advertising system.
It may process technical information such as:
- Device information
- Operating system
- Application version
- Crash logs
- Diagnostic information
- Technical identifiers
- Information associated with application failures
This information helps us:
- Detect crashes
- Diagnose bugs
- Improve stability
- Identify recurring technical problems
- Improve application reliability
11. Analytics
Meethouse will only use analytics technologies that are actually implemented in the service.
As of the effective date of this policy, Firebase Crashlytics is used for crash reporting and technical diagnostics.
Crashlytics should not be interpreted as a general-purpose advertising or behavioral analytics system.
If Meethouse later introduces a separate analytics platform, we may update this Cookie Policy and Privacy Policy as appropriate.
Where applicable law requires consent before analytics technologies are used, we will seek the required consent.
12. Google Maps and Location Technologies
Meethouse may use the Google Maps SDK and related Google mapping technologies.
These technologies may be used to:
- Display maps
- Support location-based features
- Enable nearby discovery
- Process location-related functionality
- Provide map-related services
Location information may be particularly sensitive.
Meethouse will only request precise location permissions where reasonably necessary for the relevant feature and subject to applicable permissions and law.
You may control device-level location permissions through your operating system.
13. Cookies Used by Third Parties
Some technologies may be provided by third-party service providers.
These may include:
| Provider | Technology / Service | Potential Purpose | | ----- | ----- | ----- | | Firebase | Authentication | Login and OTP | | Firebase | Firestore | Application infrastructure | | Firebase | FCM | Push notifications | | Firebase | Crashlytics | Crash reporting | | Vercel | Website infrastructure | Hosting and security | | Google | Maps SDK | Maps and location | | Razorpay | Payment systems | Payment processing | | Google Play | Billing | Android purchases | | Apple | App Store/payment systems | iOS distribution and purchases |
The exact technologies used may change as Meethouse evolves.
Third parties may process information according to their own privacy policies and terms.
14. Consent Technologies
Where applicable, Meethouse may use a consent-management mechanism to remember your choices concerning optional Cookies and Similar Technologies.
A consent mechanism may remember:
- Whether consent was provided
- Which categories were accepted
- Which categories were rejected
- When consent was provided
- When consent should be renewed
We may retain records of consent where reasonably necessary to demonstrate compliance with applicable law.
15. Your Cookie Choices
Depending on your location and applicable law, you may be able to:
- Accept optional cookies
- Reject optional cookies
- Change your cookie preferences
- Delete existing cookies
- Block cookies through your browser
- Restrict certain device technologies
You can generally manage browser cookies through your browser settings.
16. Essential Cookies Cannot Always Be Disabled
Some technologies are essential to providing the service.
If you block or disable essential technologies, certain functionality may stop working.
For example:
- Login may fail
- Sessions may not be maintained
- Security controls may not work correctly
- Payment functionality may fail
- Certain website features may become unavailable
17. Mobile Application Technologies
The Meethouse mobile application may not use traditional browser cookies.
Instead, the application may use:
- SDKs
- Device identifiers
- Application identifiers
- Local storage
- Notification tokens
- Authentication tokens
- Crash-reporting technologies
- Security technologies
These technologies perform functions similar to cookies but operate differently from browser cookies.
18. Do Not Track
Some browsers provide a Do Not Track setting.
Because there is no universally adopted technical standard requiring all websites to respond to these signals in the same way, Meethouse may not respond to every Do Not Track signal.
Where applicable law requires us to recognize a legally valid privacy signal, we will comply with applicable requirements.
19. Global Privacy Controls
Where applicable law recognizes a legally valid browser or device privacy signal, Meethouse may process that signal according to the requirements applicable to the user and the relevant service.
The availability and functionality of such signals may vary depending on:
- Jurisdiction
- Browser
- Device
- Applicable law
- Technical implementation
20. International Users
Meethouse is intended for users worldwide.
Cookies and Similar Technologies may result in technical information being processed outside your country of residence.
Where required by applicable law, appropriate safeguards will be used for international transfers.
For additional information, see our Privacy Policy.
21. Data Security
We take reasonable technical, organizational, and administrative measures designed to protect information processed through Cookies and Similar Technologies.
However, no internet transmission, website, application, server, database, or electronic system can be guaranteed to be completely secure.
You should also take reasonable steps to protect your own device and accounts.
22. Retention
Cookies may remain on your device for different periods.
They may be:
Session Cookies
Deleted when your browser session ends.
Persistent Cookies
Remain for a defined period or until deleted.
The retention period may depend on:
- The purpose of the technology
- Technical requirements
- Security requirements
- Applicable law
- Your preferences
23. Third-Party Privacy Policies
Third-party providers may have separate policies governing their use of cookies and similar technologies.
Examples may include:
- Firebase
- Vercel
- Razorpay
- Apple
- Other providers used by Meethouse
You should review the applicable third-party policies where relevant.
24. Changes to This Cookie Policy
We may update this Cookie Policy when:
- We introduce new technologies
- We change service providers
- We introduce new features
- Applicable laws change
- Our privacy practices change
- Our website architecture changes
The Last Updated date at the top of this policy will indicate when it was most recently revised.
Where required, we may provide additional notice or request renewed consent.
25. Relationship With the Privacy Policy
This Cookie Policy explains our use of Cookies and Similar Technologies.
Our broader collection and use of personal information is described in our Privacy Policy.
If there is a conflict between this Cookie Policy and the Privacy Policy, the applicable privacy requirements and the more specific provision concerning the relevant technology will apply to the extent required by law.
26. Contact Us
For questions concerning this Cookie Policy or your privacy choices:
Skyroket - Meethouse
Address:
330 DDA SFS Flats
Sector 22, Dwarka
Delhi, India
Privacy & Grievance:
founder@meethouse.in
General Support:
support@meethouse.in
27. Related Documents
© 2026 Skyroket. All rights reserved.
Meethouse is operated by Skyroket.