Subprocessors & Third-Party Services Policy
Effective Date: September 19, 2026
Last Updated: September 19, 2026
This Policy explains the categories of third-party service providers used by Meethouse and how those providers may support the operation, security and functionality of the service.
Meethouse is operated by Skyroket.
1. Why Meethouse Uses Third-Party Services
Meethouse relies on specialized infrastructure and service providers to operate functions such as:
- cloud hosting
- databases
- authentication
- push notifications
- crash reporting
- maps
- payments
- app distribution
- website hosting
- security
- technical operations
These providers may process information on behalf of Meethouse or may independently process certain information according to their own terms.
2. Current Technology Providers
Firebase / Google Cloud
Meethouse uses Firebase infrastructure for several technical functions.
Potential services include:
- Firebase Authentication
- Firestore
- Firebase Cloud Messaging
- Firebase Crashlytics
Firebase Authentication
Used for account authentication, including supported login and OTP-related functionality.
Firestore
Used as a database for application information.
Firebase Cloud Messaging
Used for push notifications.
Firebase Crashlytics
Used for crash reporting and technical diagnostics.
Crashlytics should not be interpreted as Meethouse's general-purpose behavioral analytics platform.
3. Vercel
Meethouse uses Vercel for website hosting and related web infrastructure.
Vercel may process technical information necessary to provide and secure the website.
4. Google Maps
Meethouse uses Google Maps services for location-related functionality.
Google Maps may support:
- Nearby Police
- Nearby Hospitals
- Nearby Malls
- Nearby Metro Stations
- Open Map
- map exploration
- directions or map-based navigation where implemented
When a user chooses a mapping feature, location information may be transmitted to the applicable mapping provider.
Google may independently process information according to its applicable terms and privacy documentation.
5. Razorpay
Meethouse may use Razorpay for payment processing.
Depending on the transaction, Razorpay may process information such as:
- transaction details
- payment status
- amount
- currency
- subscription information
- payment identifiers
- payment-method information
Meethouse does not claim to store complete payment-card credentials when those credentials are handled directly by the payment provider.
6. Google Play
For Android distribution and applicable in-app purchases, Meethouse may use Google Play services, including Google Play Billing where implemented.
Google may independently process information according to Google's applicable terms and policies.
7. Apple App Store
For iOS distribution and applicable in-app purchases, Meethouse may use Apple services, including Apple's applicable in-app purchase infrastructure where implemented.
Apple may independently process information according to Apple's applicable terms and policies.
8. Email Providers
Meethouse may use an email provider for:
- customer support
- account communications
- transactional messages
- security communications
- legal notices
- other permitted communications
The specific provider may change over time.
Meethouse will update this Policy where required by applicable law.
9. What Is a Subprocessor?
A subprocessor is generally a third-party service provider that processes personal data on behalf of a controller or processor under an applicable contractual arrangement.
Not every third-party service used by Meethouse necessarily acts as a subprocessor.
Some providers may act as independent controllers for particular processing activities.
10. Third-Party Controller Processing
Certain providers may process information independently for their own purposes.
Examples may include:
- payment providers
- application stores
- mapping providers
- infrastructure providers where applicable
Where a provider independently determines its purposes and means of processing, that processing may be governed by the provider's own privacy policy.
11. Security Requirements
Meethouse seeks to use service providers that provide appropriate security measures suitable for the relevant service and risk.
Depending on the provider, contractual and technical safeguards may include:
- access controls
- encryption
- authentication
- logging
- monitoring
- incident response
- data-security commitments
- confidentiality obligations
12. International Transfers
Some service providers may process information outside India, the EEA, the UK or the country where a user resides.
Where applicable law requires a lawful transfer mechanism, Meethouse will seek to implement an appropriate mechanism.
13. Adding New Providers
Meethouse may add or replace service providers when necessary for:
- security
- scalability
- reliability
- functionality
- payments
- compliance
- technical operations
- customer support
Where legally required, Meethouse will provide applicable notice or obtain applicable consent.
14. User Choice
Certain third-party services depend on user choices or device permissions.
For example:
- location permission may control access to location-based features
- notification permissions may control push notifications
- payment providers process payments when you initiate purchases
- mapping services may receive information when you open mapping functionality
15. Data Minimization
Meethouse seeks to disclose only information reasonably necessary for the applicable service.
The exact information disclosed may vary depending on:
- the feature used
- device
- operating system
- permissions
- provider
- legal requirements
16. Third-Party Links
Meethouse may contain links or redirects to third-party services.
Meethouse does not control the privacy or security practices of third-party websites or applications.
Users should review the relevant third party's privacy terms.
17. Provider Changes
This Policy may be updated when Meethouse:
- adds a provider
- removes a provider
- changes a technical service
- changes payment infrastructure
- changes mapping infrastructure
- changes hosting infrastructure
- changes applicable data-processing arrangements
18. Current Provider Summary
| Provider / Service | Primary Function | | ----- | ----- | | Firebase Authentication | Authentication | | Firestore | Database | | Firebase Cloud Messaging | Push notifications | | Firebase Crashlytics | Crash reporting / diagnostics | | Vercel | Website hosting | | Google Maps | Maps / Nearby functionality | | Razorpay | Payment processing | | Google Play | Android distribution / applicable billing | | Apple App Store | iOS distribution / applicable billing | | Email provider | Email communications, where implemented |
19. Contact
Questions regarding third-party processing may be directed to:
General support:
Meethouse
Operated by Skyroket
330 DDA SFS Flats, Sector 22, Dwarka, Delhi, India