מדיניות פרטיות

0. Key points (non-binding summary) and notice under section 11 of the Israeli Privacy Protection Law

0.1 Key points

• AfterUp is a social app for adults (18+) where you create a "Plan", get matched with participants and chat. To make that work we process account details, profile, photos, your city, Plans you created or joined, and messages.
• Location: when location permission is on, the app sends your device location to the server only while you use the app (never in the background) and only for actions that need it: setting your city, creating a vacation Plan (your starting location is stored) and fixing a place that was not found on the map. We may keep your last known location to show you Plans and people nearby and an approximate distance; other users never see your location, only a city or a rounded distance. A Plan's location is shown to everyone blurred (about 500 m); the exact address is revealed only to participants the host approved.
• The verification badge is optional. You submit a selfie inside the app, following the on-screen instruction, and a member of our team reviews it manually against your profile photos and against a social account linked on your profile (Instagram/Facebook, if you added one; optional, but it helps the review). The selfie is kept in private storage only until the decision and is deleted when the review is completed, and in any case within 30 days. No automated face matching is used for the badge.
• Chat is not end-to-end encrypted. Messages are kept until account deletion. Our team's access to messages is limited to safety and report handling, security, support at your request, operations and legal requirements, and is logged. A notification about a new message may include a preview of it, which passes through the push provider (Google / Apple).
• We do not sell personal data. We use providers (hosting, media, error monitoring, analytics, push, purchases, maps) and measure our ad campaigns: the app embeds the AppsFlyer SDK (a mobile measurement partner) on iOS and Android, which records the install, sessions and a registration completed event with device and app details (on iOS the vendor identifier IDFV and Apple SKAdNetwork; on Android the Google Advertising ID) and reports attribution postbacks to our ad partners Meta and TikTok; our server sends Meta one event when registration is completed, with hashed identifiers; and the website loads the Meta Pixel. The app does not embed a Meta or TikTok SDK, AppsFlyer does not receive your name, phone or email, we do not read the IDFA and do not show a tracking prompt. As of today the events are sent for every user, without a prior consent layer (for the EU and UK a consent layer is pending); you can object, ask us to stop future uses and ask that the data be deleted, and on Android reset or limit your advertising ID.
• Users in Israel who received cards can redeem their value for a bank transfer. For that we collect, once, an image of an identity document, a selfie and bank details; our team reviews them manually, they are kept in private storage, and they are retained as Israeli tax and anti-money-laundering law requires (typically 7 years). Details in section 3.17.
• Account deletion is available in the app, on the website (https://afterup.io/delete-account) and by email. On request the profile is hidden and anonymised and stories are deleted; logging in within 30 days cancels the deletion and restores the account, the profile and the coin balance (stories deleted with the request are not restored); after that the data is permanently deleted, except data we must keep by law.
• You have the right to access, correct, delete, obtain a copy of your data, object, restrict and withdraw consent. Write to support@afterup.co.il and we answer within the period set by applicable law (in Israel usually within 30 days).
• Push notifications about activity on your account, new features in the app and what is happening around you are part of the Service; you can turn them off in your device settings only (there is currently no notification-management screen inside the app). Marketing SMS and email are sent only with separate, unticked opt-in consent and are labelled "Advertisement"; you can opt out at any time by email or by replying "STOP" to an SMS.

0.2 Notice under section 11 of the Israeli Privacy Protection Law, 5741-1981

• Legal duty or voluntary: You are not legally required to give us information. Providing basic account and profile details (phone number, date of birth, gender, display name, at least two photos, city, Plan preferences, wishlist places) is a condition for opening an account and using the Service, because without them we cannot match you with Plans and users. Other information (answers to profile prompts, social links, height, occupation, languages, music clip, contact phone, verification badge, marketing consent) is voluntary and not a condition of use.
• Purposes: operating the Service (account, profile, Plans, matching, chat, stories, AfterCoins), safety and fraud prevention, support, product improvement and marketing measurement, and compliance with legal duties. Details in section 5.
• Recipients and purposes of transfer: other users according to your privacy settings (section 7.2); providers that process data on our behalf (hosting, media, analytics, error monitoring, push, purchases, maps, photo checks) and providers acting as independent controllers (the app stores), table in section 7.1; Meta, AppsFlyer and TikTok for advertising measurement (section 3.13); our bank for executing card redemption payouts (section 3.17); authorities where the law requires.
• Consequences of refusal: without the basic information an account cannot be opened or some capabilities cannot be used (for example, without location permission the map around you will not be shown). Refusing voluntary information does not prevent use of the Service.
• Controller of the database and contact details: Monoloco Ltd., company no. 516332269, 45 Menachem Madmon St., Tel Aviv-Jaffa 6767634; support@afterup.co.il.
• Right of access and correction: under sections 13 and 14 of the Law you may inspect the information about you held in the database and ask to correct or delete it if it is not accurate, complete, clear or up to date. How to do so: section 11.
• Data of special sensitivity: we process location data and content you choose to share that may reveal your intimate life. Location requires a dedicated device permission; intimate content is your choice of what to write and upload. We do not use this data for advertising. Details in section 4.
• Data transferred from the European Economic Area (EEA): data of EEA users is stored together with all other data, so we apply to the whole database the Privacy Protection Regulations (Instructions for Data that was Transferred to Israel from the European Economic Area), 5783-2023: minimisation, deletion when no longer needed, accuracy, and rights of access, correction and deletion for all users. We do not automatically delete accounts for inactivity; if we decide to do so we will give advance notice.

1. Who we are

1.1 Controller of the database (the "Company", "AfterUp", "we"): Monoloco Ltd., an Israeli company, company no. 516332269, 45 Menachem Madmon St., Tel Aviv-Jaffa 6767634, Israel.

1.2 Privacy contact: support@afterup.co.il (put "Privacy" in the subject line). You may also contact us through the chat with the AfterUp support account in the app.

1.3 Privacy Protection Officer / DPO: privacy matters are handled by the Company's privacy team; a Privacy Protection Officer will be appointed as required by law and published here. Contact: support@afterup.co.il (subject: Privacy).

1.4 EU representative (GDPR Article 27): not yet appointed. The Service is not yet offered to users in the EU/EEA; a representative under Article 27 GDPR and Article 13 of the Digital Services Act will be appointed and published here before the Service is offered there.

UK representative (UK GDPR Article 27): not yet appointed. The Service is not yet offered to users in the UK; a representative under Article 27 UK GDPR will be appointed and published here before the Service is offered there.

1.5 Brazil (LGPD): the contact channel for the person in charge (encarregado) is support@afterup.co.il.

1.6 Canada / Quebec: details of the "person in charge of the protection of personal information" are in section 15.3.

2. Scope and definitions

2.1 This Policy applies to the AfterUp app for iOS and Android, to the website afterup.io (including campaign links under go.afterup.io and landing pages), and to your communications with us (support, email). It does not apply to processing by independent third parties: the app stores (Apple, Google), venues or hosts you meet, or other users regarding what they do outside the app.

2.2 Short definitions:

• "Personal data" - any information that identifies you or can identify you, directly or indirectly.
• "Plan" - a meet-up or activity that a user (the "host") creates in the app and that other users ask to join. A person the host approved is an "approved participant". A "match" is created when a join request is approved.
• "Story" - content (photo or video) a user shares for a limited time.
• "AfterCoins" ("AC") - an internal virtual currency bought through the app stores or received as a bonus. Referred to below as "AC".
• "Cards" - virtual items that can be received from other users (sending cards is currently disabled; see section 3.8).
• "Verification badge" - a profile mark showing that a verification selfie you submitted was reviewed manually by our team and found to match your profile photos (and a linked social account, if provided) at the time of the review. It is not identity or age verification.
• "Provider" - a third party that provides us a service. A "processor" is a provider that processes data for us and only on our instructions; other providers (for example the app stores) act as independent controllers under their own terms. The classification appears in the table in section 7.1.
• "Terms" - the AfterUp Terms of Service at https://afterup.io/terms.

3. Data we collect - by feature

3.1 Account and sign-in

• Phone number - the primary account identifier. Verified with a one-time code (OTP) by SMS sent through our authentication system (Supabase Auth) and an SMS delivery provider (for example Twilio).
• Sign in with Apple / Google - if you choose this, we receive from the provider a user identifier and an email address (Apple may provide a relay address). Phone verification is still required.
• Account security data - IP address and time of last login, login count, logout events and security logs.
• Version of the Terms and Policy you accepted, time of acceptance, display language and additional consents (see 3.14).

3.2 Profile

What you fill in, part of which is shown to other users (see 7.2):

• Basics: display name, gender, date of birth (used to enforce 18+, to show your age and to filter by the age range a host set for a Plan), bio, home city (city centre point, not an address), country.
• Photos: between 2 and 9 profile photos. For each photo we keep the storage address, position in the gallery, a digital fingerprint (hash) for duplicate detection, face-detection status and review status.
• Plan preferences: the Plan types you are interested in (at least two, for example after-party, food, club, vacation).
• Profile prompts: short answers to prompts you selected (optional, up to five).
• Wishlist: places you want to visit, by category (at least two categories with two places each). For each place we store its name and the place's coordinates (not your location).
• Music clip: a clip from our in-house music library you chose for your profile, and music preferences.
• Voluntary fields: height, occupation, languages, Instagram/Facebook links, interface language, and a contact phone with a preferred contact method. Note: a contact phone you entered is shown to participants you approved for your Plan (section 7.2); the account's own phone number is shown to no one.
• Settings: public/private profile, direct-invite policy, display order of categories.
• Data we generate about the profile: account status, verification status, internal activity points (XP), karma score, warning count, follower and following counts, last active time, your app build number and platform, profile completeness.

3.3 Location

• Device location (GPS): collected only while the app is in the foreground and only for actions that need it; there is no background location collection. To set your city, the location is converted on the device to a city, and the server receives the city (city name, country, region and city centre point). When you create a vacation Plan, your starting location (the GPS fix at creation time) is sent to the server and stored to calculate the distance to the destination; when you fix a place that was not found on the map, the device location is sent to locate the place. We may store the device's last known location (no location history) to show you Plans and people nearby and an approximate distance to them. Other users never see your location: at most a city or a rounded distance. The last known location is deleted with the account.
• Plan location: when you create a Plan you choose a venue. We store on the server the venue's exact coordinates (not your location) and a blurred version (about 500 m). The blurred version is shown on the map to everyone; the exact address is shown only to approved participants.
• In summary, the location levels: device location - sent to the server only while you use the app, for the actions above, and kept at most as a last known location; city - on the server and shown on the profile; exact location of the Plan venue - on the server, revealed to approved participants; blurred Plan location - shown to everyone; rounded distance - shown to other users, if the feature is active.
• Place search and map: when you type a venue name, the text you typed is sent to Google Places for autocomplete, and city names are sent to Google's Geocoding service (converting a city name to coordinates). Map tiles load from Mapbox servers, which receive your IP address and the map area viewed. The Mapbox SDK may collect usage and location telemetry under Mapbox's privacy policy; the Mapbox attribution menu (the ⓘ symbol) on the map includes Mapbox's telemetry setting.
• You can revoke location permission in your device settings at any time; some capabilities (map, nearby Plans) will not work without it.

3.4 Plans and participation

• Plans you created: title, cover image, venue, exact and blurred location, country, duration, age range, and preferred gender for participants. The age range and preferred gender are host settings for the Plan, and the app uses them to decide to whom the Plan is shown (section 6.2).
• Participation: join requests, approvals and rejections, participant list, direct invites.
• Social actions: follows and followers (and unfollow history), "pings" you sent or received, profile views, ratings, photo likes, super-likes (with a daily cap), and blocks.
• Scoring: XP log and actions that earn points.

3.5 Chat and media

• Messages: message content, sender, recipient, timestamps, read status. A one-to-one chat opens after a Plan match (without a match you can send one message until the other side replies). Each Plan has a group chat for its participants.
• Chat media: photos and videos are stored with our media provider (Cloudinary). "View-once" media can be opened once by the recipient and cannot be reopened after viewing or after 4 hours; the file itself is retained as part of the message until the message or the account is deleted; screenshots are not technically prevented, and the media is not end-to-end encrypted.
• Message notifications: a notification about a new message may include the sender's display name and a preview of the beginning of the message. This content passes through the push provider (Google Firebase Cloud Messaging, and on iOS also Apple's notification service) to reach your device, and may appear on a locked screen. You can turn notifications off in device settings.
• Local copy: the app keeps a local copy of conversations on your device to allow offline viewing. The copy lives on your device and is removed when you uninstall the app.
• Encryption and access: messages are encrypted in transit (TLS) and at rest, but not end-to-end. AfterUp is technically able to access messages. Such access is limited to authorised staff, is logged, and is made only for these purposes: safety and the handling of reports and moderation, security and fraud prevention, support at your request, technical operations and maintenance, and compliance with legal requirements or an order.
• Retention and deletion: messages are kept until permanent account deletion. A message you deleted is marked as deleted and disappears for both sides, and the record is permanently deleted from our servers with the account; the other user's device may keep an offline copy. In a Plan's group chat, messages you sent may remain in the group after your account is deleted, without your name (the sender is shown as "Deleted User").

3.6 Stories

• A story you upload (photo/video, upload time) is shown for 24 hours and then moves automatically to your private Archive in the app, where you can view it, restore it or delete it permanently.
• We store who viewed and who reacted to your story and show this to you as the story owner.
• Media files are deleted from the media provider when you permanently delete a story or when the account is permanently deleted. Live stories are deleted immediately when you request account deletion and are not restored even if you cancel the deletion.

3.7 AC and purchases

• AC purchases are made through the Apple App Store or Google Play. We do not receive or store credit card numbers or payment instrument details.
• From our purchase management system (RevenueCat) and the stores we receive: our user identifier, the product purchased, transaction identifier, price and currency, the store and the purchase time.
• We keep an internal ledger of your AC balance: purchases, bonuses (for example a welcome bonus) and uses (Boost, super-likes). This ledger is needed for fraud prevention and dispute resolution.
• We do not currently offer a subscription. Legacy internal status fields relating to a subscription or "premium" are not in use. If we offer a subscription in the future, we will update this section before launch.

3.8 Cards received

• Sending cards is currently disabled. Cards you received in the past are still displayed: the card type and value, who sent it and when.
• Cards are virtual items. Users in Israel who received cards can ask to redeem their value for a bank transfer (Terms, section 13); the data collected for that purpose is described in section 3.17. Redemption outside Israel is not offered today; if and when it is offered, it will be governed by separate Redemption Terms and executed through a licensed payout provider.

3.9 Verification badge (manual selfie review)

• The verification badge is optional. Without it all other capabilities of the Service are available.
• The process: you take a selfie inside the app, following the on-screen instruction (for example holding a note with the text shown). A member of our team reviews the selfie manually against your profile photos and against a social account linked on your profile (an Instagram/Facebook URL, if you provided one; a social link is optional, but it helps the review), and approves or rejects the request. We do not use facial recognition, biometric identification, automated face comparison or automated face detection for verification: no face template is created, and no software compares the selfie to your photos.
• What we store: the selfie in a private storage bucket (it is never shown on your profile and does not enter your gallery), the request status, the time of submission and of the review decision, and the staff member who reviewed it.
• Retention: the selfie is kept only until the decision and is deleted when the review is completed, and in any case within 30 days; the decision record (status and time, without the selfie) is kept as proof of the badge until the badge is revoked or the account is deleted.
• The verification badge is not verification of identity, age or criminal background, and may be revoked.
• Automated photo checks for all users: every profile photo uploaded goes through an automated check that a face is visible (AWS Rekognition DetectFaces, Frankfurt region, European Union) and a duplicate check against existing photos. The face check is face detection only - it does not identify anyone and does not compare faces. These checks store no face template, only a result (face detected / not detected) and a digital fingerprint of the file.
• You can ask us at any time to delete your verification selfie and revoke the badge by emailing support@afterup.co.il.

3.10 Reports, blocks and enforcement records

• Reports you filed or that were filed about you: the category (for example inappropriate content, scam/fake, spam, safety, harassment, intimate image shared without consent, other), free text, the reported content or profile, and time. A report button exists on profiles, Plans and messages; a story is reported through the profile of the person who uploaded it or by email.
• Blocks: who blocked whom and when (blocking is mutual and not disclosed to the other side).
• Enforcement records: decisions of our enforcement team, warnings, hides, freezes, bans, ban reason, internal notes, account status history and an audit log of enforcement team actions.
• Reports in the "intimate image without consent" category are automatically flagged for priority handling with a removal target of up to 48 hours.

3.11 Device and technical data

• Push token (FCM), platform (iOS/Android), app version and build number, language.
• IP address and time at login, login count, logout events.
• Notifications: the push provider (Google Firebase Cloud Messaging, and on iOS also Apple) receives the push token and the notification title and body, which may include a display name and a message preview (section 3.5).
• Crash and error reports (Sentry, servers in the European Union): stack trace, release, environment and our internal user identifier (no name, email or IP).
• Font loading: the app loads fonts from Google Fonts servers, which receive your IP address in the request.

3.12 Analytics events (Mixpanel)

We use Mixpanel (servers in the European Union) to understand how the app is used. As of today analytics runs for all users (see 13.1 for your choices).

• Events: sign-up, app opened, app backgrounded, screen view and screen duration, login and logout, profile viewed, card sent, AC purchased, AC spent, Boost activated, Plan created, message sent (chat type and whether it included media - not the message content), story created, story viewed (including the story owner's identifier), days since registration, and submitting a report about a user who has a DJ profile (we record the DJ profile's city, genres and whether it has external links - not the report content).
• Analytics profile: our user identifier, name, gender, email and phone (if present), user type, internal "premium" status (not in use), platform and app version.
• What the SDK adds automatically: device and operating-system data (model, OS version, carrier, language, screen resolution) and an approximate city/region-level location derived from your IP address.
• What is not sent: precise GPS location, message content, photos or verification selfies.

3.13 Marketing measurement (Meta, AppsFlyer, TikTok)

• On the website: certain landing pages and campaign links load the Meta Pixel, which reports page views, content views and leads to Meta, together with Meta cookies and your IP address. See section 13.2.
• In the app (AppsFlyer SDK, iOS and Android): the app embeds the SDK of AppsFlyer Ltd. (Israel), a mobile measurement partner, on iOS and Android, for install attribution and measurement of our Meta and TikTok ad campaigns. The SDK initialises when the app starts and automatically records the install, first open and sessions; in addition we send through it one explicit event today: "registration completed" (with the registration method "phone"); we may add events such as profile completed, Plan created and invite accepted. We do not send purchase or revenue events, and we do not pass your name, phone, email or our customer identifier to AppsFlyer. With these events AppsFlyer receives: on iOS the vendor identifier (IDFV) and Apple SKAdNetwork data (aggregated, without IDFA; the app does not show a tracking prompt, App Tracking Transparency); on Android the Google Advertising ID (GAID) and Android device identifiers; and on both platforms your IP address, device model, operating system and language, app version, install time and first-open and session events. AppsFlyer reports install and event postbacks to our ad partners Meta and TikTok for attribution: on iOS through SKAdNetwork (aggregated, without a device identifier), and on Android at device level using the advertising ID. Partner sharing scope: only install and in-app event postbacks are shared with Meta and TikTok for attribution; we have disabled AppsFlyer's advanced data sharing and advanced matching, so no hashed personal details (such as email or phone) are sent to them through AppsFlyer. On iOS these postbacks are aggregated SKAdNetwork data without a device identifier; on Android they are sent with the device advertising ID. For Meta we have also enabled the 'limit use of personal information' (CCPA) setting in AppsFlyer. AppsFlyer stores the data in the United States (AppsFlyer's global region); AppsFlyer Ltd. is an Israeli company acting as our processor under a data processing agreement, with standard contractual clauses for the US storage where required. There is no TikTok SDK in the app; TikTok receives attribution postbacks through AppsFlyer only. The SDK stores identifiers on the device.
• From our server (Conversions API): when you complete profile registration, our server sends Meta a single event - "CompleteRegistration" - containing your email, phone and user identifier after one-way hashing (SHA-256), your IP address, a device/software identification string (User Agent), and Meta cookie identifiers if you arrived from a campaign. We store only the time of sending. As of today the event is sent once for every user who completes registration, without a prior consent mechanism.
• Purpose: to measure which campaigns bring installs and registrations, to optimise our Meta and TikTok app-install campaigns, and to let Meta avoid showing our ads to people who already registered (audience exclusion). We do not pass data to Meta, TikTok or AppsFlyer for their own independent marketing. Meta does not receive a clear-text phone or email from us, but hashed data and advertising identifiers are still personal data.
• Roles of Meta, AppsFlyer and TikTok: AppsFlyer processes the data on our behalf as a processor. Under Meta's business tools terms, Meta Platforms Ireland Ltd. (and in the US Meta Platforms, Inc.) is a joint controller with us for the collection and transmission of the events, and an independent controller for the subsequent processing in its services; the essence of the arrangement is available in Meta's business tools terms. TikTok (TikTok Technology Limited in Ireland, and in the US TikTok Inc.) receives the attribution postbacks under its business products terms and processes them as a controller for its own purposes.
• Choice: you can object at any time by emailing support@afterup.co.il - we will stop sending future measurement events about you, instruct AppsFlyer to delete the data and ask Meta and TikTok to delete what was sent to them (US state residents see also section 15.2 regarding "Do Not Sell or Share"). On Android you can also reset or limit your advertising ID in the Google settings on the device; on iOS no IDFA is used, so there is nothing to switch off. For users in the EU and UK a prior consent mechanism will be introduced before the Service is marketed to users in the EU/EEA or the UK; until then the events (SDK and server) are sent as described above, and you can object as stated.

3.14 Consent records

• We keep: the version of the Terms and Privacy Policy you accepted, the time of acceptance and display language, marketing consent and its time, terms region, and a non-editable log of consent events (source: consent window, login screen, OTP verification, settings, consent gate).
• When we change the documents materially, the app asks you to accept the new version again.
• The records are deleted when the account is permanently deleted, except a minimal acceptance log, written automatically by the database when a consent event is deleted (SHA-256 hashed user identifier, event type, version accepted, timestamp and source), kept for the limitation period as proof of acceptance and for the defence of claims (section 9).

3.15 Support and enquiries

When you contact us (email, chat with the support account in the app, website forms) we keep the content of the enquiry, the contact details you gave and the correspondence, to handle the enquiry and improve the Service.

3.16 Referrals

If you joined through a referral code or link, we store the referral source on your profile. A click on a campaign or referral link on the website may be logged (time, IP address, browser type) for campaign measurement; automatic attribution of such a click to an account opened later is not active today. Referral rewards are points, AC or cards only, never money.

3.17 Identity verification and bank details - only if you apply to redeem cards (Israel)

If you are in Israel and apply to redeem received cards (Settings > Wallet > Redeem), we collect, in order to execute the payout and as required by Israeli tax and anti-money-laundering law: an image of an identity document (front/back), a selfie, the account holder's name and bank account details (bank, branch, account number), and the request records (amount, status, decision and payment time). Identity verification is completed once; later requests reuse it unless your details change. Purpose and legal basis: performance of the contract (executing the redemption you requested) and compliance with legal obligations (tax, anti-money-laundering). Storage and access: the documents are kept in a private storage bucket, access is restricted to authorised staff, the application is reviewed manually by our team, and the documents are not shown to other users; bank details are passed to our bank only to execute the transfer. Retention: identity documents, bank details and payout records are kept as required by Israeli tax and anti-money-laundering law, typically 7 years, and then deleted; an abandoned or rejected application is deleted within a reasonable time. Redemption outside Israel is not offered today; if and when it is offered, it will run through a licensed payout provider under separate terms, and this section will be updated before launch.

3.18 Website forms

The waitlist and contact forms on the website collect email and/or phone, IP address and campaign parameters (UTM). The details are emailed to us through the Resend service and received in a team mailbox hosted by Google (Gmail), and are used to contact you about the launch and to respond. The website is hosted on Vercel and uses country-level location derived from your IP address to show a localised version of the site (a preference cookie).

3.19 Data about you coming from other users

Other users may generate data about you: reports, blocks, ratings, likes, profile views, join requests, messages to you. We process this data to operate the Service and for safety, and we do not disclose to the reporter or the reported person the other side's identity beyond what is already visible.

4. Sensitive data and special categories

4.1 Whether data counts as "sensitive" depends on the law. This is how we treat the relevant types:

• Location: "data of special sensitivity" under the Israeli Privacy Protection Law and "sensitive data" under US state laws; it is not a "special category" under GDPR Article 9 and not sensitive data under the LGPD. The device location is sent to the server only while you use the app and for the actions listed in section 3.3, and is kept at most as a last known location; the server also receives the city; the location of a Plan you host is stored precisely and displayed blurred. Basis: a dedicated device location permission, which you can revoke at any time, and performance of the Service you requested.
• Content revealing your intimate life: what you choose to write or upload in your profile, chat and stories may reveal intimate information. That is your choice; we do not ask for such information and do not infer characteristics from it. We process this content only to provide the Service and enforce the rules.

4.2 We do not ask about sexual orientation and the profile has no such field. A Plan host may set a preferred gender for participants in their Plan; that is a setting of the Plan that decides to whom it is shown, not data about anyone's orientation.

4.3 We do not use sensitive data for advertising and we do not sell it. We do not pass location, verification selfies, message content, photos, bio, prompt answers, wishlist places or Plan preferences to analytics or advertising providers. The analytics profile at Mixpanel receives only the attributes listed in section 3.12: display name, gender, email and phone (if present), user type and the internal "premium" flag (not in use), plus platform and app version. Meta receives only the data listed in section 3.13, and we do not use Meta's tools to build segments based on sensitive characteristics.

4.4 Legal basis: for profile content you chose to display to other users - data you yourself made manifestly public (GDPR Article 9(2)(e)), to the extent Article 9 applies to it. For chat and story content - provision of the Service you requested, and in safety or legal-defence situations, the law that permits it (including GDPR Article 9(2)(f)). You can withdraw consent at any time (section 11.6).

5. Purposes, legal bases and retention

5.1 Purposes and bases table:

5.2 Where the basis is legitimate interest, we have balanced it against your rights, and you may object (section 11.5). Where the basis is consent, you may withdraw it at any time without affecting the lawfulness of processing before withdrawal.

6. Automated decision-making and profiling

6.1 Deck ranking and visibility: the order in which Plans and profiles are shown is set automatically based on your Plan preferences, app activity, geographic proximity (city level), freshness and profile completeness. In addition: paid Boost temporarily raises a Plan's prominence; the verification badge and enforcement restrictions (including reduced visibility of an account that broke the rules) affect ordering and inclusion; mutual blocks hide the parties from each other; and the age and gender preferences a host set for a Plan decide to whom it is shown (6.2).

6.2 Host preferences: a host may set an age range and preferred gender for their Plan. The app uses this to decide to whom the Plan is shown and who can ask to join. The final decision on approving a participant is the host's (a human).

6.3 Automated photo checks: a photo without a visible face or a duplicate photo is rejected automatically and you are asked to upload another one. You can appeal and request human review via support@afterup.co.il.

6.4 Rate limits and anti-spam: automatic limits on how often actions can be performed (for example messages, requests, daily super-likes) to prevent harassment and spam.

6.5 Enforcement: decisions to warn, hide, restrict, freeze or ban an account are made by humans on our team, assisted by reports and automated checks. Three kinds of actions happen automatically: a temporary block for security reasons (for example unusual sign-in attempts), rejection of a photo that does not meet the rules (6.3), and rejection of a sign-up or closure of an account when the declared date of birth shows an age under 18. Each of these can be appealed and reviewed by a human (6.6).

6.6 Your right: to ask for an explanation of a decision concerning you, to express your point of view and to request human review, via support@afterup.co.il or the appeal channels described in the Terms (https://afterup.io/terms).

7. Who we share data with

7.1 Providers and recipients

The following providers receive data as described. A "processor" processes data for us under a data processing agreement and only for the stated purpose; an "independent" or "joint" controller also processes the data under its own terms. For US providers we rely on the provider's Data Privacy Framework (DPF) certification where it is in force, and otherwise on Standard Contractual Clauses (SCCs), in the UK with the Addendum or IDTA (section 8.2).

We check that every processor commits to a level of protection not lower than this Policy.

7.2 Other users

• Public profile: your display name, age, gender, photos, bio, prompt answers, Plan preferences, wishlist, music clip, city, verification badge, social links and voluntary fields you filled in (height, occupation, languages) are visible to registered users.
• Private profile: if you enabled a private profile, your profile is not shown in general discovery and suggestions; it remains visible to users you interact with in the app (for example followers you approved, hosts of Plans you asked to join, participants in shared Plans and existing conversations). The setting is preserved if you cancel a deletion request and restore the account.
• Plans: a Plan you created is shown to users who match the preferences you set, with a blurred location. A host sees the profile of anyone who asked to join. Approved participants see the exact address, the other participants in the group chat, and the host's contact phone if the host entered one.
• Chat and stories: messages are visible to their recipients; stories are visible to registered users who can see your profile (subject to the private-profile setting and blocks); the story owner sees who viewed and reacted.
• Actions: pings, follows, likes and requests are visible to the other side. A block is not disclosed to the blocked person.
• What is not shown: your account phone number, email, IP address, push token, verification selfie and data, internal notes and enforcement records are not shown to other users. If you entered a "contact phone" in your profile, it is shown only to participants you approved for your Plan, so they can reach you (for example on WhatsApp or by call); you can remove it from your profile at any time.

7.3 Hosts and venues

A host is not our agent. What you give a host in chat or at a meet-up is the host's responsibility. We do not pass your details to venues.

7.4 Authorities and legal demands

We will disclose data to law enforcement, courts or regulators where the law requires it (a valid order or legal demand), and in emergencies involving a real risk to life or safety. We report suspected child sexual exploitation to the competent bodies (such as NCMEC) where the law requires, and preserve the relevant content for the period the law requires.

7.5 Corporate transactions

In a merger, acquisition, sale of assets or similar process, data may pass to the acquiring entity subject to this Policy; we will notify you in advance of a change in the identity of the controller of the database.

7.6 With your consent

In any other case we share data only if you asked for it or agreed to it.

7.7 We do not sell personal data

We do not sell personal data for money and we do not pass it to third parties for their own independent marketing. Sending measurement events to Meta, and attribution data through AppsFlyer to Meta and TikTok (3.13), may count as "sharing" or a "sale" under the broad definitions of certain US state laws; see section 15.2 for the right to opt out.

8. International transfers

8.1 We are an Israeli company and our team accesses data from Israel. The main database and the automated photo checks are hosted in the European Union (Germany), and some providers operate in the USA or on global networks. Providers' support teams may access data from other countries under the processing agreements. Your data may therefore be processed outside your country of residence. Our measurement partner AppsFlyer (section 3.13) is an Israeli company and stores the measurement data in the USA (see section 7.1); our ad partners Meta and TikTok receive the attribution postbacks in Ireland and the USA.

8.2 Users in the EU/EEA and the UK: Israel is recognised by an adequacy decision of the European Commission (reconfirmed in 2024) and by the UK adequacy regulations, so transfer to us requires no additional measures. Transfers to US providers rely on the Data Privacy Framework (including the UK Extension) where the provider is certified, or on the Commission's Standard Contractual Clauses (and in the UK the IDTA/Addendum), and where required, a transfer assessment. You can request a copy of the safeguards via support@afterup.co.il.

8.3 Users in Israel: transfers abroad are made under the Privacy Protection Regulations (Transfer of Data to Databases Abroad), 5761-2001, including to countries with an adequate level of protection (the European Union) and to providers that undertook in writing to comply with the Israeli data-holding conditions and adequate security.

8.4 Users in other countries: transfers are made in accordance with local law (for example LGPD Article 33, APP 8, PIPEDA), with contractual safeguards.

9. Retention periods

9.1 Retention table:

Version 3.1 (2 September 2026): clarifies that push notifications about account activity, app news and activity around you are part of the Service and can be turned off in device settings;; and the location sections (0.1, 3.3, 4.1, 5) were updated: the device location is sent to the server while you use the app and may be kept as a last known location to show Plans, people and an approximate distance; creating a vacation Plan stores your starting location.

Retention required by law: in every case in the table, we may keep data beyond the stated period where the law requires it, where legal proceedings or a pending enquiry are ongoing, where evidence must be preserved (for example reports of child sexual exploitation, for the period the law sets), or where needed for the defence of claims - and then only for the necessary period and with restricted access. We do not automatically delete accounts for inactivity.

9.2 Account deletion - what actually happens:

• On request: the profile is hidden and anonymised immediately - the display name is replaced with "Deleted User"; photos, bio, date of birth, city and country, music preferences, social links and contact phone are removed; the account is marked deleted and no longer appears to others. Live stories are deleted immediately. Conversations with other users remain on their side marked "Deleted User" for the 30 days. The AC balance is preserved at this stage.
• 30-day grace period: logging in within 30 days cancels the deletion and restores the account, the profile (including the public/private setting) and the AC balance; stories deleted with the request are not restored.
• Permanent deletion: after the 30 days the deletion is scheduled and completed promptly thereafter: messages, conversations, stories and archive, Plans, follows, blocks, reports (as reporter and as reported), purchase records, consent records, verification data and account details are deleted, and the phone number is released. Media files are deleted from the media provider. One-to-one messages and conversations are deleted from our servers; the other user's device may keep an offline copy. Messages you sent in a Plan's group chat may remain without your name.
• What remains: a minimal staff audit record (9.1), a minimal acceptance log of consent (3.14), aggregate accounting records that do not identify you, identity-verification and payout records if you redeemed cards (3.17, for the legal retention period), and data we must keep by law or for pending proceedings (9.1).
• AC: the AC balance is forfeited on permanent deletion. Before final deletion you may ask by emailing support@afterup.co.il for a refund of AC bought with money and not used; it is granted where applicable law or the store's rules entitle you to it, and otherwise at our reasonable discretion, as set out in the Terms.

10. Security

10.1 We implement technical and organisational measures in line with the Israeli Privacy Protection (Data Security) Regulations, 5777-2017, and GDPR Article 32, including: encryption in transit (TLS) and at rest; row-level security (RLS) in the database restricting each user to the data they are allowed to see; least-privilege access for staff; mandatory two-factor authentication for the admin panel; audit logs of staff actions; backups; storage of sensitive documents (verification selfies, identity documents for card redemption) in private buckets; serving of user media through the media provider at unique addresses; and security testing.

10.2 No method is 100% secure. Keep your OTP code to yourself, never share it, and log out of devices that are not yours.

10.3 Security incident: in the event of a security incident we will assess its scope and risk and notify the competent authority (in Israel - the Privacy Protection Authority; in the EU - the relevant supervisory authority, within 72 hours of becoming aware where the law requires; in the UK the ICO; in Canada the OPC; in Australia the OAIC; in Brazil the ANPD; in the US state authorities) and affected users, within the time and at the threshold set by applicable law.

11. Your rights and how to use them

11.1 Access: to know whether we hold data about you and to receive it (Israeli Privacy Protection Law s.13; GDPR Article 15).

11.2 Copy and portability: there is currently no automated export tool in the app. You may request a copy of your data in a common, readable format by emailing support@afterup.co.il, and we will provide it within the legal time limits.

11.3 Correction: most profile details can be edited directly in the app. To correct other data, contact us.

11.4 Deletion: in the app (Settings > Delete account, with double confirmation), on https://afterup.io/delete-account, or by email to support@afterup.co.il. See section 9.2 for the process and the 30-day grace period. In the app you can delete photos, stories (including from the Archive), Plans and messages yourself; deletion of other data items without deleting the account can be requested through support, where the law grants it and as far as technically feasible.

11.5 Restriction and objection: to ask us to restrict processing, and to object to processing based on legitimate interest (for example analytics and campaign measurement) and to direct marketing at any time.

11.6 Withdrawing consent: verification badge - ask us at any time to revoke the badge and delete your verification selfie and data; marketing - section 12; location permission - device settings; notifications - device settings; Meta measurement and analytics - sections 3.13 and 13.1.

11.7 Information about automated decisions: section 6.

11.8 Complaint to us: write to support@afterup.co.il with "Privacy complaint" in the subject. We acknowledge within 30 days (and in the UK, as required by the Data (Use and Access) Act 2025) and respond without undue delay.

11.9 Complaint to an authority: in Israel - the Privacy Protection Authority (www.gov.il/he/departments/the_privacy_protection_authority); in the EU - the supervisory authority in your country of residence; in the UK - the ICO; in Canada - the OPC (and in Quebec the CAI); in Australia - the OAIC; in Brazil - the ANPD; in the US - your state Attorney General or the competent agency (in California the CPPA).

11.10 How to ask and what happens next: email from an address linked to your account or contact us through the app. To protect you we will verify your identity (for example confirmation via the account's phone number) before disclosing or deleting data. We respond within the period set by applicable law (in Israel usually within 30 days; regional timelines in section 15); if more time is needed, as the law permits, we will tell you and explain. Exercising rights is free unless requests are manifestly repetitive and unreasonable. We will not discriminate against you for exercising rights.

11.11 Authorised agent: you may act through an authorised agent with written authorisation; we will also verify the user's own identity.

12. Marketing and communications

12.1 Service messages (login code, join approval, new message, Plan update, security, changes to the legal documents) are sent as part of the Service and do not require consent. The same applies to push notifications about activity on your account, about features and news in the app, and about activity and new users in your area: they are part of the Service. Push notifications can be turned off in your device settings only; there is currently no option to choose notification types inside the app. Security and mandatory notices will still be sent through an available channel.

12.2 Marketing SMS and email (promotions, partnerships, campaigns) are sent only if you ticked, at sign-up or later, the separate consent box, which is unticked by default and is not a condition of use. Every marketing message is labelled as required by the law that applies to it (in Israel: "פרסומת", meaning "Advertisement") and includes our details and a simple, free way to opt out in the same channel, as required by section 30A of the Israeli Communications (Telecommunications and Broadcasting) Law, 5742-1982, CAN-SPAM, CASL and similar laws.

12.3 Opting out: write to support@afterup.co.il; for a marketing SMS - reply "STOP" (in Hebrew "הסר"); for a marketing email - click the unsubscribe link. Push notifications can be turned off in your device settings. Opt-out takes effect promptly and no later than the time set by law.

12.4 Direct mailing (Israeli Privacy Protection Law ss.17C-17F): if we contact you based on characterisation (for example by city or preferences), the message will state that it is direct mailing, that the source of the data is the details you gave us at sign-up and in use, and your right to be removed from the mailing list at any time by emailing support@afterup.co.il.

12.5 We do not give your contact details to other advertisers.

13. Cookies, SDKs and tracking

13.1 In the app

• AppsFlyer SDK in the app: the app embeds the AppsFlyer SDK on iOS and Android, as described in section 3.13; it initialises when the app starts. There is no Meta SDK in the app and no TikTok SDK; Meta and TikTok receive attribution postbacks from AppsFlyer only. We do not pass our user identifier, name, phone or email to the SDK, we do not read the IDFA and we do not show a tracking prompt (App Tracking Transparency); on iOS attribution uses the vendor identifier (IDFV) and Apple SKAdNetwork (aggregated postbacks), and on Android the Google Advertising ID, which you can reset or limit in the device's Google settings. The SDK stores identifiers on the device. In addition, a measurement event is sent from our server to Meta (Conversions API), and the Meta Pixel runs on the website only.
• EU and UK: as of today analytics (Mixpanel) and the measurement events (the AppsFlyer SDK initialises at app start, and the Meta server event) run for all users, without a prior in-app consent layer. A consent layer for users in the EU and UK, which will hold analytics and measurement until consent, will be introduced before the Service is marketed to users in the EU/EEA or the UK. Until then you can ask us to stop via support@afterup.co.il, and we will honour the request for future processing.

13.2 On the website afterup.io

• Essential cookies: operating the site, remembering your choice in the cookie banner (stored locally in the browser), and the preference for a country-localised version of the site.
• Meta Pixel (marketing): campaign landing pages and campaign links load the Meta Pixel when the page opens. The main site pages show a cookie banner; as of today the banner does not prevent the Pixel from loading on campaign pages. Making the Pixel load only after prior consent for visitors from the EU and UK will be completed before the website is marketed to users in the EU/EEA or the UK. In the meantime you can prevent the Pixel in browser settings, with a tracking blocker, or in the advertising settings of your Meta account.
• No Google Analytics or other tracking tools on the site as of this date.
• Global Privacy Control (GPC): the site does not currently detect a GPC signal automatically. We are working to honour GPC signals; until then, opt-out requests for sharing/sale are received by email (13.3) and honoured.

13.3 "Do Not Sell or Share" (USA)

You may ask us not to share your data for measurement or targeted advertising by emailing support@afterup.co.il (subject: "Do Not Sell or Share"). See section 15.2.

14. Children and minors

14.1 The Service is for people aged 18 and over only, in every country. We enforce this with a date-of-birth declaration and automatic blocking under 18, we use the 18+ age rating in the app stores, and we may use operating-system or store age signals where available - for age compliance only.

14.2 We do not knowingly collect data from minors. If we discover that a user under 18 opened an account, we close the account and delete the data in accordance with section 9.2, and the account will not be restored.

14.3 Reporting a minor: support@afterup.co.il with the subject "Child safety", or via the report button in the app. Full child safety policy: https://afterup.io/child-safety.

15. Regional annexes

15.1 European Union / EEA and United Kingdom

• Legal bases: see the table in section 5. For special categories: profile content you chose to display to others - Article 9(2)(e), to the extent Article 9 applies (section 4.4).
• Whether providing data is required and the consequences of refusal: section 0.2.
• Rights: access, rectification, erasure, restriction, portability, objection (including to direct marketing at any time), withdrawal of consent, and not to be subject to a solely automated decision (Articles 15-22). Exercised under section 11, free of charge, response within one month (extendable by two months in complex cases, with notice).
• Representatives: section 1.4. Data protection officer: section 1.3.
• Complaint: to any supervisory authority in the EU, in particular in your country of residence or work; in the UK to the ICO (ico.org.uk). In the UK we acknowledge a complaint to us within 30 days and respond without undue delay.
• Transfers: section 8.2.
• ePrivacy: section 13.1 (current state and the date the consent layer goes live).
• Children: section 14 (18+).
• Changes and notice: material changes are notified at least 30 days in advance (section 16).

15.2 United States (state privacy rights)

This section applies to residents of states with comprehensive privacy laws (for example California, Colorado, Connecticut, Virginia, Texas, Oregon and others). We may not meet the applicability thresholds of some of these laws; we honour the following rights as a matter of policy for every US user.

• Categories of personal information collected in the last 12 months (in CCPA terms), their source, recipients for a business purpose, and whether "sold"/"shared":

• Purposes: section 5. Disclosure for a business purpose: to the processors in section 7.1.
• "Sale"/"sharing" and targeted advertising: sending app activity and the advertising ID (Android) or vendor identifier (iOS) to AppsFlyer and the resulting attribution postbacks to Meta and TikTok, sending hashed identifiers, IP and UA to Meta (3.13) and the website Pixel may count as "sharing" for cross-context behavioural advertising (and under some state laws a "sale"). We do not sell data for money, and we do not sell or share sensitive data or data of anyone we know to be under 16.
• Opt-out: email support@afterup.co.il with the subject "Do Not Sell or Share". We honour a request within 15 business days, stop sending future events and ask AppsFlyer, Meta and TikTok to delete. In AppsFlyer we have enabled the 'limit use of personal information' setting for Meta and disabled advanced data sharing and advanced matching for Meta and TikTok. On Android you can also reset or limit the advertising ID in the device's Google settings, which stops device-level attribution; on iOS no IDFA is ever used and no tracking prompt is shown. The site does not currently detect a GPC signal automatically; we are working to honour GPC signals (13.2).
• Sensitive data: part of it is necessary to provide the Service you requested (login credentials, the content of messages you send, the location of the Plan venue you chose) and is processed for that purpose only; the device location is kept at most as a last known location (section 3.3). We do not use sensitive data to infer characteristics or for advertising, and you may ask us to limit its use to what is necessary for the Service.
• Rights: to know/access, to obtain a copy (portability), to correct, to delete, to opt out of sale/sharing/targeted advertising/profiling with significant effects, and non-discrimination for exercising rights (we will not deny service or change price or quality).
• Verification: we verify requests using the account's phone number and additional information if needed. Authorised agent: permitted with signed authorisation; we will also verify you.
• Response time: within 45 days (extendable by a further 45 days with notice). Appeal: if we denied a request, you may appeal by email with "Appeal" in the subject; we respond within 45 days and inform you of the option to contact your state Attorney General.
• Notice at collection: sections 3, 5 and 9 constitute the notice. Financial incentives: we do not offer a financial incentive in exchange for personal information; bonuses and referral rewards are given for actions in the app and not for providing data or consenting to sale/sharing. "Shine the Light" (California): we do not disclose data to third parties for their direct marketing, so it does not apply.
• No arbitration in this Privacy Policy. Dispute resolution arrangements appear in the Terms.

15.3 Canada (PIPEDA and provincial laws, including Quebec)

• We collect, use and disclose personal information with meaningful consent and for purposes a reasonable person would consider appropriate, as set out in sections 3 and 5. The four key elements: what is collected (section 3), with whom it is shared (section 7), why (section 5), and risks (transfer to other countries, section 8; no end-to-end encryption, section 3.5).
• Information is processed and stored outside Canada (access from Israel; storage in the European Union and the USA) and is subject to the laws of those countries.
• Rights: access, correction, withdrawal of consent (subject to contractual consequences: for example, without a phone number an account cannot be held, and without location permission the map is not shown), complaint to us and to the OPC (priv.gc.ca). We respond to an access or correction request within 30 days; if we refuse, we give written reasons and note the right to complain, and if a correction is disputed we attach a note of the requested correction to the record. Complaints to us are reviewed by a human and answered in writing.
• Breaches: we keep records of incidents and notify the OPC and affected individuals where there is a real risk of significant harm.
• CASL: commercial electronic messages only with express consent, with sender identification and an unsubscribe mechanism (section 12).
• Quebec (Law 25): person in charge of the protection of personal information: the Company's privacy team, support@afterup.co.il. Information is communicated outside Quebec (section 8). Availability of this Policy in French: the Service is not currently offered in Quebec; a French version will be provided before it is.

15.4 Australia (Privacy Act 1988, APPs)

• Kinds of information, how collected and held: sections 3, 9 and 10. Purposes: section 5.
• Overseas disclosure (APP 8): information is stored and processed in the European Union (Germany) and the USA by the providers in section 7.1, and our team accesses it from Israel. Some providers operate global delivery networks (for example Vercel, Cloudinary), and internal operational alerts (identifiers and counts only) pass through Telegram, whose servers are outside Israel and the EU.
• Access and correction (APP 12-13): section 11; response within 30 days. If we refuse, we give written reasons, note the right to complain, and on your request attach a statement of the requested correction to the record.
• Complaints: first to us (support@afterup.co.il); we acknowledge, investigate and respond in writing within 30 days. If you are not satisfied, you may contact the OAIC (oaic.gov.au). You may also contact the eSafety Commissioner regarding online harm.
• Breaches: we follow the Notifiable Data Breaches scheme.
• Government identifiers: we do not collect them (except identity documents for card redemption in Israel, section 3.17).

15.5 Brazil (LGPD)

• Legal bases (Article 7): performance of a contract (rows 1-7, 10, 15 of the section 5 table), consent (row 11), legitimate interest (rows 7-9, 12-15, 18), compliance with a legal obligation (rows 16-17), and exercise of rights in proceedings. Sensitive data (Article 11): location is not sensitive data under the LGPD; content you choose to share that may reveal your intimate life is treated as described in section 4.
• Other controllers: Meta and TikTok (section 3.13) and the app stores (section 7.1) also act under their own terms.
• Rights (Article 18): confirmation of processing, access, correction, anonymisation/blocking/deletion of unnecessary data, portability, deletion of data processed with consent, information about sharing, information about the option not to consent and its consequences, withdrawal of consent, review of automated decisions (section 6).
• Person in charge (encarregado): support@afterup.co.il.
• International transfer (Article 33): per section 8, through ANPD standard contractual clauses or another recognised mechanism, where applicable.
• Complaint: to the ANPD (gov.br/anpd).

16. Changes to this Policy

16.1 We will update this Policy when the Service or the law changes. For a material change (for example new purposes, new data types, processors of a new category, a change in rights) we will give at least 30 days' notice by email or in-app message and ask you to accept the new version again in the app. We record the version you accepted, the time of acceptance and the display language.

16.2 The version number and effective date appear at the top of the document. Previous versions are kept by us, and a copy can be obtained by emailing support@afterup.co.il.

16.3 Changes do not operate retroactively and do not reduce rights granted by law.

17. Contact

Monoloco Ltd. (מונולוקו בע"מ), company no. 516332269

45 Menachem Madmon St., Tel Aviv-Jaffa 6767634, Israel

Email: support@afterup.co.il (privacy, rights, complaints, "Do Not Sell or Share", child safety)

Privacy Protection Officer: privacy team, support@afterup.co.il (Privacy Protection Officer to be appointed)

EU representative: not yet appointed (the Service is not yet offered in the EU/EEA; a representative under Article 27 GDPR and Article 13 of the Digital Services Act will be appointed and published here before it is) | UK representative: not yet appointed (the Service is not yet offered in the UK; a representative under Article 27 UK GDPR will be appointed and published here before it is)

LGPD person in charge (Brazil): support@afterup.co.il

Terms of Service: https://afterup.io/terms | Account deletion: https://afterup.io/delete-account

© 2026 Monoloco Ltd. All rights reserved.