Data minimisation
The strongest privacy posture usually starts with collecting only what the workflow actually requires.
Privacy Policy
A draft summary of the data Craeftmann collects, why it is collected, and how control should be handled.
Privacy on Craeftmann should support identity confidence, payment protection, operational support, and regulatory hygiene without collecting more than the product actually needs.
Draft legal scaffold
This privacy page is an implementation draft. It should be reviewed against actual data flows, vendors, and regulatory requirements before launch.
- data that supports onboarding and trust
- Identity
- data needed for payments, disputes, and support
- Operations
- controls users should have over communication and access
- Choice
Operational necessity
Some data exists to help accounts, jobs, payments, notifications, and dispute investigation function safely.
User transparency
People should be able to understand what data is held and how it affects the service they receive.
Section 01
What data the platform may collect
Craeftmann may process account details, contact information, onboarding materials, profile content, payment references, device or session signals, and service communication that supports booking and support operations.
Section 02
Why the data is used
Most processing exists to keep the product functional and trustworthy: account access, professional verification, booking coordination, payment handling, notifications, fraud detection, support, and dispute review.
Section 03
Sharing, retention, and user requests
Vendor use, retention windows, export rights, and deletion handling should be documented in line with the real production stack. Those specifics need legal and implementation review before the policy is final.
This route should be refined alongside actual infrastructure, analytics, messaging, and payment integrations.
Next move
Need the browser-side detail?
The cookie policy explains how site-level storage and similar technologies fit into the user experience.