Security posture and abuse controls.
GoLowKey keeps the public trust layer crawlable while protecting member routes, APIs, lead claims, support tickets, provider connections, and enrichment signals behind server-side controls.
Company-email members receive four verified leads per day after verification.
Email or CRM access increases only after scoped consent, provider verification, and audit.
GoLowKey accepts business signal summaries, not raw mailbox or CRM dumps.
Measured from ticket opened to fix ready for customer review. Customer review delay is tracked separately.
GoLowKey is a verified business lead search platform, not a chat, messaging, or social app.
- HTTPS only, HSTS, strict content security policy, frame blocking, and no public API write access from untrusted origins.
- Business-domain access only; common consumer email domains are blocked.
- Quota is enforced on the server with D1 lead claims and a KV quota ledger to survive database rebuilds: 4 daily verified leads standard, 20 after verified provider connection.
- Provider access is consent scoped. Higher daily access starts only after a verified email or CRM connection is completed and audited.
- Raw email bodies, raw contact dumps, and raw deal records are rejected by ingestion endpoints.
- Email authentication uses Microsoft 365 SPF/DKIM plus DMARC quarantine enforcement with aggregate reports routed to the GoLowKey admin mailbox.
- Enterprise trust requests, DPA review, subprocessor review, and data-rights requests start at https://golowkey.app/trust-request.
GoLowKey keeps the customer flow simple: company email access, market search, verified public business records, visible score reasons, and feedback that improves future results.
Confidence rises with source trace, complete profile fields, freshness, category fit, and explainable evidence.
Intent rises when approved public evidence points to timing, need, service fit, forms, active pages, or recent business motion.
Growth rises when public data shows services, hiring, marketing language, active updates, or expansion clues.
Outreach rises when a public contact route exists and the profile has enough context for careful business outreach.
Profile reliability, source trace, freshness, category fit.
Public contact path plus responsible contact context.
Evidence that outreach may matter now; generic why text does not count.
Expansion, activity, hiring, launch, or service clues.
The remaining proof adjustment rewards source trace, freshness, public contact paths, website, and location. No proof lowers the score. Missing source trace applies a rank penalty because provenance is required before a record is treated as fully clean.
GoLowKey uses these public standards and agency references as methodology anchors. They support provenance, data quality, explainability, and outreach caution. They are not a claim that every individual record is perfect.
Used as the public reference for source trace and provenance language.
ISO/IEC 25012Used as the public reference for structured data-quality concepts.
NIST AI RMFUsed as the public reference for explainability, reliability, and transparency language.
FTC CAN-SPAMUsed as the public reference for careful commercial email outreach language.
FCC TCPAUsed as the public reference for call and text outreach caution language.