Privacy Policy

Effective date: November 18, 2026

This policy explains what personal data Langferry collects, why, how long we keep it, who helps us process it, and the choices you have. It covers this website (langferry.com), the Langferry dashboard at app.langferry.com, and the Langferry service that the Langferry WordPress plugin connects to (together, the “Service”).

1. Who we are

Langferry is a product of PageAuthority Inc., a Massachusetts corporation (“Langferry”, “we”, “us”). For anything about this policy or your data, email [email protected].

2. Our two roles

  • Your account. When you sign up and use the dashboard, we decide how your account data is used. For that data we are the controller (or “business”).
  • Your website’s text. When your WordPress site sends us text to translate, we process it only to provide the Service to you. For that content we act on your behalf, as your processor (or “service provider”). You remain responsible for telling the visitors and customers of your own website how their data is handled.

3. What we collect, why, and for how long

DataWhyHow long we keep it
Account name, billing status, Stripe customer IDRunning your account and billingUntil the account is deleted
Each user’s name, email address, role and sign-in timesSigning inUntil the user or the account is deleted
PasswordSigning inStored only as an Argon2 hash, never in plain text
Failed sign-in attempts: the email address tried, IP address and timeSlowing down password guessingAbout a day
Password reset tokensResetting a passwordStored only as hashes; each works for one hour
Sites: address, name, settings, glossary, plugin, WordPress and PHP versions, number of translated stringsRunning the ServiceUntil the site is deleted
Site API keys and one-time connect codesLetting the plugin connectStored only as hashes
Characters translated per site each month, and daily totalsAllowances and limitsPer site for as long as the site exists. When a site is deleted, its monthly totals are kept under its domain name, with no link to your account, so that domain’s allowance can’t be reset
Translation cache: machine translations of text sent by sites, stored under a fingerprint (hash) of the source textNot paying twice for the same translationUntil it has gone 12 months without being used. Text from order emails and from pages shown to signed-in visitors is never kept in this shared cache
Support topics: the subject and messages you write, who wrote each, the site you chose, and a snapshot of your account and site when the topic was opened: the account’s name, ID and standing (for example suspended or payment failed), the opener’s name, email address and whether it is confirmed, the site’s ID, name and address, its plan, billing (monthly, yearly, free or invoiced) and trial end date, its plugin, WordPress and PHP versions, when it last connected and its connection status, whether it is verified, its URL mode, default language and languagesAnswering your support requestsUntil 24 months after the topic’s last activity once it is closed; an open topic stays until closed. Deleted with your account
Session cookie (signed): your user ID and a security tokenKeeping you signed in to the dashboard14 days
Server and network logs: IP addresses, requested addresses, timesSecurity and troubleshooting14 days on our web server; our hosting and network providers keep their own short-term logs under their policies

What we never store: card numbers, card security codes, bank details, plain-text passwords or plain-text API keys. The billing page shows your card’s brand, last four digits and expiry date, which it reads from Stripe each time you open it.

4. Text from your website

The Langferry plugin translates pages inside your WordPress site. It sends us only pieces of text (segments) that it has not translated before, together with your site’s address and the language pair. We never fetch your pages, and we never receive your visitors’ requests, IP addresses or cookies: the plugin talks to us from your server.

Those segments may contain personal data, depending on what your site shows:

  • Text on any page the plugin translates, including pages shown to signed-in visitors, such as a shop’s account or order pages. You can exclude pages by path, or parts of pages by CSS selector, in the plugin settings.
  • If you use WooCommerce email translation, the text of customer emails about orders, which can include a customer’s name, address and order details.

We send each new segment to a machine translation provider (see Subprocessors) and keep the result in the translation cache described above. The cache is shared between customers: a stored translation is reused only when exactly the same source text is sent again for the same language pair, so a site only ever receives translations of text it sent itself. The translations your site uses are stored in your own WordPress database.

Edits you make to translations in the plugin’s translation editor stay in your WordPress database and are not sent to us.

5. Payments

Payments are handled by Stripe. You enter card details only on Stripe’s own pages, and Stripe sends them straight to its systems; we never see or store them. Stripe receives your name, email address, card and billing details, and keeps invoices and payment records. Stripe’s own privacy policy applies to its processing.

6. Emails

Langferry itself sends sign-up links (or, when the address already has an account, a note saying so with sign-in and password reset links), password reset emails, emails to confirm your address or a change of your sign-in email (and a notice of that change to your old address), notices about your usage (for example when a site nears its allowance) and replies to your support topics, through our email provider. When you write in a support topic, our support team may also get a notice by email that quotes your message with your name, email address, account and site (see section 7). We send them because they are part of running your account, not for marketing. Stripe sends receipts, invoices, refund receipts, renewal reminders and notices about failed payments or expiring cards. We don’t send marketing emails. If that changes, we’ll ask for your consent where the law requires it, and every message will have an unsubscribe link.

7. Support

When you open a support topic in the dashboard, we store its subject and messages, the site you picked, and a snapshot of your account and site (the details listed in section 3). We never include your API key, password or payment details, and the dashboard refuses messages that contain a Langferry API key. Please don’t put passwords or other secrets in a message.

Our support team works from a private channel in Slack (Salesforce), where each topic’s subject and messages, your name and email address, your account name and its standing (for example suspended or payment failed), your site’s name and URL, your plan and billing, your plugin, WordPress and PHP versions, and whether your site is connected or when it last connected are posted, and where our team’s replies are written. When Slack isn’t set up, can’t take a message, or may no longer show a topic’s thread (after 80 days), your message, with your name, email address, account name and its standing, and your site’s name and URL, is emailed to our support team by our email provider instead of or as well as being posted. Replies are emailed to your confirmed sign-in address by our email provider. If we use Trello (Atlassian) to track topics, it receives the topic’s reference, its subject, your account name, your site’s name and URL, the status and a link to our staff console, never the message text or your email address. See Subprocessors.

A closed topic is deleted from our database 24 months after its last activity. When you delete your account, we delete your topics and ask Slack and Trello to delete the messages and card our application posted, and we retry if they fail. Our team’s own replies in Slack are typed by people, so our application can’t delete them; they stay in our Slack workspace until Slack removes them under the workspace’s retention settings. The data download in your account includes your topics and the messages you can see, not our internal notes.

8. Cookies

  • Dashboard (app.langferry.com): one strictly necessary session cookie that keeps you signed in. It is not used for tracking.
  • This website (langferry.com): no analytics, advertising or tracking cookies. WordPress sets its own cookies only if you sign in to this website’s admin area. If we add analytics, we’ll update this policy first and ask for consent where required.

9. Who we share data with

We share data only with the providers that help us run the Service, listed with what each receives on our Subprocessors page. We also disclose data when the law requires it, to protect our rights or users’ safety, or to a buyer or successor if the business is sold, under terms that keep this policy’s protections. We don’t sell personal data, and we don’t share it for advertising.

10. Your choices and rights

You can do most of this yourself in the dashboard:

  • See your data: Account → Download your data gives you a JSON file with your account, users, sites, settings, usage and support topics. Invoices and your card are in Stripe, which you can reach from Billing.
  • Correct it: Account → Profile.
  • Delete it: Account → Delete account (account owner only; your password is required). This deletes the account, its users, sites, settings and usage, and deletes your Stripe customer record, which cancels subscriptions and removes saved cards. Past invoices stay in Stripe because we must keep accounting records. For each deleted site, its monthly character totals are kept under its domain name, with no link to your account, so neither re-adding the site nor a new account can reset a used allowance. Deleted data can remain in our database backups for up to 7 days, until they expire.

Depending on where you live, you may also have the right to object to or restrict some processing, to receive your data in a portable format, to withdraw consent, and to complain to your local data protection authority. To use any of these rights, email [email protected]. We’ll answer within the time the law sets and may need to confirm your identity first.

Where these laws apply, we rely on: performing our contract with you (your account, the Service, support and billing); our legitimate interests (security, preventing abuse, troubleshooting, and the shared translation cache that keeps prices down); and legal obligations (keeping accounting records).

Our servers are in the United States, and some providers process data in other countries. We serve customers worldwide, including in the EEA, the UK and Switzerland. When personal data leaves those regions, we rely on the Standard Contractual Clauses (and the UK and Swiss equivalents) in our providers’ data processing terms.

12. Security

Our websites are served over HTTPS. Passwords are stored only as Argon2 hashes, and API keys, connect codes and reset tokens only as hashes. Card details are entered only on Stripe’s pages. Failed sign-ins are throttled. No system is perfectly secure; if a breach affects your data, we’ll tell you and the authorities as the law requires.

13. Children

The Service is for businesses and website owners. It is not directed at children, and we don’t knowingly collect children’s personal data. If you believe a child has given us personal data, email us and we’ll delete it.

14. Changes to this policy

When we change this policy, we’ll update the effective date above. If a change is significant, we’ll also email account owners before it takes effect.

15. Contact

PageAuthority Inc. (Langferry)
[email protected]