Privacy policy
Updated on 8 November 2026
Your location is never visible to another angler. Lura may keep the location of your sessions for you, hosted in the European Union and protected by access rules tied to your account; no profile, no catch shared with your friends, no shared image, no ranking and no answer from the assistant ever shows it to anyone else.
Lura shows no ads, sells no data and does not track you across other apps.
This policy explains what data the Lura app (iPhone and Android) and its server process, why, with which providers, for how long, and how to exercise your rights. The lura.fish website uses no cookies, no third-party scripts and no audience measurement; like any host, its host (Hostinger) receives the IP address and the address of the page requested, invitation code included for an invitation page (lura.fish/ami/…), in its technical logs. The home page's "Tell me when it's out" form keeps only your email address (see section 2).
1. Who is responsible
Lura is published by Liminal, the controller of the data described here. For any question or request about your data: support@lura.fish.
2. What Lura processes, why, and on what basis
Forecast, map and regulations (performance of the contract)
- For the forecast, the app sends Lura's server the point of the chosen place (your location if you allow location access, the town or body of water you picked, the point you picked on the map, or one of your spots), the type of water (river, lake or sea) and your fishing category. A point picked on the map travels exactly like your location or the chosen town: in that forecast request. The server computes the forecast for an area of about one kilometre, keeps it in memory for at most one hour for that area, and never writes coordinates to its logs.
- The app only asks for your location while it is open, never in the background.
- When you search for a town or a body of water (lake, pond, bay), the text you type goes through Lura's server to the Géoplateforme geocoding service (for towns in France) and to MapTiler (for the rest of the world and for bodies of water). To name the place of a forecast, the server sends them the centre of the area of about one kilometre, never your exact point: MapTiler thus receives the text you type to search for a town or a body of water, and a point rounded to about 1 km to name the place. Neither your account nor your IP address is passed on to them. When the server cannot name the place, your phone asks its system's geocoder (Apple on iPhone, Google on Android), with the same point rounded to about 1 km; Lura keeps only the town's name, on your phone.
- The map is made of MapTiler tiles, which your phone loads directly.
- Sea depth is served by Supabase (European Union) from a public file: when the map frames a sea place covered by this data, the app reads the start of this file; then, while the Depth layer is on, the parts for the area shown. Supabase then sees your IP address and which parts of the file are requested, that is roughly the area you are looking at, like MapTiler for the base map. Lura's server does not see these reads. Depth covers the sea only; its sources are credited in section 9.
Account and synced journal (performance of the contract)
- An account is required: you sign in with Apple, Google or an e-mail address and a password. The first time you open the app, before you sign in, Lura creates a provisional account without an e-mail address to keep your journal; signing in attaches it to your account. The sign-in service keeps the account's e-mail address (the one you enter, or the one Apple or Google passes on; Apple may hide it) and, for a Google account, the profile information Google passes on. If Apple or Google gives your first name, Lura suggests it as your display name: you keep it or change it before confirming. Your Google account's photo shows in your avatar, on your phone only: Lura copies it nowhere and your friends don't see it.
- Information received from Google is only used to create and secure your account, and to suggest your first name as your display name and your photo in your avatar. It is never sold, never used for advertising, and never used to train or feed AI models. Lura's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Lura syncs with your account: your sessions (dates, type of water, target species, town, conditions, rig; the GPS location only for a session started live, a chosen town or a trip logged afterwards keeping only the town's name), your catches (species, length, weight, time, release, rig, conditions, up to five photos), your gear (name, specifications, photo), your badges, your level, your display name and your answers to the app's welcome questions (waters, species, disciplines, beginner or not, fishing category).
- Photos are stripped of their metadata, including the GPS location, on your phone before anything is sent, then stored in private storage.
- If you sign in with Apple, the server keeps a token issued by Apple, used only to withdraw the authorisation given to Lura when you delete your account.
Purchases (performance of the contract)
- Subscriptions (3 species, Every species) are paid through the App Store or Google Play: Lura never sees your bank card.
- RevenueCat manages purchases for Lura: it receives your Lura account identifier (a random string, with no name or e-mail), your purchases and the store receipts, and technical information about the device. Lura's server keeps your entitlements (the end of your subscription) and, with the 3 species plan, your 3 species and the date of your last swap. This data stays after the subscription ends, until you delete your account, so you can resubscribe; no other angler sees it, not even your friends; it leaves with your account. Your plan and the names of your 3 species are also sent to Anthropic with your questions to the assistant (see below).
AI assistant (performance of the contract; sending to Anthropic with your agreement)
The assistant and the AI gear helper answer with Claude, Anthropic's model. Before your first request, the app asks for your agreement: without it, nothing is sent, and the rest of the app works. For each request, Lura sends Anthropic:
- your question and your latest messages, from which the server removes anything that looks like coordinates;
- the town of the forecast (never a more precise place), the type of water, your category, the language and the species in view;
- your plan (free, 3 species or Every species) and, with 3 species, the names of your 3 species;
- a summary of your journal with no place at all: the current session (start, target species, number of catches) and your last five trips (date, type of water, target and caught species, blank or not);
- the names of your active gear;
- facts added by the server: the time, water and wind conditions, the best hours of the day, and the town's regulations taken from Lura's files;
- for the gear helper, your search or the photo you picked, reduced and stripped of its metadata.
Your location and the forecast area are never sent to Anthropic. Lura's server keeps neither your questions nor the answers: it counts your uses (for your credits) and keeps a technical log of each call (date, purpose, model, size in tokens, duration, outcome), without its content. Your conversations stay on your phone. You can withdraw your agreement in Profile › Settings › Privacy.
Coverage requests (legitimate interest)
Outside the areas Lura already covers, the "Bring Lura here" button asks Lura's server to note your region: it finds it from the forecast's area and only keeps your country and your region, never your town or your location, linked to your account so that only one request is counted, deleted with it. Lura only reads the number of requests per region, to choose where to open next. Nothing is sent unless you tap the button.
Species reports (legitimate interest)
With an account, "Report a mistake" on a species page tells Lura that a species is not found where you fish, or that it is there but Lura doesn't score it. Lura's server keeps the species, the kind of report, your region (the département in France, the state or province elsewhere), found from the forecast's area, the date and, for "found here", the catch from your logbook you picked as proof, with its photos already cleaned of their metadata. It never keeps your town or your location: it reads the location of that catch's session only to know whether it was made in the same region, and keeps only yes or no. The report is linked to your account so that only one is counted per species and region, and deleted with it. Nobody but you sees it (in Profile › Settings › My reports); only Dany, who publishes Lura, reads the totals per species and region, and the chosen catch when it needs checking, to correct where a species is said to live. No number of reports is shown to other anglers.
Local anglers' feedback (legitimate interest)
With an account, Lura may ask you two one-tap questions: on a species page, whether it is in season where you fish this month; at the end of a trip, whether the announced score was right. Lura's server keeps the species, the question, your answer (yes, mixed or no; "I don't know" is never sent), the month, your region (the département in France, the state or province elsewhere), found from the forecast's area, and, for the end of a trip, the announced score and a hashed key that stops the same trip from being counted twice. It never keeps your town, your location or your session. The answer is linked to your account so that only one is counted per angler, and deleted with it. Other anglers only see a total per region, and only once five different anglers have answered; it never changes the score or its confidence. Dany, who publishes Lura, reads these totals to review the species' seasons.
Audience measurement (exempt from consent)
It is on by default: these are anonymous usage statistics, used only to improve Lura (which screens are used, where people stop, what works badly). You can turn it off at any time in Profile › Settings › Privacy: nothing more is sent, and the installation identifier is erased from your phone. The app sends PostHog usage events: app opened, screen viewed (its name only, never its content), forecast viewed (type of water), species sheet opened, session started, catch logged (species, released, with or without a photo), blank trip, badge earned, question asked, offers shown, plan chosen (type of offer), purchase started (type of offer), purchase (type of offer), purchase failed (type of offer and kind of error), purchases restored (outcome), rig advice viewed, gear added, Depth layer turned on or off, invitation shared (link or QR code), friend request sent, request accepted or declined, visibility of a catch chosen (private, friends or chosen friends, with or without water and weather), Bravo sent, photo reported, angler blocked, store review prompt requested, coverage request sent (country and region), species report sent (kind and country), local anglers feedback sent (question and country); the friends events carry no identifier, no username, no code and no number of friends. Each event carries the app version, the system (iOS or Android), the language (French or English) and an installation identifier drawn at random, never your account identifier, never a place finer than a region (only the coverage request carries a country and a region; the species report and the local anglers feedback, a country); Lura asks PostHog to create no person profile and to infer no town from your IP address, and Lura's PostHog project keeps no IP addresses.
The installation identifier is renewed before 13 months, whether or not you use the app; deleting your account, signing out or turning the measurement off erases it too. These statistics serve Lura alone: no advertising, no profiling, no cross-referencing with your account, your journal or other apps and sites, no transfer to a third party; PostHog processes them on Lura's behalf only. This is the audience measurement that the CNIL (the French data protection authority) exempts from consent, based on Lura's legitimate interest in improving the app; you object to it by turning it off.
Security, abuse prevention and crashes (legitimate interest)
- Anti-bot check: when an account is created (guest included), when you sign in and when you reset a password, the app runs an invisible check, Cloudflare Turnstile. Cloudflare receives your IP address and technical signals from the device and the check page, to tell a person from a bot.
- Limits: the server counts requests per account or per IP address, in memory, to curb abuse. Guest accounts' requests to the assistant are also counted per IP address and per day: the server keeps a keyed fingerprint of the address (HMAC), never the address itself, erased every day at most three days after the last request. Invitation code attempts are counted per account and per hour (20 at most); counts older than a day are erased at the next attempt, and all of them with the account.
- Crashes: when the app or the server hits an error, a report goes to Sentry: the error, the app version, the device model and system, and your Lura account identifier. No screenshot, no session recording, no coordinates: request bodies and query strings are filtered.
- Lura's server logs: one line per request (method, path, status, duration), with no IP address, no location and no content.
- Supabase logs: the app talks to Supabase directly, which sees your IP address. Its sign-in service keeps a log of account events (sign-in, sign-out, deletion…) with the account identifier, the e-mail address, the IP address, the type of device and the date; the platform also keeps technical logs of requests.
The website's "Tell me when it's out" list (consent)
- If you leave your email address in the form on the lura.fish home page and tick the box, Lura keeps that address, the date, the language of the page and the version of the text you accepted, in a file at Hostinger, outside the public website. Nothing else: no IP address, no cookie.
- It is used only to announce the app's launch on the App Store and Google Play: one message, two at most if the two stores do not open on the same day. Never advertising, never passed on to anyone, never linked to an app account.
- You can withdraw your agreement at any time, by replying to the message or by writing to support@lura.fish: your address is then erased.
What is required, and what is not
No law requires you to provide this data. Location is optional (you can pick a town); an account, even a guest one, is needed to sync your journal; without your agreement, the AI assistant stays closed; audience measurement, on by default, can be turned off in the settings. Lura makes no fully automated decision with legal effects on you: the forecast score is about fish, not about you.
3. What stays on your phone
Your journal, photos, gear, conversations with the assistant, the chosen place, your spots (the places you keep with the star: the list is never sent; a spot you choose as your place travels like any chosen place, in the forecast request), your settings (theme, language, units, audience measurement, AI agreement), the regions where you asked for Lura, your plan and your 3 species (a copy for display) and recent forecasts are kept in the app. They are erased when you delete your account, when you sign out, or when you uninstall the app; only your choice about audience measurement stays after a deletion or a sign-out, so that a measurement you turned off does not come back on.
4. Providers and countries
- Supabase (Supabase, Inc.; project hosted in the European Union): database, accounts, photos, and account e-mails (confirmation, password reset); serves the public sea depth file; sees your IP address and keeps the logs described above.
- Fly.io (Fly.io, Inc.; Lura's server in Paris): hosts Lura's server, which receives the app's requests, including the forecast point and your IP address.
- Anthropic (Anthropic PBC, United States): the AI assistant, with your agreement (see above).
- RevenueCat (RevenueCat, Inc., United States): purchase management.
- Apple and Google: sign-in with your Apple or Google account, payment and management of purchases in the App Store and Google Play, under their own privacy policies.
- MapTiler (MapTiler AG, Switzerland): map tiles; sees your phone's IP address and the map area shown. Town search outside France, search for bodies of water everywhere, and place names: only Lura's server queries it, with the text of your search or the centre of an area of about one kilometre, never your IP address.
- Open-Meteo (OpenMeteo GmbH, Switzerland), WorldTides (Brainware LLC) and Hub'Eau (eaufrance, France): weather, sea, river flow, water temperature and tides. Only Lura's server queries them, with the centre of an area several kilometres wide or the code of a gauging station, never your point or your IP address.
- USGS (U.S. Geological Survey, United States), ECCC (Environment and Climate Change Canada) and NOAA (National Oceanic and Atmospheric Administration, United States): measured river flow and water temperature in the United States and Canada, tides in the United States. Only Lura's server queries them, with an area of about 40 km around a rounded point, or the code of a public station, never your point or your IP address.
- Environment Agency (England, United Kingdom) and Rijkswaterstaat (the Netherlands): measured river flow, river level and water temperature in England and the Netherlands, tides in the Netherlands. Only Lura's server queries them, with the centre of an area several kilometres wide or the code of a public station, never your point or your IP address.
- PEGELONLINE (WSV, federal waterways, Germany) and SMHI (Swedish Meteorological and Hydrological Institute): measured river flow and water temperature in Germany, measured river flow in Sweden. Only Lura's server queries them, with the code of a public station, never your point or your IP address.
- Pegel Aktuell (BMLUK, hydrographic service, Austria), LVĢMC (Latvian Environment, Geology and Meteorology Centre) and Keskkonnaagentuur (Estonian Environment Agency): measured river flow in Austria, measured water temperature in Latvia and Estonia. Only Lura's server queries them: it reads the national file of readings and picks the station itself, never sending them your point or your IP address.
- LHMT (Lithuanian Hydrometeorological Service): measured water temperature in Lithuania. Only Lura's server queries it, with the code of a public station, never your point or your IP address.
- WMIP (Water Monitoring Information Portal, Queensland, Australia): measured river flow and water temperature in Queensland. Only Lura's server queries it: it reads the readings of all the state's stations and picks the station itself, never sending your point or your IP address.
- SAICA Ebro (Confederación Hidrográfica del Ebro, Spain): measured water temperature in the Ebro basin. Only Lura's server queries it, with the code of a public series, never your point or your IP address.
- Provincia di Bolzano (Civil Protection Agency of South Tyrol, Italy): measured river flow and water temperature in South Tyrol. Only Lura's server queries it, with the code of a public station, never your point or your IP address.
- Euskalmet (the Basque Government's meteorology agency, Spain): measured river flow and water temperature in the Basque Country. Only Lura's server queries it, with the code of a public station and a token of Lura's own, never your point or your IP address.
- Copernicus Marine (the European Copernicus Marine Service, Mercator Ocean International): sea temperatures measured by coastal buoys and tide gauges. Only Lura's server queries it, with the name of a buoy's public file, never your point or your IP address.
- Géoplateforme (IGN, France): finds the town at the centre of an area of about one kilometre, and the towns matching your search. Only Lura's server queries it.
- Sentry (Functional Software, Inc., United States): crash reports.
- PostHog (PostHog, Inc.; data hosted in the European Union, in Frankfurt): audience measurement, unless you turned it off; the project keeps no IP addresses.
- Cloudflare (Cloudflare, Inc., United States): Turnstile anti-bot check.
- Hostinger (Hostinger International Ltd., Cyprus): hosts the lura.fish website and the "Tell me when it's out" list, and carries the email that announces the launch.
5. Transfers outside the European Union
Anthropic, RevenueCat, Cloudflare, Sentry, Apple and Google may process data in the United States or in other countries outside the European Union. Supabase, Fly.io and PostHog host Lura's data in the European Union but are American companies. These transfers and accesses rely, as each provider states, on the EU–US Data Privacy Framework or on the European Commission's standard contractual clauses. MapTiler and Open-Meteo are in Switzerland, whose data protection the European Commission recognises as adequate.
6. How long
- Your account and its data: as long as your account exists. When you delete it, its data is erased at once: journal, locations, photos, gear, badges, profile, credit counters, your plan and your 3 species, log of AI calls and Apple token; Lura also asks Apple to withdraw the sign-in authorisation and RevenueCat to delete your customer record. Only what is described below remains.
- What you delete in the app: a deleted session, catch or piece of gear stays marked as deleted for at most 90 days, so that your other devices erase it too, then disappears. The photos of a deleted catch go with it.
- Removed or replaced photos: kept for at least 30 days (so another device does not bring them back), then erased by the app, or by the server's clean-up once nothing has referred to them for 90 days.
- Files arriving after an account was deleted: erased after 2 days.
- Fingerprint of guests' IP addresses: 3 days at most.
- Friends and reports: see section 11.
- Backups: when the project's Supabase plan includes them, the database is backed up daily; according to Supabase's documentation, these backups are kept for at most 30 days. Deleted data may remain in them until they are replaced, without being used.
- Supabase logs: technical request logs are kept for 1 to 90 days depending on the project's plan, according to Supabase's pricing. The log of account events, when it is also written to the database, has no set duration and is not erased by the account deletion (the deletion event is in it).
- Anthropic deletes requests and answers received through its API within 30 days, except for legal obligations or enforcement of its usage policy (up to 2 years for a flagged request), according to its policy.
- Sentry keeps crash reports for 30 to 90 days depending on the plan.
- PostHog: audience measurement events are kept for 25 months at most (currently 1 year, the length of PostHog's free plan); they are not linked to your account. The installation identifier is renewed before 13 months.
- Coverage requests: as long as your account exists; deleted with it.
- Species reports: as long as your account exists; deleted with it.
- Apple, Google and RevenueCat keep your purchases under their own rules and accounting obligations.
- On your phone: until you delete your account, sign out or uninstall the app.
- The "Tell me when it's out" list: erased once the launch is announced, and at the latest 12 months after you signed up.
7. Your rights
You can access your data, correct it, erase it, restrict its use, object to processing based on legitimate interest, withdraw your consent at any time, and get your data in a readable format (portability). You can also set directives on what happens to your data after your death (French Data Protection Act, article 85).
- Export: Profile › Settings › Export my journal gives a JSON file of your sessions (with their locations), catches, gear and badges, without the photos.
- Delete your account: Profile › Settings › Delete my account, or by e-mail (Delete your account).
- Withdraw your consent to the AI assistant, or object to audience measurement by turning it off: Profile › Settings › Privacy.
- For everything else: support@lura.fish. We answer within one month. We may ask you to prove the account is yours, never for your password.
- If you believe your rights are not respected, you can lodge a complaint with the CNIL (the French data protection authority) or the authority of your country.
Your rights by country or state
- United States. Depending on your state (California, Colorado, Virginia, Texas…), you can ask to access, correct, delete and get a copy of your data, and opt out of its sale or its sharing for targeted advertising. Lura sells no data and shares none for targeted advertising. Your precise location is treated as sensitive data: it is only used for the forecast, your log and your devices, never shown to another angler. Requests go to the same addresses as above; you can appeal a refusal with us, then with your state's attorney general.
- Canada. The Personal Information Protection and Electronic Documents Act (PIPEDA) applies. Your data is hosted outside Canada, in the European Union and, for some providers, in the United States (sections 4 and 5), where it is subject to the laws of those countries. You can complain to the Office of the Privacy Commissioner of Canada.
- Quebec. The person in charge of the protection of personal information is the president of Liminal (named in the legal notice), reachable at support@lura.fish. Before communicating information outside Quebec, Lura assessed the privacy factors (providers' countries, contractual safeguards, sensitivity of the data). You can also contact the Commission d'accès à l'information du Québec.
- United Kingdom. The UK GDPR applies: the same rights as in section 7. The United Kingdom recognizes the European Union as providing adequate protection, and the European Commission renewed its adequacy decision for the United Kingdom on 19 December 2025 (until 27 December 2031). The authority is the ICO (Information Commissioner's Office). For a place in England or the Netherlands, Lura's server queries the Environment Agency and Rijkswaterstaat about gauging stations, never with your location or your account.
8. Age
A Lura account (guest included) is open from age 13. Lura is not directed at children under 13: when the store (Apple or Google) gives an age bracket under 13, the app stays on the phone (forecasts and log), with no account, no friends, no AI assistant and no reports. This age bracket stays on your phone: it is never sent to Lura, to audience measurement or to crash reports. In France, under 15, what relies on your consent (the AI assistant) also needs the agreement of a parent or legal guardian. If you think a child under 13 has given us data, write to us: we will delete it.
9. Depth data: sources and credits
The depth lines of the Depth layer are drawn by Lura from public data sets, reprocessed by Lura. Depth covers the sea only.
Depths are below chart datum (lowest astronomical tide, LAT): at high tide there is more water. Indicative depth: not for navigation.
- SHOM, 2015. MNT Bathymétrique de façade Atlantique (Projet Homonim) DOI 10.17183/MNT_ATL100m_HOMONIM_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 6 June 2019. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2015. MNT Bathymétrique de façade du Golfe du Lion - Côte d'Azur (Projet Homonim) DOI 10.17183/MNT_MED100m_GDL_CA_HOMONIM_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 30 October 2018. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2015. MNT Bathymétrique de façade de la Corse (Projet Homonim) DOI 10.17183/MNT_MED100m_CORSE_HOMONIM_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 30 October 2018. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2020. MNT topo-bathymétrique côtier d'une partie du golfe normand-breton (PAPI Saint-Malo) DOI 10.17183/MNT_COTIER_GNB_PAPI_SM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 12 April 2021. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2015. MNT topo-bathymétrique côtier de la zone « Morbihan » à 20m (Projet TANDEM) DOI 10.17183/MNT_COTIER_MORBIHAN_TANDEM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 30 October 2018. Data modified by Lura: the depth lines are drawn from the grid.
- Shom, 2022. MNT topo-bathymétrique côtier des Pertuis Charentais (Projet HOMONIM) DOI 10.17183/MNT_COTIER_PERTUIS_HOMONIM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 17 July 2023. Data modified by Lura: the depth lines are drawn from the grid.
- Shom, 2022. MNT topo-bathymétrique côtier de l'estuaire de la Gironde - Aval V2.0 (Projet HOMONIM) DOI 10.17183/MNT_COTIER_GIRONDE_AVAL_HOMONIM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 15 September 2026. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2022. MNT topo-bathymétrique côtier du bassin d'Arcachon et ses abords (Projet HOMONIM) DOI 10.17183/MNT_COTIER_ARCACHON_HOMONIM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 17 July 2023. Data modified by Lura: the depth lines are drawn from the grid.
- SHOM, 2016. MNT topo-bathymétrique côtier de la baie de Saint-Jean-de-Luz et de ses abords à 20m (Projet TANDEM) DOI 10.17183/MNT_COTIER_BAIE_SJL_TANDEM_20m_WGS84 (data set page). Licence Ouverte (Etalab Open Licence). Data set updated on 30 October 2018. Data modified by Lura: the depth lines are drawn from the grid.
- EMODnet Bathymetry Consortium (2024): EMODnet Digital Bathymetry (DTM 2024) DOI 10.12770/cf51df64-56f9-4a99-b1aa-36b8d7b743a1 (data set page). CC BY 4.0. EMODnet product of the European Union, under the CC BY 4.0 licence. Data set updated on 19 February 2025. Data modified by Lura: the depth lines are drawn from the grid.
10. Species catalogue: source and credit
The names and classification of the fishes and cephalopods in the species catalogue come from TAXREF, the taxonomic reference for France from PatriNat, bundled in the app. This catalogue processes no angler data.
- TAXREF v18.0 (January 2025), PatriNat (OFB-MNHN-CNRS-IRD), Licence Ouverte 2.0 (Etalab Open Licence 2.0) — data modified by Lura (fishes and cephalopods of mainland France and Corsica, angler names added). Etalab Open Licence. Gargominy, O., Tercerie, S., Régnier, C., Ramage, T., Dupont, P., Daszkiewicz, P. & Poncet, L. 2025. TAXREF, référentiel taxonomique pour la France : méthodologie, mise en œuvre et diffusion. Rapport PatriNat (OFB-CNRS-MNHN), Muséum national d’Histoire naturelle, Paris. 47 pp. (data set page).
11. Friends
Friends are optional and need a linked account and a username. A friendship starts from an invitation code or link that you give yourself, and only counts once the request is accepted: Lura has no search by name, no directory and no public profile. Your catches and your outings are shared with « My friends » by default since 12 November 2026: after each catch, the « Share a catch » screen lets you pick « Private » in one tap, and you change this default in Profile › Settings › Friends and privacy. « My friends » also means the friends you add later. Your location is never shared. This processing serves the feature you use (performance of the contract); reports, blocks and moderation also serve the safety of the community (legitimate interest) and the duties of a host of content (legal obligation, the EU Digital Services Act).
What your friends see
- Your card: your username, your level, your points, your number of badges, the day since which you have been friends, and, among the catches you share with « My friends », how many this month and the biggest one (species and length). The ranking, between friends only, is made from these numbers; leaving the ranking removes you from it, not from your card. In Profile › Settings › Friends and privacy, you can leave the ranking, refuse every request, change your invitation code (the old one stops working) and unblock an account.
- The catches you share with them, with « My friends » or with the friends you choose: species, length, weight, released or kept, the day and the time of day (dawn, morning, midday, afternoon, evening, night; never the hour), the photos and the number of Bravos. Only if you tick « Include water and weather »: the type of water (river, lake or sea), the light phase (night, dawn, day, dusk), the water and air temperatures, the cloud cover, the wind strength, the flow trend or the tide phase, without tide coefficient or name of a station or a body of water.
- The outings you share with « My friends » (from the summary or the detail of an outing): the day and the time of day of the start, the duration (to 5 minutes), the number of fish, species and released fish, and your biggest catch (species and length, and its photo only if that catch is itself shared with « My friends »). Never the place, the town, the body of water, the type of water, the weather or the rig of the outing.
- Your profile photo, if you set one: chosen or taken in Lura (never the one of your Apple or Google account), reduced and cleaned of its metadata (GPS included) on your phone, kept in Lura's private storage. Your friends see it through links valid for 120 seconds, like photos (see “Your friends' photos”). Other anglers never see it.
- Who said Bravo to a catch: only the catch's author sees it; other friends only see the number.
- Before any friendship: anyone who has your code or your link sees your username and your level before sending their request, and a request shows your username to the other person. Nothing else.
Your friends never see your location: no place, no map, no town, no body of water, no distance, not the place of an outing, no rig, no gear, nothing else from your journal, not the hour of a catch or of a share in the app, not your list of friends, not who else sees a catch. Three limits, stated as they are: your level, points and number of badges are computed from your whole journal, private catches included, so a friend sees them rise without knowing what or where; and a photo can show the spot (a landmark, a sign): look at it before you share it; and the phone of a friend who loads a photo can read when it was sent to Lura (see “Your friends' photos”), never where.
Your friends' photos
Shared photos stay in Lura's private storage, which no friend can access directly. To show them, a friend's app asks Lura's server, which first checks, with that friend's account, that they may see the catch (current friendship, catch shared with them, not paused), then gives them links valid for 120 seconds. The server records neither the catch, nor the photo, nor the angler. Lura writes no friend's photo into the journal, but the phone's image cache may keep a photo already seen: removing a friend or making a catch private again stops new displays, and Lura cannot erase a photo already shown on their phone. A last limit, stated as it is: when loading a photo, a friend's phone also receives, with the image, the moment it was sent to Lura (to the second, often soon after the catch). It never receives the place: the photo's metadata, GPS included, is erased on your phone before it is sent.
Reports, blocking and requests
- You can report a photo or an angler, 10 reports a day at most. A report keeps the account concerned, the catch for a photo, the reason, the date and your account. The person reported is told neither about the report nor about its author; if their content is removed or their account deleted, they receive the reason by e-mail. A reported photo is paused for everyone while it is looked at; a new report after a decision reopens the review (if the same angler reports again a catch already dismissed, it stays visible meanwhile; a different angler pauses it again).
- Liminal reviews every report within 24 hours. For a photo: no action, and the catch comes back; or removal, and the catch stays paused for good, with, for abuse, the deletion of the account. For an angler, on their username: no action, a warning by e-mail, or the deletion of the account.
- Reports are kept as long as the reported account exists. If you delete your account, the reports you made remain, without naming you any more.
- Removing or blocking a friend does not notify them, and erases the friendship and the Bravos exchanged; blocking also erases the requests between you and stops them from sending you one. A declined request can be sent again after 7 days, 3 times at most: for this, Lura keeps the number of declines and the date of the last one.
How long, and deletion
This data lives as long as your account exists. A catch or an outing made private again or deleted stops being shared as soon as your phone has sent it. A profile photo replaced or removed is erased from the storage. What the app reads from your friends stays in memory, never in your journal, and their notifications stay in the app (no push notification). Deleting your account erases at once your card, your invitation code, your requests and their declines, your friendships, your blocks, your shared catches and outings, your profile photo, your Bravos and the reports about you.
12. Changes
This policy follows the app as it changes. The date at the top of the page shows its last update.