# Seller Decision Diary — consent and data protocol

**Status:** recruitment materials prepared; zero participants and zero observations  
**Protocol date:** August 24, 2026

## Purpose

The diary would document how a self-selected group of watch owners compares selling channels. It is not a market census, price index, appraisal database, lead-generation form, or source of individual selling advice.

## Minimum release threshold

Do not publish aggregates until a named privacy owner, reviewer and publisher approve the consent language and at least 30 usable, consented diaries exist. Small cells must be suppressed when a combination of watch category, value band, location, channel and narrative could re-identify someone. No deadline overrides the threshold.

## Information requested

- broad watch category, never a full serial number;
- broad value band chosen by the participant;
- channels considered;
- count of written offers;
- participant-reported deductions and conditions;
- time from first inquiry to decision in broad bands;
- chosen channel or decision not to sell;
- final net band only when voluntarily supplied; and
- optional evidence-verification status recorded by the researcher without retaining unnecessary documents.

Names, email addresses, exact home/work locations, full serials, account numbers, identity documents, buyer identities, free-text accusations and uploaded ownership records are outside the research table. Contact/consent records must be stored separately from diary responses under an approved retention schedule.

## Consent language draft

> I understand that this is voluntary editorial research, not an appraisal or selling service. I may skip questions or withdraw before anonymized publication. Enjoy Watches will not publish my name, contact details, full watch serial, buyer identity, exact address, or submitted documents. Aggregate findings will describe a self-selected sample and may not represent the wider market. I can ask how my response is used or request deletion before the stated anonymization cutoff by contacting the published privacy address.

This language requires jurisdiction-specific privacy review before recruitment.

## Release rules

Publish the protocol, date range, recruitment channels, response count, missingness, verification levels, suppression rules, conflicts and corrections method. Separate “reported” from “document-checked.” Do not claim causation, typical market outcomes, fraud rates, channel rankings or time-to-sale benchmarks from this opt-in sample.

## Operational checklist

- [ ] Real controller/operator and privacy jurisdiction supplied.
- [ ] Consent, retention, withdrawal and deletion workflow reviewed.
- [ ] Secure form/provider and access roles approved.
- [ ] Contact table separated from research table.
- [ ] Minimum cohort and small-cell suppression implemented.
- [ ] Researcher conflict disclosures recorded.
- [ ] One independent analyst reproduces all aggregates.
- [ ] Participants receive the correction/contact route.