Skip to main content

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

DO:
DON’T:
Use dedicated secrets management for production:
  • AWS Secrets Manager
  • HashiCorp Vault
  • Azure Key Vault
  • Google Cloud Secret Manager
Rotate API keys if compromised:
  1. Contact Sticker support immediately
  2. We’ll issue a new key
  3. Update key in secrets manager
  4. Deploy configuration update
  5. Old key is invalidated

Access Control

Limit who can access API keys:
Never expose API keys in:
  • Client-side JavaScript
  • Mobile app code
  • Public repositories
  • Log files
  • Error messages
  • URLs or query parameters

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:
Required permissions:
  • allow-same-origin - Required for authentication cookies
  • allow-scripts - Required for functionality
  • allow-forms - Required for search and checkout
  • allow-popups - Required for payment windows
  • allow-popups-to-escape-sandbox - Required for Stripe
  • allow-top-navigation-by-user-activation - Required for redirects
Avoid unless necessary:
  • allow-top-navigation (without user activation) - Can redirect parent unexpectedly
  • allow-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:

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

  1. Contact Sticker immediately
  2. We will revoke the key immediately
  3. We’ll issue a new key within minutes
  4. Update your systems with the new key
  5. Review logs for any unauthorized access

Emergency Contacts

Security Checklist

1

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
2

Requests

  • All requests over HTTPS
  • Input validation before API calls
  • Rate limiting implemented
  • Error messages don’t leak sensitive data
3

iframe

  • Sandbox attribute configured correctly
  • CSP headers allow Sticker domains
  • HTTPS required for parent page
4

Sessions

  • Fresh token generated for each session
  • Tokens never cached or stored
  • Expired/failed tokens handled gracefully
5

Monitoring

  • Security events logged
  • Anomaly detection active
  • Incident response plan documented

Resources

Partner Support

Get help with security questions

Report Vulnerability

Responsible disclosure