HOP Privacy Policy
HOP is built to know as little about you as possible. You don’t create an account, you don’t give us a phone number or an e‑mail, and the content of your messages is end-to-end encrypted — we can’t read it. Below we describe exactly what data exists, where it lives and who can see it.
This English version is provided for convenience; the Polish version is legally binding.
1. Controller
The controller of personal data is Appifi Sp. z o.o., Piotrkowska 276A, 90-361 Łódź, Poland, KRS 0001150929, NIP (VAT) PL7252351636, REGON 540700682 (“we”). For privacy matters write to privacy@hop-app.eu or by post to our registered office.
On the App Store the app is published from the Apple developer account of Rafał Mirowski, CEO of Appifi Sp. z o.o., on the company’s behalf. This does not change the controller of your data, which is Appifi Sp. z o.o.
This policy covers the HOP app for Android and iOS, the HOP internet relay, the hop-app.eu website and contact with us by e‑mail or through the contact form.
2. In short
- We run no user accounts and do not store your messages, contacts or conversation history — everything stays on your phone.
- Private messages are end-to-end encrypted. Phones along the way and our relay don’t know their content — they only see who a message is from and to (HOP identifiers), when it was sent and how big it is.
- By default HOP works without the internet. It connects to our server only if you turn the internet on in the app.
- We use no ads, no analytics, no profiling and no trackers. The hop-app.eu website sets no cookies.
3. Data on your phone
The app stores locally your cryptographic key pair (your HOP identity), name and status, contacts, messages, photos you sent and received, settings, and other people’s encrypted messages your phone carries on. On Android this data is in an encrypted database whose key is protected by the system key store (Android Keystore). On iPhone the identity keys are in the iOS Keychain and the rest is in app files protected by iOS Data Protection — readable only after the phone has been unlocked once since it was switched on. We have no access to this data. Uninstalling the app removes it from the phone.
Moving to another phone. “Move HOP to another phone” creates — only when you ask for it, after you unlock the phone — a backup file (.hopbackup) with your identity keys, name and status, your contacts with their verification state and, unless you turn it off, your chats and photos (without temporary and disappearing messages). The file is encrypted with a password you set (Argon2id and AES-256-GCM); without the password it cannot be opened, and we do not know it and cannot recover it. The file is created on the phone and saved wherever you choose — HOP never sends or uploads it; it leaves the phone only if you move it yourself. Whoever has the file and the password has your HOP identity: keep it like a key and delete it once the new phone works. After the move you can turn HOP off on the old phone, which removes your identity, contacts and chats from it.
4. What other phones in the mesh see
- Your card — name, status and public key — is visible to HOP phones nearby and passed on through the network. With “Hide me from strangers” on, strangers get a card without name and status; only your friends and people you write to get the real one.
- Private messages are end-to-end encrypted (X25519, HKDF-SHA256 and ChaCha20-Poly1305, Ed25519 signatures). Phones that carry them see the sender and recipient identifiers (public keys), time, size and hop count — not the content. Messages are encrypted to the recipient’s long-term key (no forward secrecy): someone who kept copies of encrypted messages and later obtained the recipient’s keys (for example from their unlocked phone) could read them. Disappearing messages are deleted only from the sender’s and recipient’s phones.
- “Nearby” announcements are public: signed but not encrypted. Every HOP phone around (up to 4 hops) sees them for the time you choose (15–60 minutes).
- Sharing HOP (Android) — when you pass the app on over Wi‑Fi, your phone creates its own Wi‑Fi network without internet access (Wi‑Fi Direct or a local-only hotspot) for at most 15 minutes and offers a page with the app file on it. The page and the file contain none of your data, and nothing of it reaches us.
- “Tap phones” (NFC) — when, on that screen, you hold your phone to the other person’s phone, the two phones exchange directly, over NFC, what the QR code shows: your card (name, status and public key) and a one-time invitation code, signed with your HOP key. None of it goes over the internet or reaches us. An Android phone answers over NFC as HOP only while that screen is open; an iPhone only reads an Android phone.
- An SOS alarm to everyone nearby is public: it contains your name, an optional note, battery level and — if you decide — your GPS position, updated as you move. It travels only through the mesh, never over the internet.
5. Internet relay (optional)
When you turn the internet on in the app, HOP connects over TLS to our relay (a server in an OVHcloud data centre in Poland). The relay stores and delivers encrypted messages to your contacts, also when they aren’t nearby. For this it processes:
- your IP address (for the duration of the connection),
- your card, which every HOP connection exchanges — your public key plus name and status (without name and status when “Hide me from strangers” is on),
- HOP device identifiers (public keys) of sender and recipient, packet time and size,
- encrypted packets — until delivered or expired (3 days by default, at most 7 days),
- encrypted “I’m online” signals HOP sends every few minutes to your verified contacts.
When the internet in the app is “Always on” and you and the recipient are both connected to the relay at the same time, the message goes through the relay even when you are next to each other (it may also go directly, phone to phone, in parallel). The relay then sees the same data as above — never the content.
The relay doesn’t know message content, tells no one who else is connected and doesn’t log who connects — it records aggregate counters only. If you turn on the “bridge” (hub) feature, your phone carries other people’s encrypted messages between the nearby network and the internet, within a daily data limit you set.
Legal basis: Art. 6(1)(b) GDPR (providing the service you request by turning the internet on) and Art. 6(1)(f) GDPR (security of the service).
Push notifications on iPhone (optional)
iOS puts apps to sleep in the background, so without this feature an iPhone receives internet messages only once HOP is opened. If you turn on “Notifications for messages over the internet” in the app (off by default, available only with the internet always on), your iPhone gives the relay its Apple notification token, signed with your HOP key. The relay then stores:
- this iPhone’s notification token,
- the ID of your HOP key (a hash of the public key — a pseudonym, no name or number) the token belongs to,
- the time of the last registration and of the last notification.
When a message is waiting for you and your phone isn’t connected at that moment, the relay asks the Apple Push Notification service (APNs) to show “New message in HOP” — no sender, no content and no other data about the message, at most one a minute. Apple delivers it to your iPhone as a processor; it sees the token, the app and the time of the notification. We delete the registration when you turn the feature or the internet off in the app, after 60 days without the phone connecting to the relay again, or when Apple reports the token as invalid (e.g. after the app was uninstalled). The relay’s logs contain numbers only, never tokens or identifiers. Legal basis: Art. 6(1)(b) GDPR (a service you turn on yourself).
Push notifications on Android (optional)
Android may put HOP to sleep in the background (especially on Samsung phones) and cut its internet access, so a message sent over the internet may wait until you open the app. If you turn on “Notifications over the internet (push)” in the app (off by default, available only with the internet always on), your phone gets a Firebase Cloud Messaging (FCM) token from Google and gives it to the relay, signed with your HOP key. The relay then stores the same data as for iPhone: the token, the ID of your HOP key (a pseudonym) and the time of the last registration and of the last wake-up.
When a message is waiting for you and your phone isn’t connected, the relay asks Google (FCM) to silently wake the app — the message contains only a “wake up” marker, no sender, no content and no message count, at most one a minute. HOP then connects to the relay and shows the notification itself. Google (Google Ireland Limited / Google LLC) delivers this message as a processor; it sees the token and the app installation ID, the Firebase project and the time of the wake-up. Before you turn the feature on the app does not connect to Firebase; we use neither Google Analytics nor the advertising ID. When you turn it off we delete the registration on the relay, and the app deletes the token and the installation ID at Google. Everything else (60 days, logs with numbers only, legal basis Art. 6(1)(b) GDPR) is as for iPhone above.
6. Location
HOP doesn’t track your location. Your GPS position is used only when you attach it to an SOS alarm or open the compass to reach someone calling for help. Only the recipients of the alarm see it; it reaches us only inside an encrypted SOS message to your contacts carried by the relay. On Android the system may require the location permission to scan for Bluetooth devices — HOP doesn’t read your position for that.
7. SMS and 112
If you wish, HOP prepares an SMS with your position for people you choose. You send it yourself with the system SMS app; it goes through your carrier and isn’t encrypted. The list of people is stored only on your phone. Calls to 112 are made by the system phone app.
8. App permissions
- Nearby devices / Bluetooth / Wi‑Fi — finding HOP phones and connecting to them.
- Notifications — new messages and SOS alarms, an ongoing notification while working in the background; on iPhone and Android optionally also push notifications through the relay (see section 5); optionally a notification when a friend from your contacts comes nearby — your phone works this out by itself from the mesh, sends nothing for it and keeps no history of who was around.
- Camera — only while scanning a contact’s QR code; the image is neither saved nor sent.
- NFC — only while the “Tap phones” screen is open: exchanging the contact code with the phone held to yours (see section 4).
- Location — see section 6.
- Photos — you pick a specific photo to send; it is compressed and encrypted on the phone.
- Contacts — only picking people for SMS SOS; HOP doesn’t read your address book.
- Background work / battery optimization (Android) — so the phone relays messages with the screen off.
9. Third-party services in the app
On Android HOP uses the Nearby Connections service of Google Play services, which connects phones locally. Google may process diagnostic data under its own privacy policy (policies.google.com/privacy). The app contains no advertising, analytics or crash-reporting libraries.
Update checks
HOP checks whether a newer version exists only when the internet in the app is “Always on” — with “Off” and “SOS only” it does not check at all. It does so at most once a day while the app is open (on Android also at most once a day in the background), and when you tap “Check now” in You → Updates. Turn the automatic checks off with the “Notify me about new versions” switch.
- Android from Google Play — HOP asks the Play Store app on the phone (the Google Play In-App Updates interface) and passes it no data about you. The Play Store contacts Google under Google’s terms (policies.google.com/privacy). Google Play downloads and installs the update once you agree.
- Android installed from a file (from the hop-app.eu website or passed on phone to phone) — HOP downloads hop-app.eu/version.json from our server, a file with the latest version number signed with our key. The request contains no identifiers and no phone data: our server sees the IP address and the header “User-Agent: HOP”, which go into the standard logs kept for 14 days (section 10). HOP never downloads or installs anything itself — it opens the page from which you download the file.
- iPhone — HOP asks Apple’s public service (itunes.apple.com) which version of HOP is in the App Store. Apple receives the IP address and the standard header iOS adds to every request (the app’s name and build number, the system version); Apple’s terms: apple.com/legal/privacy. You install the update in the App Store.
Legal basis: Art. 6(1)(f) GDPR (our legitimate interest: the security and proper operation of the app).
10. The hop-app.eu website, contact form and e‑mail
The website uses no cookies or analytics. The server keeps standard logs (IP address, date, page address, browser) for 14 days for security (Art. 6(1)(f) GDPR).
Contact form and e‑mail
You can write to us by e‑mail or through the contact form on hop-app.eu. A message sent through the form goes to the mailbox for the topic you choose: pomoc@, sugestie@, wspolpraca@, prasa@ or privacy@hop-app.eu.
- What data: your e‑mail address, your message, the topic you chose and — if you give them — your name and a subject. When you write a regular e‑mail, also whatever you put in it yourself (e.g. a signature).
- Purpose: replying to your message and handling the matter you contact us about.
- Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in answering messages sent to us. Where your message concerns entering into or performing a contract (e.g. a partnership), the basis is Art. 6(1)(b) GDPR.
- How long: for as long as needed to handle the matter and then no longer than 3 years, e.g. in case of follow-up questions or to establish, exercise or defend legal claims.
- Where: messages are stored only in our own mailboxes on our server in the European Union (a VPS at OVHcloud, the same one that hosts hop-app.eu). The form passes no data to any other service.
- No tracking: the form uses no cookies, no trackers and no third-party CAPTCHA. It is protected against spam by a single-use, short-lived code fetched from our server, a hidden trap field and a limit on the number of messages.
- IP address: to limit abuse, the server briefly uses your IP address to count how many messages were sent from the same address in a short time. The form does not store your IP address and does not attach it to the message; it may appear only in the standard server logs described above.
- Spam protection: before delivery, the message content is checked automatically by a spam filter running on our server (without your IP address and without passing the message to other companies). A message flagged as suspicious goes to our mailbox's "Spam" folder rather than being deleted. Your browser also performs a short calculation ("proof of work") that makes bulk sending harder; it collects no data.
- Who has access: only the members of our team who answer messages. OVH, as our server provider, processes data only on our behalf (see section 11).
- Is it required: giving your e‑mail address and a message is voluntary, but without them we can’t reply. Name and subject are optional.
- Your rights: you can ask for access to this data, its rectification, erasure or restriction of processing, and you can object — write to privacy@hop-app.eu. More in section 12.
11. Recipients and transfers outside the EEA
The relay, website and mail servers run at OVH (OVHcloud) in the European Union; OVH processes data only on our behalf. If you turn on push notifications on iPhone, the device token and the notification request (without content or sender) go to Apple (APNs), which may process them also outside the European Economic Area under its terms for that service. If you turn on push notifications on Android, the token and the wake-up request (without content or sender) go to Google (FCM), which may also process them outside the EEA under its terms for that service. For update checks, Google (Android from Google Play) or Apple (iPhone) receives the IP address and may also process it outside the EEA under its own terms (see section 9). Apart from that we don’t transfer data outside the EEA and we don’t sell it to anyone.
12. Your rights
You have the right to access, rectify and erase your data, to restrict processing, to data portability and to object to processing based on our legitimate interest. Since we run no accounts, you control most data yourself in the app (deleting chats, hiding, turning the internet off, uninstalling). To exercise your rights write to privacy@hop-app.eu. You may lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (ul. Stawki 2, 00-193 Warszawa), or with the authority in your country.
13. Children
HOP is intended for people aged 13 and over. People under 16 may use the internet features with the consent of a parent or guardian.
14. Changes
We will announce material changes to this policy on hop-app.eu and in the app’s update notes.
Effective 8 November 2026.