Security Overview & Controls
Exhaustive technical overview of security architecture, encryption standards, threat intelligence, and Chrome Extension sandbox protection across Stackly (v1.0.2).
TLS 1.3 Encryption
Data in Transit
AES-256 Storage
Data at Rest
Anti-Phishing
Threat Intelligence
SOC 2 / ISO 27001
Cloud Data Centers
At-A-Glance Security Summary
Data Encryption
TLS 1.3 enforced for all network transit; AES-256 for persistent database storage. Salted bcrypt/argon2 hashing for user authentication credentials.
Chrome Extension Isolation
Tokens stored in isolated chrome.storage.local containers. Minimal Manifest V3 permissions; zero background DOM scraping or silent tracking.
Threat Protection
Real-time threat engine checks shortened links against Google Safe Browsing and heuristic anti-phishing filters. Cloudflare WAF mitigates DDoS attacks.
Security-First Architecture & Commitment
At Stackly (operated by Forepine Technologies Pvt. Ltd.), security is not an afterthought—it is embedded into every layer of our platform, edge routing infrastructure, developer APIs, and official Stackly Chrome Extension (v1.0.2).
We process millions of link redirects and dynamic QR code interactions. To maintain maximum platform integrity, we adhere to a Zero-Trust Security Architecture, ensuring every request, API invocation, and Chrome Extension payload is authenticated, authorized, and continuously monitored.
Security Architecture Guarantee
100% of network traffic is encrypted in transit via TLS 1.3, all databases are encrypted at rest with AES-256, and all link redirections pass through real-time automated anti-phishing threat engines.
Data Encryption Standards (Transit & Rest)
Encryption in Transit
All HTTP communications across Stackly web apps, Chrome Extension, and API endpoints are enforced strictly over HTTPS with modern TLS 1.3 / SSL encryption. Legacy unencrypted HTTP requests are automatically upgraded or rejected.
Encryption at Rest
All database volumes, file uploads, campaign configurations, and system backups are encrypted using industry-standard AES-256 bit encryption at rest across ISO 27001 certified cloud data centers.
Password & Auth Hashing
User passwords are never stored in plain text. We utilize salted, one-way cryptographic key derivation algorithms (bcrypt/argon2 with high work factors) to prevent credential extraction.
Chrome Extension Security & Sandbox Isolation
The official Stackly Chrome Extension (v1.0.2) is engineered to meet Google Chrome Web Store's strictest Manifest V3 security requirements:
Isolated Storage Sandbox
JWT session tokens are stored within isolated chrome.storage.local containers, preventing third-party websites or malicious scripts from accessing authentication keys.
Zero Background DOM Scraping
The extension does NOT execute background content scripts to monitor page DOM, capture keystrokes, or harvest form inputs. Tab URLs are accessed strictly upon explicit user click.
Infrastructure & Edge Network Security
Stackly relies on tier-1 cloud infrastructure providers and edge delivery networks:
- Tier-1 Cloud Hosting (AWS / Render / Vercel)Hosted in SOC 2 Type II, ISO 27001, and PCI-DSS certified data centers with 24/7 physical security, biometric controls, and redundant power infrastructure.
- Cloudflare WAF & DDoS ProtectionEnterprise-grade Web Application Firewall (WAF) filtering layer to instantly neutralize Distributed Denial of Service (DDoS) attacks, automated botnet floods, and HTTP floods.
Anti-Phishing & Automated Threat Engine
To prevent Stackly short links from being abused by malicious actors, every destination link created via our web dashboard or Chrome Extension is analyzed by our real-time threat engine:
Google Safe Browsing Sync
Destination URLs are checked against global malware and phishing threat intelligence databases.
Heuristic Pattern Analysis
Automated scanning for suspicious redirects, typosquatting domains, credential harvest forms, and malicious payloads.
Instant Deactivation
Flagged links are immediately disabled with warning intermissions to protect end-users.
Application & API Security Protocols
- JWT Bearer Token Authentication: Stateless JSON Web Tokens signed with strong cryptographic secrets to validate every API request.
- Strict Rate-Limiting: Adaptive rate limiting headers prevent brute-force login attempts and automated credential stuffing.
- CORS & Security Headers: Strict Cross-Origin Resource Sharing policies, Content Security Policy (CSP), X-Frame-Options, and HSTS headers enforced across all responses.
- Input Sanitization: Strict parameter validation and ORM query parameterized bindings to prevent SQL Injection, NoSQL Injection, and Cross-Site Scripting (XSS).
Database Security & Backup Management
Stackly maintains automated continuous database snapshot backups encrypted at rest with AES-256. Backups are stored across geographically separated cloud availability zones to guarantee rapid Point-in-Time Recovery (PITR) in the event of a disaster.
Compliance & Security Monitoring
Our infrastructure undergoes continuous automated vulnerability scanning and dependency security checks. Security audit logs are maintained for administrative actions to detect suspicious system behavior.
Responsible Vulnerability Disclosure Program
We welcome feedback from ethical security researchers. If you discover a potential vulnerability in Stackly or our Chrome Extension, please report it to our security team at security@stackly.in.
Researcher Guidelines:
- Provide detailed steps to reproduce the vulnerability.
- Do not access or modify user data without authorization.
- Give us reasonable time to remediate the issue prior to public disclosure.
Security Officer & Incident Contact
Security Reporting: security@stackly.in
Support Email: support@stackly.in
SLA Handling: Critical security reports reviewed within 4 hours.