Nativey keeps settings local and sends text only to your chosen provider.

Data Nativey Stores

Nativey stores extension settings in Chrome extension local storage on your browser profile. This can include provider names, provider endpoints, API keys, enabled models, active model selection, prompt preferences, target language, toolbar preferences, and per-site toolbar disable settings.

Data Sent To Model Providers

When you run a transform, Nativey sends the selected text, the selected transform instruction, and related prompt settings to the model provider endpoint configured in the extension. Requests use the API key you added for that provider.

Nativey does not operate a Nativey-hosted backend for transform requests in version 0.0.1. Provider requests are made from the extension to the configured provider endpoint.

Data Nativey Does Not Collect

Nativey does not sell personal information, does not track browsing history for advertising, does not run third-party analytics in the extension, and does not store selected text after the transform flow finishes.

Permissions

Nativey uses Chrome extension permissions to read the current selection, show its toolbar in browser writing surfaces, save local settings, call configured model providers, and replace text only after you approve the result.

Provider Policies

Your configured model provider may process prompts, selected text, and responses under that provider's own terms and privacy policy. Review the provider policy before adding an API key.

Contact

Use the support contact listed on the Chrome Web Store listing for privacy questions, deletion requests, or product support.