Response Goal
48-hour initial reply
If you report a credible security issue, we aim to acknowledge it quickly and keep the conversation moving.
Linket Connect
Legal
Security at Linket
How we think about protecting live profiles, lead capture, and the infrastructure behind every tap and scan.
What This Page Covers
Security at Linket is about practical safeguards: protecting data, limiting access, routing profiles safely, and responding clearly when issues are reported. This page summarizes the controls and reporting path we use today.
Covers
Profiles, routing, dashboards, and lead data
Security work spans the hosted product, public profile flows, analytics, and the infrastructure behind them.
Report To
security@linketconnect.com
Send details, reproduction steps, and impact so the team can evaluate the report without guesswork.
Core safeguards
These are foundational controls built into the product and its supporting systems.
Data handling
Encryption in transit and at rest
Sensitive product data is protected during transmission and while stored so common traffic and storage risks are reduced.
Access
Role-aware dashboard controls
Access to internal tools and account features is limited to the people who need it, helping reduce unnecessary exposure.
Routing
Secure public-page delivery
QR and NFC routes are designed to resolve to the correct live profile without relying on brittle, manually updated destinations.
Operational practices
Security is not a one-time checklist. It depends on consistent engineering and support discipline.
- We review product changes, deployment behavior, and configuration updates as part of day-to-day engineering work.
- Audit awareness around profile edits and operational activity helps us understand what changed and when.
- Vulnerability scanning and targeted fixes are part of the ongoing maintenance needed to keep the service healthy.
- No security policy can promise zero risk, so we continuously tighten controls as the product grows.
Reporting a vulnerability
Responsible disclosure works best when the report is specific and the testing stays within authorized limits.
- 1Email security@linketconnect.com with the affected surface, reproduction steps, expected impact, and any screenshots or proof-of-concept material that helps explain the issue.
- 2Do not publicly disclose the issue before giving us a reasonable opportunity to investigate and respond.
- 3Avoid actions that would damage customer data, interrupt service, or access accounts that you do not own or have explicit authorization to test.
- 4We will review the report, confirm scope where possible, and follow up with next steps or mitigation details.
Response expectations
We keep the process simple: acknowledge, investigate, and resolve as quickly as the issue allows.
Triage
Initial acknowledgement
Our target is an initial response within 48 hours for reports that include enough detail to investigate.
Investigation
Context and validation
We may ask follow-up questions, test reproduction paths, and verify whether the behavior affects customer data or system integrity.
Resolution
Mitigation and communication
Once confirmed, we prioritize a fix, mitigation, or operational response based on severity and keep communication practical and direct.
Security contact
Support
Need to report a security concern?
Email security@linketconnect.com with enough detail for us to reproduce the issue and understand the potential impact.
Email security