What Frankly sees

Frankly reads text you deliberately select, sends it to be translated, and keeps none of it. This page explains that in full.

Last updated: 12 August 2026

Who runs Frankly

Frankly is built and operated by Oscar Lezama, trading as Zama, an independent one-person software studio. Questions about anything on this page go to hello.franklyapp@gmail.com and I answer them personally.

What leaves your browser

Two things are sent to Frankly's server, and only when you ask for a translation:

The text you selected. Only the current selection, read once at the moment you request a translation. Frankly does not read the rest of the page.
Your licence key. Sent so the server can confirm your subscription is active before doing any work.
Your glossary, if you've added terms. These are sent alongside the selection so translations use your company's own vocabulary.

Nothing is sent when you're simply browsing. No selection, no request.

What happens to that text

The selected text is passed to Anthropic's Claude API to produce the translation, then returned to you. Frankly does not write it to a database, because Frankly has no database.

Anthropic processes the text under their own terms as a service provider. Their privacy policy governs that step: anthropic.com/legal/privacy.

What's stored, and where

On your device

Your licence key and its last known status, in Chrome's synced extension storage. If you use Chrome sync, this travels between your own signed-in browsers.
Your glossary terms, stored locally in the browser.

You can erase both at any time by removing the extension, or by clearing the fields in its popup.

On the server

Frankly's own code stores nothing. However, the request has to reach a server, and that server is operated by Netlify, who keep platform access logs the way any web host does. These may include your IP address and request metadata.

Netlify's documentation states that function logs are retained for at least 24 hours of activity, with longer retention on higher-tier plans. Frankly runs on a plan at the shorter end of that range, but the exact retention is Netlify's to set, not mine. Their policy: netlify.com/privacy.

Payment

Payments are handled entirely by Gumroad, who act as merchant of record. Frankly never sees or handles your card details. Gumroad holds your email address and billing information under their own policy: gumroad.com/privacy.

Frankly's server contacts Gumroad only to ask one question — whether a given licence key is currently valid.

What Frankly never does

No analytics, telemetry, or usage tracking of any kind.
No advertising, and no selling or sharing of data with anyone.
No reading of pages you haven't selected text on.
No logging of your selected text or your licence key.
No remotely loaded code — everything the extension runs ships inside it.
No accounts, no passwords, no profile of you.

Where Frankly runs

The extension only activates on a fixed list of work tools — email, chat, documents, and issue trackers. It does not run on every site you visit, and the full list is visible in the extension's permissions before you install it.

Children

Frankly is a workplace tool and isn't directed at children under 13. I don't knowingly collect information from them.

Your choices

Since Frankly stores nothing about you server-side, there's little for me to delete on request. What exists is on your own device and under your control:

Clear your glossary and licence key from the extension popup.
Remove the extension to erase everything it holds.
For anything Gumroad holds about your purchase, contact them or write to me and I'll help.

Changes to this policy

If Frankly ever starts storing something it doesn't store today, this page changes first and the date at the top updates. Anything that materially changes what happens to your text will also be announced in the extension itself, not buried here.