No Public Lead Database
Lead, contact and career information is never rendered into public website pages or exposed through a public dashboard.
STRONGX
SECURITY & DATA PROTECTION
STRONGX protects website forms, lead handling and operational data with practical safeguards and disciplined access control.
Security
CONTROLLED ACCESS. CLEAN HANDLING. NO PUBLIC DATABASE.
Security is treated as an operating discipline, not a decorative statement.
No Frontend Secrets
No admin passwords, private keys, payment credentials or Google Sheet credentials are stored in the frontend code.
HTTPS Endpoint
Forms send information only to configured HTTPS endpoints. Payloads use normal form encoding to support reliable Google Apps Script handling.
Spam Controls
Forms use validation, consent checks, honeypot fields and rate-limiting patterns to reduce automated abuse.
Access Control
Operational sheets, emails and systems should be accessible only to authorized owners and team members who need the information.
Data Minimization
We avoid asking for sensitive documents, passwords, payment card numbers or unnecessary personal identifiers through public forms.
Operational Review
As STRONGX scales, access lists, form endpoints, sheet permissions and event-day data flows should be reviewed regularly.
Incident Response
If a data issue is suspected, STRONGX will review access, preserve relevant records, limit exposure and contact affected users where appropriate.
User Responsibility
Users should share accurate information, avoid sending sensitive documents unless requested and contact support@strongx.in for data concerns.
HTTPS Enforcement
Production hosting is configured to redirect HTTP traffic to HTTPS and send strict security headers for browser protection.
Browser Protection
Headers reduce risk from clickjacking, MIME sniffing, insecure resources, unnecessary browser permissions and script injection.