Who runs this site
Visible Origin is operated by John Patzi, an independent consultant based in Chile. Contact: [email protected]
What this site collects
When you email me or send the form. Whatever you choose to put in your message. The contact form asks for a name, an email address and a domain; submissions are stored in this site’s database and also emailed to me. Writing to the address above instead goes straight to my mailbox and is not stored here. Either way I use it to answer you and to keep a record of the conversation. Nothing else.
Server logs. Like every web server, this one records the IP address, the page requested, the time, and the browser string of each request. These logs are kept for a limited period and used to diagnose problems and detect attacks.
Cloudflare. This site sits behind Cloudflare, which processes requests before they reach my server and may set a functional cookie for security purposes. See the Cookie Policy.
Analytics
Since September 2, 2026 this site uses Google Analytics, and only if you accept it. Decline and the Google script is never requested, so nothing about your visit reaches Google. Accept and Analytics records the pages you view, roughly where you are and what browser you use. I use it to see which pages are read and whether the free check is being found. Google is the processor; their terms govern what they do with it.
AI assistant (on-site chat)
Since October 13, 2026 most pages offer an optional chat assistant (“Ask a question”). It is an automated AI system, not a person: it answers from the notes and pages of this site, it can be wrong, and nothing it writes is an offer, a quote or a promise. If you never open it, nothing in this section applies to you. It does not appear on this page, the Cookie Policy or the Terms.
What is sent when you ask. Opening the assistant sends nothing to any AI provider; that only happens when you send a message. Then: the text of your message (up to 500 characters), the last few messages of the same conversation, and the title of the note or page you are reading, if it is one the assistant knows. It does not ask for your name, your email or an account.
Who processes it. To write the answer, my server sends that text, together with excerpts from my own notes and pages, to an AI model provider through OpenRouter, in the United States. I use a no-cost model tier. Under that tier OpenRouter and the model provider handle the text under their own privacy policies, and the provider may retain the messages it receives and may use them to improve its models. Your IP address and other identifiers are not sent with them.
What I keep. A log with the date, the question you asked, a short search query derived from it, the notes or pages the answer linked, token counts, whether “Yes” or “No” was tapped under the answer, and when the assistant was opened or a link to a page of this site was clicked in it (the page address, without parameters). The log holds no IP address, cookie or other identifier, and entries are deleted after 60 days. I use it to check that the assistant answers well. The web server’s ordinary access log (see “Server logs” above) still records requests to the assistant like any other request.
Abuse limits. Requests are counted with a one-way keyed hash of your IP address that changes every day. The counter expires within 24 hours, holds only a number and is not linked to what you wrote.
Saved answers. To save capacity, the answer to a short opening question may be kept for up to 48 hours and shown to the next visitor who asks the same thing. The saved answer is not linked to who asked.
In your browser. The conversation is kept in your browser’s session storage so that it survives moving between pages, and it is erased when you close the tab. The assistant sets no cookies and loads no third-party scripts or fonts.
Please do not type personal, financial or confidential information into the chat. To ask me to delete something you wrote, write to [email protected] with the approximate date and time and the text of the message, so that I can find it.
llms.txt checker
Since October 16, 2026 the llms.txt checker lets you enter a domain. My server then requests public files from that domain: its /llms.txt, up to five links listed in it, /llms-full.txt and, only if the file is refused, its homepage. No AI provider or other third party receives the domain.
What I keep. The domain and the result are cached on my server for ten minutes, so repeated checks do not hit the same site, and then deleted. They are not logged. To limit each visitor to six checks every ten minutes, a one-way keyed hash of your IP address is kept with a counter for ten minutes; the address itself is not stored. A daily total of checks, with no domains or addresses, is kept for one day. The request itself also appears in the web server’s ordinary access log (see “Server logs” above), like any other request.
What this site does not do
There is no advertising, no tracking pixel and no third-party marketing script on this site. Nothing you do here is shared with an advertising network. If that changes, this page and the Cookie Policy will be updated before the change goes live — as they were for Analytics and for the chat assistant.
How long data is kept
Emails are kept while the conversation is useful and deleted on request. Server logs rotate automatically after a short period. The chat assistant’s log is deleted after 60 days.
Your rights
You can ask me what data I hold about you, ask for it to be corrected, or ask for it to be deleted. Write to [email protected] and I will answer.
Audit work on client sites
Audits are performed with public HTTP requests only. No access to a client’s systems is used or required for an audit. When implementation work is agreed, credentials are handled separately, used only for that engagement, and removed when it ends.