Privacy Policy
November 1, 2026: clearer wording on where requests are handled, what our hosting logs are kept and used for, how long we keep email and when we delete it, our email provider, our search ads on Google, Do Not Track, our legal basis and transfers, and your UK rights. Angel's chat is switched off for now; when it is on, its replies come only from an AI model that Cloudflare runs, and Microsoft is no longer one of our AI providers. We collect nothing new.
October 2026: email you send us about a mistake is also used to correct the page. We also removed the line about a search-improvement log: there is no such log. And we now say more exactly what leaves your device when you tap "have Angel try" in Ask or "I did this" on a tip. Nothing else changed.
In plain words (this summary is for convenience and is not the policy): you can use everything we offer without telling us who you are — that's by design. No accounts, no cookies, no ads, no trackers, nothing sold. Conversations with Angel are not stored or read by us. What little our systems touch is described honestly below.
What we don't do
- No accounts. You can't sign up, log in, or be profiled here.
- No cookies. We set no cookies. That's why there is no cookie banner.
- No trackers, and no ads on our pages. No advertising networks, no cross-site tracking, no fingerprinting, no social-media pixels. We buy search ads on Google. If you click one, Google records the click under its own policy, and the address you land on may carry a Google click code that reaches our hosting logs; we send nothing back to Google.
- No selling or renting of data. There is nothing to sell.
- No AI training on your conversations. We don't use your conversations to train models, and our AI provider's terms say it doesn't either (see "Angel and Ask" below).
- Do Not Track: we do no cross-site tracking, so we treat every visit the same whether or not your browser sends a Do Not Track or Global Privacy Control signal.
We touch little data — most of it, described below, never reaches us at all.
What stays on your device only
Some features save data in your own browser's storage so they work without accounts. This data never leaves your device, and we cannot see it, except where a line below says so:
- Your pocket (saved tips) and your steps ("I did this") — stored in localStorage. Tapping "I did this" also sends our counter service a signal for that tip that carries no name, account or ID (Cloudflare still sees your IP address, as described under "Serving pages"; see also "The lantern and the candle" below).
- Your Ask conversation trail — stored in sessionStorage and erased when you close the tab. If you tap "have Angel try", the last few questions in it, and the answers they got, go with the question you tapped it under.
- What you search for and ask. Search runs in your browser. Ask answers from the library in your browser. Neither sends us what you typed. Only if you tap "have Angel try" under an answer does that question, with your last few questions on that tab, go to our AI service to make a reply (see "Angel and Ask" below).
- The "Let it out" tool, and the river at A quiet place — what you type there is never sent anywhere, never stored anywhere, and dissolves (or sails away) on your screen. These run entirely on your device.
- The candle latch. If you light a candle for the next visitor, the day you lit it is saved on your device so the page doesn't count you twice. Just the date — nothing else.
The "Clear everything" button on your pocket page erases all of this in one tap. Your browser history is separate — your browser's own settings control that.
What our systems do process
- Serving pages. Like every website, our infrastructure providers (Amazon Web Services for hosting and content delivery; Cloudflare for our chat and counter services) process standard request data — including IP addresses — to deliver pages, prevent abuse, and rate-limit. They keep standard request and security logs under their own retention settings, and we sometimes download copies to keep the site working and secure and to see which pages people read; we keep those copies only while we need them for that. We do not use this data to identify or profile visitors, and it feeds no advertising or analytics product. Our pages are hosted in the United States. Our chat and counter code runs on Cloudflare's network, so a request may be handled in a data centre near you, in the United States, or elsewhere on its network.
- No analytics product or beacon. We run no analytics service and load no measurement script in your browser — not Cloudflare Web Analytics, not Google Analytics, nothing that watches what you do. Any operational counts come only from the infrastructure logs described just above, which we read to keep the site working and secure and to see which pages people read, never to build a profile of you.
- The lantern and the candle. Tapping "I did this" or "Not for me" — or lighting a candle for the next visitor — sends our counter service a signal that carries no name, account or ID (Cloudflare still sees your IP address, as described under "Serving pages"). No identifier is stored with it — every light is the same size, and none has a name.
- Writing to us. There is no web form to fill in — the contact page and the "Tell us by email" and "Report a mistake by email" links on resource pages and emergency guides simply open your own email app. If you email us, we receive what you send and use it only to reply and, if you tell us about a mistake, to correct the page. If you ask us to delete it, we will, unless we need to keep it to deal with a dispute or because the law requires it. We keep it for as long as we need it to reply, to correct the page, or to deal with any dispute about it. In the words of UK data-protection law, our basis is our legitimate interest in answering you and keeping our pages right. Our email provider is Google (Google Workspace), which may store email in the United States or other countries.
Angel and Ask (our AI features)
Angel's chat is switched off for now: the chat page and Ask send nothing to it. When it is switched on and you talk with Angel or tap "have Angel try" under an Ask answer, your message and the conversation you're having are sent to an AI model that Cloudflare runs for us (Workers AI), solely to generate the response. Cloudflare says publicly that it does not use this content to train AI models and that, for requests like ours, it does not keep the inputs or outputs once the reply is delivered, except where it must to meet a legal obligation or a commitment described in its agreements or privacy policy. The request to the model is made by our code running on Cloudflare's network, not by your browser, and we send the model no IP address or other identifier. Because Cloudflare runs that code and carries the chat to it, it handles your IP address as described under "Serving pages" above. Your browser checks each message before it is sent. When it finds certain words, for example in some questions about how to end a life or some messages saying someone has taken an overdose, that message is never sent anywhere, and the page answers in our own words. It won't catch every one.
We do not store your conversations. We do not read them. Our systems do not log their content — we log only technical facts (timestamps, response status). Your side of the conversation lives in your browser's memory and disappears when you close the tab.
We cannot share or produce your conversations, because we do not have them. If we ever receive a legal request, we can only provide what we actually hold — which for conversations is nothing. Still, conversations with an AI are not legally privileged the way conversations with a licensed professional can be, so we suggest not sharing details that identify you or others.
Our legal basis, and where your data goes
In the words of UK data-protection law, our basis for the request data, logs, counter signals and AI requests described here is our legitimate interest in running a safe, working website and answering what you ask. Our providers are US companies; where UK law asks, we rely on the UK-US data bridge or the providers' standard data-transfer terms.
Embedded videos and outside links
Tip pages can include our short videos hosted on YouTube. We use a click-to-play facade: nothing loads from YouTube until you press play. If you do, YouTube receives standard request data, may set its own cookies, and applies its own privacy policy. Links to other organizations (including our resource directory) lead to sites we don't control — their privacy practices are their own.
Children
Our services are not directed to children under 13, and we do not knowingly collect personal information from children under 13. Since we operate no accounts and no profiles, we hold no such information to collect. (As a 501(c)(3) not-for-profit, Find Angel Inc. is generally not subject to the Children's Online Privacy Protection Act — but what this page says applies to everyone, of every age, regardless.) If you believe a child has somehow provided us personal information (for example by emailing us), contact us and we will delete it, unless the law requires us to keep it.
Your rights
Privacy laws in some places give you rights to access, correct, or delete personal information an organization holds about you. We hold essentially none: no account, no profile, no conversation logs. Data saved on your device is yours and can be erased with "Clear everything" or your browser settings. If you've emailed us and want that correspondence deleted, write to us. If you ask us to delete it, we will, unless we need to keep it to deal with a dispute or because the law requires it. If you are in the UK, you can also object to our handling of your data, complain to us, or complain to the Information Commissioner's Office (ico.org.uk).
Changes to this policy
If we change what we collect or how we use it, we will update this page and change the date below before the new practice begins. Material changes will be noted at the top of this page.
Contact
Questions or requests: info@findangel.org · Find Angel Inc., a 501(c)(3) nonprofit.
Last updated: November 1, 2026 · Prior versions: October 18, 2026 · July 2026.