Privacy Policy

Effective: 28 September 2026
Last changed: 14 October 2026

1. Who we are

The Adriba app and website are operated by Adriba d.o.o. ("Adriba", "we").

• Full legal name: Adriba društvo s ograničenom odgovornošću za informatičke usluge i trgovinu
• Address: Viktora Cara Emina 6, 52000 Pazin, Croatia
• OIB (tax identification number): 78069317416
• Court register number (MBS): 130176392
• Email for privacy matters: info@adriba.eu

Adriba d.o.o. is the data controller under the General Data Protection Regulation (GDPR).

2. In short

Adriba is an app for sea fishing. Where you fish, what you wrote down and where you took the boat are the most sensitive things an angler has, so we do not keep them in readable form.

• The exact coordinates of your catches, your notes, your location names and your recorded routes are encrypted on your device before they leave the phone. The key is on your device and we do not have it. We could not read this data if we wanted to, and neither could anyone who reached our server.
• We do not sell data. There are no advertising trackers in the app and we use no third-party analytics.
• What leaves the app is listed in sections 7 and 8, along with what does not.

This summary does not replace the text below, but it is what that text is for.

3. What data, why, and on what legal basis

3.1 Account

If you sign in with Google, Apple or Facebook, we receive your email address and an account identifier from them, never your password. Apple lets you hide your email address; if you choose that, we only receive a relay address.

3.2 Your fishing log

The blurred location is an approximation your device computes before anything is sent. It is used only where someone else can see the catch (friends, the public list if you turn it on). The spots you actually fish cannot be reconstructed from it.

3.3 Trips and routes

If you turn on route recording, your device records route points during an active trip. The route is encrypted on the device and is unreadable to us. What stays on the server are numeric summaries only: distance covered, duration, number of stops, time spent stationary. These summaries contain no coordinates.

Background recording happens only when both conditions are met: a trip is active and you granted the "Always" location permission. When you end the trip, recording stops. The app cannot follow a phone in a pocket all day.

3.4 Sightings and saved locations

The same as for catches: coordinates, names and descriptions are encrypted on the device.

An honest warning: saved locations created before encryption was introduced may still be on the server in readable form. The app quietly re-encrypts them the next time you open them, and since the safeguard was added no new or edited location can be created in readable form again. Until the old records are drained, this part of the promise does not fully hold for them.

3.5 Friends and shared trips

When you add someone as a friend, they see your catches with the blurred location. They never see your notes and never the exact spot, with one exception: when you hand a catch or a whole trip over to them yourself.

Handing over works by having your device encrypt the data specifically for the recipient's device (their public key). The server carries a record it cannot open. The recipient gets their own copy, which from that moment is theirs and no longer syncs with yours.

For this, every account publishes its public key. The private key is derived on the device from your encryption key and never leaves the phone.

3.6 Helping improve Adriba (optional)

This is off by default. If you switch it on in the privacy settings, your phone sends five coarse things for each of your catches: the species, the weather and sea in classes (temperature, wind, pressure, waves, moon, not the readings), the month, the region (for example western Istria) and the part of the day (morning, day, evening, night). Your phone works all of this out, not the server.

We do not send an exact location, date and time, notes, a photo, your name, your account or a catch id. Catches entered by a friend are not used. A contribution has nothing on the server that would connect it to you, so we cannot connect it to you either.

That is why what was sent cannot be withdrawn or deleted, not even when you delete your account. You can switch it off at any time: sending then stops. When you switch it on, the catches you logged earlier are sent too, and then every new one.

We use the data for better predictions of when and where fish bite. We do not sell it and never show anyone an individual's catches. The legal basis is your consent (Art. 6(1)(a)), which you give by switching it on.

3.7 Photos

Photos are not end-to-end encrypted. This is a deliberate decision: encrypted photos would mean your friends could not see them.

Instead:

• they sit in private storage; there is no public link
• every time one is displayed, a temporary link with a limited lifetime is created
• a catch photo is reachable by you and your accepted friends, a gear photo by you alone
• on upload the app re-encodes the photo, stripping its metadata, including the GPS tag written by the camera

3.8 Push notifications

If you allow them, we keep a device token so we can send you a notification. The token is removed when you sign out.

3.9 Key backup (optional)

If you turn it on, your encryption key is wrapped with a PIN you choose and stored with us in that wrapped form. We do not have the PIN and never see it, so the key cannot be unwrapped without it. A standard key-derivation function with a high iteration count is used.

If you forget the PIN, we cannot help you. That is not an administrative obstacle, it is a consequence of us not having the key.

3.10 Technical logs

Our hosting provider records technical data on every request, including the IP address, to detect abuse and fix faults. These are kept briefly and are not used for profiling. The legal basis is our legitimate interest in keeping the service running and unabused (Art. 6(1)(f)).

4. Device permissions

Any of these can be withdrawn at any time in your phone's settings. The app keeps working, without that part.

5. What we do not do

• We do not sell or rent personal data.
• There are no ad networks and no cross-app trackers in the app.
• We use no third-party analytics.
• We do not read your notes, because we cannot.
• We do not use your content to train AI models. The exceptions are two consents you have to turn on yourself. The first: a cropped, metadata-stripped copy of a photo of a confirmed catch may, after human review, become a reference image for species recognition. Without your consent this does not happen. You can withdraw the consent at any time, and we then remove your images from that set. The second: coarse, anonymous catch data from section 3.6, which cannot be withdrawn after sending because it cannot be connected to you.

6. Children

The app is not intended for anyone under 16. If we learn that we have collected data from someone under 16 without the appropriate consent, we delete it.

7. Artificial intelligence

Adriba uses Google's models (Gemini) for two things.

Species recognition from a photo. The photo goes to Google. Nothing else does: not the location, not your notes, not your log. The app says so at every point where a photo leaves the device.

VprašAI, the fishing assistant. What goes to the model: your question, the weather and sea conditions for the selected area, and those extracts from your own data that the answer actually required (for example "nine gilt-head bream in the past year in this area"). Exact coordinates never go.

The tools that read your data run on your device. The server is only a gateway to the model.

Saved conversations. If you choose to keep conversations, they are stored on your phone, encrypted with a key that never leaves the device, and we cannot read them. If you have also set up the recovery password, an encrypted copy is stored on our servers so that a new phone can restore it. That copy is as unreadable to us as your catches are: without your recovery password nobody, including us, can open it. It is deleted when you delete the conversation, when you switch recovery off and when you delete your account. You can delete one conversation or all of them at any time, or have them deleted after 30 or 90 days. As in any conversation, the last few messages travel to the model together with a new question.

What you choose to keep. Saved answers, open questions and your VprašAI settings and rules follow the same rules as saved conversations above: encrypted on your phone and, with recovery set up, an unreadable copy on our servers. When you point back at an earlier conversation (for example "as we said last time"), up to three short snippets of it are sent to the model with that one question, in addition to the last few messages that travel with every question. For an open question, the app asks the creator search, when you open the app and at most once a day, whether new material has appeared; only the question you already asked goes there, never your log, spots or other conversations.

Creator knowledge. If you choose to be answered in a creator's voice, the only things sent to search their material are your question and at most the species you are asking about. Not your log, not your spots, not your rules, not the conversation.

AI answers are not a guarantee and are not professional advice. See the Terms of Use.

8. Who we entrust data to

These are our processors. Each one handles only what is listed.

Your account, your log and your photos are stored in the European Union, in a data centre in Frankfurt, Germany (region eu-central-1).

Some of the providers listed above do process the data they receive outside the European Economic Area, chiefly in the United States. This applies to Google, Apple, Meta and Expo. Where that happens, the transfer is made on the basis of the European Commission's standard contractual clauses or an adequacy decision.

We may also disclose data where the law or a competent authority requires it.

9. How long we keep it

• Account data and your log: as long as you have an account. Deleting the account deletes them.
• Photos: until you delete them or delete your account.
• Contributions to improvement (optional): they stay after you delete your account, because they have nothing that would connect them to you.
• Technical logs: briefly, for as long as the hosting provider keeps them.
• Records a friend has adopted: stay theirs. When you hand a catch or a trip over, it becomes their record, exactly as if they had entered it. Deleting your account cannot delete that.

10. Your rights

Under the GDPR you have the right:

• to access your data,
• to have inaccurate data corrected,
• to erasure,
• to restriction of processing,
• to data portability,
• to object to processing based on legitimate interest,
• to withdraw consent at any time, where processing depends on it.

Account deletion is in the app, under profile settings, and takes effect immediately. For anything else, write to info@adriba.eu. We reply within one month at the latest.

There is a practical limit on encrypted data: because we cannot read it, we cannot produce it for you in readable form either. You can export it from the app, where it is unlocked with your key.

If you believe we are handling your data wrongly, you can complain to the Croatian Personal Data Protection Agency (azop.hr), which is our lead supervisory authority, or to the supervisory authority in your own country of residence.

11. Security

Data is transmitted encrypted. Access to rows in the database is restricted to their owner by row-level security. The most sensitive fields are encrypted on the device, as described above. Nobody can promise perfect security, but we can say what we have done to make a break-in on the server worth as little as possible.

12. Changes

If we change this policy, we publish the new version on this page and update the date at the top. For significant changes we will tell you in the app or by email.

13. Contact

Adriba d.o.o., info@adriba.eu

This policy is written in Croatian, Slovenian, English and German. In case of any discrepancy between versions, the Croatian version prevails.