This policy covers PairMee on pairmee.com and app.pairmee.com. It works together with our Terms of service.
Note: This document is informational and is not an agreement. Accepting the terms of use does not constitute blanket consent to the processing of personal information.
1. Who we are and what this policy is for
1.1. PairMee is a technology platform that connects people travelling to the same event or in the same direction. The platform includes the website pairmee.com, the app at app.pairmee.com and the event pages within them (together: the "Platform"). The Platform is operated by Bar Ziv Neuman ("PairMee", "we" or "us").
1.2. This document explains what personal information we collect in connection with use of the Platform, for what purposes, who can see it, with whom we share it, how long it is kept and what options are available to you.
1.3. This policy is an informational document, not an agreement. It is here to explain what happens with your information. The terms of use are the contractual document between us, and they are separate from this policy.
1.4. Accepting the terms of use is not blanket consent to every processing operation described here. Where the law requires consent for a particular processing operation, we will ask for it separately and specifically, and explain why. See section 13.
1.5. "Personal information" in this policy has the meaning given to it in the Israeli Protection of Privacy Law, 5741-1981.
1.6. The Hebrew version of this policy is written in direct, plural address and is intended for all users alike.
1.7. Who is responsible for your information. Bar Ziv Neuman, Israel, whose postal address for mail is PairMee, 1000 Brickell Ave, Suite 715, PMB 438, Miami, FL 33131, United States and whose email address is bar@pairmee.com, is the controller of the database in which your personal information is held, within the meaning of the Protection of Privacy Law as amended by Amendment 13 (in force since 14 August 2025). The service providers listed in section 8 hold information on our behalf and under our instructions. Our privacy contact is set out in section 18.
1.8. Notice under section 11 of the law. The controller of the database is Bar Ziv Neuman, Israel, reachable by post at PairMee, 1000 Brickell Ave, Suite 715, PMB 438, Miami, FL 33131, United States and by email at bar@pairmee.com. You are not required by law to give us the information described in this policy. The consequence of not giving it is that some or all of the Platform cannot be provided to you. The purposes for which the information is collected are set out in section 4, the recipients in sections 5 to 9, and your rights of access and correction in section 15.
1.9. Registration and notification. PairMee is not a data broker, does not provide direct mailing services to others and is not a public body, so under Amendment 13 our database is not subject to registration. If our database ever holds data of special sensitivity about more than 100,000 people, we will notify the Privacy Protection Authority as the law requires. We are not currently at that scale.
2. Who and what this policy applies to
2.1. This policy applies to everyone who uses the Platform — whether or not they have opened an account.
2.2. You can view event pages and other open content on the Platform without opening an account and without signing in. An account is required only when you want to publish a ride, ask to join a ride, approve a join request or exchange messages with another user.
2.3. How much information we collect therefore depends on how you use the Platform: a visitor who only views an event page gives us far less than a registered user who publishes a ride.
2.4. The Platform is not intended for anyone under 18. Before your first meaningful action on the Platform you will be asked to declare that you are 18 or older. This is your own declaration. We do not verify age, we do not collect a date of birth and we do not check documents.
2.5. Children under 13. The Platform is not directed at children and we do not knowingly collect personal information from a child under 13. If we learn that we hold such information, we delete it. A parent or guardian who believes a child has given us information can write to the address in section 18, and we will act on the request promptly.
3. What information we collect
3.1. Information you give us
Account details. Signing in is done using your Google account or a one-time code sent to your email address. With a code, we receive the email address you entered and the name you give us. From Google we receive an account identifier, an email address, a name and a profile picture, where one exists. This is a sign-in to an account and not identity verification. We do not request and do not collect identity documents or other official documents for the purpose of verifying identity, and we do not run background checks.
Profile details. First name, profile picture, age, gender, and in addition fields you may fill in if you choose, such as interests, nationality and usage preferences. These fields are not mandatory, beyond what is needed to have an active profile.
A note on gender, nationality and location. Gender is used only for the women-only ride filter and for what other users see on your profile. Nationality is optional. The origin, destination and meeting point you enter describe a ride, not your whereabouts: we do not track your location continuously and we do not use location details to profile you. Under Israeli law some of these details may be treated as data of special sensitivity, and we apply the security duties that attach to such data. Under some United States state laws precise geolocation is sensitive personal information; we do not collect precise geolocation except for the one action you ask for, as set out in section 3.2.
Ride details. When you publish a ride or search for one, we collect the origin and destination, the meeting point and its location, the date and time window, the type of ride (shared taxi or private car), the number of seats, a women-only marking, luggage details, a flight number if you provided one, free-text notes you write, and recurrence details if you set up a repeating ride.
Join requests and matches. Requests you submitted or received, the message attached to a request, its approval or refusal, and the ride groups formed as a result.
Content you created. Messages you wrote in the chat between ride participants, and ratings and feedback you provided.
Enquiries and reports. Your approach to support (subject, message content and email address), a report you submitted about a ride, and blocks you applied.
Communication preferences. If you enabled push notifications, the technical registration details of the device with the notification service; and your preferences regarding email, quiet hours and consent to receive marketing messages.
3.2. Information collected while you use the Platform
Technical and usage information. IP address, browser type and operating system, usage identifiers, pages viewed, actions you performed on the Platform (for example searching, publishing a ride, sending a request, forming a match) and their timing.
Fault information. When an error occurs on the Platform, technical information about the fault is collected, including the error message, the address at which it occurred and browser and device data.
Location. We use the locations you enter (origin, destination, meeting point). If you asked to use device location, we use it for that action only, and you can refuse in your device settings.
Cookies and similar technologies. See section 10.
3.3. Forms on pairmee.com
Contact and help forms. If you write to us through the contact or help form, we receive the subject, your message and the email address you give (or the one on your account). The message is delivered to our mailbox by our email provider.
Careers applications. If you apply for a role on the careers pages, we receive your name, your email address, the role you chose, a link you may add (for example a LinkedIn profile) and the text you write about yourself. We do not ask for a CV file, an identity number or a date of birth. The application is delivered to our mailbox by our email provider and is used to consider you for the role and, if you agree, for similar roles.
Waitlist and partner enquiries. If you join a waitlist or ask about an event partnership, we receive the details you enter on that form.
3.4. What we do not collect
We do not collect identity numbers, dates of birth, identity documents or payment details. PairMee does not process payments for rides — the financial arrangement is made between users themselves, outside the Platform, and we do not see it.
4. How we use the information
We use personal information for the following purposes:
- to operate the Platform, open and manage your account and let you sign in to it;
- to show relevant rides and produce matches between users based on route, timing and preferences;
- to enable join requests, their approval, and communication between users who have matched;
- to operate the women-only ride filter, based on the gender information you provided;
- to send you operational messages related to your use — for example a join request received, an approval, a ride update or a reminder — by email or push notification, according to your preferences;
- to send you marketing messages about PairMee only if you opted in to receive them, with the option to unsubscribe in every message;
- to keep a record of the legal acknowledgments you made on the Platform, as set out in section 13;
- to handle support enquiries, reports and blocks, and to protect users' safety and the integrity of the Platform;
- to prevent misuse, fraud or use contrary to the terms of use or the law, and to enforce them;
- to understand how the Platform is used and to improve it, using analytics and usage-analysis tools;
- to identify and fix technical faults;
- to comply with any law and with the requirements of a competent authority.
- to consider a careers application you sent us, and to answer an enquiry you made through a form on the website.
Aggregate information, or information that does not identify a particular person, may also be used by us for measurement, research and product improvement.
We do not use personal information for automated decisions that have a legal or similarly significant effect on you, and we do not use it to profile you for advertising.
5. What other users can see
This is the most important part of the policy, which is why it is set out in detail. Exposure on the Platform is built up in stages.
5.1. A visitor who is not signed in
A visitor who is not signed in sees published rides — including the area of origin and destination, the date and time, the type of ride and the number of seats available.
- Locations are shown at area or city level, not as an exact address. An address with a house number is automatically shortened before it is displayed.
- A visitor who is not signed in does not see the names, profile pictures, age, gender, nationality, interests or ratings of the users who published the rides.
- A visitor who is not signed in does not see the list of users looking for a ride to an event.
- An event page may display aggregate figures about the level of activity for that event.
5.2. A signed-in user
A signed-in user additionally sees the profile of the person who published the ride: name, profile picture, age, gender, nationality, interests, rating and number of completed rides, to the extent you provided those details.
5.3. The ride creator and the person requesting
- When you submit a join request, the ride creator sees your profile and the message you attached to the request.
- The ride creator is the one who decides whether to approve the request.
5.4. After approval — the ride participants
Once a request has been approved and a ride group has formed, the members of the group see one another and the coordination details for that ride, including the exact meeting point. The exact meeting point is not displayed before this stage.
5.5. Chat
Chat messages are shown to the members of that ride group only. The messages are stored by us.
5.6. Ratings
A rating and the number of completed rides are shown to signed-in users as part of the profile.
5.7. What we do not show other users
Your email address is not shown to other users on the Platform. Your support enquiries, the reports you submitted and the blocks you applied are likewise not shown to other users.
5.8. What you choose to share yourself
If you choose to give another user further details — such as a telephone number or an address — in the chat or outside the Platform, you do so at your own risk. The Platform does not require it.
6. Event pages and event organizers
6.1. An event organizer may distribute a link to the event page among the event's audience. Anyone entering through the link uses the Platform directly with us.
6.2. In the ordinary model, the event organizer does not give us their list of attendees or their ticket-buyer database.
6.3. An event organizer may receive from us aggregate information only about the level of activity on their event page — for example the volume of visits to the page, the volume of searches, the number of rides published, the volume of join requests and the number of matches.
6.4. An event organizer does not receive from us names, email addresses, telephone numbers, chat messages, profiles or ride records of any particular user.
6.5. We are aware that at a small event an aggregate figure could in certain circumstances point to a particular person. We avoid presenting figures at a level of detail that would allow this, and treat such a figure as personal information for all purposes.
6.6. The scope of information an organizer receives in a particular pilot may also be governed by an agreement between us and that organizer.
7. Registering for official event transport
7.1. At some events an option is shown to register or express interest in official transport provided by the event organizer. This is a separate path, and it differs from ordinary matching between users.
7.2. This path does not require an account and does not require signing in. It can be completed without a Platform account.
7.3. On such a form we collect a name and an email address only, together with the identity of the transport service you registered for. The information is collected in order to register you for that service and to update you about it.
7.4. The information is stored by us. The event organizer receives the number of registrants for each service, and not the registrants' names or contact details, unless otherwise agreed with you or with the organizer in advance and expressly.
7.5. Such a registration does not create a Platform account and does not include matching between users.
9. Free-text processing by an external service
9.1. In search on the Platform you can write a free sentence (for example "looking for a ride to Tel Aviv on Thursday evening"). In order to understand the sentence and convert it into search fields — origin, destination, date and time — the text you wrote is sent for processing by an external provider, Anthropic.
9.2. What is sent: only the text you typed, up to 500 characters, together with a fixed technical instruction that includes the current date and time and the time zone.
9.3. What is not sent: we do not send your name, your email address, your user identifier, your profile details or your ride history along with the text.
9.4. What comes back: a data structure only — the breakdown of the sentence into fields. The search results themselves are computed by us, not by the provider.
9.5. If you would prefer your text not to be processed in this way, you can enter the ride details directly into the dedicated fields on the ride publication form, without using free-text search.
9.6. We use the provider under its commercial terms for developers. Under those terms, as we understand them at the date of this version, the provider does not use the text to train its models, and may keep it for a limited period for the purpose of detecting misuse of its service. We restate the provider's terms here as we understand them; the binding text is the provider's own, and we do not give an undertaking on its behalf.
11. Is information transferred outside Israel?
11.1. Yes. The service providers listed in section 8.3 are for the most part international providers, and information may be processed and stored on servers outside Israel, including in the United States and in the European Union.
11.2. From the technical configuration available to us, our analytics service operates against servers in the United States, and our fault-monitoring service operates against servers in the European Union. For the other providers we have stated in section 8.3 where data may be processed, based on the provider's published information.
11.3. The basis for the transfer. Under the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 5761-2001, we transfer information to a provider outside Israel only where the provider has undertaken in writing towards us to protect the information under conditions that are no less protective than those that apply to it in Israel, or where the destination is a country whose law offers a level of protection recognised for this purpose, including the European Union. Each provider in section 8.3 has given such an undertaking in its data processing terms.
11.4. We do not make a claim here about the storage location of a provider beyond what is stated in section 8.3, or about certification schemes, unless these have been examined and verified.
12. Information security
12.1. We take reasonable technical and organisational measures to protect the information, in accordance with the Protection of Privacy (Data Security) Regulations, 5777-2017, including encryption of traffic between the browser and the server, permission management at the database level so that each user can access only the information they are entitled to see, limiting internal access to information to the people who need it for their role, and a record of the consent and notice events described in section 13.
12.2. We do not claim compliance with any standard or certification, and we do not operate a continuously staffed security desk.
12.3. No system is entirely secure. We cannot undertake that a security incident will not occur, and we work to reduce the risk and to handle an incident if one occurs.
12.4. If a security incident happens. If we learn of a security incident that has affected, or is likely to have affected, your personal information, we will: assess it without undue delay; contain it; notify the Privacy Protection Authority where the Data Security Regulations require it, and within the time they set; notify you by email, or by a notice on the Platform where email is not possible, where the Authority directs us to, where the law of the place where you live requires it, or where we judge that the incident creates a real risk to you; and tell you what happened, which information was involved, what we have done and what you can do. For a user in a state of the United States with a breach notification law, we will notify within the time that law sets.
12.5. Keep your sign-in credentials secure, and do not let others use your account. If you suspect that your account has been accessed by someone else, write to us at the address in section 18.
13. Acknowledgments and records on the Platform
13.1. While you use the Platform we keep a record of the confirmations you made. These are separate actions, and they are not to be treated as one blanket consent:
- Acceptance of the terms of use — an active step you take before your first meaningful action, together with the version number of the terms shown;
- Confirmation that you have read the safety guidelines — a separate tick of its own, alongside the version number shown;
- A declaration that you are 18 or older — your declaration, not age verification by us;
- An acknowledgment concerning private car rides — before you first take part in such a ride.
13.2. For each of these records we keep the user identifier, the type of confirmation, the version of the document shown and the time of confirmation.
13.3. Separately from these, we also record the fact that a notice or warning was displayed on the Platform. Such a record shows that the notice was displayed, not that you confirmed anything. We are careful to keep the two apart.
13.4. These records are kept as evidence of what was shown and what was confirmed. They are not replaced and are not deleted at our initiative.
14. How long we keep information
14.1. As a rule, we keep information for as long as the account is active and for as long as it is needed for the purposes for which it was collected, or for the period required by law. This section sets out the periods by category.
14.2. Retention periods
- Account and profile details. For as long as the account is open. Deleted, or anonymised where a record must be kept, within 30 days after the account is closed or deletion is requested, except as set out below.
- Rides, join requests and ride groups. For as long as the account is open, so that your ride history and rating are available to you and to the users you travelled with. On account closure your rides are removed from display and the records are deleted or anonymised within 30 days.
- Chat messages. For as long as the ride group exists and the account is open. Deleted or anonymised within 30 days after the account is closed. A message that is the subject of a report may be kept for as long as the report is handled.
- Ratings and feedback. A rating you gave stays with the rated user's profile after your account is closed, without your name. A rating you received is deleted with your account.
- Reports, blocks and support enquiries. Kept for up to three years after they are closed, so that we can handle repeated conduct and defend claims.
- Consent and notice records (section 13). Kept for seven years after the account is closed, so that we can show what was displayed and what was confirmed.
- Reminder log. Deleted automatically after 30 days.
- Analytics events. Kept by our analytics provider for up to twelve months, then deleted or aggregated.
- Error and fault records. Kept by our monitoring provider for up to 90 days.
- Contact form messages. Kept in our mailbox for up to two years after the enquiry is closed.
- Careers applications. Kept for up to twelve months after the role is filled or closed, then deleted, unless you ask us to delete them earlier or agree to be considered for future roles.
- Official transport registrations (section 7). Kept until 90 days after the event, then deleted.
- Backups. Deleted information may remain in encrypted backups for up to 30 days after deletion, and is not restored from them except to recover from a failure.
14.3. Deletion and account closure. There is currently no delete-account button on the Platform. You can write to us at the address in section 18 to close your account and delete your information, and we will act on the request within the time set out in section 15 and in accordance with the law. We will keep only what this section or the law requires us to keep.
14.4. Where a legal proceeding, a report or a legal obligation requires it, we may keep specific information for longer than the period above, limited to what is needed for that purpose.
15. Your rights and options
15.1. Access. You are entitled to review the personal information about you that we hold. Some of it is shown to you directly in your profile and on your ride screens.
15.2. Correction. If you find that the information is not correct, complete or up to date, you are entitled to ask to have it corrected. Some details can be updated by you directly on the profile screen.
15.3. Deletion and account closure. You are entitled to approach us with a request to delete the information or close the account, as set out in section 14.3.
15.4. Communication preferences. You can change your notification and email preferences at any time, including consent to receive marketing messages, and you can unsubscribe from push notifications in your device settings.
15.5. Search without free-text processing. As set out in section 9.5.
15.6. Blocking and reporting. You are entitled to block another user and to report problematic conduct to us.
15.7. To exercise any of these options, or for any question about your personal information, you can contact us at the address in section 18. We will respond to the enquiry and act in accordance with the law.
15.8. How quickly we respond. We will confirm receipt of a request within ten days and act on it within 30 days. Where a request is complex or there are many, we may extend by up to a further 30 days, and we will tell you why before the first period ends. Under the Israeli law the period for an access request is 30 days; under the United States state laws it is 45 days extendable once by 45 days; we apply the shorter period where we can.
15.9. Verification. Before acting on a request we may need to verify that it comes from you, usually by asking you to write from the email address on your account or to sign in. We will not ask for an identity document. An agent authorised by you may make a request on your behalf if they can show that authorisation.
15.10. No penalty. We do not discriminate against you for exercising any of these rights: we do not deny you the Platform, degrade it or treat you differently because you asked.
15.11. Complaints. If you are not satisfied with our answer you can write to us again and we will have a second look. You may also complain to the Privacy Protection Authority in Israel (gov.il/privacy), or, if you live outside Israel, to the data protection or consumer protection authority where you live.
16. Changes to this policy
16.1. This policy may be updated, including following a change in the Platform, in the service providers or in the law.
16.2. The updated text will be published on the Platform, with the update date at the top.
16.3. For a material change in how we collect or use personal information, we will bring it to your attention by a reasonable means, and will not rely on a silent update to the document.
17. Users in the United States
17.1. Where we stand under the state privacy laws. PairMee is operated from Israel for rides in Israel. We have no revenue from users, we do not sell or share personal information, and the number of United States residents whose information we hold is far below the thresholds at which the California Consumer Privacy Act and the comprehensive privacy laws of the other states apply. We therefore do not believe those laws apply to us today. We nonetheless give every user in the United States the rights in this section, so that your rights do not depend on that threshold.
17.2. Categories of personal information. In the terms those laws use, over the preceding twelve months we have collected the following categories: identifiers (name, email address, account identifier, IP address); personal characteristics (age, gender, nationality where you gave it); internet and network activity (usage events, pages viewed, browser and device data); approximate location, in the form of the places you enter for a ride; the content of your messages on the Platform; and inferences limited to your ride preferences. The sources are you, your device and, if you use it, Google sign-in (section 3). The purposes are in section 4. The categories of recipients are other users (section 5), event organizers in aggregate only (section 6), and the service providers in section 8.3. Retention is in section 14.
17.3. Sensitive personal information. Of the categories the state laws treat as sensitive, we collect only what you volunteer in your profile (gender and, if you choose, nationality) and the places you enter for a ride. We use them only to provide the Platform and we do not use them to infer characteristics about you. You may limit our use of them by leaving the optional fields empty.
17.4. Do Not Sell or Share. We do not sell personal information and we do not share it for cross-context behavioural advertising, and we have not done so in the preceding twelve months. We therefore do not provide a "Do Not Sell or Share My Personal Information" link. We honour Global Privacy Control signals as set out in section 10.7. We have no actual knowledge that we sell or share the personal information of anyone under 16.
17.5. Your rights. You have the right to know what personal information we collect, use, disclose and for what purposes; to access it and receive a copy in a portable form; to correct it; to delete it; to opt out of sale, sharing and targeted advertising (none of which we do); to limit the use of sensitive personal information; and not to be discriminated against for exercising these rights. Section 15 explains how to exercise them, how we verify a request, how long we take and how an authorised agent may act for you.
17.6. Appeal. If we decline a request, we will tell you why. You may appeal by writing to the address in section 18 with the subject line "Privacy appeal", and we will answer within 45 days. If we deny the appeal, we will tell you how to contact the Attorney General of your state.
17.7. California: Shine the Light. Under California Civil Code section 1798.83, a California resident may ask a business whether it disclosed personal information to third parties for their direct marketing purposes. We do not, and have not, so there is nothing to disclose.
17.8. Nevada. We do not sell covered information as defined in Nevada law.
17.9. Children. See section 2.5. We do not knowingly collect personal information from anyone under 13, and we do not sell the personal information of anyone under 16.
17.10. Where your information goes. Your information is processed in Israel and by the providers listed in section 8.3, some of which are in the United States and the European Union. Israeli privacy law applies to it in our hands.
18. How to contact us
18.1. For questions about this policy, to exercise rights, to report a security concern, or for any matter concerning your personal information, write to our privacy contact by email, or by post to the address in section 18.2:
bar@pairmee.com
18.2. Privacy contact. Bar Ziv Neuman, the operator of the Platform, is the person responsible for privacy at PairMee and answers at the email address above or by post at PairMee, 1000 Brickell Ave, Suite 715, PMB 438, Miami, FL 33131, United States. Under Amendment 13 a statutory privacy protection officer is required for public bodies, data brokers, and organisations whose core activity is systematic monitoring or large-scale processing of data of special sensitivity. PairMee does not meet those criteria at its current scale and has not appointed a statutory officer. We will appoint one, and publish the contact details, if and when the law requires it.
18.3. Please put the subject of your request in the subject line (for example "Access request", "Deletion request", "Privacy appeal" or "Security concern"), and write from the email address on your account where you have one.