← Home

Privacy Policy

Last updated: 2026-05-24. Service operated by Vermilion Holdings LLC, an Arizona limited liability company. This Privacy Policy describes how Watch Sale Prep collects, uses, and shares information. It is not legal advice and does not mean we meet every privacy law in every country.

1. Who operates the service

Watch Sale Prep is operated by Vermilion Holdings LLC, an Arizona limited liability company (“Vermilion Holdings LLC,” “we,” or “us”). For privacy questions or requests, use the Support page and select “privacy request” (Use the Support page and select "privacy request".).

2. Information we collect

  • Account information: the email address you sign in with and an internal Supabase user identifier.
  • Listing content you submit: the watch listing details you enter, including item descriptions, condition notes, transaction preferences, asking prices, usernames you choose to include, and any other information you choose to add to a listing or to your saved seller defaults.
  • Photos you upload: images you attach to a listing or batch row.
  • AI-generated outputs: the title text, post body, optional images, checklists, and export packets we produce based on your inputs.
  • Timestamp challenge records: Challenge IDs, required watch times, issuance times, status/expiration, and optional usernames you enter. These records are public by design once issued. Having a paid subscription or signing in does not mean we verified the watch, seller, photos, or transaction.
  • Share tokens and helper recipients: the random tokens we generate for your share links, and the email addresses you enter when you ask us to deliver a packet link to a helper.
  • Subscription and billing metadata: Stripe customer and subscription identifiers, plan, period, and payment status. Card numbers are handled by Stripe and are not stored by us.
  • Support messages: the email address, subject, message, and any draft identifier you submit through the Support form.
  • Usage and product events: first-party visit and click counters and other non-sensitive event records used to operate and improve the Service (for example sign-in success, generation runs, exports, share opens), along with a first-party anonymous and session identifier stored in cookies.
  • Operational logs: minimal request metadata (for example a hashed IP address) used for rate limiting and abuse prevention.
  • Error reports (if enabled): if Sentry is configured for the deployment, runtime errors and stack traces may be sent to Sentry.

3. Sources

We collect information directly from you when you sign up, save defaults, create a listing, generate drafts, share a packet, or contact support. We also receive information from Stripe (subscription events) and Supabase (authentication events).

4. How we use information

We use the information above to operate the service, generate AI-assisted drafts and images, store your work, deliver packet shares and helper emails, process payments, enforce rate limits and prevent abuse, measure basic product usage, respond to support requests, and improve the Service. We do not use your information to serve third-party advertising.

5. Subprocessors

We rely on the following categories of providers to run Watch Sale Prep. We do not sell personal information to data brokers.

  • Supabase— database, authentication, and file storage for listings, photos, generated images, and exports.
  • Stripe— subscription billing and Customer Portal. Card data is collected and stored by Stripe under their terms.
  • OpenAI— generation of draft titles, post bodies, and structured facts. Listing content and instructions you submit are sent to OpenAI when you run a generation. We configure the Service to send prompts and receive outputs needed for your request. Whether OpenAI retains or uses API inputs for model training depends on OpenAI’s account settings and policies for the API product we use; we do not state here that your content is or is not used for training — please review OpenAI’s current documentation and our account configuration, and contact us through the Support page if you need a written summary of our current settings.
  • Bannerbear— optional generation of catalog and summary images. When you trigger image generation, the relevant inputs (for example watch metadata and uploaded photos) are sent to Bannerbear. Retention and secondary use are governed by Bannerbear’s terms; we do not independently verify whether Bannerbear uses customer content for model training.
  • Resend— transactional email delivery (magic-link sign-in, helper-share packet emails, and support messages routed to our inbox).
  • Sentry— error monitoring and performance tracing. Runtime errors, stack traces, and low-rate performance samples may be sent to Sentry to help us detect and fix production issues. We strip request bodies, authentication headers, cookies, and other sensitive fields before transmission; session replay is not enabled.
  • PostHog— product analytics. We mirror non-sensitive product usage events (such as page views, feature usage, plan state, and attribution data) to PostHog to understand how the Service is used and to improve it. Autocapture, session replay, and heatmaps are not enabled. We do not intentionally send listing text, generated content, payment details, or secrets to PostHog.
  • Railway— application hosting and runtime.
  • Cloudflare— DNS and network edge (for example routing traffic to the application).

6. AI processing of your content

When you generate a draft, the listing content you have entered (and, where applicable, uploaded images) is sent to our AI subprocessors so the draft can be produced. AI outputs may be inaccurate or incomplete and are returned to you as drafts only. Do not submit information you are not authorized to share, including confidential third-party information.

7. Public sharing you control

You may choose to generate a private, time-limited packet share link, and you may ask us to email that link to a helper recipient you specify. Anyone with a packet share link can view the listing materials covered by it until the link expires or is revoked. Timestamp challenge records are public by design once issued; anyone with a Challenge ID can open the public record. You decide what to share and with whom.

8. Cookies and first-party identifiers

We use first-party cookies to keep you signed in and to attribute sessions for our own product analytics (anonymous and session identifiers, plus simple visit and click counters for internal improvement). Our analytics service (PostHog) may also store a device identifier in a cookie or localStorage to link usage events across sessions; this identifier is used for product analytics only, not advertising. We do not use third-party advertising cookies and we do not sell or share information for cross-context behavioral advertising. If you prefer not to be included in product analytics, contact us through the Support page and we will disable analytics identifiers for your account where technically feasible.

The Service is U.S.-focused. We do not target marketing at the EU or UK. If we later market in jurisdictions that require a consent banner or similar mechanism, we will add the controls required for that posture.

9. Retention and deletion

We retain account, listing, and generated content while your account is active or as needed to operate the service. You can delete your account from Account; deletion removes the account record and listing photos we control under your user-scoped storage prefix. Operational logs are retained for a short security window. Subprocessors (including Stripe, OpenAI, Bannerbear, Resend, Railway, Cloudflare, Sentry, and PostHog, where used) may retain data they have received under their own terms even after your account is deleted; we do not have the ability to remove records from those providers’ logs on demand.

10. Security

The service uses TLS in transit, Supabase row-level security on user data, and server-side controls to gate access. No system is perfectly secure; you are responsible for keeping your sign-in email account safe and for not sharing share links with people who should not see them.

11. Children

The service is not directed to children under 13 and we do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us through the Support page.

12. U.S. state privacy rights

If you are a resident of a U.S. state with a comprehensive privacy law, you may have rights to access, correct, or delete personal information we hold about you, and to opt out of certain processing. You can submit a request through the Support pageby selecting “privacy request.” We will respond consistent with the applicable law.

At our current scale we use a minimal small-business posture: we do not sell personal information to ad networks, we route requests through Support, and we track internally whether we grow into thresholds that require expanded disclosures (for example additional California or other state-specific mechanics). This section is not a certification that we meet every state exemption test.

13. International users

Watch Sale Prep is intended for use in the United States and has not been adapted to EU/UK GDPR as a primary compliance program. We may allow passive access from other countries without EU/UK-targeted marketing. If you access the service from outside the United States, you do so at your own initiative and are responsible for compliance with local law.

14. Changes

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the “Last updated” date and, where appropriate, by additional notice.

Service operated by Vermilion Holdings LLC, an Arizona limited liability company. Last updated: 2026-05-24.