Privacy Policy

Last Updated: September 17, 2026

Hopme Privacy Policy

Hopme ("Hopme", "we", "our", or "us") respects your privacy and is committed to protecting your personal information.

This Privacy Policy explains how we collect, use, store, disclose, and protect information when you use the Hopme mobile application and related services.

By using Hopme, you agree to the practices described in this Privacy Policy.

1. About Hopme

Hopme is a mobile application that allows users to:

Discover local events
Create and manage events
Join events
Communicate event-related information
Manage personal profiles

The application is operated by:

Developer: Ihor Shymkov

Contact Email: hopme.app@gmail.com

2. Information We Collect

2.1 Information You Provide

When using Hopme, you may provide:

Email address (for sign-in and optional profile contact)
First and last name
Date of birth
Biography or profile description
Profile photo
Preferred language(s)
Optional phone number (profile contact only — not used for SMS authentication)
Event information
Event descriptions
Event locations
Event pricing information
Event participant information
Payment-related identifiers (when you purchase event creation packages)

Providing some information is necessary to use certain features of the application.

2.2 Authentication Information

To authenticate users, Hopme may process:

Email address
One-time email verification codes (6-digit OTP) sent to your email
Google account identifiers and OAuth tokens (when you choose Continue with Google)
Firebase Authentication user identifiers and session tokens

Email sign-in: When you request a verification code, our backend generates a short-lived code, stores a hashed version temporarily in our database, and sends the code to your email through Brevo, our email delivery provider. Codes expire after a limited time and are deleted after successful sign-in or expiry.

Google sign-in: Authentication is handled through Firebase Authentication and Google Sign-In. We receive basic profile information from Google (such as name, email, and profile photo URL) according to your Google account settings.

Phone numbers: Phone numbers may be added optionally in your profile for contact purposes. Hopme does not use phone numbers or SMS for account authentication.

2.3 Location Information

With your permission, Hopme may access:

Approximate location
Precise location

Location information is used to:

Display nearby events
Improve event discovery
Show your position on the map
Assist with event creation

Location access can be disabled at any time through your device settings.

2.4 Event Information

When creating or managing events, Hopme may store:

Event title
Event description
Event category
Event location
Event dates and times
Event language preferences
Participant limits
Pricing information
Organizer information

This information may be visible to other users depending on event visibility settings.

2.5 Device and Local Storage Information

We may automatically collect:

Device model
Operating system version
Application version
Preferred language
Time zone
Technical diagnostics
Crash reports

The application may also store certain data locally on your device (for example session preferences and cached profile data) to improve performance and allow offline access to some features.

2.6 Cloud Storage and Synchronization

When you use Hopme with our online backend, profile and event data may be stored and synchronized using Google Firebase services, including:

Cloud Firestore — user profiles, events, participation records, and purchase-related metadata
Firebase Authentication — account credentials and session management
Firebase Cloud Functions — server-side processing for email verification codes and payment completion

This allows your events and profile to be visible to other users across devices when you are signed in.

2.7 Local Notifications

With your permission, Hopme may schedule local notifications on your device (for example, reminders before an event you joined or organized). These reminders are processed on your device and do not require us to collect additional personal data beyond the event information already stored in your account.

You can disable notifications in your device settings at any time.

2.8 Payment Information

When you purchase event creation packages (credits that allow you to create additional events beyond the free limit), payments are processed by Stripe, Inc., our payment processor.

Hopme does not store full payment card numbers on our servers.

We and Stripe may process:

Purchase amount and currency (PLN)
Package identifier (e.g. number of event credits)
Payment status and transaction identifiers
Billing-related metadata required to complete the purchase

Card details are entered directly into Stripe's secure payment interface and are handled according to Stripe's Privacy Policy.

2.9 Website Analytics

When you visit the Hopme website, we use Vercel Web Analytics to understand how the site is used. This may include:

Page views (for example the landing page, city catalog, map, and event pages)
Clicks on App Store and Google Play download links
Clicks that try to open the Hopme mobile app from the website

Vercel Web Analytics is designed to be privacy-friendly: it does not use cookies and does not identify you as an individual. We use these insights to improve the website and understand whether visitors browse pages or continue to the app stores.

We use payment information to:

Complete purchases
Grant event creation credits to your account
Prevent fraud and duplicate charges
Provide purchase-related support
Comply with legal and accounting obligations

Purchase records may be retained as required by applicable law.

During beta testing, the application may grant event creation credits in test mode without processing a real payment.

3. How We Use Information

We use collected information to:

Create and manage accounts
Authenticate users
Provide application functionality
Display and manage events
Improve user experience
Maintain application security
Prevent abuse and fraud
Respond to support requests
Send email verification codes for sign-in
Synchronize data across devices
Process in-app purchases of event creation packages
Comply with legal obligations

4. Legal Basis for Processing (EEA and GDPR)

If you are located within the European Economic Area, we process personal data under one or more of the following legal bases:

User consent
Performance of a contract
Compliance with legal obligations
Legitimate business interests

Where consent is required, you may withdraw consent at any time.

5. Information Sharing

We do not sell personal information.

We may share information only in the following circumstances.

5.1 Other Users

Certain information may be visible to other users, including:

Display name
Profile photo
Languages
Public events you create
Event participation status

Phone numbers and email addresses are not publicly displayed unless explicitly shared by the user in their profile contact settings.

5.2 Service Providers

We may use trusted third-party providers to operate the service.

Examples may include:

Authentication providers (Firebase, Google)
Email delivery providers (Brevo)
Cloud hosting and database providers (Google Firebase)
Payment processors (Stripe)

These providers process information only as necessary to perform services on our behalf.

5.3 Legal Requirements

We may disclose information when required to:

Comply with legal obligations
Enforce our policies
Protect users
Protect public safety
Prevent fraud or abuse
Respond to lawful requests from authorities

6. Data Retention

We retain personal information only for as long as necessary to:

Provide services
Fulfill legal obligations
Resolve disputes
Enforce agreements

Retention periods may vary depending on the type of information.

7. Account Deletion

Users may delete their accounts from within the application.

To delete an account:

Open Hopme.
Navigate to Profile.
Open Edit Profile.
Select Delete Account.
Confirm deletion.

Upon deletion:

Your Firebase Authentication account is deleted where technically possible.
Your Firestore user profile is removed.
Events you created as organizer are removed from the platform.
Personal profile information will be removed or anonymized on our systems and local caches.
Event participation records may be removed or anonymized.
Unused purchased event creation credits are forfeited upon account deletion and are not refundable, except where required by applicable law.

If deletion cannot be completed immediately (for example, because recent re-authentication is required), you may need to sign in again and retry, or contact support.

Some information may be retained where required by law (for example payment records processed by Stripe).

Deletion is usually processed immediately when confirmed in the app; backup systems may take up to 30 days to fully purge data.

8. Data Security

We implement reasonable technical and organizational measures to protect information.

Measures may include:

Secure authentication
Encrypted communications
Access controls
Infrastructure security measures

However, no method of transmission or storage is completely secure.

We cannot guarantee absolute security.

9. Children's Privacy

Hopme is not intended for children under 13 years of age.

We do not knowingly collect personal information from children under 13.

If we become aware that personal information from a child under 13 has been collected, we will take reasonable steps to delete it.

10. Your Privacy Rights

Depending on your jurisdiction, you may have rights including:

Access to personal information
Correction of inaccurate information
Deletion of information
Restriction of processing
Objection to processing
Data portability
Withdrawal of consent

To exercise these rights, contact:

hopme.app@gmail.com

11. International Transfers

Your information may be processed in countries outside your country of residence.

Where required by law, we implement appropriate safeguards for international data transfers.

12. Third-Party Services

Hopme may use third-party services whose privacy practices are governed by their own policies.

Examples may include:

Firebase Authentication
Google Cloud Firestore
Firebase Cloud Functions
Google Sign-In
Brevo (transactional email for verification codes)
Mapping and geolocation providers
Cloud storage providers
Stripe (payment processing for event creation packages)
Apple Sign-In (where offered on iOS and required by platform policies)
Vercel Web Analytics (website page views and download-button clicks)

Users should review the privacy policies of applicable third-party services.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

Updated versions will be published within the application or on associated websites.

Continued use of Hopme after updates become effective constitutes acceptance of the revised Privacy Policy.

14. Contact Information

For questions regarding this Privacy Policy or your personal information, contact:

Ihor Shymkov

Email: hopme.app@gmail.com

Application: Hopme

15. Acceptance

By creating an account or using Hopme, you acknowledge that you have read and understood this Privacy Policy and agree to its terms.