<!-- contracts.md starter: data-handling. What data an agent may use, what it keeps and for how long. Every name, number and date is an example: replace each with what the parties stated, run check_contract, and keep status draft until the person says the agreement is in force. A record of terms, not a contract; not legal advice. -->
# CONTRACTS.md

- format: contracts.md/1
- owner: agent:reply-drafter
- updated: 2026-10-23
- currency: USD

## Support ticket data handling

- id: support-ticket-data
- status: draft
- parties:
  - data_owner: the support team
  - processor: agent:reply-drafter
- scope: The agent may read exported support tickets to draft replies, and keeps them no longer than the limits below.
<!-- Uses of the data, as tags: in_scope is allowed, out_of_scope never, needs_approval only after the person says yes. -->
- in_scope: read-tickets, draft-replies, redact-personal-data, delete-on-request
- out_of_scope: model-training, sharing-outside-the-team, marketing, profiling
- needs_approval: new-data-fields, retention-extension, bulk-export
- deliverables:
  - 2026-12-01: data inventory listing every field the agent reads
  - 2027-04-30: deletion log for the first half year
<!-- No fee for this record, so the price is 0; tools still read it. -->
- price: 0 USD per month
- payment: net 30
- service_levels:
  - deletion_time: at most 7 days
  - incident_notice_time: at most 24 hours
<!-- Count limits: days to keep data, and records per export. scope_check checks them when you send usage. -->
- limits:
  - retention: 30 days
  - backup_retention: 90 days
  - records_per_export: 500 records
<!-- liability_cap: add the figure the parties stated, if any. Never compute or suggest one. -->
- term: 2026-11-01 to 2027-10-31
- notice: 30 days
- renewal: renegotiate
- dispute: the parties talk first, then follow the path they name here
- notes: retention counts from the day a ticket is exported; deletion_time counts from a deletion request