Security and privacy for virtual try-on integrations
Virtual try-on involves customer photographs and production credentials. A responsible integration minimizes collected data, obtains appropriate image consent, keeps license keys on trusted servers, validates inputs, limits abuse, and ensures protected results are shown only to the intended user.
Credential controls
Keep license and webhook secrets outside source control and public clients. Restrict access, redact logs, rotate after exposure, and use separate credentials for separate merchant boundaries.
Image controls
Accept only required formats and sizes, remove unnecessary metadata where appropriate, enforce user consent, and never publish customer images as SEO or analytics content.
Result controls
TryRobe uses protected, time-limited result links. Merchants should avoid shared caching, respect expiry, and prevent one customer's session from accessing another customer's result.
Actual platform protections
The service applies URL safety checks, upload limits, merchant scoping, rate limits, Redis capacity controls, transactional credit locks, idempotency, encrypted sensitive records, signed webhook handling, and short-lived storage delivery.
Frequently asked questions
Does TryRobe claim to be perfectly secure?
No system should make that claim. TryRobe documents concrete controls and continues to review dependencies, configurations, logs, and production behavior.
Can customer photos be sent to GA4?
No. Do not send photos, signed image URLs, names, emails, API keys, or other sensitive content to analytics.