Grapevinee

Open app

Legal

Cookie & Analytics Notice

Last updated October 19, 2026Version 2026-10-19Previous versions

This is the dated copy of the version in force since October 19, 2026. It will stay at this address after the Cookie & Analytics Notice changes. Read the current Cookie & Analytics Notice

The short version

  • We use very little. Two cookies keep you signed in, one makes sure a shared browser never shows the previous person’s details, one tells us whether to ask before analytics, one remembers your answer so our servers follow it too, and a few settings are saved in your browser.
  • Analytics are optional. We use PostHog to see how Grapevinee is used. What you type, and the names and other details on your screen, are never sent.
  • In the EU, UK and Switzerland analytics stay off until you choose “Allow analytics”. Everywhere else they are on, and one tap turns them off.
  • Global Privacy Control in your browser switches analytics off without a question.
  • Advertising cookies only with your yes. The free version may show ads. No advertising cookie, social media pixel or cross-site tracking is used today, and none ever will be unless you say yes, wherever you live (Advertising).
  • What changed on October 19, 2026: our cookies have new names that start with __Host-, so no other website can plant one in your browser, and the Google and Apple sign-in cookies now go with every request to Grapevinee for their 10 minutes (Always on). For members and visitors these are the same cookies, with the same purposes and lifetimes, and nothing new is collected. This version also lists the Apple sign-in cookie and four settings kept only while a tab is open, which the previous version left out, and the cookies set only in a Grapevinee staff member’s own browser while they use our admin console: two for its support tools, three that remember a search for 30 minutes, so it never goes in a web address, and one for its sign-in step. Two lifetimes now say the longest they can be. The previous version is in Versions.

This summary helps you find your way. The full text below is what applies.

Your choice

Product analytics in this browser: …

  • In the EU, EEA, UK and Switzerland: analytics are off until you choose “Allow analytics”. “No thanks” is just as easy, and closing the banner counts as no.
  • Everywhere else: analytics are on by default, and you can turn them off at any time.
  • Anyone can change their mind at any time, with Change cookie settings on this page or, once you are signed in, in Settings under Privacy & permissions.
  • When you are signed in, turning analytics off is saved to your account too, so they stay off on every device you sign in on. Saying yes lifts that account-wide “off”, but a device where you said no, or where we ask first, keeps its own answer until you change it there.
  • If your browser sends Global Privacy Control, we treat it as “No thanks” to analytics and recordings, and we don’t ask.
  • Turning analytics off changes nothing else about how Grapevinee works for you.

We work out whether to ask first from the country our load balancer sees your connection coming from, or, if that isn’t available, from your device’s time zone and languages. If in doubt, we ask.

Always on: needed to run Grapevinee

Strictly necessary cookies

  • __Host-gv_at

    Type
    Cookie (httpOnly, Secure, SameSite=Lax)
    What it does
    Keeps you signed in (a short-lived access token)
    Lasts
    15 minutes

  • __Host-gv_rt

    Type
    Cookie (httpOnly, Secure, SameSite=Lax)
    What it does
    Renews your sign-in. A stolen one is detected and revoked.
    Lasts
    30 days

  • __Host-gv_sm

    Type
    Cookie (Secure, SameSite=Lax; our pages can read it)
    What it does
    A random value that changes each time you sign in, so this browser never shows the previous person’s details. Holds nothing about you.
    Lasts
    As long as your sign-in (up to 30 days); deleted when you sign out

  • __Host-gv_region

    Type
    Cookie (Secure, SameSite=Lax; our pages can read it)
    What it does
    Your country as a two-letter code, so we know whether to ask before any analytics. Nothing else.
    Lasts
    1 day

  • __Host-gv_aoff

    Type
    Cookie (Secure, SameSite=Lax; our pages can read it)
    What it does
    Set only when your account has analytics switched off, so no screen sends anything before we have checked. Holds no id.
    Lasts
    Until you sign out or switch analytics back on (at most 400 days)

  • __Host-gv_ac

    Type
    Cookie (Secure, SameSite=Lax; our pages can read it)
    What it does
    Remembers whether you allowed analytics, so Grapevinee’s servers respect your answer too. Holds only “yes” or “no”.
    Lasts
    Until you sign out (at most 400 days); a new answer replaces it

  • __Host-gv_google

    Type
    Cookie (httpOnly, Secure, SameSite=Lax)
    What it does
    Only while you sign in with Google: ties Google’s answer to the request you started, so nobody can slip in theirs. Sent with every request to Grapevinee for those 10 minutes.
    Lasts
    10 minutes, then deleted

  • __Host-gv_apple

    Type
    Cookie (httpOnly, Secure, SameSite=None)
    What it does
    Only while you sign in with Apple: ties Apple’s answer to the request you started, so nobody can slip in theirs. SameSite=None because Apple sends you back to us with a form from its own site. Sent with every request to Grapevinee for those 10 minutes.
    Lasts
    10 minutes, then deleted

  • __Host-gv_signup

    Type
    Cookie (httpOnly, Secure, SameSite=Lax)
    What it does
    Only while you finish creating an account after Google, Apple or an email code: carries the proof of your address to that one screen
    Lasts
    Up to 2 hours; deleted when you finish

Grapevinee can’t work without these, so they don’t need your consent. They are never used for analytics, and page scripts can’t read the httpOnly ones: the two sign-in cookies, the Google and Apple sign-in cookies, and the account-creation cookie.

Staff only. When Grapevinee staff use the support tools in our admin console, their own browser also keeps __Host-gv_va (httpOnly) and __Host-gv_vam (our pages can read it), both Secure and SameSite=Strict, for up to 12 hours, deleted when they finish. The admin console’s search boxes keep what staff last searched for, so the search never goes in a web address, in gv_admin_search_users, gv_admin_search_email_list and gv_admin_search_product_news (httpOnly, Secure, SameSite=Strict, sent only to the admin console’s pages), for 30 minutes, deleted sooner when they clear the search or sign out. While staff turn on the console’s second sign-in step, gv_2s_new (httpOnly, Secure, SameSite=Lax, sent only to that sign-in screen) keeps the screen on their recovery codes for up to 15 minutes, deleted when they go on to the console. None of these is ever set in a member’s or visitor’s browser.

Why most names start with __Host-. All of these are first-party cookies: only Grapevinee sets them and reads them. The __Host- at the start of a name tells your browser to accept the cookie only from grapevinee.com itself, over a secure connection, for the whole site, and never from any other address, not even another part of grapevinee.com. So nobody else can plant a cookie in your browser to sign it in to someone else’s account or to change your answers. Every cookie in the table carries it, and so do the two support-tool cookies above. The four other staff-only cookies can’t: a __Host- cookie must go with every request to the site, and each of these is meant for one part of the admin console only, so it is sent nowhere else. They are still first-party and Secure, and none of them can sign anyone in.

The names they had before. Until October 19, 2026, the same cookies had the same names without __Host-: gv_at, gv_rt, gv_sm, gv_region, gv_aoff, gv_ac, gv_google (then sent only to the Google sign-in address), gv_apple (then sent only to the Apple sign-in address), gv_signup and, for staff, gv_va and gv_vam, with the same purposes and lifetimes. While browsers move over, for about 30 days (the life of a sign-in), we still accept a cookie under its old name: when your browser comes back, we replace it with the new name and delete the old one, so nobody is signed out. A cookie with an old name in a browser that doesn’t come back simply runs out at the end of its lifetime above.

Settings saved in your browser

Local and session storage

  • gv-theme

    Where
    Local storage
    What it does
    Remembers dark or light theme

  • gv_tz

    Where
    Local storage
    What it does
    Remembers that we already saved your time zone, so reminders arrive in the morning where you are

  • gv-analytics-consent

    Where
    Local storage
    What it does
    Your analytics answer (yes or no), so we don’t keep asking

  • gv-analytics-consent-at

    Where
    Local storage
    What it does
    When you gave that answer, so an older answer on this device never overrides a newer one you gave elsewhere

  • gv-analytics-notice-seen

    Where
    Local storage
    What it does
    That the analytics notice has been seen on this browser, so it is shown only once to visitors who are not signed in

  • gv-analytics-notice-seen-by

    Where
    Local storage
    What it does
    Who has seen the analytics notice on this browser (account internal ids, or that it was seen signed out), so each person who signs in sees it once

  • gv-analytics-consent-by

    Where
    Local storage
    What it does
    Whose analytics answer that is (your account’s internal id, or that you were signed out), so on a shared browser one person’s answer never becomes another’s

  • gv-a2hs-hint-dismissed

    Where
    Local storage
    What it does
    That you closed the “add to your home screen” tip, so it doesn’t come back

  • __ph_opt_in_out_…

    Where
    Local storage
    What it does
    PostHog’s own copy of your analytics answer, written only once you answer

  • gv-analytics-consent-synced

    Where
    Session storage (gone when you close the tab)
    What it does
    That your answer is already saved to your account, so it isn’t sent twice

  • gv-vine-view

    Where
    Session storage (gone when you close the tab)
    What it does
    Whether your home screen shows the bunch, the spread or the Tapestry

  • gv-path-q

    Where
    Session storage (gone when you close the tab)
    What it does
    Your last “Who can introduce me to…” search, so going back shows the same answer (never in the page address)

  • gv-path-room

    Where
    Session storage (gone when you close the tab)
    What it does
    How much room the answer to that search took on the page (a height only), so the page doesn’t jump when the answer comes back

  • gv-person-from

    Where
    Session storage (gone when you close the tab)
    What it does
    Which list you opened someone from, so Back returns you there

  • gv-person-new

    Where
    Session storage (gone when you close the tab)
    What it does
    Which person you just opened from a ringed (new) grape, by internal id, so their page can say why they were ringed

  • gv-person-cluster

    Where
    Session storage (gone when you close the tab)
    What it does
    Which cluster you just opened someone from, by internal ids, so their page can offer to take them out of it in one tap

  • gv-grape-clip

    Where
    Session storage (gone when you close the tab)
    What it does
    The people you cut or copied to put in another cluster, by internal ids only (never a name), so a reload doesn’t lose them

  • gv:auth-email

    Where
    Session storage (gone when you close the tab)
    What it does
    The email you typed, carried from “Create account” to “Sign in” when you already have an account, then deleted

They stay in your browser until you change them or clear your browser’s data. We don’t use them for anything else.

Analytics: optional

We use PostHog to see how Grapevinee is used, so we can find what confuses people and fix it. PostHog keeps an identifier in a cookie and in local storage named ph_<project key>_posthog. Where we ask first, your browser doesn’t contact PostHog and nothing is stored until you choose “Allow analytics”, and if you turn analytics off it stops storing anything. It records:

  • pages you view, and the buttons and links you click (but not the text of what you clicked, which in Grapevinee is usually someone’s name);
  • how long screens take to load and how long you spend on them, and where clicks go nowhere;
  • errors;
  • device and browser type;
  • approximate location (country or city), worked out from your IP address; and
  • once you are signed in, your Grapevinee account ID and account facts (plan, role, sign-up date and method, trial end). We never send PostHog your name or email address, or anything about the people on your vine.

To keep it that way, before anything leaves your browser we remove:

  • the page title (in Grapevinee it can be a person’s or a cluster’s name);
  • the wording, labels and other attributes of what you clicked;
  • where a link to another website, an email address or a phone number points (it is sent only as “external”); and
  • the secret part of links that carry one (invitations, sign-in codes).

Session recordings let us replay how a page behaved: clicks, scrolling and movement, like a video of the layout. In them:

  • everything you type is hidden;
  • all text on the page is hidden, including names, notes and messages. Only fixed wording that is the same for everyone, like button labels and headings, may be visible;
  • images and video are not recorded; and
  • network requests are not recorded: what the app sends and receives stays out of recordings.

We keep analytics events for up to 12 months and recordings for up to 30 days. PostHog processes the data for us as our service provider, in the United States, and doesn’t use it for its own purposes.

Analytics are not advertising: PostHog never chooses or measures ads.

Advertising: only with your yes

The free version of Grapevinee may show ads; Pro, and the free trial of Pro, has none. Without your yes, an ad is chosen only from where it appears, never from who you are, and it sets no cookie. Ads are never chosen from your contacts, notes, messages or anyone in your network.

Today we use no advertising cookies, social media pixels or cross-site tracking. If we add an ad partner, we will list it here, with every cookie it sets and how long each lasts, before it is used. Its cookies will stay off until you say yes, wherever you live, and Global Privacy Control will count as no. You will be able to change your answer at any time.

More information

The Privacy Policy explains everything else we do with personal information. Questions: privacy@grapevinee.com.

Versions

Every version we publish stays online at its own address, so you can always see what applied when.