Policies
Privacy
Operator contact details are not configured yet. Use the reporting form for now; the operator must add a real contact address before launch.
What the service collects
- Artist account data: email address, display name, username, bio, profile images, external links, password hash, passkey public credentials, and account settings.
- Purchase data: buyer email, artwork, amount, currency, payment state, timestamps, and identifiers returned by Stripe. The site does not receive or store full card numbers.
- Technical data: server logs and rate-limit records such as IP-derived keys, errors, and security events. Access tokens are stored only as hashes.
- Reports: the information you submit in the content-reporting form.
How it is used
To run artist pages, publish artwork, process purchases, verify payments, deliver downloads, send transactional email, prevent abuse, respond to reports, and comply with legal obligations. The site does not currently include advertising trackers or sell personal data.
Cookies and sessions
The site uses an HTTP-only session cookie for sign-in and CSRF protection. Stripe sets its own cookies during hosted checkout. There are no analytics cookies in this application by default.
Service providers
Stripe processes payments and connected-account onboarding. An SMTP provider chosen by the operator delivers transactional email. Hosting and storage providers may process data on the operator’s behalf. Each provider has its own privacy terms. The operator must list actual providers before launch.
Retention
Artist and purchase records are kept while needed to operate the service, honor downloads, resolve disputes, and meet legal obligations. Security logs are kept for a limited operational period. The exact retention schedule is a launch decision and must be documented by the operator.
Your choices
Artists can edit profile data and remove passkeys. Buyers can request a fresh access email, and can contact the operator through the reporting form. Legal rights such as access, correction, deletion, or objection depend on the operator’s jurisdiction and must be implemented before launch.
International transfers and legal basis
The operator must document the legal basis for processing, international transfer safeguards, and any required representative or data-protection officer. This draft does not claim compliance with any specific privacy law.
Data controller identity and contact: not configured in this draft. The operator must complete this before launch.