Skify Privacy Policy
Version 1.0 · Publication date: 26 October 2026
This English version is a convenience translation. The Hebrew version is the binding version; if the two differ, the Hebrew version prevails.
1. Who is responsible for your information
1.1 The service is operated by Itamar Apel (hereinafter: “Skify”). Skify is responsible for the information collected in the service (the database controller under Israeli law; the “controller” under the EU GDPR).
1.2 For any privacy question or request: [email protected].
1.3 This policy applies to the Skify app and forms part of the Terms of Use.
1.4 The Hebrew text is the binding text. This English version is a translation for convenience only.
2. In short
- We collect what is needed to run the service.
- There are no ads, no usage analytics tools and no tracking tools in the service. We do not sell information.
- We do not collect your location: there is no GPS and no location permission.
- Your profile, open requests and community content are visible to every signed-in user. Chats are visible only to the participants in the conversation.
- Deleting your account from within the app takes effect immediately. Some content remains without your name and photo, and photos you sent in chats remain — details in section 12.
3. What information is collected and who can see it
You provide most of the information yourself. Technical information is collected automatically, as noted.
| Information | How it is collected | Who can see it |
|---|---|---|
| Account: email and password, or sign-in through Google | From you, at registration | Only you |
| Approval of the terms: the version number you approved and when you approved it | Automatically, when you approve | Skify |
| Profile: full name, photo, gender, age, ski level, ski style, trip style, favorite resorts, bio (up to 300 characters), country of residence (country only) | From you | Every signed-in user. The profile photo is stored at a public address — anyone who has the link can view it, even without an account |
| Settings: interface language, the device identifier for notifications (push token) and the operating system type | Automatically, from the app | Skify |
| Ski requests: resort, dates, group name, description (up to 200 characters), gender preference for people joining, an indication that the group includes children, ski level | From you | Open requests — every signed-in user |
| Group members who are not users: name, age and ski level (section 8) | From the group creator | Same as the request |
| Joining groups: a message attached to a join request (up to 200 characters), reasons for declining, leaving or removal from a group | From you and from the group creator | The group creator, group members and the person who asked to join |
| Chat: messages (up to 2,000 characters), photos, a message preview (up to 100 characters) and read status; and previous versions of messages that were edited or deleted | From you | Only the participants in the conversation; previous versions: Skify only |
| Communities: posts (up to 500 characters), comments (up to 200 characters), likes and community membership | From you | Every signed-in user |
| Saved requests | From you | Only you |
| In-app notifications: title, body, the first name of the person who performed the action, community name | Automatically | The recipient |
| Reports: who reported, what was reported (type and identifier), reason and details (up to 500 characters). The report itself does not store a copy of the content. When a chat message is reported, Skify sees the message and, if it was edited or deleted, its previous versions (see 11.7) | From you | You and Skify |
| Blocks: the list of users you have blocked | From you | You and Skify |
| Requests to add a ski resort: resort name and country | From you | Skify |
| Support requests: text (up to 1,000 characters), up to 3 images, app version, operating system and interface language | From you; device details automatically | Skify |
| Technical event log: user identifier, the action performed, severity and technical data — mainly identifiers and codes, without names or content. Error records may include the technical error text | Automatically | You (your own records) and Skify |
| Error reports (Sentry): details of the error, and technical performance data from a sample of sessions. No user identifier, name or email | Automatically | Skify |
| On the device only: interface language and resorts you hid from the list | — | Stored on your device and not sent to us |
4. What we do not collect
- Location: no GPS and no location permission. The only place-related information is the country of residence you chose. The app uses the device’s time zone setting to order the list of ski resorts, and this value is not stored in your account.
- Phone number: we do not ask for a phone number.
- Contacts, microphone and cross-app tracking: we do not ask for access to them.
- Usage analytics, advertising and tracking: there are no such tools in the service.
5. Device permissions
| Permission | Why | How to revoke |
|---|---|---|
| Notifications | To send you notifications on your device | In your device settings, at any time |
| Photo library (iPhone) | To pick a photo for your profile, a chat or a support request | In your device settings |
| Camera (iPhone) | To take a profile photo only | In your device settings |
On Android, the app asks for the notifications permission only. The app does not ask for location, contacts or microphone permissions.
6. Required or voluntary — and what happens if you do not provide information
6.1 You are under no legal obligation to provide us with any information. Providing it is up to you.
6.2 What happens if you do not provide it:
- Without an email address (or a Google account), an age declaration and the other fields the app requires at registration, an account cannot be opened.
- Fields the app does not require can be left empty. Your profile will be less detailed, and finding suitable partners will be harder.
- Without the notifications permission, notifications will not reach your device. They will still appear inside the app.
- Without the photo library or camera permission, you will not be able to attach photos.
- Without approving the Terms of Use and this Privacy Policy, the service cannot be used.
7. Why we use information, and on what basis
We use information only for the purposes in this table. The legal basis is given under the GDPR, for users in the European Union.
| Purpose | Information | Legal basis |
|---|---|---|
| Opening an account, signing in and sending verification and password-reset codes | Account | Performance of our agreement with you |
| Showing profiles, posting requests, joining groups and finding partners | Profile, requests, joining, saved requests | Performance of the agreement |
| Chat and communities | Chat, communities | Performance of the agreement |
| In-app notifications | Notifications | Performance of the agreement |
| Push notifications to your device | Device identifier and notification content | Consent (the device notifications permission) |
| Showing group members who are not users | Name, age and ski level | Legitimate interest: so that people joining know who is in the group |
| Handling reports, enforcing the terms and user safety | Reports, the reported content, blocks | Legitimate interest: a safe service; and legal obligation where the law requires |
| Answering support requests | Support requests | Performance of the agreement |
| Adding ski resorts to the list | Requests to add a resort | Legitimate interest: improving the list |
| Finding and fixing errors, and securing the service | Event log, error reports | Legitimate interest: a working, secure service |
| Recording your approval of the terms | Version and time of approval | Legitimate interest and legal obligation: proof of consent |
| Complying with the law and responding to authorities | As required | Legal obligation |
Skify does not make automated decisions about you that have legal or similarly significant effects, and does not use information for advertising.
8. Information about people who are not users
8.1 A group creator can list existing group members who do not use Skify: name, age and ski level. These details are shown to anyone who can see the request.
8.2 Under the Terms of Use, whoever adds such details is responsible for obtaining those people’s consent, and details of a minor may be added only by the minor’s parent or guardian, or by someone who has their consent.
8.3 A person whose details were added this way may write to us and ask to access, correct or delete them, even without an account.
9. Who receives information
9.1 Other users see information as set out in the “Who can see it” column in section 3.
9.2 Service providers — Skify uses these providers to run the service:
| Provider | What it receives | Why | Where |
|---|---|---|---|
| Supabase | All information in the service: database, authentication, files and server functions | Storing and running the service | the European Union (Ireland) |
| Sentry | Error details and technical performance data, without user identifier, name or email | Finding and fixing errors | European Union (Germany) |
| Google — Firebase Cloud Messaging; and on iPhone, also Apple’s notification service | The device identifier for notifications, and the notification title and body. In a notification about a chat message: the sender’s first name and the first 100 characters of the message | Sending notifications to your device | Google and Apple servers (USA and other countries) |
| Brevo | Your email address, and a verification code or password-reset code; and internal emails to Skify about reports: the report details and the content of the reported message, including previous versions | Sending registration and password-reset emails, and internal notice of reports | A French company (European Union) |
| Google — Sign in with Google | Google knows that you signed in to Skify. Skify uses only the account identifier and the email address | Signing in to your account |
9.3 These providers process information on Skify’s behalf only, under their own terms and data protection commitments. Skify chooses providers that commit to a level of data protection no lower than the one described in this policy.
9.4 Skify itself: the operator has technical access to the information in the service. The operator uses this access only to run the service, provide support, handle reports, keep users safe and comply with the law.
9.5 Authorities: Skify will disclose information to authorities when the law requires it, or when there is a real danger to a person’s life or safety.
9.6 Transfer of the service: if the service is transferred to another operator, we will give notice in advance, and the new operator will be bound by this policy.
9.7 Skify does not sell information and does not pass it to advertisers.
10. Transfers of information outside Israel
10.1 Information is stored with Supabase in the European Union (Ireland), and is also passed to the other providers in section 9, some of which operate outside Israel and outside the European Union.
10.2 Transfers are made as the law permits, relying on the providers’ terms and data protection commitments.
10.3 For users in the European Union: the European Union recognizes Israel as providing an adequate level of data protection, so transferring information from the EU to Skify in Israel is permitted.
11. How long information is kept
11.1 While your account is active, information is kept so that the service can work.
11.2 Content you delete yourself is removed from the service and no longer shown. Exception: when you edit or delete a chat message, the previous version is kept by Skify (see 11.7).
11.3 Skify currently does not automatically delete inactive accounts.
11.4 What happens when you delete your account — see section 12.
11.5 Information that remains after account deletion without being linked to your user identifier (the event log, support requests and requests to add a resort) is kept for as long as it is needed for security, running the service and handling claims or disputes.
11.6 Error reports are kept by Sentry according to the retention period configured with that provider.
11.7 Previous versions of chat messages. When a message is edited or deleted, its previous version is kept separately. It is not shown to any user, including the sender. It is used only to handle reports and enforce the terms of use, so that an offensive message cannot be made to disappear after it has been reported. The previous version is kept for as long as the original message exists in the service, including after account deletion (see 12.3).
12. Deleting your account — what is deleted and what remains
12.1 How to delete: from within the app. If you do not have access to the app, you can request deletion at skify.app/en/delete-account or by email: [email protected]. Deletion from within the app is immediate, there is no waiting period, and it cannot be undone. A request by email is handled within 30 days, and we will confirm by email.
12.2 Deleted immediately:
- your profile details and profile photo;
- your account details: email, password and the link to your Google account (the Google connection is disconnected);
- messages you attached to join requests, and the reasons you wrote when leaving a group;
- your notifications, your saved requests and your device identifier for notifications;
- reports you filed.
Only an internal identifier and dates remain of the account, with no identifying detail, so that the remaining content can be shown as “Deleted user”.
12.3 Remains, shown as “Deleted user” without a name or photo:
- chat messages, posts, comments and likes — so that conversations and discussions remain understandable to the other participants;
- your membership in groups, marked as having left;
- details of group members who are not users that you added;
- reports other users filed about you.
12.4 Photos you sent in chats remain visible to the participants in the conversation after your account is deleted. If you want them deleted, write to us at [email protected], and Skify will delete them manually. The same applies to any other specific content that remains (a message, post or comment). We recommend sending the request before deleting your account, from the email address registered to the account. After deletion we no longer hold your email address, so we will ask for details that help us find the content (for example, which conversation and roughly when).
12.5 Images you attached to support requests are deleted manually by Skify within 30 days of account deletion. The text of support requests, requests to add a resort and the event log are kept without being linked to your user identifier.
12.6 Your name in notifications and system messages already delivered to other users remains with them.
12.7 Groups you created pass to their longest-standing member, or are closed if there is no one to pass them to.
12.8 There is currently no tool in the app for exporting your information. You can ask for a copy by email (section 13), and we recommend doing so before deleting your account.
13. Your rights
13.1 Under the Israeli Privacy Protection Law, and for users in the European Union also under the GDPR, you have these rights:
| Right | How |
|---|---|
| Access — to know what information is held about you and to receive a copy | Most information is shown to you in the app; for a full copy — by email |
| Correction — to correct wrong or outdated information | Edit your profile in the app, or by email |
| Erasure | Delete your account in the app, at skify.app/en/delete-account, or by email. Deleting specific content — by email |
| Portability — to receive the information you provided in a common format | There is currently no export tool in the app. Write to us, and we will send you the information in a file in a common format |
| Restriction and objection — to ask us to stop or limit using information, especially where the use is based on legitimate interest | By email |
| Withdrawing consent — to stop push notifications or access to photos and the camera | In your device settings. Withdrawal does not affect what was done before it |
13.2 Send requests to [email protected]. To make sure a request comes from you, we will ask you to send it from the email address registered to your account, or ask for details to verify it.
13.3 We will reply as soon as possible, and no later than the time the law sets (usually up to 30 days).
13.4 Complaint to an authority: if you believe your rights have been infringed, you may complain to the Israel Privacy Protection Authority. Users in the European Union may also complain to the data protection authority in the country where they live or work. We would appreciate it if you contacted us first, but you are not required to.
14. Information security
14.1 Permission rules on the server limit access to each item of information, so that only those listed in the “Who can see it” column in section 3 can see it. Communication between the app and the servers is encrypted.
14.2 Skify acts in accordance with the Israeli Privacy Protection (Data Security) Regulations. No method guarantees complete security. If a security incident occurs, Skify will act as the law requires, including giving notice where the law requires it.
15. Minors
15.1 The service is for people aged 18 and over. Skify does not knowingly collect information from anyone under 18. If an account turns out to belong to a minor, it will be deleted.
15.2 Marking a ski request as “includes children” does not include any details about the children. Details of a minor as a group member may be added only by the minor’s parent or guardian, or by someone who has their consent (section 8).
16. Changes to this policy
16.1 Skify may update this policy. Each new version will have a version number and a date.
16.2 A new version will be shown to you in the app, and will apply to you only after you approve it by tapping the approval button. The approval is recorded together with the version number and the time of approval. Until you approve, the previous version continues to apply.
17. Contact
Privacy questions and requests: [email protected]