This is a translation of the German version, provided for convenience. In the event of any discrepancy, the German version prevails.
This policy tells you which data we process when you use Fruit Pin, why we do it, what we rely on, and what rights you have.
1. Who is responsible?
The controller under the General Data Protection Regulation (GDPR) is:
Fruit PinInh. Eray YilmazEuroparing 9053757 Sankt AugustinGermanyEmail: info@fruitpin.comopenKontaktformular-AdresseData protection officer: We have not appointed one and are not required to. The obligation under section 38(1) sentence 1 of the German Federal Data Protection Act applies from 20 people permanently engaged in automated processing; Fruit Pin is a sole proprietorship. The obligation under section 38(1) sentence 2, which applies regardless of headcount where processing requires a data protection impact assessment, does not apply either: we have assessed and documented that none of our processing requires a data protection impact assessment under Article 35 GDPR. The conditions of Article 37(1) GDPR are likewise not met.
2. The short version
You can view the map, all spots, photos and profiles without an account. You only need an account to add spots or upload photos yourself. We do not ask for your real name — a display name you choose is enough. We do not sell data and we do not run personalised advertising.
3. If you are just looking
3.1 Visiting the website (server logs)
When you open Fruit Pin, your device transmits technically necessary information to our host so the page reaches you: IP address, time, the address requested, the amount of data transferred, browser type and operating system, and the page you came from if your browser sends it.
- Purpose: delivering the site, stability, detecting and preventing attacks and abuse.
- Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is the secure and functioning operation of the service.
- Retention: opensiehe deutsche Fassung 3.1
- Recipients: our host, see section 7.
Our database provider (Supabase, Frankfurt am Main region, see section 7) also logs every request the app makes to the database, sign-in or file storage: IP address, the country derived from it, time, browser type, the interface called including its parameters (for example the map area requested) and the domain of the page the request comes from. The content the app sends with it — for example which product you clicked in the shop — is not included.
- Purpose and legal basis: as above.
- Retention: according to the provider, 1 day for our plan; the logs are then deleted.
3.2 What we do not do
We set no cookies for advertising or analytics, we do not build a profile of you across websites, and we embed no social network scripts. That is why you see no consent banner here. What counting we do instead is set out in section 4.4 — in full.
4. Services involved in showing the map
4.1 Why third parties appear here at all
A map consists of many small image tiles, and a place search needs a database of place names. Both come from specialised providers. It is technically unavoidable that your device fetches this content directly from the provider — and transmits your IP address in doing so. Without that transmission your device could not receive the content.
4.2 Map tiles
The map tiles come from the free OpenFreeMap project. Your device does not fetch them there, but from us. We retrieve the tiles with our own servers, cache them and deliver them to you.
What this means for you: displaying the map transfers none of your data to third parties. Neither your IP address nor cookies nor details about your browser leave our infrastructure. When retrieving tiles we send only what is technically needed to deliver them, identifying ourselves with our own signature.
- Purpose: displaying the map.
- Legal basis: Article 6(1)(b) GDPR — the map is the main function of the service you open.
- Third country transfer: none takes place.
- Recipients: none. OpenFreeMap only learns that our servers requested tiles — not who viewed them.
- Logging on our side: the details on server logs in section 3.1 apply. opensiehe deutsche Fassung 4.2 — Zusage zur Nichtprotokollierung der Kartenausschnitte erst eintragen, wenn technisch umgesetzt (L-10.38).
The map data comes from OpenStreetMap and is licensed under the Open Database License (ODbL). The attribution appears at the edge of the map.
4.2a Aerial imagery
You can display the map as aerial imagery. The images come from the "World Imagery" service of Esri, Inc. (USA). Your device does not fetch them there, but from us: our server fetches each tile from Esri and passes it on to you without caching it on our side.
What this means for you: Esri learns nothing about you. Neither your IP address nor cookies nor details about your browser are passed on to Esri. Esri only sees that our server requested a map area — not who is viewing it.
- Purpose: displaying the map as aerial imagery.
- Legal basis: Article 6(1)(b) GDPR — the map is the main function of the service.
- Recipients and third-country transfer: none as far as your data is concerned. For delivery, the information on server logs in 3.1 applies.
- Your choice between map and aerial view is remembered by your browser until you close the tab (
sessionStorage). Only this one setting is stored, no identifier. This is strictly necessary for the view you chose (Section 25(2) No. 2 TDDDG).
The credits ("Powered by Esri" and the image sources) are shown at the edge of the map.
4.3 Place search
When you type a place into the search field, your input is sent to the geocoding service Photon, operated by komoot GmbH. According to our check on 28 September 2026 this service runs on servers of Hetzner Online GmbH in Germany; no transfer to a third country takes place.
Your search term and your IP address are transmitted.
- Purpose: finding places on the map.
- Legal basis: Article 6(1)(b) GDPR — you trigger the search yourself to use a function you deliberately want.
- Data minimisation: your input is only sent after a short delay and from a minimum length, so not every keystroke is transmitted.
- Retention: we do not store search queries.
4.4 Anonymous page view counting
We want to know which pages are used — but not who uses them. So we count anonymously.
Only three items are transmitted:
| Item | Content |
|---|---|
| Path | the page requested, without query parameters, so search terms are not included |
| Referring domain | only the domain you came from — never the full address |
| Language | the interface language you chose, i.e. de or en |
What expressly does not happen: No cookie is set, nothing is stored on your device or read from it. There is no visitor identifier, not even a calculated one. No fingerprinting takes place — we do not read screen resolution, time zone or fonts. Two visits by the same person are not recognisable to us as the same person.
- Purpose: understanding which content is used, in order to improve the service.
- Legal basis: Article 6(1)(f) GDPR. Our legitimate interest is developing the service on a sound basis. Because no identifier and no IP address are stored, the interference with your rights is very low.
- No consent required: As nothing is stored on or read from your device, section 25(1) of the German Telecommunications Digital Services Data Protection Act does not apply. That is why you do not have to dismiss a cookie notice here.
- Analysis: aggregated only, never related to an individual.
- Who does the counting: we do. The counts run through our own endpoint on our existing infrastructure and are stored in our own database. No third-party analytics service is involved — neither hosted nor self-operated. The reason is the assurance above: common analytics tools count "unique visitors" using a value calculated from IP address and browser signature. That would be a calculated identifier, and we have ruled those out. So we count ourselves.
- What we can say about your IP address — and what we cannot: no IP address is stored in the counts; it is not one of the three items transmitted and is not recorded. As with any page request, our infrastructure does technically see the IP address, and for retention in the general server logs what is stated in section 3.1 applies. opensiehe deutsche Fassung 4.4
- Retention: We keep the daily counts for 24 months. After that we consolidate them into monthly totals and delete the daily figures; we keep the monthly totals indefinitely so that we can compare years. This is unproblematic because these figures contain no information about individual people in the first place.
4.5 Shop: affiliate links to Amazon
In the "Shop" section we show harvesting gear available on Amazon. We do not sell anything ourselves.
Viewing the shop does not transmit anything about you to Amazon. The product photos come from Amazon but are fetched by our server and cached there for no more than 24 hours. Your browser loads them only from fruitpin.com. When fetching them, our server passes on no information about you — neither your IP address nor your browser nor the page you came from. No scripts or other content are loaded from Amazon.
If you click a link, two things happen:
- We count the click anonymously. The only thing transmitted is which product was clicked. For each product we store only a total – no IP address, no time, no identifier, nothing on your device, and no link to your account. This produces the "most clicked" order. The legal basis for the technically unavoidable, transient processing of your IP address is Article 6(1)(f) GDPR; our legitimate interest is a comprehensible order of the products. Counting takes place in our own database at our service provider Supabase (see section 7); no other service is involved. As with every database request, the provider technically logs the IP address and time – but not which product was clicked; section 3.1 applies to this.
- You move to Amazon. From that moment, Amazon is a separate controller – not us. The link contains our affiliate ID so that Amazon can attribute a purchase to us; for this Amazon sets its own cookies and processes your data under its own terms. The controllers are Amazon Europe Core SARL, Amazon EU SARL and Amazon Media EU SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg, and Amazon Digital Germany GmbH, Anni-Albers-Str. 21, 80807 Munich. Details: Amazon's privacy notice, https://www.amazon.de/gp/help/customer/display.html?nodeId=GX7NJQ4ZB8MHFRNJ
What we learn from Amazon: only aggregated reports of which products were viewed and bought via our links and the resulting commission – no names, no addresses, no information about who bought anything.
- Retention: we keep the click totals per product for as long as the product is in the shop and delete them when we remove it. They never contain information about individuals.
5. If you create an account
5.1 Registration and account
For an account we need an email address, a password and a display name. You also confirm that you are at least 16 years old.
- Data processed: email address, password (only as a cryptographic hash, never in plain text), display name, time of registration, confirmation of the minimum age.
- Purpose: creating and maintaining your account, signing in, attributing your contributions, contacting you about your account.
- Legal basis: Article 6(1)(b) GDPR (user agreement).
- Mandatory information: without it we cannot set up an account. We do not require your real name — it is never requested.
- Your display name is pre-filled with a random name at registration. You can change it but do not have to. That way you stay pseudonymous even if you would rather not think about the question.
5.1a Signing in with Google
Instead of an email address and password you can also sign in with your Google account, or create an account that way. This is voluntary and always a separate decision; every account can also be used without Google.
As long as you do not choose it, nothing is transmitted to Google. Our pages contain no Google scripts, buttons or tracking pixels — the "Sign in with Google" button is an ordinary link on our own site.
What happens if you choose it: you are redirected to Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) and sign in there. Google processes your data under its own responsibility and under its own privacy terms; this includes your IP address being transmitted there and data possibly reaching its parent company Google LLC in the USA. Google then sends you back to our own address (fruitpin.com). We never learn your Google password.
- What we receive from Google: the identifier of your Google account, your email address and whether Google has verified it. Nothing else. We ask Google only for the permissions
openidandemail, so we expressly do not request a name, a profile picture or any further details — not even if your Google account holds them. We have no access to your mailbox, your contacts or any other content of your Google account. - Your display name is not derived from your Google name. You receive the same randomly pre-filled name as with email registration. This way no real name of yours can reach the map by this route.
- New account: an account created through Google can only be used once you have confirmed, as at registration, that you are at least 16 years old (see 5.1) and have confirmed your username. If you cancel at that point, you are signed out. If you do not complete this step within 7 days, we delete the account automatically.
- Existing account: if we already hold an account with the same email address, verified by Google, signing in with Google is added to that account; no second account is created. If that account had not yet confirmed its email address, its password no longer works afterwards, and you confirm the username and your age yourself in the next step.
- Purpose: signing in without a separate password with us.
- Legal basis: Article 6(1)(b) GDPR — you choose this route in order to enter into and use the user agreement.
- How it works technically: after you sign in, Google hands your browser a one-time code. Our server (hosted by Netlify, see section 7) exchanges it with Google for a confirmation of your sign-in signed by Google; this is checked by our processor Supabase (see section 7), which handles sign-in on our behalf and stores the details above with your account. So that the return only counts in the browser tab where you started, your browser keeps two random values until then (
sessionStorage); they contain no identifier and are deleted on your return. This is strictly necessary for the sign-in you chose (§ 25(2) no. 2 TDDDG). - Retention: as long as your account (see 5.4 and section 8); an account whose first step you do not complete, 7 days (see "New account").
- Disconnecting: you can remove Fruit Pin's access at any time in your Google account at myaccount.google.com/connections. Your Fruit Pin account is not affected; you can keep signing in with a link by email.
5.1b Emails about your account
To operate your account we send you emails: the confirmation of your address at registration and, if you need it, a link to reset your password. Later the seasonal reminders from 5.5 will be added, if you have switched them on.
- Data processed: your email address and the content of the respective message.
- Purpose: confirming your address, restoring access, notifications about your account.
- Legal basis: Article 6(1)(b) GDPR — without these messages an account could not be set up or recovered.
- Processor: delivery runs through Plus Five Five, Inc. (trading as "Resend"), based in the USA. We have entered into a data processing agreement under Article 28 GDPR with them; delivery is configured for the Ireland (EU) region. More on the transfer to the USA in section 7.
- No performance tracking: we do not measure whether you open an email or which links you click. Open and click tracking are switched off, no tracking pixels are included, and links are not rewritten.
- Retention: your address remains with the processor only as long as needed for delivery and technical troubleshooting. opensiehe deutsche Fassung 5.1b
5.2 Public profile
Your profile is publicly visible, including to people without an account. It shows your display name and, if you add them, a profile picture and a short text about you, along with your spots and contributions.
- Legal basis: Article 6(1)(b) GDPR. Public visibility is core to the service: spots should be traceable, and that includes who reported them.
- Your control: the picture and description are optional. You can change or remove them at any time. Please do not put anything in your profile that you do not want to be public.
Publishing without your profile name. In your settings you can choose not to show your profile name on your contributions. Such contributions do not appear on your public profile, are not counted there and do not trigger notifications. Internally, the link to your account remains — for moderation, for your own overview and so that we handle them correctly if you delete your account (5.4).
5.2a Profile picture and profile gallery
A profile picture is optional. Without one, we show a placeholder.
- Where it appears: on your profile, next to your contributions — except those you publish without your profile name — and in notifications to people who follow you (5.6). It is visible to everyone, including people without an account.
- What happens to the file: before the picture is uploaded, the app crops it to a square on your device, scales it down and saves it anew. Embedded additional details such as the location and camera model are removed in the process. We only receive this version. If you replace the picture, we delete the previous one.
- Legal basis: Article 6(1)(b) GDPR.
- Retention: until you remove or replace the picture or delete your account.
Please bear in mind: a face in your profile picture reveals who you are — and, together with your spots, where you go. A picture without a face protects you better. Other people must not appear in your profile picture (Terms of Use 6.7).
Your profile gallery shows the photos of your spots and contributions and the number of your spots, contributions, followers and the profiles you follow. It shows no date per entry and no map. Anything you publish without your profile name does not appear there and is not counted.
5.3 Spots, photos and videos
When you add a spot (called a "pin" in the app) or upload a contribution, we process the location, the species, your accessibility details, your description, your image and video files, the time, the link to your account, and your confirmation of the rules on image content (Terms of Use 6.2) together with when you gave it.
- Purpose: showing the spot on the map and in detail.
- Legal basis: Article 6(1)(b) GDPR.
- All of this is public, including to people without an account.
We strip location data from your files. Photos and videos from mobile devices often contain the exact coordinates of where they were taken. We remove this and other embedded metadata on our server before a file becomes public, and we publish only the cleaned version.
We do not keep the original file. Cleaning happens on upload; only the cleaned version is stored. This also means: if you export your data (see section 9), you receive that version — the original file containing the location data is not held by us and therefore cannot be part of the export. This is intentional: that data is precisely what we do not want to hold.
Two requests, for your own protection:
- Do not place spots at your home address. The position is public, and combined with your profile it can reveal where you live.
- Do not upload images showing recognisable people. Our terms of use do not allow it — we have no legal basis to publish images of third parties. If you notice such an image, report it and we will remove it.
You can also create contributions through the programming interface; the same removal of location and additional data, the same Privacy Mode and the same moderation apply there.
5.3a Privacy Mode: delayed publication
A spot reveals where you were. So that it does not reveal when, Privacy Mode is switched on by default:
- New spots and contributions become public to others only after at least 24 hours, namely at 6:00 a.m. German time on the first morning that is at least 24 hours after the upload — together with all others due that morning. The delay is therefore between 24 and 48 hours. This means nobody can tell at what time of day you were there. Others see the day of publication as the date, not the day of upload.
- You see your own contributions immediately and can still edit or delete them until they are published. Whether your profile name appears on them is set in your settings (5.2).
- Data processed: your setting and, for each contribution, the time from which it is public.
- Legal basis: Article 6(1)(b) GDPR; the default follows Article 25(2) GDPR.
You can switch Privacy Mode off in your profile. New spots and contributions are then public immediately, and your followers are notified immediately (5.6). This applies only to contributions you upload afterwards.
5.4 If you delete your account
You can delete your account yourself at any time. Then:
- Deleted: your account, email address, password hash, display name, profile picture and profile text — and with them everything that is assigned only to your account and is not publicly attached to a spot, such as your saved list and your settings.
- Retained: the spots and the cleaned photos and videos you contributed — but with no link to you whatsoever. The attribution to your account is permanently removed; we keep no key that could restore it. A note such as "deleted user" appears in place of your name.
5.5 Saved species and spots, seasonal reminders
You can save species and individual spots, and have a reminder sent to you when each one is in season.
Nobody but you can see your saved list.
- Data processed: which species and spots you have saved, the time, whether you want a reminder for each one, and by which channel.
- Purpose of saving: keeping the list available for you.
- Legal basis for saving: Article 6(1)(b) GDPR — the save function is part of the service you use.
- Purpose of the reminder: notifying you when a saved species is in season according to the catalogue.
- Legal basis for the reminder: Article 6(1)(a) GDPR — your consent, given separately for each saved item. You can withdraw it at any time, individually or for all items at once; every reminder also contains an unsubscribe link. Withdrawal takes effect for the future.
- Separate from the newsletter: a reminder is not the newsletter. Ordering reminders does not subscribe you to the newsletter, and vice versa. Both are asked for separately.
- What a reminder contains: the saved species or spot, the seasonal information from the catalogue and a link. We do not use reminders to offer you anything — no shop references, no events, no project news.
- Retention: until you remove the saved item or delete your account. Removing deletes the record, not just the display.
- Recipients: the email delivery provider, see section 7.
What we expressly do not do: your saved list does not appear in your public profile or anywhere else. There is no counter on a spot showing how many people have saved it — not even an aggregated one. We derive no recommendations, rankings or interest profiles from your saved items, neither for you nor for us.
If a saved spot disappears: where a spot is removed — for example because the landowner has contacted us — the reminder for it stops immediately. We will not send you to a place that should no longer be on the map.
5.6 Following and notifications
You can follow other profiles and be notified when they publish a new spot or a new photo.
Nobody but you can see whom you follow — not even the person you follow. Only the number of followers and followed profiles is public.
- Data processed: whom you follow, since when, and whether the bell is on for that profile. For each notification: who receives it, who triggered it, the spot, the photo where applicable, the time and whether it has been read.
- Purpose: to show you what profiles you follow have newly published.
- Legal basis: Article 6(1)(b) GDPR — following is part of the service you use. For the person being followed, visibility does not change: followers only see what is public anyway.
- The bell is switched on when you follow and can be switched off for each profile.
- Notifications are only created once a contribution becomes public — in Privacy Mode, after the delay described in 5.3a, never at upload.
- Anything you publish without your profile name does not trigger a notification. If you later remove your profile name from a contribution, or the content is removed or hidden, the notification disappears too.
- Notifications exist only in the app — no emails, no push messages.
- Retention: follows until you unfollow or either account is deleted. Notifications for 90 days, after which we delete them automatically; on account deletion immediately. If you unfollow a profile, we also delete the notifications you received from that profile.
5.7 Programming interface (API) and AI agents
You can create an API key in the settings so that your own programs or an AI agent can use Fruit Pin. This is optional.
- Data processed: the name you give the key, its first 14 characters (so you can recognise it), a fingerprint of the key (SHA-256; we do not store the key itself), the permissions (read or write) and the times it was created, last used and revoked and, for write keys, the time and version of the notice you confirmed (as proof, Art. 6(1)(f) GDPR).
- During use: counters for the request limits per key and per account (continuously overwritten, deleted after one day at the latest), a log of write operations for the daily limits (account, type, time, no content) for 2 days and, for requests with an idempotency key, the response for 24 hours so that a retry does not create anything twice.
- After a failed sign-in with a key: a value derived from the IP address and a counter, for at most 1 day, to slow down guessing of keys. The value is formed with a secret key and cannot be traced back to the address without it.
- If we block a key: the reason and the time of the block on the key (as long as the key is kept, see below) and our notice to you in the sending queue (30 days after sending). Legal basis: Art. 6(1)(c) GDPR in connection with Art. 17 of Regulation (EU) 2022/2065 (statement of reasons for restrictions) and (f) (proof).
- Purpose and legal basis: providing the function you asked for (Art. 6(1)(b) GDPR); protection against misuse and spam (Art. 6(1)(f) GDPR).
- Recipients: none new. The interface runs at Supabase (Frankfurt) behind a forwarding service of Netlify (see 7).
- Your AI agent: what you tell your agent and what it retrieves through the interface reaches the agent's provider (for example Anthropic, OpenAI or Google). It processes it under its own terms; we have no contract with it and no influence on it. You decide what your agent retrieves and passes on.
- Deletion: we delete keys, counters, log and stored responses with your account. We delete revoked keys 12 months after revocation.
6. Reporting, moderation and newsletter
6.1 If you report content
Anyone can report content — including without an account. This matters for people who own land where a spot has been added.
- Data processed: the reported content, the reason you select, your explanation, the time, and — optionally — your email address and name. Without contact details we cannot send you an acknowledgement or a decision; the report is still processed.
- Purpose: reviewing the report, deciding, replying to you, documenting our handling.
- Legal basis: Article 6(1)(c) GDPR — Article 16 of Regulation (EU) 2022/2065 (Digital Services Act) requires us to offer such a procedure and to handle reports. Additionally Article 6(1)(f) GDPR for documentation.
- Recipients: if a report is justified and concerns a contribution, we inform the affected person of our decision with a statement of reasons (Article 17 of the Regulation). We disclose your identity only where strictly necessary. Where we suspect a criminal offence involving a threat to the life or safety of persons, Article 18 of the Regulation requires us to inform law enforcement.
- Retention: We do not keep everything for the same length of time, only as long as the respective purpose requires:
- Your contact details (name, email address) are deleted six months after we have told you our decision. The report itself is retained without them.
- Reports that led to no measure are deleted twelve months after closure. We need that time to evidence our handling and to recognise where the same content is reported repeatedly without cause. For a seasonal service, a full annual cycle is the sensible benchmark.
- Reports that led to a measure — such as the removal of a spot — are kept for three years after closure. Reason: the person affected may challenge our decision, and we must be able to show why we acted. Three years corresponds to the standard limitation period.
- Where a landowner has contacted us, we permanently record that no spot should be published at that location — but without the details of the person who contacted us. Without that record, someone else could re-add the same place shortly afterwards and the objection would be ineffective.
Where ongoing legal proceedings require longer retention, we limit it to the information needed for that purpose and to the people handling the case. An open report is not a reason for us to delay the deletion of an account.
6.2 Newsletter
You receive our newsletter only if you expressly request it.
- How it works: after you enter your email address we send you an email with a confirmation link. You are only added once you click it. This ensures nobody signs up someone else's address.
- Data processed: email address, time of sign-up, time of confirmation.
- Purpose: sending the newsletter about the season, new species and the project.
- Legal basis: Article 6(1)(a) GDPR (your consent); the record required by Article 7(1) GDPR is the confirmation.
- No performance tracking: we do not measure whether or when you open an email or which links you click. There are no tracking pixels and we do not rewrite links.
- Withdrawal: you can unsubscribe at any time — every email contains an unsubscribe link. We then delete your address from the list.
- Processor: the same as for account emails — Plus Five Five, Inc. (trading as "Resend"), see 5.1b and section 7. Open and click tracking are switched off here too.
- Retention: until withdrawal. We keep the record of your consent for as long as it is needed to defend against claims.
7. Who else processes your data
We work with service providers who support us technically. Where they process data for us, they are bound by contract to our instructions under Article 28 GDPR.
| Provider | Task | Location | Third country transfer |
|---|---|---|---|
| Netlify, Inc. | website hosting | USA | Yes. The transfer relies on the Standard Contractual Clauses under Article 46 GDPR, incorporated in the data processing agreement. Netlify additionally states that it is certified under the EU-U.S. Data Privacy Framework (as of its privacy statement dated 10 April 2026), which would also engage Article 45 GDPR. We rely primarily on the Standard Contractual Clauses so that the transfer remains covered even if the certification status changes. |
| Supabase Pte. Ltd. | database, file storage, authentication | Singapore | Yes. Storage and primary processing take place in the Frankfurt region. There is no adequacy decision for Singapore; the transfer relies on the Standard Contractual Clauses under Article 46 GDPR, incorporated in the data processing agreement. opensiehe deutsche Fassung 7 |
| Tile provider | displaying the map | see 4.2 | see 4.2 |
| komoot GmbH | place search (Photon) | Germany | No — servers in Germany (checked 28 September 2026). |
| Analytics provider | page view counting | open | open |
| Plus Five Five, Inc. (trading as "Resend") | sending account emails and the newsletter | USA, sending region Ireland (EU) | Yes. The transfer relies on the Standard Contractual Clauses under Article 46 GDPR, incorporated in the data processing agreement (Module Two, controller to processor). Choosing the EU region limits the sending route, not access: the provider expressly states in its agreement that its primary processing operations take place in the USA. |
One point that is often left unsaid: providers based in the USA can be compelled under US law to hand data to authorities — even when the data is physically located in the EU. Choosing the Frankfurt region therefore limits where data is stored but is not protection against government access. We keep the amount of data held there as small as possible.
Beyond these providers we disclose data only where legally required, for example to law enforcement. We do not sell data and do not pass it on for advertising.
8. How long we keep data
| Data | Duration |
|---|---|
| Account, profile | until you delete it |
| Spots, photos, videos | indefinitely; after account deletion with no link to you (5.4) |
| Server logs | opensee 3.1 |
| Reports and decisions | staggered: contact details 6 months, report with no measure 12 months, report with a measure 3 years; landowner block record permanently without personal details (6.1) |
| Media in quarantine | 30 days after the final decision; where challenged, until that is resolved. Uploads rejected on technical grounds are not stored at all |
| Newsletter | until withdrawal (6.2) |
| Aggregated counts | daily figures 24 months, then monthly totals indefinitely (4.4) — no personal reference |
| API keys | until you delete your account; revoked keys 12 months after revocation (5.7) |
| API: request-limit counters | at most 1 day (5.7) |
| API: log of write operations | 2 days (5.7) |
| API: stored responses (idempotency key) | 24 hours (5.7) |
| API: value derived from the IP address after a failed sign-in | 1 day (5.7) |
Beyond this we keep data as long as statutory retention obligations exist or we need it to pursue or defend against claims. In that case it is kept for that purpose only and with restricted access.
9. Your rights
You have the following rights towards us:
- Access (Article 15 GDPR) — which data we process about you.
- Rectification (Article 16 GDPR).
- Erasure (Article 17 GDPR) — see 5.4 on account deletion.
- Restriction of processing (Article 18 GDPR).
- Data portability (Article 20 GDPR) — your data in a common format.
- Withdrawal of consent (Article 7(3) GDPR) — at any time, with effect for the future. For us this concerns the newsletter.
Access, export and deletion of your account are available directly in your profile — that is the fastest route. You can also contact us any time: info@fruitpin.com
10. Complaint to a supervisory authority
You can lodge a complaint with a data protection supervisory authority at any time (Article 77 GDPR). The authority responsible for us is:
Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-WestfalenPostfach 20 04 4440102 Düsseldorf, GermanyPhone: +49 211 38424-0Email: poststelle@ldi.nrw.deComplaint form: ldi.nrw.deYou may also contact the authority where you live or work.
11. No automated decision-making
We do not make decisions about you that are based solely on automated processing and significantly affect you legally (Article 22 GDPR). Reports and measures against content are decided by people. Where we do use automated tools, we say so in the statement of reasons.
12. Changes to this policy
We update this policy when the service or the law changes. The current version is always on this page; the date appears at the top. For significant changes we will additionally inform you if you have an account.
13. Language versions
This policy is available in German and English. The English version is a translation provided for your convenience. In the event of any discrepancy between the versions, the German version prevails.