Contact PRISM IP
This page provides the official communication channels for PRISM IP. If you need support for lookup errors, API behavior, translation mistakes, accessibility concerns, or privacy and legal questions, use the contact method below and include enough technical context for triage. We review requests in batches and prioritize messages that include reproducible details.
How to reach us
- Email: [email protected]
- Security and abuse: [email protected]
- Repository issues: open a ticket with steps, expected result, actual result, browser, and network region.
What to include in a support request
To help us resolve your issue faster, share the IP query input used for testing, the approximate timestamp of your request, the page URL, and a short screenshot or copied output block. If your concern is related to wrong geolocation data, please note that PRISM IP relies on third-party datasets and performs fallback switching when sources are unavailable. Some regional discrepancies can occur across providers and may not indicate an application defect.
For policy questions, include the specific clause from our Privacy or Terms pages. For SEO and indexing concerns, mention which crawler reported the issue and whether you tested with a fresh crawl or cached data. For accessibility feedback, include keyboard steps and contrast context so we can evaluate remediation accurately.
Response scope
PRISM IP is a lightweight public utility. We cannot provide guaranteed response SLAs, emergency production support, or legal advice. We can confirm product behavior, clarify data source limitations, document known constraints, and publish fixes when issues are actionable in the codebase. If your request involves sensitive material, avoid sending personal identifiers and use minimal data required for diagnostics.
Before submitting a request, verify whether your issue is environment-specific by testing from a second network or browser profile. If results differ, include both outcomes in your report so we can determine whether the root cause is cache state, provider variance, or rendering logic. Well-structured reports reduce turnaround time and improve fix quality for everyone.