Szedd Magad Gazda – Privacy Policy

Last updated: 2026-07-31

Szedd Magad Gazda ("Gazda" is Hungarian for farmer) is the staff application of the Nagy Család Gyümölcsöse pick-your-own fruit orchard in Győrszentiván, Hungary. It is used by the orchard owner and a handful of family members to edit what the visitor-facing Szedd Magad app shows, and to see who has booked a visit day.

This app is not for visitors. It is distributed only through a Google Play closed test to a named list of orchard staff, and it cannot be used without a staff account issued by the orchard. If you are a customer of the orchard, the policy that applies to you is the Szedd Magad privacy policy.

Where this policy says “we”, that means the orchard as data controller. This page is written for two audiences: the staff who use the app (what it stores about them), and anyone who wants to know how customer data is protected once it reaches a staff phone.

Controller

Nagy Család Gyümölcsöse, Győrszentiván, Hungary. Contact for any privacy question or request: lexandro2000@gmail.com

You need an account, and only we can create it

Unlike the visitor app, this one requires a sign-in. There is no self-registration: accounts are created by the orchard for named staff members. Until the server accepts a username and password, the app draws no screen and sends no other network request at all.

Data	Why we need it
Username	Identifies who is signed in, so a single person can be locked out without changing everyone else’s password
Display name	Shown in the app so staff can tell accounts apart
Password	Stored on the server only as a salted PBKDF2 hash. The plain password is never stored, logged, or recoverable — it can only be replaced
Time of the last successful sign-in	So an unused or unexpected account is noticeable
A signed session token, valid 30 days	So the app does not ask for the password on every launch. Held on the staff device; can be invalidated centrally

We deliberately do not ask staff for: email address, phone number, postal address, date of birth, or any payment details. The account is a username and a password, nothing more.

Customer data shown in this app

The app displays the bookings customers made in the visitor app: name, phone number, chosen day and party size. This is the whole point of the arrivals screen — the orchard has to know who is coming.

The app is a window onto that data, not a second copy of it. It does not create customer records, does not export them, and does not keep them after you close the screen: the list is fetched over HTTPS when you open it and is not written to the device’s storage. The controller, legal basis and 5-year retention period for those records are described in the Szedd Magad privacy policy, which governs them.

Only the endpoint behind this app returns customer names and phone numbers, and it requires a valid staff token. The public endpoint the visitor app calls returns per-day totals only, never a name.

Location

The app asks for the device’s location in exactly one place: the “I am standing here” button on the variety-location screen, which the owner uses while walking the orchard to record where each fruit is growing.

The permission prompt appears only when that button is tapped — never at launch, never in the background.
The coordinate is written into the orchard’s own catalogue (which variety grows where) and published to visitors as part of the orchard map.
It describes a place in the orchard, not a person. It is not stored as a location history, not linked to the staff account, and not shared with any third party.
Declining the permission is fully supported: coordinates can also be typed in by hand.

Legal basis

Performance of a contract / legitimate interest (GDPR Art. 6(1)(b), (f)) for the staff account: the orchard cannot let someone edit published content or read customer bookings without knowing who they are.
Legitimate interest (Art. 6(1)(f)) for the sign-in timestamp and the per-IP and per-username attempt counters that protect the login endpoint from guessing. Counters are kept for at most one hour.
The legal basis for the customer records this app displays is set out in the Szedd Magad privacy policy — showing them to staff is part of the same purpose they were collected for.

There is no marketing, no profiling, no automated decision-making, and no advertising in this app.

How long we keep it

Data	Retention
Staff account (username, display name, password hash)	Until the orchard deletes the account. Deletion is immediate and irreversible
Session token	30 days, then it expires on its own. Signing out removes it from the device at once
Login attempt counter	1 hour
Customer bookings	Not stored by this app. On the server: 5 years — see the Szedd Magad privacy policy

Data stored only on the staff device

The following never leaves the phone:

The session token and the signed-in display name
The content draft being edited, until it is published
The cached orchard content downloaded for offline use

Uninstalling the app removes all of it. It does not delete the staff account itself — see Account & Data Deletion.

Your rights, and how to use them

Right	How
Erasure (Art. 17)	Any signed-in staff member can delete an account from Beállítás → Felhasználók, or email us. See Account & Data Deletion.
Access, rectification, restriction, objection, portability	Email lexandro2000@gmail.com. The account is identified by its username.
Complaint	You may lodge a complaint with the Hungarian supervisory authority (NAIH, naih.hu).

Who else touches the data

Who	What they do	Where
Cloudflare, Inc.	Processor: runs the server functions and stores the database	The database region is EEUR (central/eastern Europe), so the data stays in the EU
Google Play	App distribution to the closed test list	Google’s own privacy policy applies to the store itself. To join the test, Google needs the tester’s Google account — that is a Google relationship, not ours

We do not sell, rent, or share data with anyone for their own purposes, and we do not transfer it outside the EU.

Security

All traffic uses HTTPS.
Passwords are stored as salted PBKDF2 hashes and are re-hashed with a current iteration count on sign-in. They are never sent back to any client, in any form.
Session tokens are signed on the server and carry the account they belong to, so a deleted or disabled account stops working immediately — without forcing anyone else to change password.
The signing key is a server secret and is never in the app. Replacing it signs every device out at once, which is the intended response to a lost phone.
Sign-in is rate limited per IP address and per username, so a stolen username cannot be attacked by guessing from many addresses.
The endpoint that returns customer names and phone numbers rejects every request without a valid staff token.

No analytics, no ads, no tracking

The app contains no analytics, advertising, or tracking SDKs of any kind, and does not use an advertising identifier.

Sharing from the app

The app can hand the orchard’s content file (opening hours, varieties, prices, places) to another app on the phone — e-mail, chat — as an offline fallback for publishing when the orchard has no signal. That file describes the orchard, and contains no customer data. Once it is handed over, the receiving app’s own privacy policy applies.

Children

The app is a work tool for orchard staff. It is not directed at children and its declared target audience is 18 and over.

Changes to this policy

If a future version processes data differently, this page will be updated before that version is released. The date at the top always reflects the current version.

Contact

Questions about this policy, or any request about your data: lexandro2000@gmail.com