1. Information we handle

Frame Localizer handles only the information reasonably necessary to operate the plugin, process translation requests, manage billing-backed plan access, and maintain service reliability and security.

This may include your Figma user id, entitlement and plan state, locale preferences, translation request content, and related request metadata such as request ids, language pair details, runtime diagnostics, and selection or node context used to execute or troubleshoot translation requests. The plugin may also store limited runtime values in figma.clientStorage and may write limited plugin metadata using setPluginData when needed for plugin behavior, such as preserving translation-source context across repeated runs.

The backend may also store usage counters, translation request logs, billing identifiers and events, and private security-report submissions. If you submit a security report through /security, we may handle the contact details and report contents you provide, along with limited anti-abuse metadata such as request path, user agent, and a one-way hash of the reporting IP address.

2. How we use the information

We use this information to verify plans, process translation requests, apply usage rules, provide billing-backed credits, maintain service reliability, investigate issues, review private security reports, prevent abuse, and operate necessary review or observability tools.

3. Service providers

Frame Localizer relies on third-party service providers for hosting, payment processing, and translation execution. Information shared with those providers is limited to what is reasonably necessary to operate the service flow you use.

4. Billing and payment data

When a Pro checkout is created from the plugin, the service associates the billing event with the current Figma user so the subscription and monthly credits can be applied correctly. The backend may store subscription ids, customer ids, transaction ids, product or price identifiers, billing period dates, subscription status, cancel-at-period-end state, and current credits state.

Payment card handling is delegated to the billing provider shown during checkout. Frame Localizer does not need full card details to operate the subscription state described here.

5. Retention and security

Information may be retained as long as reasonably needed for active service operation, subscription state management, abuse review, troubleshooting, security analysis, private vulnerability handling, and compliance with legal obligations.

For security process details or private vulnerability reporting, use /security. That route is intended for security issues rather than general support or billing questions.

6. Policy updates and related pages

Frame Localizer may update this privacy page as the product, hosting model, billing workflows, or data flows change. Continued use after updates means the service is being used under the then-current published version of this page, subject to any rights required by law.