← Back to D2M Shot

D2M Shot · Legal

Privacy Policy

A factual overview of what the current beta service collects and how that information supports the product.

Effective August 24, 2026

1. Information we collect

D2M Shot collects the minimum account and product information needed to authenticate users, operate the editor, understand reliability, and improve the service.

  • Account data such as email address, display name, avatar, authentication provider, confirmation status, and sign-in timestamps.
  • Operational profile data such as locale, timezone, plan, onboarding state, and last activity time.
  • Product activity such as editor opens, screenshot uploads, preview actions, export format and status, and feedback submissions.
  • Technical analytics such as page URL, browser and device information, approximate network-derived location, performance metrics, and session recordings with input masking enabled.

2. Screenshot content

Screenshots selected in the editor are processed in the browser for the current editing session unless a feature explicitly states that content will be saved or uploaded. D2M Shot does not intentionally capture screenshot contents through product analytics; upload controls and sensitive inputs are excluded or masked from session recording.

3. How information is used

Information is used to provide authentication and product features, maintain account profiles, measure activation and exports, diagnose failures, protect the service, and prioritize product improvements.

D2M Shot does not sell personal information or use screenshot content for advertising.

4. Service providers

D2M Shot uses Supabase for authentication and database services, Vercel for application hosting and delivery, Google for optional identity authorization, and PostHog for product analytics, performance monitoring, and session replay. These providers process data under their own security and privacy terms.

5. Cookies and analytics storage

Authentication and analytics may use cookies or browser storage to keep a session active, distinguish product usage, and preserve attribution. Blocking these technologies may limit sign-in, analytics, or product functionality.

6. Retention and security

Data is retained only for as long as needed for product operations, security, analysis, or legal obligations. Access controls, encrypted transport, database row-level security, and server-only administrative credentials are used to reduce unauthorized access. No online service can guarantee absolute security.

7. Your choices

Users may sign out at any time and may request access, correction, or deletion of account-related information through the in-product feedback channel. Some records may be retained where required for security, fraud prevention, or legal compliance.

8. Changes and contact

This policy may be updated as D2M Shot evolves. Material changes will be reflected by a revised effective date. Privacy questions and data requests can be submitted through the feedback control available inside D2M Shot.