Privacy policy · Translated Page Copies

In short

The plugin runs inside the Framer editor, in your browser. I run no server for it, and nothing you translate is ever sent to me.
The text you translate goes only to the provider you pick: OpenAI, Anthropic or Google Cloud Translation, straight from the plugin, with your own key. The file route (CSV or XLIFF) sends nothing anywhere.
Licence checks go to Lemon Squeezy (api.lemonsqueezy.com), with your licence key and an activation ID only.
Your provider keys, licence and preferences are kept in your browser’s local storage, on your device, never in your project.
The plugin stores small markers in your Framer project (source fingerprints, languages and settings) so it can keep copies in sync. Everyone with access to the project can see them.
There are no analytics, no tracking, no cookies of mine and no ads.

Who this policy covers

This policy covers the Framer plugin Translated Page Copies (“the plugin”), made by Christian Ortiz, an individual publishing as Christian Ortiz Studio (“I”, “me”). It explains what the plugin does with your data while it runs in the Framer editor, what happens when you buy a licence, and how I handle the information you share with me.

It doesn’t cover Framer itself, which is governed by Framer’s privacy policy; the translation provider you choose, which is governed by its own terms and privacy policy under your account with it; or Lemon Squeezy’s checkout, which is governed by Lemon Squeezy’s privacy policy.

Questions about this policy: support@christianortiz.studio.

What the plugin reads in Framer

Framer runs the plugin in a separate frame inside the editor and gives it the Framer plugin API. The plugin reads:

Your web pages: their names and paths, and the text layers on the pages you select (their names and text). To read a page that isn’t loaded yet, it opens that page in the editor and then returns to the page you were on.
Your CMS collections: their names, fields and items, for the collections you select.
Links on the copies it makes, to point them at the translated pages.
Your code files and the site’s custom code, only to find its own language switcher and hreflang snippet.
What you’re allowed to do in this project, so it can tell you if you’re in view-only mode.

What it reads is used in the plugin’s memory to scan, translate and write, and is gone when you close the plugin, except what’s described below.

What the plugin writes to your project

Only when you click Apply, Insert switcher or Add to site custom code:

Copies of the pages you chose, as drafts, at the language path (for example /fr/pricing), with translated text and their links pointed at other copies.
Translated collections, such as Blog (FR), with their items.
A LanguageSwitcher code file.
The hreflang snippet in the site’s custom code, only after you tick the box to agree. It runs on your published site and adds alternate link tags to each page; it sends nothing anywhere.

Your source pages and collections are never changed. Every write goes through Framer’s plugin API, so you can undo it in the editor.

Plugin data stored in your project

To keep copies in sync, the plugin stores small records with Framer’s plugin data, which every member of the project can read:

Settings, languages and the glossary, at project level.
On each copy page: which page it was copied from, the source and copy paths, the language, a fingerprint of the source page and when it was last applied.
On each copied text layer and translated CMS item: which source layer or item it came from, a fingerprint (hash) of the source text, the language, and whether you skipped it. The copy’s own text is the translation, so this is the translation memory.
On each translated collection: which collection it came from, the language, its item count and when it was last applied.

Forget translation history in Help clears the markers. Removing the plugin doesn’t delete them; deleting the copies or the project does.

What it sends over the network, and to whom

The text to translate, to the provider you choose, with your key. When you choose Translate, the plugin sends the new or changed strings, the language pair and your glossary terms directly from your browser to that provider, using your API key: OpenAI (api.openai.com), Anthropic (api.anthropic.com) or Google Cloud Translation (translation.googleapis.com). Test key in Engine settings sends one tiny request. Nothing is sent to a provider you haven’t chosen, and nothing passes through me. The provider processes the text under its own terms and your account with it, and bills you for the usage. Don’t translate content you aren’t allowed to send to that provider.
The file route sends nothing. Exporting and importing CSV or XLIFF files happens in your browser. Where you take the file afterwards is up to you.
Licence check, to Lemon Squeezy (api.lemonsqueezy.com). When you activate a key, the plugin sends the licence key and the label Framer plugin. Later checks (when you open the plugin and the last check is more than 7 days old), and Deactivate on this browser, send the licence key and the activation ID Lemon Squeezy gave it. Lemon Squeezy answers whether the key is valid and for which product. Like any website, Lemon Squeezy also receives your IP address and browser details with each request. Nothing from your project is sent.
The Inter font, from Framer. The plugin’s interface uses Framer’s own stylesheet, which loads the Inter font from Framer’s servers.

Links in the plugin (Buy Pro, Refund policy, Documentation, Support, Privacy, the providers’ pricing pages) open in a new browser tab only when you click them.

What it keeps on your device

The plugin keeps these records in your browser’s local storage for the plugin, on your own device. They’re never written to your project, and they never leave your device, except your keys as described above.

Provider keys: for each provider you save, the API key, the model name and when you saved it. A saved key is shown only by its last four characters.
Licence: your licence key, its activation ID, its status and when it was last checked (for the 30-day offline grace period).
Preferences: the engine and file format you used last.
Last run report: the report of your last run in each project (page paths, counts and manual steps), so Home can show it again.
Tour: whether you’ve seen the first-run tour.

To delete them: Remove key in Engine settings deletes a key; Deactivate on this browser deletes the licence; clearing your browser’s site data removes all of them. If your browser blocks storage, the plugin keeps them in memory until you close it.

Buying a licence

The Pro licence is sold through Lemon Squeezy, which acts as the reseller (merchant of record): it runs the checkout, takes the payment, handles sales tax, sends the receipt and the licence key, and processes refunds. Framer doesn’t take part in the payment. The plugin never sees your payment details.

As the seller, I can see in Lemon Squeezy what it shares with sellers about each order: your name, email address, country, what you bought and when, the price paid, refunds, and the licence key with its activations. I use this only to provide the licence, support and refunds, and to keep the business and tax records the law requires. I keep it for as long as those purposes need, and no longer than tax law requires for records.

I don’t add you to a mailing list, and I don’t send marketing email.

Support emails

If you email me, I receive your email address, your name if you include it, and whatever you write and attach. I use it only to answer you, and delete it when you ask, unless I need to keep it for a legal reason. Please don’t send me your API keys.

Who’s responsible for your data

Your project’s content never reaches me. It’s processed by the plugin on your device, and by the translation provider you choose, under your own account and agreement with that provider.
For your purchase and licensing data and your support emails, I’m the controller. Lemon Squeezy is a separate controller for the checkout and payment, under its own policy.
Under the California Consumer Privacy Act, I don’t sell or share personal information.

I don’t sell, rent or share your data. The plugin’s only third parties are Framer, the platform it runs in; the translation provider you choose, which you contract with yourself; and Lemon Squeezy, which sells the licence and checks keys. I’d disclose information only if the law required me to.

Security

No project content passes through a server of mine, so there’s nothing of yours on my side to protect or lose.
Provider calls and licence checks go over HTTPS, directly to the provider or Lemon Squeezy. The plugin never contains or needs a secret of mine.
Your API keys and licence key are kept in your browser’s storage for the plugin, not in your Framer project, so other members of a shared project can’t read them, and they never appear in plugin data, reports or exported files.
Security contact: email support@christianortiz.studio with Security in the subject line. I acknowledge security reports within two business days.

Your rights

Depending on where you live, you may have the right to access, correct, delete or move your personal data, or to object to how it’s used. Email me and I’ll respond within 30 days.

Children

The plugin is a professional tool for building websites and isn’t directed at children.

Changes to this policy

If I change this policy, I’ll update the date at the top of this page. If a change affects how your data is handled in a meaningful way, such as a new network request, I’ll also say so in the plugin’s Marketplace listing before it takes effect.

Contact

Christian Ortiz, publishing as Christian Ortiz Studio
support@christianortiz.studio