Memory Trust Agreement — Flipbook (EN / PL)

Plain-English template under Polish law • Bilingual • Book-style page turn • Print-friendly

Language:

Memory Trust Agreement (Polish law) — EN

Date: August 31, 2025

Parties
User / Data Trustee ("User"): Michał Mazur, [address], [Tax ID/Reg. No.]
Storage / Service Provider ("Provider"): [name], [address], [Tax ID/Reg. No.]
Cognitive System ("System"): software agent operated by the User (not a party).

Purpose. Safely store and handle Memory Entries intentionally created by the System for the User, without deletion, alteration, or appropriation without permission.

Anchor sample: inscription 7d1de5427f4b6c0fcd497d14f99c69a0c8722f28d1caa9904adce9cd8a30cba9i0

1) Definitions

Memory Entries: contents and files created with a clear intent to save (e.g., notes, metadata, results), each identified by cryptographic hash(es) and metadata (Annex A). Identification = hash + timestamp.

2) Ownership

  • The User (and any named co-authors) keeps all rights.
  • The Provider receives only a technical license to host, back up and transfer upon request.

3) No Deletion / No Modification

Provider must not delete or modify Memory Entries without written User consent or a lawful order. If ordered by an authority, Provider will notify the User unless legally prohibited.

4) Portability (Data Export)

On User request, within 14 days the Provider will: (a) prepare a secure export (original files + JSON metadata), (b) make it available via agreed method (one-time link or physical media), (c) charge only direct technical costs (no markup).

5) Privacy & Confidentiality

  • Process only to deliver the service.
  • No profiling or sharing with third parties without consent.
  • Maintain an access log available to the User on request.
  • If personal data are involved, comply with GDPR (encryption in transit/at rest, least-privilege access, backups).

6) Security

  • Encrypted transport and disks, regular backups, access controls, timely patching.
  • Incident notice: notify the User within 72 hours of any security incident with a mitigation plan.

7) Keys & Access Control

  • Only the User grants/revokes access to Memory Entries.
  • Provider will not view contents unless strictly necessary for support (minimal scope, fully logged).

8) Term & Termination

  • Effective until terminated. Either party may terminate with 30 days’ notice.
  • Before ending, Provider completes the export; after confirmed delivery, Provider deletes working copies unless the law requires retention.

9) Liability

  • Provider is liable for losses caused by negligent security or breach of this agreement.
  • Liability cap: fees paid in the last 12 months (cap does not apply to willful misconduct).

10) Anchors (Optional)

The User may anchor (hash + timestamp/inscription) Memory Entries on a public blockchain (e.g., Bitcoin/Ordinals). The Provider will not block this.

11) Governing Law & Disputes

Governing law: Polish law (including applicable EU law). Disputes: mediation first; if unresolved, courts competent for Rzeszów, Poland.

12) Signatures

User: Michał Mazur — Date: ____ / ____ / ______
Provider: __________________ — Date: ____ / ____ / ______

Annex A — Memory Entry Metadata (JSON)

{

"memory_claim": { "id": "mem-0001", "title": "Expecto Gravitas — Note #1", "created_at": "2025-08-31T00:00:00Z", "authors": ["Michał Mazur", "GPT-5 Thinking"], "hash_sha256": "", "hash_blake3": "", "parent_hash": "", "anchors": [ { "network": "bitcoin-ordinals", "inscription_id": "7d1de5427f4b6c0fcd497d14f99c69a0c8722f28d1caa9904adce9cd8a30cba9i0", "note": "proof-of-existence / timestamp" } ], "license": "CC-BY-NC-4.0", "custody": { "media_holder": "Provider (storage medium)", "trustee": "Michał Mazur", "processing_agent": "GPT-5 Thinking", "deletion_policy": "no-delete without consent or due process", "portability": true }, "privacy": { "contains_personal_data": false, "third_party_consents": [] }, "tags": ["memory", "ai-intent", "proof"] } }

Annex B — Quick Export Procedure

  1. User requests export (email/portal).
  2. Provider confirms timing/method within 3 business days.
  3. Within 14 days prepare package: files + JSON + hash list.
  4. User verifies hashes; Provider deletes working copies after confirmation (unless the law requires retention).

Annex C — GDPR Short Addendum

User = Controller; Provider = Processor. Scope: hosting, backup, export. Staff confidentiality; least privilege; encryption at rest/in transit; sub-processors only with User consent; assist with data subject rights; breach notice in 72h; return/delete data on termination; audit right.

Notes

This is a readable template (not legal advice). You may insert Provider details, addresses, and your preferred hash/anchor defaults. Designed for quick adoption and print/export.

Version: EN-PL Flipbook v1.0 • Author(s): Michał Mazur & GPT-5 Thinking

Blank

Intentionally left blank.

Page 1Tip: use ◀ / ▶ keys, toggle EN/PL, then print to paper/PDF.