What the public site is for
The public website introduces LOCORBIT, identifies the human and AI roles, explains the process, and gives people a way to ask or make contact. It also offers a shareable link and a QR code. Those are public-facing functions. They should make the experience understandable without turning private administration into a feature of the homepage. A visitor does not need access to deployment credentials, submission dashboards, or internal operator settings to understand how to begin. Good boundaries make the entry point simpler, not more mysterious.
What to keep out of a message
Do not paste passwords, two-factor codes, recovery phrases, private keys, or unrelated account records into a question. Redact screenshots before sharing them. When a problem involves another person, include only the information needed to explain it. A useful response rarely requires every identifying detail. If a task later needs sensitive access, that access should use an appropriate, specifically authorized workflow rather than a public text field. Being direct about the problem and being careful about the material are compatible. Neither should be sacrificed to the other.
What the IP display does—and does not do
The network panel displays the address observed by the lookup service. The production path uses the site’s own Netlify function. Local previews and static deployments can fall back to ipify, an external public-IP service; that request exposes the ordinary connection address to that provider, not the contents of your form. The frontend does not store the result in browser storage or attach it to the question. An address alone does not establish a person’s exact physical location, identify a specific individual, or reliably prove whether a VPN or proxy is in use. The panel therefore leaves VPN status unverified.
Share the address, not the private exchange
The share tools are designed to pass along the public LOCORBIT link. They do not automatically publish the question you typed, your email, or an operator response. External share destinations may require their own login and follow their own policies. The same separation applies to AI assistance: an operator should only access material and take actions within the permissions actually granted. Clear boundaries are an operating rule, not a decorative privacy slogan. Public identity can be visible while personal context, account access, and internal controls remain properly separated.
Show the system clearly. Do not expose people or credentials to prove that it exists.