Last Contact

Privacy Policy

This page describes how Last Contact handles the information you share with us — through the waitlist, your account, and Guide. We've written it in plain language, and it describes our actual practices.

What we collect

If you join the waitlist, we collect what you submit in that form: your name (if provided), email address, and your answers about your experience with unwanted contacts. If you create an account, we additionally store the contacts you choose to track, the platform statuses and handles you enter, and any incident notes you write.

How we use it

We use your email only to update you about Last Contact. We use waitlist answers to understand what to build. Account data is used only to provide the dashboard back to you. We do not sell your data to anyone.

Who can see it

Your account data is private by default — only you can access your own contacts and notes. Waitlist submissions are stored securely and are only accessible to the Last Contact founder. Nothing is publicly visible.

Advertising and measurement

We advertise Last Contact on Google and Meta (Facebook and Instagram). To understand which ads bring people here, we use the Meta Pixel and Meta's Conversions API, which share limited information with Meta: that a visit, an account signup, an account activation, or a subscription happened, along with the ad click identifier you arrived with. When we report a signup, activation, or subscription, your email address is converted into an irreversible code (a cryptographic hash) before it is sent — we never send Meta your actual email address.

We deliberately limit this in two ways. First, the Meta Pixel only loads on our public pages — the home page, sign up, log in, terms, and this privacy policy. It is never active inside the app itself, so Meta is never told that you opened your Timeline, wrote in your Journal, or looked at a contact. Second, we do not send Meta any of your content: never a journal entry, a note, a contact name, a platform handle, or anything you type to Guide.

We also use PostHog for product analytics. PostHog is configured to mask all text and input content, so recordings and analytics never capture what you write.

You can limit this further with your browser's tracking protection or an ad blocker; Last Contact works normally either way.

Guide conversations

Guide conversations are not saved to our database. What you type to Guide exists only in your browser for that session and is gone once you leave or refresh the page.

Guide checks what you type for specific language that may indicate you're in danger — for example, signs of an immediate threat, an ongoing stalking pattern, an abusive relationship, or thoughts of self-harm. This check exists for one purpose: to surface a relevant resource, like a crisis line, alongside Guide's response, when it might help.

This is not profiling, scoring, surveillance, or diagnosis. Nothing about this check is stored, nothing is used to evaluate or label you, and no person reviews your messages as part of it.

Guide currently responds using a fixed set of rules we've written. It is not powered by artificial intelligence.

What we will and won't do with what you share

We will never proactively contact authorities or any other third party based on anything you share with Guide. This is a decision entirely within our control, and we make it without exception.

Separately: if we are compelled by valid legal process — such as a subpoena, warrant, or court order — we will disclose only the minimum information legally required, will challenge requests we believe are overbroad wherever legally possible, and will notify you unless we are legally prohibited from doing so.

These are two different kinds of commitments. The first is a choice we make and control completely. The second depends on the law, not on us — we're being precise about that difference rather than implying a guarantee we couldn't actually keep.

Questions

Reach out at hello@lastcontact.app.