Download

Privacy Policy

What we do to protect your privacy. How we use your data and your rights regarding your data.

This Privacy Policy describes how apreet, Inc. (a Delaware corporation; "we," "us," or "apreet") collects, uses, and protects your personal data. We are committed to your right to privacy and we take your privacy seriously. We keep your personal data confidential and secure according to this Privacy Policy and applicable laws and regulations. We have strict internal privacy policies and procedures and strive to keep your personal data secure.

This Privacy Policy applies to the apreet software and services and does not apply to any other websites, software, products, or services that you may access from apreet, each of which may have privacy policies materially distinct from this one. Note that the transmission of data over the Internet may not always be secure. Email was not built for confidential information.

We use the following services to deliver you the best experience.

SMS Verification

To verify your mobile phone number we send a one-time SMS with a code through Vonage Holdings Corp., 23 Main Street, Holmdel, NJ 07733, USA. Their privacy policy: vonage.com/legal/privacy-policy.

Signing In with Google or LinkedIn

You can create an apreet account or sign in using your Google or LinkedIn account. If you choose to do so, the provider authenticates you and shares a limited set of profile information with us, typically your name, email address, profile photo, and a provider account identifier (and, for LinkedIn, basic professional details such as job title and company). We use this information to create and secure your account and to populate your profile. We do not post anything to your Google or LinkedIn account.

Google sign-in is provided by Google LLC, 1600 Amphitheatre Parkway, Mountain View, California 94043, USA (Google Privacy Policy). LinkedIn sign-in is provided by LinkedIn Corporation, 1000 W. Maude Avenue, Sunnyvale, CA 94085, USA (LinkedIn Privacy Policy). Using these providers is optional; you can also register with your phone number instead.

Support & User Engagement

You can chat with us. We use Intercom as a chat service. We also use Intercom to push emails and notifications to help you get the most out of apreet. Sign-up date, chats, chat histories, app usage, emails, and notifications are stored on Intercom systems. Intercom, Inc., 55 2nd Street, 4th Floor, San Francisco, California, 94105.

As part of our service agreement, Intercom collects publicly available contact and social information related to you (email address, gender, company, job title, photos, website URLs, social network handles, physical addresses) to enhance your user experience. Intercom's privacy practices: intercom.com/terms-and-policies#privacy. Intercom's terms of use: intercom.com/terms-and-policies#terms. If you want to opt out of having this information collected by or submitted to Intercom, please contact us.

Tracking of App Crashes

apreet uses an SDK from Firebase Crashlytics, provided by Google LLC, 1600 Amphitheatre Parkway, Mountain View, California 94043, USA. The SDK lets us see reports of bugs in our iOS and Android app. After a crash, the app sends information about the incident to Crashlytics: device type, OS version, certain phone information, time of the crash, the state of the application at the time of the crash, and stack traces. Crashlytics uses Installation UUIDs to measure how many users are impacted and minidump data to process NDK crashes. The following personal data is processed and transmitted to Firebase Crashlytics:

Firebase Crashlytics retains crash stack traces, extracted minidump data, and associated identifiers (including Crashlytics Installation UUIDs) for 90 days. Data transmitted to Firebase Crashlytics is neither stored nor transferred to other services or resources, nor associated with other data available to Google. Personal data processed by Firebase Crashlytics is transferred to Google servers in the U.S.

Full list of data processed by Firebase Crashlytics: firebase.google.com/support/privacy. Crashlytics' privacy is governed by the Google Privacy Policy.

App Analytics

Our iOS and Android apps use Google Analytics for Firebase, provided by Google LLC, 1600 Amphitheatre Parkway, Mountain View, California 94043, USA, to understand how the app is used in aggregate, for example which features are used, app version adoption, and retention. This SDK processes app usage events, a Firebase installation identifier, and device and OS information, and transmits them to Google servers in the U.S.

We use this only to improve the product. We do not display advertising in apreet, we do not use this data to build advertising profiles, and we have not enabled advertising-identifier collection on either platform. On Android we set Firebase's advertising-identifier collection to off and remove the advertising-identifier permission from the app entirely. On iOS we do not present an App Tracking Transparency prompt, so iOS would supply no usable advertising identifier to Firebase. As with any connection to a server, reaching Google's servers also reveals your device's IP address. Firebase Analytics' data handling is governed by the Google Privacy Policy; see also firebase.google.com/support/privacy.

Referrals and Install Attribution

Our iOS app uses the Grovs SDK to credit referrals and to measure how the app is used after it is installed, such as whether it gets opened and whether somebody comes back after a while away. It is active for every install on iOS, not only for people who arrived through an invitation, because establishing that an install did not come from a referral takes the same measurements as establishing that it did. Our Android app does not use it. Grovs publishes its privacy contact address as Blvd. 21 Decembrie 1989, 95-97, Cluj-Napoca, Romania, and its privacy policy at grovs.io/privacy.

The SDK sends the following to Grovs, at sdk.sqd.link: an identifier for vendor (IDFV), which Apple issues per vendor rather than per app, so it is shared across apps from the same vendor, differs from the identifier any other company sees, and changes once all of that vendor's apps are removed from the device; your device model, screen size, preferred language, time zone, and the web user agent string your device reports; and the app's version, build number, and bundle identifier. As with any connection to a server, reaching that address also reveals your device's IP address, which can indicate your approximate location.

It also sends events: opening the app, opening a link, viewing content, installing, reinstalling, returning after a period away, and time spent. Referral codes travel in both directions: when you share an invitation, the code in that link is sent, and when you open or install apreet through somebody else's invitation, the code in their link is sent too, which is what allows the referral to be credited.

All of the following describes the app as it is built today. The SDK does not receive your name, your email address, or your phone number. Our integration passes only the referral code, together with the technical data and the events listed above; the channel it uses could carry more, and we do not put more into it. The SDK does not use your device's advertising identifier (IDFA): we have written no advertising-identifier code in our iOS app, and because we do not present an App Tracking Transparency prompt, iOS would supply no usable advertising identifier in any case. We do not use any of this for advertising. Grovs describes its own handling of the data in its privacy policy, linked above.

Grovs names Hetzner (Germany and Finland), Cloudflare, and Stripe as its own suppliers. We have not independently confirmed where all processing happens, and some of those suppliers operate globally, so we do not claim that this data stays in the EEA.

Server Log Files: apreet App

We automatically collect server logs that your device sends to our servers when using our app:

We attribute this data to your account. We track server logs to better understand your usage and improve the service for you. We may analyze the server logs if we see irregular usage patterns or suspect illegal use.

How and Why Do You Use My Contact Data?

apreet processes your contacts (names, phone numbers, email addresses, addresses) periodically, both people already using apreet and other contacts. Where permitted by applicable law, you confirm that you are authorized (and have your contacts' permission) to share their information with us. apreet processes your contacts only to find your matches and the nearby cities where your paths may cross; we do not use them to build advertising profiles.

apreet determines if any of the phone numbers in your address book is already associated with an apreet user. If so, and if your mobile number is in that user's address book, we match you as friends and show both of you where your paths will cross in the next four weeks. For all other contacts, apreet processes the location information in the address book, i.e., the city. For any destination on your itinerary, apreet shows you contacts nearby.

We do not read or transfer the notes section of your contacts in your address book. Those are strictly private and we keep it that way. We do not write to your address book; we do not change or create new contact information. We process your contact data internally. We do not share your contact data with third parties, with one exception you control: if you connect an AI assistant yourself and grant it any of the permissions that return people (contacts:read, matches:read, digest:read, proximity:read, or trip_search:read), that assistant's provider receives the name, job title, and company of each contact the Agent Gateway returns, and, depending on the permission, a relevance score, a distance, or the stops that contact overlaps with. It does not receive their phone numbers, email addresses, or street addresses (see "AI Assistants You Choose to Connect" below).

How and Why Do You Use My Calendar Data?

apreet uses your calendar events to build your itinerary for the next four weeks. This is mainly based on the dates and location information of the calendar events. For flights, we determine the airport of departure and arrival based on the title/summary/subject and the location data.

We do not read or transfer data in the description or notes section of your calendar events. Those are strictly private and we keep it that way. We do not write to your calendar; we do not change or create new events. We process your calendar data internally. We do not share your calendar data with third parties, with one exception you control: if you connect an AI assistant yourself and grant it itinerary:read, digest:read, or trip_search:read, that assistant's provider receives the itinerary we derived from your calendar, such as destinations and dates. Under those permissions, that provider does not receive your calendar events themselves (see "AI Assistants You Choose to Connect" below).

How and Why Do You Use My Location Information?

We collect and use, with your permission, the location information from your device while you are using the app, when you choose to use location-related features, such as using your current location as a starting point for your itinerary. We try to match it to a nearby town or city and your contacts who have an address in your address book that is close by, and contacts using apreet currently or planning to be in the near future nearby. We may also use your location information to troubleshoot errors such as mistaken localization or matches.

apreet accesses your location only while the app is in use; it does not track your location in the background. You can turn off the app's access to location information in your device settings. If the app gets the starting point wrong, it feels "wrong", which is why we believe using the current location as a starting point of your itinerary is an important part of your user experience, and we recommend enabling location permission. We process your location data internally. We do not share the location we collect from your device with third parties, with the exceptions described in this section, one of which you control: if you connect an AI assistant yourself, geo:read lets it look up cities and places, and proximity:read additionally returns your contacts near a place the assistant asks about: their name, job title, and company, together with the distance from that place to each of them. The assistant chooses the radius, and each request returns up to 100 contacts, though an assistant can make more than one request. Neither of these sends your own device location. The location you use as a starting point for an itinerary reaches a provider through itinerary:read, digest:read, or trip_search:read, as part of the itinerary those permissions expose (see "AI Assistants You Choose to Connect" below). Separately from all of this, any server the app contacts sees your device's IP address, which can indicate your approximate location. That includes Google (see "App Analytics" above) and Grovs (see "Referrals and Install Attribution" above).

How Do You Use Notifications?

apreet notifies you, with your permission, of contacts you may meet three days before a trip; of friends and contacts joining apreet; and of new destinations added to your itinerary.

How Do You Use My Photos?

You may select and upload a profile picture from your photo library. Profile photos are stored on Amazon Web Services (AWS) infrastructure (Amazon Web Services, Inc.); see aws.amazon.com/privacy.

Who Has Access to My Data?

Your data is important to us. We strive to keep the data you provide secure, and we do not share or disclose this data to third parties unless otherwise stated in this Privacy Policy or required by legal obligations.

AI Assistants You Choose to Connect (Agent Gateway)

You can connect an AI assistant to your apreet data through apreet's Agent Gateway. You add apreet as a connector in the assistant, the assistant sends you to apreet's own consent screen, and you approve the permissions you want to grant. This is optional and off by default: no assistant reaches your data until you complete that approval yourself. You can disconnect an assistant at any time in the app, under More → API Keys & Devices. For a plain-language explanation of what an assistant can and cannot do, and where your data goes, see Agent Gateway security.

Who receives your data. Two assistants are confirmed to work today: Claude, from Anthropic (Anthropic's privacy policy), and ChatGPT, from OpenAI (OpenAI's privacy policy for Europe and for other regions). Their policies identify the legal entity responsible in your region. When you connect one of them, that company receives the apreet data covered by the permissions you approved, including, if you grant it, information about the people in your address book. The Agent Gateway is built on an open standard, so other assistants that support that standard may also be able to connect. We do not limit connection to a fixed list of companies, so we cannot tell you in advance every assistant that will work.

What you can grant. Here is what each permission discloses if you grant it. The consent screen does not offer all eight as independent choices: depending on what an assistant requests, some may combine into a single choice, and one may be included automatically rather than offered as a choice of its own, as the note below the list explains. You can decline the whole connection, or grant whatever combination the screen actually offers:

The consent screen does not treat these eight as eight separate checkboxes. profile:read is never grouped with anything. When an assistant requests both itinerary:read and geo:read, the two combine into a single choice, Itinerary & Location: you grant both together or grant neither, and neither appears as its own checkbox in that case. When an assistant requests all four of matches:read, contacts:read, proximity:read, and trip_search:read, they combine the same way into a second choice, Matches & Contacts. If an assistant requests only some of a group's permissions, those render as their own separate choices instead of a combined one. digest:read works differently: when an assistant requests it alongside both full combined choices above, it is not offered as a choice of its own. It is granted only if you grant both, and not granted if you decline either one. Only when an assistant requests digest:read without also requesting both full groups does it appear on the screen as its own independent choice.

Where a permission returns people from your address book, the assistant receives each person's name, job title, and company, and, depending on the permission, a relevance score, a distance, or the stops they overlap with. It does not receive their phone numbers, their email addresses, or their street addresses, and it never receives the notes on a contact. Note that a distance is calculated from the location we hold for a contact, so an assistant that asks about several places can narrow down roughly where a contact is, without ever being sent an address.

Every permission listed above grants read access only. None of them permits an assistant to change your profile, your itinerary, or your address book.

Some of what you may choose to share this way, your contacts and your matches, is about other people, not just you. As with sharing your address book with apreet itself (see "How and Why Do You Use My Contact Data?" above), it is your responsibility to have the permission of the people in your address book before you route their information to a third-party AI provider you selected. apreet is not a party to, and has no visibility into or control over, what your chosen AI provider does with the data once it receives it.

We recommend connecting only AI providers whose own privacy practices you have reviewed and are comfortable with, and, where the provider offers the option, disabling any setting that uses your data to train their models. You are responsible for confirming that your chosen AI provider's data practices comply with the law that applies to you, including the law protecting the people in your contacts. Once you authorize a connection, responsibility for that AI provider's handling of the data it received rests with you, not apreet.

Disconnecting an assistant stops future access only. It does not and cannot recall or delete data already sent to an AI provider during a prior session. By that point, it is on that provider's own systems, governed by that provider's own privacy policy and retention practices, not this one.

How is My Data Secured?

We take precautions to keep your data private. We use industry-standard measures to secure your personal data from accidental loss and unauthorized access, use, alteration, and disclosure. We restrict access to users' data to those employees who need access to perform their job functions, such as our customer service personnel and technical staff.

We use encryption to make sure your data is kept safe whenever it is transmitted between your mobile device and our servers. Note that we cannot guarantee the security of your account information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of your data at any time.

Request Your Data & Deletion of Account

You may, at any time, ask us what personal data we have stored about you. To request your personal data, contact us at support [at] apreet [dot] com.

You can delete your apreet account and all personal data associated with it: open the apreet app and tap Menu (top-left icon) → My Profile → Delete Account. Or request the deletion of your account and personal data via email.

The deletion of your account does not include any data we are obliged to keep for administrative, legal, or security purposes.

We Do Not Sell or Share Your Personal Information

apreet does not sell your personal information to third parties. We do not share your personal information for cross-context behavioral advertising. We do not use your personal data to build advertising profiles, and we do not allow third-party advertisers on the apreet app or this website.

Data Retention

We retain your personal data for as long as your account is active or as needed to provide the apreet services. After you delete your account, we make reasonable efforts to remove your data within 30 days, with the following exceptions: data retained in routine backups (which expire on their normal rotation), and any data we are obliged to keep for administrative, legal, or security purposes. Crashlytics data is retained for 90 days (see above).

California Privacy Rights (CCPA / CPRA)

If you are a California resident, you have specific rights under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), including:

To exercise any of these rights, email support [at] apreet [dot] com. You may designate an authorized agent to make a request on your behalf.

European & UK Privacy Rights (GDPR)

If you are in the European Economic Area (EEA), the United Kingdom, or Switzerland, the General Data Protection Regulation (and the UK GDPR) gives you certain rights, and we process your personal data on the following legal bases:

You have the right to access, correct, delete, restrict, or object to the processing of your personal data, the right to data portability, and the right to withdraw consent. To exercise these rights, email support [at] apreet [dot] com. You also have the right to lodge a complaint with your local data protection supervisory authority.

For data you directed us to send to an AI assistant through the Agent Gateway, we can stop sending more, and where you ask us to and it is possible to do so, we will pass your correction, erasure, or restriction request on to a provider you connected. We cannot reach into that provider's systems ourselves, so you may also need to contact them directly. The assistants you have connected are listed in the app, under More → API Keys & Devices.

Your personal data is processed on our own servers and on the systems of the service providers described in this policy. Some of these providers (such as Google, Intercom, and Mailchimp) are based in the United States, so your data may be transferred to and processed in the U.S. under their respective data-protection terms (see "International Users" below).

Separately from those providers, if you connect an AI assistant through the Agent Gateway, you direct us to send the data you approved to that assistant's provider. For your own personal data, your consent is the basis for that transfer. The data may also describe the people in your address book, who are not themselves party to your consent; you confirm that you have their permission before you route their information to a provider you selected (see "AI Assistants You Choose to Connect" above). Those providers may process your data outside the EEA. They are recipients you choose rather than service providers we appoint, so we have no data-protection agreement with them and no control over what they do with the data once they receive it. Because no such agreement is in place, your data may not have the same protection there that it has in the EEA, and you may have fewer ways to seek redress.

Children's Privacy

apreet is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact support [at] apreet [dot] com and we will take steps to delete it. The Terms of Service additionally require all users to be at least 16 years old.

International Users

apreet is operated by apreet, Inc. Your personal data is processed on our own servers and on the systems of the service providers described in this policy; some of those providers are based in the United States. If you are accessing apreet from another country, data-protection laws there may differ from those where your data is processed. By using apreet, you understand that your personal data will be processed as described in this Privacy Policy.

Newsletter Mailing List

As a recipient of our newsletter, you have provided us with your email address and information that allows us to verify you are the owner of this address and willing to receive the newsletter. Your email is used to keep you up to date about our activities.

We send emails through our partner Mailchimp, The Rocket Science Group, LLC, 675 Ponce de Leon Ave NE, Suite 5000, Atlanta, GA 30308, USA. See mailchimp.com/legal. Mailchimp is part of Intuit Inc.; see intuit.com/privacy/statement. You may unsubscribe at any time.

Server Log Files: apreet Website

We automatically collect server logs that your browser sends to our servers when visiting this site:

This data is not directly attributable to a person. We do not cross-reference this data with other data. We may analyze the server logs if we see irregular usage patterns or suspect illegal use.

Website Analytics: Plausible

We use Plausible Analytics to understand how the apreet website is used (for example: which pages are popular, where visitors come from). Plausible is a privacy-friendly, lightweight analytics tool that does not use cookies and does not collect personal data. No personal information is stored or shared with third parties for analytics.

We self-host Plausible on our own infrastructure. Plausible's data policy: plausible.io/data-policy.

Because Plausible does not use cookies, this site does not require a cookie banner.

Our website and app may link to third-party sites and profiles (for example, our founders' LinkedIn profiles or the App Store and Google Play). This website does not embed social media plugins, share buttons, or trackers, so simply visiting our pages does not send your data to those networks. If you follow a link to a third-party site, that site's own privacy policy applies, and we have no control over the data it collects.

Questions?

Email us at support [at] apreet [dot] com if you have any questions about this Privacy Policy.

Last updated August 9, 2026.