Beach4Fun is operated by Partuck Oren Moshe, an individual sole proprietor registered in Israel as an exempt dealer (osek patur).

• Beach4Fun is the name of the service. It is not a company or any other corporate body.
• "We" and "us" in this policy mean the operator.
• The operator decides why and how your personal data is used: the database owner under Israel's Protection of Privacy Law, and the data controller where other laws apply.

Privacy contact: hello@beach4fun.app — for anything in this policy, including the requests in §12.

• Email address and password (stored encrypted by our sign-in provider), or Google sign-in, or Sign in with Apple in the iOS app; on the website, a passkey too
  When: sign-up and sign-in. Why: to give you an account. Must you give it? Yes, for an account. The website and the beach information work without one.
• Display name; if you sign in with Google, your Google account photo, which is shown as your profile photo
  When: sign-up. Why: so friends and the community can recognise you. Must you give it? A name, yes.
• Age range
  When: first-run questions. Why: to apply the age rules (16 and older only; protections for 16–17, §5). Must you give it? Yes — the age rules need it.
• Region or city, interests, skin tone (for UV calculations), the social handles you choose to show, your privacy settings
  When: first-run questions and profile edits. Why: to tailor the service and show what you chose to show. Must you give it? No.
• What you create: messages in beach chat and meetup chat, direct messages (text, photos, voice messages), meetups, groups (including a cover photo), alerts and beach reports (including a description of a lost child, if you report one), BeachQuest photos, likes, friend requests and friendships
  When: when you create it. Why: it is the service. Must you give it? No.
• Check-in: which beach and when — not coordinates
  When: when you check in. Why: to show friends you are at the beach, and to suggest people you may know from recent check-ins (within the last 90 days). Must you give it? No.
• Presence: when you last had the app open (and at which checked-in beach); your choices about appearing in "who's at the beach" and online
  When: while the app is open, about once a minute. Why: to show you only to the people allowed to see you (§4), and only while you are there. Must you give it? Your choices are yours; while you are signed in, the app records when it is open.
• Website notifications: your browser's notification address and its identification string (browser, operating system and sometimes the device model)
  When: only if you allow notifications. Why: to send you notifications. Must you give it? No.
• Reports and moderation: what was reported, a snapshot of it (up to 1,000 characters), the reason, the decision; a reported direct-message photo or voice message
  When: when content is reported. Why: community safety (§6). Must you give it? —
• Feedback and business enquiries, including the contact details you give
  When: when you write to us. Why: to answer you. Must you give it? No.
• Website usage data — only with your consent (§7)
  When: while you use the website. Why: to understand use and improve the service. Must you give it? No.

We do not sell personal data, do not show it to advertisers, and do not use it for advertising. The iOS app contains no advertising or tracking SDK.

• Your precise location. Finding your nearest beach and the check-in distance check run on your device; only the beach and the result reach us.
• "Share my location" builds a navigation link that you send yourself. Your location is not sent to us.
• The tan comparison from photos, Stories and your personal beach album stay on your device until you choose to share them.
• A profile photo you upload from your device stays on your device.

• Friends, group members and meetup participants see what is meant for them. Direct messages: only the people in the conversation.
• Your profile: your display name, photo and interests can be seen by other users and by visitors where you appear (for example next to a beach-chat message) — different rules apply to 16–17-year-olds (§5). Your details card (age range and the social handles you chose to show) opens only for someone you have a friend request or friendship with.
• "Who's at the beach": you can appear only while you are checked in at that beach with the app open (you disappear about 2½ minutes after the app stops updating).
  • your friends see you;
  • other signed-in users see you only if all of these are true: you chose to appear, your profile is public, you declared that you are 18 or older — and they declared that they are 18 or older too;
  • if you are 16–17, or your account has no declared age, you are shown to your friends only, and you see only your friends;
  • visitors who are not signed in see only the number of people;
  • what is shown is a first name and photo, never a location.
• Online status: shown to friends — and to members of a group you share, if both of you declared that you are 18 or older — only if you turned it on and your profile is not private.
• Restricted or banned accounts are not shown in "who's at the beach" or as online, to anyone.
• Public: BeachQuest photos and business images. Private: photos and voice messages in direct messages, opened through short-lived links.
• Moderation team (the administrators): sees reports and the snapshots they hold. Opening a reported file is limited to administrators, and every request to open one is recorded.

Beach4Fun is for people 16 and older. Users aged 16–17 have a protected experience:

• they do not appear in user search, and are suggested as "people you may know" only to other 16–17 users;
• no contact with adults: no friendships, direct messages, shared groups or meetups across the age line — except with a family-linked account, and in groups or meetups that account is in;
• their name, photo and interests are shown only to themselves, other 16–17 users, a linked family member and the administrators — never to visitors or other adults. Where their posts appear publicly (for example in beach chat), they appear under the app's neutral label "משתמש/ת" ("user") with no photo, and no copy of their name or photo is kept on alerts and beach reports;
• a link to a meetup opens only for signed-in users, and a meetup hosted by a 16–17-year-old opens only for people allowed to see its host, or for people invited to it;
• never measured by analytics (§7), and a declared 16–17-year-old receives no friend-request emails.

Age is declared, not verified.

• The age group (16–17, or 18 and older) is stated at sign-up and cannot be changed by the user. Contact us if it was entered wrongly.
• New accounts must state an age range before they can continue. A few older accounts have no age on record; for now:
  • the rules that keep minors and adults apart, and profile visibility, treat such an account as an adult;
  • everything that shows it to non-friends or measures it treats it as under 18: in "who's at the beach" it is shown to friends only and sees only friends, it does not see the online status of non-friend group members, and it is never measured by analytics (§7).
• If we learn that someone under 16 has signed up, we delete the account.

• Before publication: an automatic keyword filter refuses some offensive text before it is published — in chats, direct messages, alerts, beach reports, meetup titles, group names and descriptions, and display names. It does not check images or voice messages.
• Reports: you can report a profile, a message (beach chat, meetup chat or a direct message, including its photo or voice message), an alert, a beach report, a meetup or a group. Every report reaches a human moderator. Reports about risk to a minor or to life are handled first.
• Enforcement: moderators can remove content and record strikes. A third strike restricts the account for 24 hours, and a fourth restricts it permanently (the Terms of Use, §4, list what a restriction stops). A restricted account can still read, leave, report, send emergency alerts and delete itself.
• What a report keeps: the content reported, a snapshot, the reason and the decision. If a direct-message photo or voice message is reported, the file is kept for the moderators while the report is open, even if the message is deleted. After the report is closed, the file stays only as long as its message.
• Authorities: where the law requires it, or where a minor or a life is at risk, we may share the relevant report and content with the authorities.

• The default is off. We measure use of the website only if you are signed in, 18 or older, and said yes. Visitors who are not signed in, 16–17-year-olds and accounts without a declared age are never measured, whatever they answered. Nothing is collected, held on the device, or sent later before you say yes.
• Tools: PostHog (servers in the United States) — pages and actions, with our user id; Google Analytics — no user id.
• Changing your answer: you can change it at any time at the bottom of this page. Your answer is kept on your device and cleared when you sign out.
• The iOS app never collects usage data.

• Supabase — database, sign-in, file storage, realtime updates. European Union (Ireland).
• Vercel — website and server hosting. United States (server functions); pages are delivered from Vercel's nearest edge location.
• Resend — the emails we send (for example about a friend request), and a notice to our team about a new report if that is switched on (no personal details). European Union (Ireland).
• ImprovMX and Google (Gmail) — receiving the emails you send to our address: forwarding, and our mailbox. ImprovMX: United States and Europe; Google: under its own terms.
• Google and Apple — sign-in, if you choose them. Under their own terms.
• PostHog and Google Analytics — website analytics, only with consent (§7). United States.
• CARTO and Esri (map tiles), and YouTube in no-cookie mode (beach cameras) — they receive your IP address when you view them.
• Sumit — payments, for businesses only, once business billing is switched on. Israel.

• Server-only sources. Weather, sea and map sources (Open-Meteo, OpenStreetMap and others) are called from our server and receive nothing about you.
• Authorities. Only where the law requires it, or where a minor or a life is at risk.
• Outside Israel. Some of these providers process data outside Israel — in the European Union and the United States — under their own terms, which include data-protection commitments.

• Account, profile and the content you created — until you delete it or your account.
• Direct-message photos and voice messages — as long as the message exists. Deleting the message, or the account of either person in the conversation, deletes the file within a day. A reported file is kept while the report is open.
• Check-in — valid for 2 hours; the record is replaced at your next check-in and deleted when you check out.
• When you last had the app open — replaced each time and deleted with your account. After 2½ minutes without an update you are no longer shown.
• Family invitation — valid for 24 hours.
• Reports and the record of their handling — 12 months after their last activity (the last decision, or the date of the report), also after an account is deleted (no longer linked to it), and then deleted.
• Alerts, including lost-child details — until the author deletes the alert or the account.
• Feedback and business enquiries — until we delete them.
• Analytics data (with consent) — Google Analytics: 2 months. PostHog: events stay available to us for 12 months (the limit of our plan), but PostHog does not commit to deleting older records; on request (§12) we delete your PostHog profile and its events.
• Backups — our database provider keeps daily backups for 7 days, so deleted data leaves the backups within 7 days.

You can delete your account at any time: in the app and on the website, Profile → "Delete account".

• What deletion removes: your profile, messages, photos, voice messages and files. The photos and voice messages in your direct-message conversations are deleted for both people, unless they are under an open report. Deletion cannot be undone.
• What is kept: reports (as in §9), business content, and analytics data already collected with your consent (§9) — you can ask us to delete it (§12).
• Sign in with Apple: if you signed in with Apple, the app asks Apple to revoke the access you gave us. If that cannot be done, the account is still deleted and the app explains how to remove Beach4Fun in your Apple ID settings.

Full details on the account deletion page.

• Measures: server-side access rules, private files served through short-lived links, content filtering, and a record of every administrator request to open a reported file.
• Limits: no system is perfect. If you find a problem, tell us.
• Security incidents: if an incident affects your data, we will act as the law requires, including reporting to the Privacy Protection Authority where required.

• What you can ask for: to see the data we hold about you and receive a copy; to correct it; to delete it; to withdraw your analytics consent; to object to a use of your data.
• How: write to hello@beach4fun.app. We may ask you to confirm that the request comes from the account's email address. We will answer within 30 days.
• Complaints: in Israel, to the Privacy Protection Authority. If you live in another country, you may also be able to complain to its data-protection authority.

When this policy changes we update this page and the date at its top. If a change materially affects how we use your data, we will tell you before it takes effect — in the service or by email.