Key

Privacy Policy

Last updated 2 November 2026. This policy is in effect, and any material change is announced by email, as the Changes section describes.

Key (operated by White Noise in a Snow Storm, LLC, “Key”, “we”) is a marketplace connecting travelers with vetted local experts for video calls at key.new. This policy explains what we collect, why, and what your choices are. White Noise in a Snow Storm, LLC is a Delaware limited liability company and is the controller of the personal data described in this policy.

What we collect

Account data: your name, email address, and timezone. Experts additionally provide profile content (photos, videos, bios, pricing) that is published publicly by design.

Sign-in security: for each browser you sign in from, its name as your browser reports it and when it was first and last used, so we can tell you about a sign-in from one you haven’t used before; kept until you delete your account. That email names the browser and the rough area your connection comes from; the area is not stored.

Bookings and the digital desk: call times, the notes, links, places, and messages you share on a booking’s shared desk. Desk content is visible to both participants of that booking.

Call recordings and transcripts: calls on Key are recorded and transcribed so both participants can replay them and keep the list of places discussed, this is a core feature, signalled by the recording indicator in the call. If you don’t want a call recorded, don’t take the call and contact us instead. By joining a call you consent to being recorded; recordings and transcripts are used under the license described in the Terms of Service.

Payments: handled by Stripe. Your card number never touches our servers; we store only booking amounts, refund state, and Stripe’s references. Experts’ bank and identity details for payouts are collected by Stripe directly, we never see them.

Post-call check-ins and surveys: after a call we may ask how it went. Your answer can affect whether the expert’s payout proceeds or a support ticket is opened, and we keep it with the booking. Optionally you can tell us your trip date and agree to a single follow-up email asking how the trip went; we use that for nothing else.

Expert applications: if you apply to become an expert, we keep your application (name, email, links, and what you wrote), including applications we decline, so we can reach out when opportunities open up, as our reply says. Ask us to delete your application at any time and we will.

Support: messages you send us and issue reports you file stay attached to the booking they concern until resolved and for our records.

Experts we approach: if we contact you about joining Key as an expert, we keep your name, your contact details and the public professional information that led us to you, where we found it, and our correspondence. Tell us you don’t want to hear from us and we’ll stop, keeping only your email address so we don’t contact you again.

Usage: two kinds of analytics, neither of which stores anything on your device. Vercel Analytics counts page visits without identifying you. PostHog records how Key is used: the pages you open, the links and buttons you click, where on a page the pointer moves and how far you scroll (as positions on the page, for heatmaps), and steps such as signing up, applying as an expert, or booking a call. With each of these it receives, where known, the country you are visiting from, which our hosting provider works out from your connection; PostHog never receives your IP address. When you are signed in, PostHog links that activity to your Key account ID and whether you are a client or an expert, never to your name or email address. PostHog may also keep a recording of how a page was used, with all text, images, and everything you type hidden, and it never records a page reached through a private link, such as a sign-in link, an invitation, or a shared list. If you arrived via a marketing link, we also keep the campaign parameters on that link. We use all of this only to understand and improve Key, and we do not run advertising cookies or cross-site tracking.

Why we’re allowed to use your data

Data protection law in the EU, the UK and elsewhere asks us to name the legal basis for each use. To provide Key under our Terms (your account and sign-in, bookings, calls, the shared desk, payments, payouts, support, and expert profiles): it is necessary for our contract with you, or for steps you ask us to take before one, such as reviewing an expert application. Call recording and transcription: your consent, given when you join a call, as described above. Analytics, search, aggregated insights, sign-up attribution, security monitoring, payout checks and fraud prevention, keeping declined expert applications, and approaching experts: our legitimate interests in running, improving and protecting Key, balanced against yours, which is why each is limited as this policy describes; you can object to any of them by writing to us. Bookkeeping, tax records and answering legal requests: our legal obligations. The single follow-up email about your trip: your consent, given by ticking the box after a call, which you can withdraw at any time by writing to us.

Product analytics and aggregated insights

We analyze activity on Key in aggregate, de-identified form, meaning we remove or generalize the details that could reasonably be used to re-identify a person and do not attempt to reverse that process, to understand and improve the product, to understand travel market trends and behavior, and to build features and insights from it, for example, lists of the places experts recommend most. Where such a feature shows which expert recommended a place, that attribution is part of the expert’s public profile by design. Clients are never identified in these features or analyses.

Cookies

Only strictly necessary ones: keeping you signed in; recognising a browser you have signed in from before, so we can email you when your account is signed in from a new one (set on the sign-in pages or once you’re signed in, kept up to 400 days after you last sign in on that browser); and a short-lived one while an expert connects a calendar. Nothing for marketing or tracking, and our analytics (see “Usage” above) store nothing on your device, that’s why there’s no cookie banner. If you arrive via a marketing link, we hold the campaign name in memory only while you’re on the site and save it if you sign up.

Google does not run as a script on our public, signed-out pages. The map on a public shared-list page is a static image our own server generates and serves from our own domain; your browser never contacts Google to display it, and clicking it opens Google Maps in a new browser tab, an ordinary outbound link you choose to follow. Place photos on those pages are resolved on our server and rendered as plain images requested from Google’s image CDN, an image request rather than a script. The interactive map, where you can search and pin places during a call, loads only for signed-in users, or when you ask for it: the call room demo in our expert guide shows a picture of a map until you start the demo, which loads the live one. We run a nightly automated check of our public pages as a logged-out visitor and are alerted if a third-party script ever appears there.

Who processes data for us

Supabase (database, authentication, file storage), Vercel (hosting and cookieless analytics), PostHog (product analytics, hosted in the EU), Stripe (payments and expert payouts), Daily.co (video calls, recording, and carrying call audio to Deepgram for transcription), Deepgram (call transcription, under Key’s own data processing agreement with Deepgram; every request tells Deepgram not to keep the audio or transcript and not to use either to train its models, so it keeps only request logs and metadata, for up to 90 days, for security, billing and running its service), Resend (email), and Google (the static map image and place photos on our public pages, and the interactive map available to signed-in users during a call, see “Cookies” above for how each is served), Amazon Web Services (storage of the original call recordings and our encrypted backups, in Stockholm), GitHub (our code, and the automated jobs that turn call recordings into replays), OpenAI through Vercel’s AI gateway (turning search text, expert profiles and place names into search vectors, so search can match by meaning), Google Workspace (our own email), Attio (our list of experts we approach), AssemblyAI (only while someone in a call turns on translation: it hears the other person’s voice to write down their words, on its EU servers, and doesn’t use them to train its models), and Anthropic (the AI tools we use to run Key, which can read account and booking data when we handle support and operations, and, while translation is on in a call, translating what’s said into the language picked). Each receives only what its function needs and acts on our instructions. We never sell personal data, and we don’t share, transfer, or disclose it to anyone beyond these processors and the two companies named below, except at your direction or where the law requires it.

Two companies act under their own privacy policies rather than ours. Stripe verifies experts’ identity for payouts and screens payments for fraud as its own controller. If you sign in with Google, Google tells us your name, email address and profile picture, and its own policy covers that sign-in.

For personal data transferred from the EEA, the UK, or Switzerland to the United States, each processor’s data processing agreement, on file with us or incorporated automatically into the service agreement we hold with it, relies on the European Commission’s Standard Contractual Clauses and the UK’s International Data Transfer Addendum, or on that processor’s own certified transfer mechanism, such as active status under the EU-U.S. Data Privacy Framework and its UK Extension, where one applies.

Calendar sync, Google and Microsoft user data

Experts can connect Google Calendar or Outlook so Key bookings never clash with their life. When you connect Google Calendar, Key accesses exactly two things: your free/busy windows (times only, we deliberately request a scope that cannot read event titles, attendees, or contents) and write access to add, update, or remove the calendar events for confirmed Key bookings. Free/busy times are read transiently to compute open slots and are never stored. What we do store: the email address of the connected account (so your dashboard can show what’s connected) and the OAuth tokens that keep the connection alive.

How this data is protected: the OAuth tokens are encrypted at rest with AES-256-GCM on top of the database’s own encryption, the decryption key lives only in the server environment, all transfers use TLS, and access is limited to the server-side code that computes availability and writes booking events.

Sharing: we do not share, transfer, or disclose Google user data to any third party. It is never sold, never used for advertising, and never used to train AI models. It resides only with the infrastructure processors listed above (Supabase stores the encrypted tokens, Vercel runs the code that uses them), acting under our instructions, or where disclosure is required by law. Key’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your control: disconnecting a calendar in your dashboard deletes the stored tokens immediately, and you can also revoke Key’s access at any time from your Google Account’s security settings (myaccount.google.com/permissions). Outlook connections work the same way, under Microsoft’s equivalent controls.

AI assistants you connect

If you connect an AI assistant (such as Claude, ChatGPT or Gemini) to your Key account, Key sends it the trip details and desk places you ask it for, at your direction. Once sent, they are part of your conversation with that assistant and are handled under its provider’s terms and your settings there, which may include using conversations to improve its models. Key never sends call recordings or transcripts to an assistant. You can disconnect an assistant at any time from My bookings.

How long we keep things

Your account and its content persist until you delete your account. Recordings and desks persist so participants can revisit them, ask us to delete a specific recording and we will. Transactional records are retained as bookkeeping requires. Where we delete a recording or a departing participant’s portion of one, we keep it no longer than 90 days after the deletion request, solely to investigate an open dispute, fraud, or safety report; a transcript with identifying details removed can be kept longer, since text is far more reliably de-identified than video or audio.

We also keep encrypted backups so we can recover from an outage or attack: copies of files, including recordings, for up to 11 weeks, and copies of our database for up to 12 months. Nobody, including us, can change or delete a backup before then. If we ever restore one, we delete again anything you had asked us to remove.

Your rights

Wherever you are, we honour the substance of GDPR-style rights: ask us for a copy of your data, a correction, or deletion at hello@key.new and a human will handle it. Deleting your account removes your profile and personal data; recordings involving another participant may be retained for them with your identity removed where technically feasible.

If you are a California resident, you additionally have the right under the CCPA and CPRA to know what personal information we have collected about you, to delete it, and to correct it; we do not sell or share personal information for cross-context behavioral advertising, so there is no opt-out to exercise for that. Call recordings can include your voice, and voice recordings can meet California’s definition of biometric information, but we do not process them to extract a voiceprint or otherwise identify you from your voice, so they are not sensitive personal information under the CPRA; if that ever changes, we will update this policy and give you the added rights that come with it.

Where data lives

Our database, file storage and application servers are in London, in the United Kingdom. Original call recordings and our encrypted backups are stored in Stockholm, Sweden, and product analytics in the EU. Email is sent through our email processor’s Tokyo region. Several processors (Vercel, Stripe, Daily.co, Deepgram, Resend, GitHub, OpenAI, Google, Attio, AssemblyAI and Anthropic) are US companies that may process data in the United States. These transfers are made under the safeguards described above.

EU and UK representative

Key has no office or establishment in the European Union or the United Kingdom, but offers paid services to people there, so under Article 27 of the GDPR and the equivalent UK requirement Key has appointed a representative. Our representative in the EU/EEA, the United Kingdom and Switzerland is Data Protection Representative Limited (trading as DataRep), an Irish company (registered number 616588) at 77 Camden Street Lower, Dublin, D02 XE80, Ireland. If you are in one of those places you may raise any question about how Key handles your personal data, including a request to exercise your rights, with DataRep instead of with us: email datarequest@datarep.com, use the form at datarep.com/data-request, or write to DataRep by post: in the EU/EEA at the Dublin address above, in the United Kingdom at 107-111 Fleet Street, London, EC4A 2AB, and in Switzerland at Leutschenbachstrasse 95, 8050 Zurich. Address post to “DataRep” and say that your request concerns Key. DataRep is also Key’s legal representative in the European Union under Article 13 of the Digital Services Act; matters under that regulation go to digitalrequest@datarep.com. DataRep acts only as our representative: for anything about a booking, a call or the service itself, write to us at hello@key.new.

Children

You must be 18 or over to hold a Key account. A child may join a call alongside the adult who booked it, with that adult present; we don’t knowingly collect data from anyone under 18 beyond what’s in that call’s recording.

Changes

We’ll update this page as the product changes and note the date at the top. Material changes get an email.

Privacy Policy · Key