Privacy Policy

Kenny Trappl, Hochwaldstraße 1, 2230 Gänserndorf, Austria, operating Retrievly as a private individual — full contact details are in the Legal notice (Impressum). No data protection officer is appointed, as none is required for a service of this size; for anything privacy-related write to trapplkenny@gmail.com.

Account: your email address, a display name you choose, an optional profile photo, and — if you're a searcher — what you write about yourself, the terrain you search and the gear you bring. Passwords are stored only as a hash.
Sign in with Google: your name, email address and Google profile picture (see the section below).
Location: the approximate area you mark for a lost-item request — the exact point is stored, but everyone except the searcher you pick only ever sees a coarse 5 km region. Your device's precise position is used only if you tap "use my location" (to centre the map or measure distances) and is not stored beyond what you save.
Content: request descriptions, photos of the item and of the spot, messages sent in the in-app chat, offers, ratings and reviews, and reports you send us.
Technical: the session cookie that keeps you signed in, a cookie for your language choice, and standard server logs (IP address, browser, time of request) kept by our hosting provider for security and troubleshooting.
How you found us: when you create an account or post a request, we note which website sent you (its name only, never the page you were on), any campaign tags on the link, whether you came from one of our Google ads (yes or no), the first page you opened and when. It is kept with your account or request, and only you and Retrievly's operator can see it.
Support and feedback: whatever you write in the feedback box or send to support, together with the page you were on.

If you use "Sign in with Google", Google sends us your name, email address and profile picture together with a token that proves the sign-in. We use these only to create and identify your account and to pre-fill your display name and photo, both of which you can change. We ask for no other Google data — no contacts, calendar, Drive or Gmail — and we never post to Google on your behalf. Retrievly's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. You can revoke Retrievly's access at any time under myaccount.google.com → Security → Third-party access.

To run the matching service — showing requests to searchers nearby, letting people offer, and connecting the two sides once someone is picked. To send the emails the service needs: confirming your address, password resets, and notifications about offers, picks, finds and messages (each of which you can switch off in Settings). To keep the platform safe: reviewing reports, blocking abuse, and keeping a short history of closed searches. We do not sell your data and do not use it for advertising.

Performance of a contract, Art. 6(1)(b) — everything needed to provide the service you signed up for. Legitimate interest, Art. 6(1)(f) — safety, abuse prevention, server logs, knowing which sites and links bring people to Retrievly, and the anonymised history of closed searches. Consent, Art. 6(1)(a) — sharing your device's precise position, optional analytics cookies (Vercel and Google Analytics), marketing cookies (Google Ads), and the profile data received from Google when you choose to sign in that way; consent can be withdrawn at any time. Legal obligation, Art. 6(1)(c) — where a law or authority requires us to keep or hand over data.

The other person in a request: once you pick a searcher, they see the exact location and can message you; a searcher's offer and profile are visible to the owner. Your email address is never shown to other users.
Supabase (database, sign-in and file storage) — servers in Frankfurt, Germany.
Vercel (hosting and delivery of the website) — served from Frankfurt; Vercel Inc. is a US company, covered by the EU–US Data Privacy Framework and standard contractual clauses.
Brevo (Sendinblue SAS, Paris) — sends our transactional emails and therefore receives your email address and the message content.
Google — if you choose to sign in with Google (see above), and, only if you allow them on the cookie sheet, Google Analytics and Google Ads.
Map tiles and geocoding: the maps are drawn with OpenStreetMap tiles and, on request, Esri satellite imagery; place search uses OpenStreetMap's Nominatim. Loading a map sends your IP address and the map area requested to those services, never your account data.
Authorities, only where the law obliges us to. Nobody else — no data brokers, and no ad network unless you allowed marketing cookies.

Your account, requests, messages and photos live in Supabase's Frankfurt (EU) region. The website is served by Vercel from Frankfurt. Where a provider is a US company (Vercel, Google), transfers are covered by the EU–US Data Privacy Framework and standard contractual clauses.

Your account and everything in it for as long as the account exists. A closed request keeps its description and photos for 90 days so it can be reposted, then the photos are deleted. When you delete your account, your name, email, profile and open requests and chats are removed at once; ratings you gave, closed searches and reports about you stay in anonymised form ("former member") so that other people's history remains truthful. Server logs are kept by the hosting provider for a short period, typically 30 days.

One essential cookie keeps you signed in and one remembers your language choice. Nothing else is set unless you allow it. Say yes to analytics on the cookie sheet and we load two things: Vercel Web Analytics, which counts page views without cookies and without a profile of you, and Google Analytics, which sets Google cookies so we can see which screens people get stuck on and whether they post a request or create an account. The same yes lets us keep one short note in this browser tab until you close it: how you reached the site, so we still know it if you sign up a few pages later. Without that yes, the note lives only in the open page and is forgotten when you reload. Say yes to marketing and we load the Google Ads tag, which sets Google advertising cookies and tells us whether an ad we paid for led to someone posting a search request; it loads only after you agree, and never before. Both choices can be changed on the Cookie controls page at any time, and turning marketing off withdraws that consent. The same yes also sends each page view anonymously to our own simple visitor counter (Vercel Frankfurt and Supabase): no cookie, no IP address stored, only a one-way code that changes every day, so we can see how many people visit per day.

Under the GDPR you can ask for access to your data, have it corrected or deleted, restrict or object to its processing, and receive a copy in a portable format (Art. 15–21). Settings → Export my data gives you that copy immediately, and Settings → Delete account does what it says. For anything else write to trapplkenny@gmail.com. If you believe we handle your data unlawfully you can complain to the Austrian data protection authority (Datenschutzbehörde, dsb.gv.at).

A request's public location is intentionally approximate. Your exact spot is withheld on our servers — not merely hidden in the app. It is revealed to one other user: the searcher you pick for that request. Retrievly's operator can access it to run and support the service, and each such access is logged. Searchers' own positions are never shown to anyone.

When the service changes in a way that affects your data, this page changes with it and the date at the top moves. Substantial changes are announced by email or in the app before they take effect.