GDPR Alignment — MoogleWord
Write for free Go Offline

GDPR Alignment

MoogleWord is designed to minimize personal data processing through architectural choice. Your drafts remain local by default, and any optional network features are user-triggered, narrow-scope, and reversible. This page explains how our design maps to key GDPR principles and obligations.

NOTE: THIS IS A PRODUCT ARCHITECTURE SUMMARY — NOT LEGAL ADVICE.
Article 5

Data minimization & purpose limitation

We do not collect document content, keystrokes, or behavioral metadata as part of normal operation. Writing, saving, and exporting happen locally. Where optional features exist (e.g., user-triggered AI), they are isolated and do not create continuous background collection.

Article 25

Privacy by design & by default

Offline-first is the default mode. No account is required, and no cloud workspace is required. Privacy is not a toggle you must remember to turn on — it is the default operating posture.

Article 32

Security of processing

The product reduces systemic risk by eliminating centralized document storage. When you use encrypted folders and local keying, your drafts are protected at rest. Network transport (when used) is designed to be encrypted in transit and limited in scope.

Articles 24 & 30

Accountability & records

Because MoogleWord operates locally without routine server-side processing of drafts, the risk surface is structurally reduced. Where we operate any supporting services (downloads, website, licensing), those are separable from document content and can be described and audited independently.

Questions people ask

Q1 Does MoogleTechnology process user files?
No. Draft content is processed on your device. We do not receive or store your documents by default.
Q2 Is data transferred to the U.S. or third countries?
No systematic transfers exist for draft content. Your work stays where your device is, unless you manually export or share it.
Q3 Is an account required to write?
No. You can use MoogleWord without creating an account or providing an email address.
Q4 How is AI handled?
AI features are user-triggered. Only the text you explicitly select is used for that request, results are returned to you, and the workflow is designed to avoid training on your content.
Q5 Are you a controller or processor of my drafts?
For draft content, we are typically not acting as a controller or processor because we do not receive the content. For separate website operations (e.g., downloads, support inquiries), we may act as a controller for those limited inputs.
Q6 What about telemetry and diagnostics?
If diagnostics exist, they should be optional, minimal, and not include document content. The goal is to keep stability data anonymous and separated from what you write.
GDPR right What it means How MoogleWord supports it
Access (Art. 15) Know what personal data is processed. Draft content stays on your device; you already have direct access. For any website/support data, we can provide a copy upon request.
Rectification (Art. 16) Correct inaccurate personal data. Your drafts are editable locally. For account/support records (if any), corrections can be requested.
Erasure (Art. 17) Delete personal data where applicable. Deleting your local files erases your draft content. For web/support records, deletion requests can be honored where legally permitted.
Portability (Art. 20) Export data in a usable format. Export is built-in (e.g., standard document formats). Because content is local, portability is immediate and not gated by a cloud account.
Objection / restriction (Arts. 18–21) Limit or object to certain processing. Offline-first defaults reduce processing. Optional features should be controllable (enable/disable) and not required to write.
FOR SCHOOLS & EDUCATIONAL INSTITUTIONS

Students can write without being watched.

In environments where privacy matters most, the safest data is the data that never leaves the device. MoogleWord is engineered so writing can happen without accounts, dashboards, or background content collection.