Privacy Policy

Last updated: June 2025

1. Privacy-First Design

SameBatch is built with privacy as a core principle. We minimize data collection and never expose your username to other batch participants. Each batch generates a unique anonymous research identity for communication.

2. Information We Collect

  • Account data: Username, hashed password, and recovery question/answer (hashed)
  • Shipping information: Address provided during batch participation, stored encrypted and used solely for order fulfillment
  • Payment data: Cryptocurrency transaction references for escrow management
  • Chat messages: Messages sent in batch chat channels

3. How We Use Your Data

  • Processing and fulfilling batch orders
  • Managing escrow and payment verification
  • Enabling anonymous batch communication
  • Platform security and fraud prevention

4. Data Sharing

We do not sell or share your personal data with third parties. Shipping information is shared only with fulfillment partners as necessary to deliver your order. Your username is never exposed — only your anonymous batch identity is visible to others.

5. Data Retention

Account data is retained while your account is active. Batch participation data, including chat messages, is retained for the lifetime of the batch. You may request account deletion by contacting support.

6. Security Measures

Passwords and recovery answers are stored using secure one-way hashing. All communications are encrypted in transit. We follow industry best practices for data protection and regularly review our security posture.

7. Cookies & Tracking

SameBatch uses minimal session cookies required for authentication. We do not use third-party analytics, advertising trackers, or fingerprinting technologies.

8. Your Rights

  • Request access to your stored data
  • Request correction of inaccurate information
  • Request deletion of your account and associated data
  • Object to specific data processing activities

9. Changes to This Policy

We may update this privacy policy periodically. Changes will be posted on this page with an updated revision date.