Privacy Policy
This service lets you gather candidate saints and blesseds for a baptismal name, compare them, and share the list by link. There are no accounts, and nothing at all that identifies you is collected. The birthday month and day you may type into the search are used only inside your browser and never reach our server.
Nothing is stored either, not even in this browser. Your shortlist lives in the address bar: adding or removing a name rewrites the address, and that is the whole of it. Close the tab without keeping the address and the list is gone. If this service were breached, there would be nothing to take.
What we never send
- Which names are on your list, what you searched for, and any birthday you typed. None of it, in any form.
- IP addresses and device information (User-Agent) are not read, and no cookies are used.
- No notifications are sent, and permission for them is never requested.
- The saint data is a file shipped with the site, fetched from Wikidata once when the site was built. Your browser does not contact Wikidata while you use this page; the links to Wikidata entries open only when you tap them.
- Connections leaving this site are blocked at the browser level, so even code that tried to send something could not.
This site is served through Cloudflare, which automatically injects a visit-tracking script into our pages. We did not add it, so we have configured your browser to refuse it. That means the tracking call does not go out. The tag itself is still injected by that layer though, so we would rather you know about it than not. We do not use cookies.
Anonymous signals the server receives
- Step names (page opened, a name was added, two or more names were on the list, link copied, first touch on the page, a name was removed or the list was cleared), the interface language, the channel label we wrote into our own link or the domain of the previous page (never the path or query), and the date you arrived (day only, no clock time).
- Which names you added or removed is not included. Only the fact that it happened is counted, once per visit.
- If something breaks on screen, that fact reaches the same place: we send only the error name (TypeError, for example) and an eight-character fingerprint of where it happened. We never send the error message, the stack, or the address. At most three per visit.
- These signals live in short-term server logs only and are never shared with third parties. We may show Google AdSense ads to cover running costs; Google may then use cookies or ad identifiers under its own policy.
- Third parties, including Google, serve these ads and may collect information through cookies, web beacons and your IP address to show them. Read how Google uses data from sites that use its services. You can turn off personalized ads in Google Ad Center.
This site is served through Cloudflare, which automatically injects a visit-tracking script into our pages. We did not add it, so we have configured your browser to refuse it. That means the tracking call does not go out. The tag itself is still injected by that layer though, so we would rather you know about it than not. We do not use cookies.
The share link
The copy-link button hands over the address that is already in your address bar. That address carries the Wikidata identifiers of the names on your list as a query string, plus a short tag that tells us a visit came from a shared link. It is read by the recipient's browser, not by our server, but whoever opens the link will see the names you are considering. Send it to the people you mean to ask.
How to delete
There is nothing to delete. No record remains in this browser or on the server. If you bookmarked the address, delete the bookmark; that was the only copy.
Business registration details and a contact address will be posted here once registration is complete.
A script we did not add
This site is served through Cloudflare, and Cloudflare injects its own Web Analytics beacon into our pages. We did not add it, and it reports the address you visited along with basic device information to Cloudflare rather than to us. We cannot remove it from their edge, so we write it down here instead of pretending it is not there. We set no cookies of our own.