Overview
Security is paramount when integrating third-party services. This guide covers security best practices to protect your users and data.API Key Security
Storage
Environment Variables
Environment Variables
DO:DON’T:
Secrets Management
Secrets Management
Use dedicated secrets management for production:
- AWS Secrets Manager
- HashiCorp Vault
- Azure Key Vault
- Google Cloud Secret Manager
Key Rotation
Key Rotation
Rotate API keys if compromised:
- Contact Sticker support immediately
- We’ll issue a new key
- Update key in secrets manager
- Deploy configuration update
- Old key is invalidated
Access Control
Limit who can access API keys:Request Security
HTTPS Only
Always use HTTPS for API requests:Input Validation
Validate all inputs before sending to API:Rate Limiting
Implement client-side rate limiting:iframe Security
Sandbox Attribute
Use restrictive sandbox permissions:allow-same-origin- Required for authentication cookiesallow-scripts- Required for functionalityallow-forms- Required for search and checkoutallow-popups- Required for payment windowsallow-popups-to-escape-sandbox- Required for Stripeallow-top-navigation-by-user-activation- Required for redirects
allow-top-navigation(without user activation) - Can redirect parent unexpectedlyallow-modals- Can show alerts in parent
Content Security Policy
Configure CSP headers to allow Sticker iframe:Session Token Security
Token Properties
Session tokens are designed with security in mind:| Property | Description |
|---|---|
| Single-use | Invalidated after first authentication |
| Short-lived | Expire after 5 minutes |
| Cryptographic | 64-character random hex (256 bits of entropy) |
| User-bound | Tied to specific user profile |
| Partner-bound | Only valid for your partner iframe URL |
Token Transmission
Safely pass tokens to iframe:Token Lifecycle
Data Security
PII Handling
Only send necessary data to Sticker:Data Encryption
All data is protected:- ✅ All API calls over HTTPS (TLS 1.3)
- ✅ Data encrypted at rest
- ✅ Session tokens are cryptographically random
- ✅ No passwords stored or transmitted
Security Monitoring
Log Security Events
Track security-relevant events:Monitor for Anomalies
Detect suspicious activity:Incident Response
If API Key is Compromised
-
Contact Sticker immediately
- Email: suyash@usesticker.com
- Subject line: “URGENT - API Key Compromise”
- We will revoke the key immediately
- We’ll issue a new key within minutes
- Update your systems with the new key
- Review logs for any unauthorized access
Emergency Contacts
- Partner Support: suyash@usesticker.com
- Schedule Call: calendly.com/usesticker/meeting
Security Checklist
API Keys
- Keys stored in environment variables/secrets manager
- No keys in source code or version control
- Different keys for sandbox and production
- Access limited to backend services only
Requests
- All requests over HTTPS
- Input validation before API calls
- Rate limiting implemented
- Error messages don’t leak sensitive data
iframe
- Sandbox attribute configured correctly
- CSP headers allow Sticker domains
- HTTPS required for parent page
Sessions
- Fresh token generated for each session
- Tokens never cached or stored
- Expired/failed tokens handled gracefully

