json410 B

GDPR Messages Export (JSON, SAMPLE)

Standalone SAMPLE messages JSON fragment for privacy-export parsers.

Preview, first 19 linesjson

{
  "subjectId": "usr_sample_002",
  "note": "Fictional SAMPLE messages \u2014 not real correspondence.",
  "messages": [
    {
      "id": "msg_1",
      "ts": "2026-01-05T10:00:00Z",
      "channel": "email",
      "body": "SAMPLE support question"
    },
    {
      "id": "msg_2",
      "ts": "2026-01-06T11:00:00Z",
      "channel": "email",
      "body": "SAMPLE follow-up"
    }
  ]
}

Specifications

Messages: 2
Note: fictional SAMPLE

Testing contract

Expected to pass

Scenario: Exercise GDPR Messages Export (JSON, SAMPLE) in its exports workflow. Standalone SAMPLE messages JSON fragment for privacy-export parsers.
Expected result: top-level keys are subjectId, note, messages; array lengths: messages=2. Declared feature checks: messages=2.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“GDPR Messages Export (JSON, SAMPLE)” is a deterministic Novus Examples fixture for Privacy export testing, Data import. Sample subject-access ZIP packages, DPA/consent templates, and fictional PII, for testing privacy-export parsers and consent UX tooling.

Documented properties for this file: 2 messages. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe, no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.

Code examples

import json

with open("gdpr-messages.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/residuals_wave_h.py. Free for any use, no attribution required, license.