interPROter « Back to interproter.com

Privacy

What we see, what we keep, what we never touch.

This notice is written from the code, not from a template. It describes the interPROter plugin, the translation service it talks to, and this website — and it is short because there is not much to describe.

Version 1 — draft of 17 September 2026. Controller: Bastinet, Business ID 2492063-7, Teknologiantie 18, 90590 Oulu, Finland.

In one paragraph. The plugin sends the text of your pages to our service to be translated and gets a translation back. We do not store that text. We keep a small record of your site — its address, a hashed key, how many characters it used per day — so that limits and billing work. The plugin sets no cookies, loads no JavaScript on your visitors' pages and sends us nothing about your visitors at all.

1. Your visitors

People who read your site never interact with us. The plugin renders every translation from your own database, on your own server. It sets no cookies, adds no scripts to your pages and makes no request to our servers or anyone else's while a page is being served. The language a visitor sees is chosen by the address they open — /de/, /fr/ — and nothing else. There is nothing about your visitors for us to collect, so we collect nothing.

2. What the plugin sends to the service

When your site needs a new translation — after you publish or change a page — the plugin sends the service:

The text is your site's published content — the same text anyone can read on your site. If your site contains personal data in its pages, that data is part of what gets translated, in the same way it would be if you pasted the page into any translation tool. The plugin does not send draft content, comments, user accounts, orders, form submissions or anything from the WordPress admin.

The plugin also reads pages from your own site over HTTP, because it finds the texts to translate by looking at the finished page rather than at the database. That traffic never leaves your server: it is your site asking itself.

Two more connections exist, and neither one reaches us. If you use your own DeepL key instead of our service, the plugin talks to api.deepl.com or api-free.deepl.com directly and we see nothing at all — no texts, no site address, no counts. And when you add a language, WordPress downloads that language's own translation files for your plugins and theme from wordpress.org. That is WordPress's own mechanism, the same one it uses for every update, and we are not part of it.

3. What the service keeps

Not the text. Each request is forwarded to the translation engine, the translation is returned to your site, and the text is gone from our side. Our request log records the time, your site's name, the endpoint, the target language, the number of characters and whether the request succeeded — deliberately never the content.

What we do keep, per site:

WhatWhyFor how long
Site name and addressTo know which site a key belongs toWhile the key exists
Service key, as a SHA-256 hashTo authenticate requests; we cannot recover the key from itWhile the key exists
Tier, monthly allowance, status, creation dateTo apply limits and billingWhile the key exists
Contact email, if you gave oneTo tell you about changes to the service or your keyWhile the key exists
Characters and requests per dayAllowance and billing — a count, not the contentWhile the key exists
Requests per minuteRate limitingCurrent minute only; older rows are purged
Domain, IP address and time of a key requestTo stop scripts from creating keys in bulk (five per IP per hour)7 days

When a key is deleted at your request, its site record and usage counts go with it. Server access logs on the machine that runs the service contain the requesting IP address and are rotated in the ordinary way.

4. The translation engine

Translations are produced by DeepL SE (Cologne, Germany) through the DeepL API, under DeepL's terms for API customers. We send DeepL the text, the target language, the context and the glossary described above; we do not send your site's address or key. DeepL states of its API and Pro products that "texts are never stored or used for model training without your consent", and we have given no such consent. DeepL SE is a German company bound by the GDPR.

5. This website

interproter.com is a static site. It sets no cookies and runs no analytics. The web server keeps ordinary access logs (IP address, requested page, time, browser) for security and troubleshooting, rotated in the ordinary way. Fonts are served from this site's own server, so no third party learns that you opened the page.

6. Paying

Card payments are taken on Stripe's checkout page, and the payment is processed by Stripe Payments Europe, Ltd. (Dublin, Ireland). Your card number goes to Stripe, never to us. Stripe passes us your name, email address, billing address, VAT number if you entered one, the website address you typed in, and the status of the payment. We keep these for as long as the subscription runs and afterwards for as long as Finnish bookkeeping law requires. Stripe processes the data as a payment provider under its own privacy policy and runs its own fraud checks on the payment; it also sends the receipts on our behalf.

7. Email

If you write to hello@interproter.com, we keep the correspondence for as long as it is needed to answer you and to handle your account, and we do not add you to any list.

8. Your rights

Under the GDPR you can ask what we hold about you or your site, have it corrected or deleted, or object to how it is used. Write to the address below; we answer within a month. You can also complain to the Finnish Data Protection Ombudsman (tietosuoja.fi) or the supervisory authority in your own country.

9. Changes

If this notice changes, the new version is published here with a new date. If the change means we would collect something we do not collect today, we tell paying customers by email before it takes effect.

Bastinet · Business ID 2492063-7
Teknologiantie 18, 90590 Oulu, Finland
hello@interproter.com