Privacy notice
About this draft
This notice describes the current seller candidate for review. It is not an approved launch privacy notice. The controller identity, legal bases, retention schedule, provider arrangements and rights-request operation still require confirmation. The existing signup destination remains Existing Privacy Policy.
Information used by the seller service
- Account and identity: email address, name, company, professional declaration, representation details, verification facts and acceptance timestamps.
- Authentication and security: password credentials, sessions, verification and recovery tokens, request metadata and abuse-prevention counters.
- Seller workspace: private drafts, fund positions, financial fields, preferences, listing status and audit records.
- Support, when configured: name, email and the text submitted for account, legal, privacy or accessibility assistance.
Private financial fields are processed by the service even though they are not public notices. Do not assume that structured fields are anonymous or that a platform can eliminate all disclosure risk.
Purposes and access
The implementation uses these records to authenticate users, preserve drafts, apply ownership and professional-access restrictions, manage listings, record account and listing changes, and handle service requests. Seller records are accessed through server-side ownership controls. Authorised operational administrators have separate access.
The controller must confirm a lawful basis for each purpose, any legitimate interests relied on, required versus optional fields and the consequences of withholding information. This draft does not assign legal bases by assumption.
Infrastructure and recipients
The seller candidate uses Vercel hosting, PostgreSQL on Neon, Better Auth running within the application, and Resend for transactional email. Better Auth is application software here, not a separate hosted identity service. Supabase describes the older production stack and is not the active candidate runtime.
Optional browser analytics may use Mixpanel and Vercel Web Analytics after an affirmative browser choice and where enabled. Mixpanel uses pseudonymous identifiers and allowlisted event properties; this is not a promise of aggregate-only anonymous collection. Names, emails, financial fields and support text must not enter analytics. Server-side event configuration is separate and remains a deployment review gate.
Provider contracts, recipients, subprocessors, processing locations and international-transfer safeguards must be verified for the actual launch configuration. A configured European endpoint does not establish that every provider operation stays in Europe.
Storage and retention
Accounts, private drafts, audit records and support mail do not share a verified deletion schedule. Security windows and session expiry are technical lifetimes, not a complete retention policy. The controller must approve purpose-specific periods or criteria, backups, deletion procedures and legal holds before launch.
See Cookies & browser storage for storage used by the browser and optional analytics controls.
Requests and choices
Account settings allow correction of supported profile fields, email change and password recovery. The current settings page does not provide a completed self-service data export or deletion workflow. Legacy request functions are not evidence that requests can be fulfilled operationally.
A verified privacy contact, identity-check procedure, response ownership and request tracking must be established. Once configured, the legal/support panel will accept privacy requests. It does not promise automatic deletion or a response deadline. This draft does not restrict applicable access, correction, erasure, restriction, portability, objection, consent-withdrawal or complaint rights; counsel must confirm the applicable notice and supervisory-authority details.
Contact
See the Legal center for current support availability and the Legal notice for operator-information status.
XXX · Complete before approval
- XXX: controller identity and monitored privacy contact.
- XXX: purpose-by-purpose legal bases, required fields and retention periods or criteria.
- XXX: provider agreements, recipients and international-transfer safeguards.
- XXX: rights-request owner, identity checks, response process and supervisory authority.