Privacy and data rights
Understand purpose limits, minimization, visibility, retention, export, correction, and deletion boundaries.
ZYNC processes identity, membership, Mission activity, submitted proof, verification decisions, rewards, safety events, and Sponsor reporting. Each category needs a defined purpose and visibility boundary.
Core principles are:
- collect only what the action needs;
- state why information is required;
- limit access by responsibility and Space;
- minimize Sponsor data;
- keep records only as long as a defined purpose requires;
- provide correction, access, export, and deletion paths where applicable;
- record exceptions that must remain for safety, disputes, rewards, or legal duties.
Rights requests cross several domains
A request may touch identity, proof, rewards, analytics, and integrations. ZYNC needs a coverage record showing which systems were searched and what happened in each one.
Deletion does not mean falsifying financial or dispute history. When a record must remain, the final policy should explain the legal or operational reason, retention period, and access restriction.
Regional rights, age requirements, Sponsor responsibilities, and exact retention schedules require counsel-approved policy before production publication.