Privacy at Nexlet.

What this is

Nexlet is the private workspace an agent uses between a client’s brief and the moment that client books a villa. An agent builds a Selection of villas and shares it with one client by a private link; the client hearts the ones they like; the villa’s owner is asked on WhatsApp whether the dates are free. It is not a marketplace, not a public directory, and not a payment processor.

Two threads run through every paragraph below. First: we collect only what the product needs to keep an agent, an owner and a client on the same page about a stay. Second: every piece of data has a known address, a Supabase project in the EU (Ireland) for records and Cloudflare for photos, and you can ask us where it is at any time by emailing adrian@adriantroop.com.

What we collect and why

Six categories of data flow through Nexlet. We describe each in the same shape: the data itself, the reason we need it, and the shortest answer to “what would happen if you didn’t collect it?”

• •Account. Your phone number, your display name, an optional profile photo, and the role memberships your agency gives you (Agent, Owner, Client). The phone number is your only credential: we verify it with a six-digit code sent on WhatsApp, there is no password and no email address. Without it there is no account.
• •Properties and photos. The villas and chalets an agency or an owner adds: names, location, rates, availability, and photographs. Photos are stored on Cloudflare R2 and served from img.nexlet.io. When an agent imports a brochure PDF, its text is sent once to Anthropic’s API to extract the listing fields (name, bedrooms, rates); the vendor does not train on data sent through its API, and we keep only the extracted fields plus the photos. Without this there would be nothing to put in a Selection.
• •Selections and requests. The Selections an agent builds, who they were shared with, the villas a client hearts, the booking requests a client sends, and the yes/no answers owners give about availability. We store these so the three of you see the same state. Without them every Selection would forget itself after a refresh.
• •Contacts, only if you ask. If you tap “Find my contacts” in Settings, the phone numbers in your address book are sent to our server once, matched against existing Nexlet accounts, and discarded; the names never leave your phone and we do not keep your address book. Nothing is read until you tap, and you can revoke the permission in iOS Settings at any time. Without it you would type invitees’ numbers by hand.
• •WhatsApp messages. Sign-in codes, and the availability questions we send owners, travel through Twilio’s WhatsApp Business API. Twilio processes the destination number and the message text to deliver it. We record whether the code was verified and what the owner answered. Without it there is no sign-in and owners would be chased by phone.
• •Push tokens. The device token Apple issues to your iPhone so Nexlet can notify you that a client hearted a villa or an owner answered. It is relayed through Expo’s push service to Apple. We keep it while you are signed in on that phone and discard it when you sign out or delete your account. Without it the app would only refresh when you opened it.

That is the whole list. The iOS app carries no analytics SDK, no crash reporter and no advertising identifier.

Where your data lives

Seven places. We list them with the legal entity and the region so an Apple Privacy Nutrition Label reviewer (and you) can match this page to the declarations in App Store Connect.

• •Supabase (Postgres + Auth + Realtime, EU region, Ireland). The durable store of record for accounts, properties, Selections, requests and availability. Row-Level Security is enforced on every table; another agency cannot read yours.
• •Cloudflare R2 (object storage). Property photos, in the sizes the app displays. No personal data beyond what is visible in the photo itself.
• •Twilio (US-based, WhatsApp Business API). Delivers sign-in codes and owner availability questions, and receives the owner’s Yes/No reply.
• •Expo (US-based, push relay) and APNs (Apple-owned). We hand Expo a notification payload and your device token; Expo hands it to Apple; Apple delivers it.
• •Anthropic (US-based, API). Receives brochure text once per import to extract listing fields. Nothing about you, your clients or your owners is sent, only the brochure.
• •Vercel (US-based, web hosting). Serves nexlet.io, the private Selection pages and the photo-upload route. Vercel sees request metadata the way any web host does.
• •Resend (US-based, transactional email). Nexlet does not email agents, owners or clients today; the integration exists for the founder’s admin sign-in and for future account emails, which will always carry an unsubscribe link.

We do not use Google Analytics, Mixpanel, Amplitude, Segment, Hotjar, FullStory, Datadog, or any other third-party product analytics or session-recording vendor. The list above is the complete subprocessor list as of the Last-updated stamp at the top of this page.

Who can see your data inside Nexlet

Your agency sees its own data. Another agency cannot see yours. We enforce this with Postgres Row-Level Security on every table, keyed on the agency that owns each row.

Inside your agency, role memberships govern what each person sees. An agent sees the agency’s villas, clients and Selections. An owner sees their own villas, the availability they have published, and the dates they have been asked about, never a client’s identity. A client sees only the Selections an agent has sent to them, under the agency’s marketing name for each villa; the owner’s name and the villa’s real name never reach a client.

Adrian (the founder) has administrative access to the Supabase project for support and incident response, for example to release a villa claimed by the wrong owner or to restore a Selection archived in error. Administrative reads are not casual reads.

We do not share your data with other agencies, with marketing partners, or with any other customer of Nexlet.

What we don’t do

A negative list is sometimes the clearest privacy statement. We do not, and will not in v1, do any of the following:

• •Resell or rent your data to anyone. Ever.
• •Run third-party product analytics. No Google Analytics, no Mixpanel, no Amplitude, no Segment, no Hotjar, no FullStory.
• •Use advertising identifiers. No IDFA, no GAID, no cross-app tracking. The iOS app never shows the App Tracking Transparency prompt because it has nothing to request.
• •Build a shadow profile of anyone: not of you, not of your clients, not of villas or owners outside Nexlet.
• •Train AI models on your data. The one AI call we make, brochure extraction, goes to a vendor API that does not train on what it receives.
• •Keep your address book. Contact matching is a one-shot lookup; nothing from your contacts is stored.
• •Run a public agent directory or a public villa search. Nexlet is closed-network; Selections are shared via private links to specific people.
• •Operate a public Selection browse. Every /s/[slug] URL is keyed to a private slug shared one-to-one.
• •Make bookings or process payments. Humans transact off-platform; there is nothing to buy in the app.

Your choices

Three levers control your data inside Nexlet, all reachable from your iPhone:

• •Delete your account. Settings → Delete account, inside the app. Per Apple App Store Review Guideline 5.1.1(v), this path is in the iOS app itself, not buried in a web flow. Your profile, phone number and push tokens are removed immediately. Villas and Selections belong to the agency and stay with it; an owner’s claimed villas return to unclaimed; a client’s open booking requests are withdrawn.
• •Contacts. Never granted unless you tap “Find my contacts”, and revocable at any time in iOS Settings → Privacy → Contacts. Revoking changes nothing on our side, because nothing was kept.
• •Notifications. Switch them off in iOS Settings → Notifications → Nexlet. The app keeps working; it just stops tapping you on the shoulder.

Contacting us

Adrian replies personally to every privacy email. Response target is five business days; the long tail is when he’s in transit between Mykonos and Courchevel during the swing season.

Email adrian@adriantroop.com with “Privacy” in the subject line. For anything tied to your account, include your agency name and the rough date and time so we can find the right record.

Mailing address: c/o Adrian Torrente Tenreiro, Mykonos / Courchevel (founder home base, exact address available on request for a registered post recipient).

If we materially change this page, for example by adding a new subprocessor, we will bump the Last-updated stamp at the top and tell pilot agencies before the change goes live.