Skip to content

GDPR Article 6(1) — Translation Analysis (GDPR-001)

Source: Regulation (EU) 2016/679 (GDPR), Article 6(1) Batch: GDPR-001 Sentences: S925–S931 New entries: none

Source text

Article 6(1) in functional paraphrase:

Processing shall be lawful only if and to the extent that at least one of the following applies: consent; contract; legal obligation; vital interests; public task / official authority; legitimate interests.

This batch is not a line-by-line legal translation. It is a structural stress test: can Tonesu render the article as a list of lawful bases without pretending the six bases are all the same kind of thing?

The answer is yes, but only if the article is modeled as a permission battery over one repeated act rather than as a taxonomy of six data categories.

Vocabulary framework

Form Reading Notes
lo-ka-to-ki lo-to-si ne i-zo-li the act of processing a person's personal data repeated legal object of the batch
ne-vo-wi consent relational convergence of will and value; here attached to the act
ne-to-fe contract formally bounded agreement
wi-fe-su legal rule / legal obligation structure institutional rule-source
zo-ra vitality / life-energy used to model vital-interests emergency
wi-ra official authority authority, not merely rule
~vo-ne ~legitimate-interest structurally vague rightful-interest claim
no-wi-fe-ka permitted / not forbidden the repeated outcome of every lawful basis

Sentence analyses

go {la-i-zo-li  ne  ne-vo-wi  lo-ka-to-ki  lo-to-si  ne  i-zo-li},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {laizoli ne nevowi lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka

Natural reading: When the person consents to the processing of that person's personal data, the processing is permitted.

Notes: Consent is attached to the act, not treated as a general favorable attitude. That matches the article's actual function: consent authorizes a particular processing relation. no-wi-fe-ka keeps the deontic force right: consent permits; it does not compel.

S926 — GDPR-001-B: Contract basis

go {la-ne-to-fe  ne  wi-fe  lo-ka-to-ki  lo-to-si  ne  i-zo-li},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {lanetofe ne wife lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka

Natural reading: When a contract requires the processing of a person's personal data, the processing is permitted.

Notes: The source of normativity is the bounded agreement itself. This keeps contract distinct from public rule even though both end in permission.

go {la-wi-fe-su  ne  wi-fe  lo-ka-to-ki  lo-to-si  ne  i-zo-li},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {lawifesu ne wife lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka

Natural reading: When a legal rule requires the processing of a person's personal data, the processing is permitted.

Notes: This looks close to S926 in English, but Tonesu keeps the source separate: wi-fe-su is institutional rule structure, not private contract.

S928 — GDPR-001-D: Vital-interests basis

go {la-i-zo-li  zo-ra  de},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {laizoli zora de}, lokatoki lotosi ne izoli nowifeka

Natural reading: When a person's vitality is in danger, the processing of that person's personal data is permitted.

Notes: zo-ra gives the article's emergency basis an organism-level anchor. This is the least category-fuzzy basis in the list.

S929 — GDPR-001-E: Public-task / official-authority basis

go {la-ka-li-su  ne  wi-ra  lo-ka-to-ki  lo-to-si  ne  i-zo-li},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {lakalisu ne wira lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka

Natural reading: When governance has official authority over the processing of a person's personal data, the processing is permitted.

Notes: This is the article's public-task basis rendered through wi-ra. The distinction from S927 matters: rule (wi-fe) and authority (wi-ra) are not the same thing.

S930 — GDPR-001-F: Legitimate-interests catch-all

go {la-ze  ne  ~vo-ne  lo-ka-to-ki  lo-to-si  ne  i-zo-li},  lo-ka-to-ki  lo-to-si  ne  i-zo-li  no-wi-fe-ka

Written: go {laze ne ~vone lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka

Natural reading: When another party has ~rightful-interest in processing a person's personal data, the processing is permitted.

Notes: This is the article's most revealing basis. ~vo-ne marks that the vagueness belongs to the statute itself. "Legitimate interests" is not a clean category like consent or contract; it is a source-system approximation that stays useful precisely because its edge remains soft.

S931 — GDPR-001-G: Structural verdict

la-wi-fe  ne  no-su-to  /  ke,  la-wi-fe  no  to-su-ki  lo-to-fe  {ne-vo-wi ; ne-to-fe ; wi-fe ; wi-ra ; ~vo-ne}

Written: lawife ne nosuto / ke, lawife no tosuki lotofe {nevowi ; netofe ; wife ; wira ; ~vone}

Natural reading: The rule is not a self-evident truth / but the rule has not comprehended the boundary among consent, contract, legal obligation, authority, and ~legitimate-interest.

Notes: Article 6(1) works as law without resolving the relations among its own categories. That is not a drafting accident. It is the article's operating strategy.

GDPR-001 Batch Summary

Entry Tonesu Written Claim Key feature
S925 go {la-i-zo-li ne ne-vo-wi lo-ka-to-ki lo-to-si ne i-zo-li}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {laizoli ne nevowi lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka consent basis consent as act-specific relation
S926 go {la-ne-to-fe ne wi-fe lo-ka-to-ki lo-to-si ne i-zo-li}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {lanetofe ne wife lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka contract basis bounded agreement as norm-source
S927 go {la-wi-fe-su ne wi-fe lo-ka-to-ki lo-to-si ne i-zo-li}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {lawifesu ne wife lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka legal obligation basis rule structure as norm-source
S928 go {la-i-zo-li zo-ra de}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {laizoli zora de}, lokatoki lotosi ne izoli nowifeka vital-interests basis vitality-threat emergency
S929 go {la-ka-li-su ne wi-ra lo-ka-to-ki lo-to-si ne i-zo-li}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {lakalisu ne wira lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka public-task basis authority distinct from rule
S930 go {la-ze ne ~vo-ne lo-ka-to-ki lo-to-si ne i-zo-li}, lo-ka-to-ki lo-to-si ne i-zo-li no-wi-fe-ka go {laze ne ~vone lokatoki lotosi ne izoli}, lokatoki lotosi ne izoli nowifeka legitimate-interests basis structural-vagueness catch-all
S931 la-wi-fe ne no-su-to / ke, la-wi-fe no to-su-ki lo-to-fe {ne-vo-wi ; ne-to-fe ; wi-fe ; wi-ra ; ~vo-ne} lawife ne nosuto / ke, lawife no tosuki lotofe {nevowi ; netofe ; wife ; wira ; ~vone} batch verdict list functions but overlaps structurally

Key findings:

  1. GDPR 6(1) is best modeled as a repeated permission result over one legal object, not as a taxonomy of six different processing types.
  2. Contract, rule, and authority remain distinct in Tonesu even when they all suspend prohibition.
  3. The article's catch-all basis is ~-marked from the start; "legitimate interests" is structurally vague by design.
  4. The list works administratively better than it classifies conceptually.

Colloquial Register Analysis

Form used CLQ entry Colloquial form Notes
ka-to-ki none — technical processing form
ne-vo-wi none — consent form — load-bearing
ne-to-fe none — formal bounded agreement
wi-fe-su none — institutional rule form
wi-ra none — authority form — load-bearing
~vo-ne none — structural-vagueness form
no-wi-fe-ka none — repeated deontic operator

Verdict: irreducibly formal — the batch's whole point is to preserve category distinctions and show where the statute itself keeps them blurry.

CLQ entries registered from this batch: none.