Frenmot
Privacy Policy
Last updated: May 25, 2025
1. Introduction
Frenmot ("we", "our", "the app") is a client-side language-learning web application. We are committed to protecting your privacy. This policy explains what data the app handles, how it is stored, and your rights regarding that data.
2. Data We Collect
Frenmot is designed with a privacy-first, local-first architecture. We do not operate backend servers that collect or store your personal data. Specifically:
- Account information — A display name, optional email, and language preference you provide during setup. This is stored only on your device.
- Vocabulary, progress, and settings — All learning data (words, SRS schedules, PDF text, chat history, review stats) is stored locally in your browser.
- API keys — If you connect an AI provider (OpenAI, Google Gemini, Groq, NVIDIA), your API key is stored locally on your device with lightweight obfuscation. It is never transmitted to any Frenmot server.
3. How Your Data Is Stored
All app data lives in your browser, using two layers for durability:
- localStorage — Primary read/write layer. Fast and synchronous.
- IndexedDB — A mirror copy with a much larger quota. If localStorage is cleared, Frenmot transparently restores your data from this mirror on the next load.
We also request "persistent storage" from your browser when supported, asking it not to evict Frenmot's data under disk pressure.
Clearing all browser site data (cookies, cache, and storage together) will permanently delete your local data, so we recommend exporting a backup periodically from Settings → Data → Export.
4. Third-Party Services
When you use AI features, your prompts and vocabulary context are sent directly from your browser to the AI provider you configured (OpenAI, Google, Groq, or NVIDIA) using your own API key. Frenmot does not proxy, log, or store these requests. Each provider's own privacy policy governs how they handle your data:
We also load the following external resources:
- Google Fonts (Inter, Fraunces) — subject to Google's Privacy Policy.
- PDF.js from cdnjs — no personal data is transmitted.
5. Data We Do NOT Collect
- We do not use analytics, tracking pixels, or advertising SDKs.
- We do not collect IP addresses, device fingerprints, or usage telemetry.
- We do not sell, rent, or share any user data with third parties.
- We do not store any data on Frenmot-operated servers — there is no Frenmot server.
- We do not sync data to the cloud.
6. Cookies
Frenmot does not set any cookies. All persistence uses browser localStorage and IndexedDB.
7. Children's Privacy
Frenmot is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided data through the app, please contact us so we can advise on clearing it.
8. Your Rights
Because all your data is stored locally on your device, you have full control:
- Access — Open Settings → Data → Export to download all your data as JSON.
- Deletion — Open Settings → Data → Reset to permanently delete all local data (clears both localStorage and IndexedDB).
- Portability — The exported JSON file is human-readable and can be imported into another Frenmot instance.
9. Security
API keys are stored with lightweight XOR obfuscation to prevent casual exposure in browser DevTools. This is not encryption — it is a best-effort measure for a client-side app. For stronger security, we recommend using API keys with spending limits and revoking them if your device is compromised.
All network requests to AI providers and Google APIs use HTTPS exclusively.
10. Changes to This Policy
We may update this policy as the app evolves. The "Last updated" date at the top reflects the most recent revision. Continued use of the app after changes constitutes acceptance.
11. Contact
If you have questions about this privacy policy, please open an issue on the project's GitHub repository or contact the developer directly.