Privacy Policy

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.

In the app we process personal data for three purposes: to verify that you hold your phone number or your Google or LinkedIn account, to show you which of your contacts will be where you are going and to show the contacts you are connected with where you are and will be, and to keep the app running and improving. If you opt in, we also send you our newsletter and connect the AI assistant you choose. Invitation-only sign-up, support chat, install attribution, the website and its analytics are described in their own sections. We may also process data where the law requires it. Every section says what we process and why. We never use your data for a purpose that is not stated in this policy.

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.

Invitation-Only Sign-Up

We can make sign-up invitation-only, and switch that on and off at any time, to manage how many people join: for example when our servers are near their limit, or to keep places in apreet limited. While sign-up is invitation-only, you can create an account only with an invitation of a kind we have switched on. There are two kinds, and we can switch each on and off: invitations from our admins and invitations from apreet users. Our admins invite one number at a time, in our admin tools; we get the number from you or from someone who knows you, though a typing mistake can put a stranger's number on the list. Our server looks the number up once with Vonage, to put it in the international format signup uses (see "SMS Verification"). An admin invitation sends you no message. An apreet user invites you from the app; the invitation goes from their phone, not from us, and carries their referral code (see "Referrals and Install Attribution"). When you sign up through an invitation that names an apreet user as its inviter, we record which user invited you. If a user's invitation is for your number, it is stored the same way as an admin invitation, without the note; how long it lasts differs, as described below. If our admins take over a user's open invitation, it becomes an admin invitation, which still names that user as its inviter until they delete their account. When an apreet user tries to invite a number that passes our first checks, our server looks it up with Vonage in the same way, with the inviter's country when the number has no country code, even if no invitation results, for example because Vonage cannot read the number or it already belongs to an apreet account. For each invitation for a number we store:

• a code computed from your number with a secret key, not the number itself; when someone signs up, we compute the same code from their number to see whether it was invited
• the last three digits of your number, so we can tell invitations apart
• for an admin invitation, a short note the admin writes to remember who the invitation is for, which may include your name
• who added it (an admin, an apreet user, or both, when our admins take over a user's open invitation), when, and, once it is used, when and by which account

Our admins see every invitation for a number; an apreet user sees at most the invitations they sent. An open invitation from our admins has no expiry date: it stays until it is used or until we revoke it. An unused invitation from an apreet user stops working after 30 days, and our daily clean-up then deletes it. Revoking deletes an invitation. Once you sign up with the invited number, the invitation is linked to your account, our admins see your account's name next to it, and it is deleted with your account. If the user who invited you deletes their account, we delete their unused user invitations and remove them from every other invitation and from your account. When an admin adds an invitation in the admin tools, the note also reaches our server's request log, which is limited by size rather than by date, so it stays there until newer entries replace it or we update the app on the server. It can also reach our error tracking, which runs on our own servers and is set to keep data for 30 days. When we revoke an invitation, that request log notes its internal id and which admin revoked it. For a revoked invitation, and for one deleted because its sender deleted their account, we keep a short security record (see Data Retention). Neither that log entry nor the security record holds your number or the note. Our encrypted backups can still hold a revoked or deleted invitation until they expire, within 30 days. If we ever restore a backup, the security record lets us delete a revoked invitation, or one deleted with its sender's account, again, and a user's invitation older than 30 days stops working again by its own date.

We use invitations to decide who can sign up while sign-up is invitation-only (see "Why We Do What We Do"). An open invitation for a number stays when we switch invitation-only off: if the invited number signs up then, the invitation is used up and linked to the account as above, so it does not stay open. If your number was invited and you do not want the invitation, write to us at the address in the "Questions?" section and we will revoke it.

Support

You can chat with us. We use Crisp as our chat service. Your name, email address, and chat history are stored on Crisp's systems. Crisp also receives device and IP information tied to your use of the chat feature. So that a reply can reach you as a push notification, the app also gives Crisp your device's push token. Crisp IM SAS, 2 Boulevard de Launay, 44100 Nantes, France.

Crisp's privacy policy: crisp.chat/en/privacy. Crisp's terms of use: crisp.chat/en/terms. Crisp publishes the list of its own sub-processors at crisp.chat/en/sub-processors. If you would rather not chat through Crisp, you can reach us at support [at] apreet [dot] com instead.

Tracking of App Crashes and Performance

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 and, on iOS, how the app performs. 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:

• IP address of the device
• device information, such as a RFC-4122 Universally Unique Identifier (UUID) to deduplicate crashes; the timestamp of the crash; the app's bundle identifier and version number; the device's OS name and version number; the device's model name, CPU architecture, amount of RAM and disk space; and language

Our iOS app also sends performance data to Crashlytics. About once a day, it sends a summary of how long the app takes to start and how much time it spends frozen. After a freeze, it sends roughly when it happened and how long it lasted. It also sends a stack trace, a technical description of which parts of the app were running during the freeze. This data carries the same device information and identifiers as a crash report. Like every Crashlytics report, it also carries the name of the screen the app was showing and your sign-up or sign-in status. Both are as they were when the report was recorded. For a freeze, that can be on a later launch.

Firebase Crashlytics retains crash stack traces, extracted minidump data, and associated identifiers (including Crashlytics Installation UUIDs and Firebase installation IDs) for 90 days before it starts to remove them from its live and backup systems. We expect the same to apply to the performance data above. 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 Android app uses 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. Our iOS app does not include Google Analytics for Firebase.

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. We set Firebase's advertising-identifier collection to off and remove the advertising-identifier permission from the app entirely. 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. An invitation link sent from our iPhone app is usually a Grovs link: whoever opens it in a browser, on any phone, first reaches Grovs' servers, which see their IP address and browser data, as any website does. On Android, an invitation link opens apreet.com (a link sent from an iPhone does so after Grovs), which passes the referral code in it on to Google Play; after the app is installed, it reads the code back from Google Play's install referrer and sends it to us when you sign up. 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:

• your device, device OS, OS version
• your apreet app version
• your current location (if you granted us permission)
• time of requests

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.

The uploaded content of each contact and calendar sync is kept in our server logs for 30 days, so our server can process the sync and our support can investigate a failed one. Each day we delete content older than 30 days; the record that a sync happened is kept.

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.

apreet never sends the notes on your contacts off your phone. Our iPhone app does not use them and sends nothing about them. Our Android app reads each note on your phone only to see whether the contact has one, and sends us just that yes or no, which we use to rank your contacts. Your notes stay private. We do not write to your address book; we do not change or create new contact information. We process your contact data internally. Apart from the names of contacts, the cities where you can meet them and your phone's id for a contact in your push notifications, which pass through Google and, on iPhone, Apple (see "How Do You Use Notifications?" below), 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).

apreet does not work without your contacts. Matching them to your destinations is the whole service, so without your address book there is nothing for apreet to show you. How much of it you sync is up to you, and both ways have their charm.

Sync your whole address book and apreet is at its best on the long tail: the people you have not seen in years and who are nowhere near the top of your mind, until apreet tells you that you will be in the same city next Tuesday. New contacts are included automatically the next time you open apreet. The more of your address book you sync, the more of those moments you get.

Or start small. On iOS 18 and later you can share only selected contacts, so only people you have approved can match with you, and someone new in your address book is not included until you add them. You can change the selection at any time in your iPhone's Settings, under apreet › Contacts. On Android the permission covers your whole address book. Whatever suits you.

If you are in someone's address book but do not use apreet

An apreet user may have synced your name, phone number, email and postal address with their labels, your job title and company, the id their phone gives your entry, and whether their entry for you has a birthday, a nickname or a photo and, if they use Android, a note, never the content of those. We use this to tell that user which city you live in, so they know when they will be near you; to rank the entry among their contacts; and, if you ever join apreet with that number and have them in your address book too, to connect the two of you. Our server processes it and support can read it when fixing a failed sync. If that user connects an AI assistant and approves the contacts or matches categories, the assistant can see your name, job title, company and distance on their behalf, never your phone number, email or address. Your name can also appear in a push notification to that user, which passes through Google's Firebase Cloud Messaging and, on iPhone, Apple's push service. We never contact you and never show you to anyone but us, the person who synced you, the assistant they chose and, in that person's push notifications, Google and, on iPhone, Apple. When they remove you from their phone, their next sync stops apreet from matching you; the entry is deleted when they delete their account. If you want your details removed sooner, write to us at the address in the "Questions?" section: we will remove the entry and ask the user who synced you to remove you from their phone, because otherwise their next sync brings it back. We or an apreet user may also invite your number; see "Invitation-Only Sign-Up".

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. apreet does not write to your calendar: it never changes or deletes your events and never saves a new one itself. When you add an office day, the app opens your phone's own calendar editor with a new entry filled in: its title, its times and, for a weekly office day, how it repeats, and usually that it shows you as free and, on iPhone, which calendar it goes in. You can change it there, and it is saved only if you save it. On iPhone, the calendar access you give apreet would also let it write to your calendar, and our Android app lists the permission to write to it; neither app uses that to write. We process your calendar data internally. Apart from the cities and dates of your trips and your office days, which can appear in push notifications to you and to your connections (see "How Do You Use Notifications?" below), 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).

Trade Fairs (Fair Matching)

When you mark one of your calendar entries as a trade fair or event, apreet records that you attend it: which entry it is, with its dates, times and location text, and, if your calendar has a flight leaving from near the fair during its days, that flight's time, which only ends your own row for the fair and is never shown to anyone. The first person to mark a fair also gives it its dates and venue, taken from their entry, and we look up the position of the venue on our own servers. You always see your own entry's title and location. Everyone else sees only a name an editor gave the fair, or a plain one such as "Event in Berlin", and the fair's city and country, never your calendar text.

Your connections who attend the same fair see you there: apreet users who have you in their address book and whom you have in yours. They see your name, which days of the fair you are there, whether you arrive early or leave late, whether you have left and, while the fair is on, whether you are near the venue and how many minutes ago your latest position was taken, if that was less than 72 hours ago. "Near the venue" means your latest position was within 3 km of it in the last three hours. They never see the position itself. You can hide that line for any fair, and you can stop attending a fair at any time. apreet also suggests a fair to a user who has a calendar entry in the fair's city on its days, when one of their connections attends it, and shows them which of their connections attend, before they join. So a connection can learn that you attend a fair in this way too, whether or not you hid your line.

While a fair you attend is on and the app is open, the app sends your position about every 10 minutes, unless you hid your line for that fair. On iPhone it asks for your precise position for this (see "How and Why Do You Use My Location Information?" below). As always, we keep only your latest position. A fair and every attendance of it are deleted 30 days after the fair ends. If you connect an AI assistant and grant it matches:read, it receives the names of your connections at the fairs you attend, the days they are there and whether they have left, never whether they were near the venue.

Offices (Office Matching)

Office Matching is off until you switch it on in the app's settings. Switching it on needs at least one saved office and, the first time, your consent; we store which version of the explanation you accepted and when. An office is a name and an address that you type. We look the address up on our own servers to find its position and time zone.

Once Office Matching is on, apreet reads your office days from your calendar: entries whose title says you will be in the office, such as "Office day", in any of 26 languages. Entries such as "Home office" or "Out of office" cancel one. To tell which of your offices an entry is at, we look up its location text on our own servers, and where we cannot tell, the app asks you. Adding an office day in the app opens your phone's own calendar editor (see "How and Why Do You Use My Calendar Data?" above).

A contact sees your office days only when each of you has the other in your address book and both of you have Office Matching on. They see that you plan to be in their office or nearby on a date, and when. They never see your office's name or address, the location of your calendar entry or your position. You can hide any office day.

To measure how much Office Matching is used, a position accurate to 2.5 km or better, or sent without an accuracy reading, that the app sends during the hours of one of your office days, within 3 km of that office, adds you to that date's count. Once the date is over everywhere, we keep only the totals and delete who was counted, together with that date's office days. Switching Office Matching off deletes your office days that have not ended and your answers about which office an entry is at; your offices stay until you remove them or delete your account. AI assistants you connect receive nothing from Office Matching.

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.

Our Android app only ever asks for your approximate position. Our iPhone app asks for an approximate position too, except while one of your trade fairs is on, around your flights and at airports. Then it asks for your precise position, until you leave the app. If precise location is off for apreet in your iPhone's settings, iOS asks you first; if you decline, the position stays approximate. We use it to tell whether you are at the airport or near a fair's venue (see "Trade Fairs" above). Like any position, we keep only the latest one, and other users never see it.

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 "Tracking of App Crashes and Performance" and "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; of new destinations added to your itinerary; and of a few other things about your account, such as the contacts planning to be in your office, a sign-in on another device, or an updated itinerary.

We send push notifications through Firebase Cloud Messaging, provided by Google LLC, 1600 Amphitheatre Parkway, Mountain View, California 94043, USA. Firebase gives the app a push token for your device, and the app sends that token to us: on iPhone once you allow notifications, on Android once you sign in. For each notification, our server sends Firebase the token, the text of the notification and a few details the app needs to open the right screen, whether or not your phone is allowed to show it. The text can name your contacts, a city, an office, dates, or the device your account was signed in on; the details can include the kind of notification, an id for a city, a contact or an office, dates, and the name and platform of that device. A notification about one of your connections can carry the city and dates of their trip, or the name of your own office where they plan to be. On iPhone, Firebase passes the notification to Apple's push service, which delivers it to your phone. Apple's privacy policy names the Apple company responsible in your region and says Apple transfers personal data out of the EEA under standard contractual clauses.

Firebase identifies the app on your phone by a Firebase installation ID. For Firebase Cloud Messaging, Google says it keeps that ID until we ask it to delete it, and then removes it from its live and backup systems within 180 days. We do not make that request today, including when you delete your account. Google's Firebase privacy page does not say how long it keeps the text of a notification. Firebase Cloud Messaging runs on Google's global infrastructure, so this data may be processed in any of Google's data centres, including in the U.S.; Google has certified that it adheres to the EU-U.S. Data Privacy Framework. See firebase.google.com/support/privacy and the Google Privacy Policy.

How Do You Use My Photos?

You may select and upload a profile picture from your photo library. Profile photos are stored in Cloudflare R2 object storage under the European Union jurisdiction, operated by Cloudflare, Inc. (see "Network and Hosting: Cloudflare"). They are served through our own server, never directly from the storage.

When you remove your photo, or delete your account, the image is deleted from our storage.

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.

Why We Do What We Do

Every piece of data we handle has one of four reasons behind it. We list them here so you can see which applies where.

• Because it is the service you asked for. Verifying you, building your itinerary, matching your synced contacts, showing you who you know at the trade fairs you mark, processing your syncs, and telling you about matches. Without these there is no apreet.
• Because you said yes. Your profile photo, your location, Office Matching, connecting an AI assistant, and our newsletter are optional. You can change your mind at any time: remove the photo, switch location off in your phone's settings, switch Office Matching off, disconnect the assistant, unsubscribe.
• Because we need it to keep apreet working and safe. Crash reports, performance data and usage statistics, the 30 days we keep sync content in our server logs, support chat, sign-in with Google or LinkedIn, this website's server logs, measuring how the website is used (see Website Analytics below), knowing which links bring people to apreet, the invitations that let us limit how many people join (when our servers are near their limit, or to keep places in apreet limited), and the records that let us repeat deletions, sign-outs and revocations after restoring a backup. We weigh each of these against your privacy and keep them as small as we can. If you object to any of them, write to us and we will look at your case.
• Because the law says so. Where we are required to keep or hand over data, we do, and only then.

Your contacts' details are a special case, because the people in your address book did not sign up. We hold their details because showing you where your own contacts are is what apreet is for. We keep only the fields listed under Contact Data, we never contact them, and anyone who finds themselves in an apreet user's address book can object or ask us to remove them; see "If you are in someone's address book but do not use apreet".

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:

• profile:read: your apreet profile.
• itinerary:read: your destinations and travel dates.
• matches:read: the contacts your paths cross with, on a trip and at your home base, with a relevance score for each, and your contacts at the trade fairs you attend, with the days they are there and whether they have left.
• contacts:read: your contacts, by name, job title, and company, each with a relevance score.
• geo:read: city and place lookups. This one returns places, not people.
• digest:read: your weekly brief, and the contacts matched to each upcoming stop, each with a relevance score, and your contacts at the trade fairs you attend.
• proximity:read: contacts matched to a place the assistant asks about, with the distance in kilometers between that place and each contact. The assistant chooses the radius, and each request returns up to 100 contacts.
• trip_search:read: contacts the assistant looks up by name among those matched to your upcoming stops, and which stops they overlap with.

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, or the short security records described under Data Retention.

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 encrypted backups, which expire within 30 days, and any data we are obliged to keep for administrative, legal, or security purposes. We also keep a short security record of each deleted account: its internal id, the random identifier we give each account for passkey sign-in, and the time of the deletion. It holds nothing else about you. If we ever have to restore a backup, it lets us delete the account again before apreet reopens. It is kept on our server and in Cloudflare R2 and deleted after about 35 days; if a backup we restore in that time, including in a test, still holds the account, we delete the account again and the 35 days start over. Sign-outs, removed or replaced passkeys, revoked access tokens and disconnected AI assistants are recorded the same way, for the same reason and for about 35 days: as a code derived from the credential or, for an assistant, the connection's id with your account's internal id. A revoked invitation, or one deleted with its sender's account, is recorded the same way, as its internal id and the time the invitation was created, with nothing about the person invited; an open invitation for a number is kept until it is used or revoked, or, while it is still a user's invitation, until it stops working after 30 days and our daily clean-up deletes it or its sender deletes their account (see "Invitation-Only Sign-Up"). Crash data in Crashlytics is retained for 90 days before Google starts to remove it, and we expect the same for the performance data (see above). Whether or not you delete your account, a trade fair and its attendances are deleted 30 days after the fair ends, and office days once their date is over everywhere (see "Trade Fairs" and "Offices").

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:

• Right to know what personal information we collect, use, and disclose.
• Right to delete personal information we have collected from you.
• Right to correct inaccurate personal information.
• Right to opt out of the sale or sharing of personal information. apreet does not sell or share personal information (see above).
• Right to limit the use and disclosure of sensitive personal information.
• Right to non-discrimination for exercising any of these rights.

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. The reasons listed under "Why We Do What We Do" are our legal bases: "the service you asked for" is performance of our contract with you (Art. 6(1)(b)); "you said yes" is your consent (Art. 6(1)(a)), which you can withdraw at any time as described there; "keeping apreet working and safe" is our legitimate interest (Art. 6(1)(f)), balanced against your rights, with the interests named there; and "the law says so" is a legal obligation (Art. 6(1)(c)). Your contacts' details are processed on our legitimate interest in showing you where your own contacts are, with the safeguards and the objection route described there and under "If you are in someone's address book but do not use apreet".

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 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, including Cloudflare, which carries every connection to apreet, 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:

• your device's browser type and version
• your device OS
• referrer URL
• your device's host name
• time of requests

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.

Network and Hosting: Cloudflare

Every connection to apreet, from the app and from this website, passes through the network of Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare terminates the encrypted connection at its edge, shields our servers from attacks, and forwards each request to us through a second encrypted tunnel. To do this it processes the connection data of every request: your IP address, the address requested, and the time. This website is served by Cloudflare, and your profile photo, the encrypted backups of our app's database and the security records described under "Data Retention" are stored in Cloudflare R2 under the European Union jurisdiction. Cloudflare has certified that it adheres to the EU-U.S. Data Privacy Framework; its privacy policy: cloudflare.com/privacypolicy.

Cloudflare also shows us aggregated statistics about these requests, such as the number of requests, visitors and countries. It builds them from the same connection data. We use them only to see how the service performs.

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). Its script sets no cookies and writes nothing to your device. It checks a setting in your browser, which lets you exclude your own visits, and whether the browser is automated. Neither is sent to our analytics server.

When you open a page, the script sends the address of that page and the page or site you came from to our analytics server, together with the technical data your browser sends with every request (browser, operating system, device type, IP address). If you scrolled or stayed for a few seconds, then when you leave the page or switch to another tab or window it also sends how far you scrolled and how long the page was visible and in focus. We also count a few actions, each with the page it happened on: clicks on download buttons (with a label for which button on the site it was), clicks on email links (with their kind: a support or legal contact, or a sign of interest), clicks on links to other sites (with the address of the link), clicks on header and footer navigation (with the label and the destination), and when the QR code is shown. The tool also counts clicks on links to downloadable files and submissions of forms on the site. On the download page (apreet.com/get, which get.apreet.com also reaches), the event for the redirect to the app store carries the store and the referral code from the link. The buttons on this website use the fixed code "web", and an invitation link carries its sender's code.

The tool derives your approximate location from the IP address and does not keep the IP address in its own records. From your IP address, your browser data and this website's domain, plus a value that is replaced every 24 hours, it forms an identifier. While that value lasts, and as long as those inputs stay the same, the tool therefore recognises the same browser and counts it as one visitor. Once the value is replaced, it can no longer recognise that browser; only a visit that is still going at that moment (one with activity in about the last 30 minutes) continues as the same visit. Nor can the tool recognise that browser on another website. The individual events (for example each page view, and the scroll depth and engaged time sent when you leave a page or switch away from it) and the session records are stored with this identifier, the page address (including a referral code in the link, if there is one), the referrer, the address, label or other detail sent with an event (as listed above), the location and the device data. They are shown as aggregated counts. The individual events and session records are deleted from the analytics server after 24 months. Encrypted backup copies of this data are stored at Cloudflare and kept for about 30 days, so a deleted record can remain in a backup for about 30 days longer. A backup copy also holds the earlier values that were replaced every 24 hours: those of the last days or weeks, and possibly older ones. The legal basis is our legitimate interest in understanding how the website is used (Art. 6(1)(f) GDPR). You can prevent the measurement by blocking the analytics script in your browser.

We self-host Plausible on our own infrastructure. Requests to the analytics server pass through Cloudflare (see "Network and Hosting: Cloudflare" above). Plausible's data policy: plausible.io/data-policy.

Links to Other Sites

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 November 6, 2026.