Privacy Policy

Last updated: 16 October 2026

This Privacy Policy explains how PULSE ("we", "us"), operated by United Distribution Group LLC, a Wyoming limited liability company (PULSE is its trade name), collects and uses personal data. United Distribution Group LLC is the controller of that data. PULSE is an independent service and is not affiliated with Whatnot, Inc.

1. Data we collect

• Account data: the email address you provide at signup, and, if you set one, a password. Your password is stored only as a salted, memory-hard scrypt hash (never in readable form) and is used to sign you in. If you answer our optional "How did you find PULSE?" question, your answer is kept with your account.
• Sign-in security: when you sign in with a password from a device we don't recognize, we email you a one-time 6-digit code (stored only as a hash) to confirm it's you. If you choose to trust that device we keep a device-trust record (a hashed token, plus a salted hash of your IP address and your browser/device user-agent) so you don't need a code on that device again. These are deleted when you delete your account.
• Billing data: payments are processed by Stripe. We do not receive or store your full card number. We retain a Stripe customer ID, a subscription ID, the Stripe price your subscription is billed at (its ID, amount and billing interval), any promotion code applied to it (the coupon, the amount or percentage it takes off, and how long it applies), and an opaque card fingerprint (a token Stripe derives from the card; never the card number, expiry, or CVC) which we use to prevent free-trial abuse.
• Approximate IP address: we store a salted, irreversible hash of your IP address (never the raw IP in our database; see the access-log note under Usage/diagnostics) at signup, when you sign in, and on other abuse-relevant actions, to enforce per-network limits and detect abuse.
• Support chat: if you use the in-app support assistant, the messages you send are matched against our help articles on our own server and may be logged to operate and improve support and to prevent abuse. No AI model is involved.
• Lead form: if you submit our no-signup interest form, we store the email address and (optional) Whatnot handle you enter, together with a salted, irreversible hash of your IP address, to follow up on your request and prevent abuse. Unless you are signed in with that address, we email the report only after you confirm the address through a link in one email, and we record when you confirmed. To limit how often we write to any one address we keep a salted, irreversible fingerprint of it, and of the network the request came from, for 30 days.
• Tracking requests: if you ask us to start tracking a Whatnot handle from its seller page, we store the handle, a salted, irreversible hash of your IP address and, only if you choose to give one, your email address. We use an address only after you confirm it: we send one email asking you to, and after you confirm, one email when that handle's first report is ready. An unconfirmed address is deleted after 7 days, and a confirmed one as soon as that email is sent or the request expires after 60 days. To limit how often we write to any one address we keep a salted, irreversible fingerprint of it, and of the network the request came from, for 30 days. Our record of emails sent keeps these emails for up to 12 months under that salted fingerprint only, never the address or the handle. The rest of the request is kept for up to 12 months so we can count how many requests we fulfil.
• Email settings: which kinds of optional PULSE email you have turned on or off and, when you open those settings, your browser's time zone, so emails name your local hours. Deleted with your account. If you use an email's own off link after your account is gone, we keep only a salted, irreversible token of the address, so that we stop.
• Cancellation feedback: if you cancel, the reason you pick (in our optional question, or on Stripe's cancellation page) and any comment you add, kept with your account so we can understand why people leave. Deleted with your account.
• Show Ledger uploads: if you use our Show Ledger feature and upload your own Whatnot order or sales export, we store the rows in that file so we can show you your own sales and per-show totals: order identifiers, item names, sale, fee and shipping amounts, and any buyer name or username your file contains. This information comes from your own records; we process it on your behalf, act only as a processor of it, use it solely to produce your Show Ledger, keep it tied to your account, do not use it for advertising, and delete it when you delete your account.
• Mobile app data: if you use the PULSE mobile app, an anonymous per-device identifier (a random identifier the app generates on first launch and keeps in the device keychain) that is sent with every request and is how your saved settings are stored while you are signed out; the Whatnot seller handle you claim and anything you save against it (watchlist and follows, goals, the categories you mark as yours); seller searches you type in the app; a push notification token, if you enable notifications (retained until the device unregisters or our push provider reports the token invalid), and the time zone you are in, so alerts respect your quiet hours; and in-app purchase entitlement data from our subscription provider. The app signs in with email and password (with the emailed-code step above for new devices), and may also offer Sign in with Apple or Sign in with Google. If you use one of those, the app sends us a signed identity token from Apple or Google that we verify ourselves; from it we receive and store only the provider's stable user identifier and the email address you approve. We never receive your Apple or Google password and gain no other access to those accounts, and this data is deleted when you delete your account. The public website has no social sign-in. There is no advertising identifier and no cross-app or cross-site tracking of any kind.
• Crash reports: when the mobile app or the website hits an error it sends us the error message, the technical stack trace, the app version and the platform, so we can fix it. These go only to our own servers (there is no third-party crash-reporting or analytics SDK) and the device, account or, for a visitor who is not signed in, network address is stored with them only as a salted, irreversible hash. Retained for 30 days.
• Dashboard view counts: when you open a dashboard view (for example Timing or Compare) we add one to a daily count for that view and your plan (free or paid). The count holds no account, device or address, so it cannot be traced back to you.
• Automated visits: page views from search engines, AI crawlers, link previewers and similar software are counted apart from people's page views, with the page, the referring site, the link's source tag and the kind of software, and no device identifier or address.
• Usage/diagnostics: standard request metadata (e.g. timestamps, rate-limit counters, and the browser/device user-agent string associated with each sign-in session) used to keep the Service available and secure. Our application keeps a short-lived access log of requests for security and troubleshooting. Each line records the method, a redacted request path, the response status, the response size and time, the browser's user-agent string, and a salted hash of the IP address rather than the address itself. It drops the query string and redacts the path segments that can carry personal data (the one-time links we email you, which encode your address, and the device endpoint the mobile app calls with its push token), so email addresses and push tokens are not written to it. Cloudflare, which delivers and protects the site, receives the requesting IP address as part of routing your request.
• Days you used PULSE: for each day (UTC) on which you use the dashboard, the app or the API while signed in, we keep one record with your account: the date, and whether you used a sign-in or your API key. It tells us how customers use PULSE. Kept for 13 months, and deleted with your account.
• Record of emails we send you: we keep a log of the transactional emails we send (recipient address, subject, kind, time and whether it was delivered) so we can answer "did my receipt go out?". We do not store the message body, and one-time sign-in codes are never recorded. Retained for up to 12 months, and deleted with your account.

2. Cookies and data stored in your browser

PULSE sets four first-party cookies. There are no third-party cookies, no advertising cookies, and no cross-site trackers:

• pulse_session: a session cookie (HttpOnly) that keeps you signed in to the dashboard after you log in. Lifetime: 30 days.
• pulse_did: a random per-device identifier we use in our own first-party analytics to count distinct visitors and conversions. Lifetime: 1 year from your most recent visit (each page view renews it). On our servers this identifier is kept only as a salted, irreversible hash (never in raw form) and it is not shared with any third-party advertising or analytics network.
• pulse_src: remembers the source that first brought you to the site (first-touch attribution), so we know which channels work. For a referral with no tag this is the referring site's hostname; for a tagged link it also includes that link's campaign labels; with neither it records "direct". It also holds the page you first landed on and when. Lifetime: 30 days from that first visit.
• pulse_td: set only if you choose "trust this device" when signing in, so we don't email you a 6-digit code every time. It holds an opaque token; on our servers only its hash is kept, alongside the device-trust record described in section 1. Deleted when you delete your account, and you can drop it by clearing your cookies.

PULSE also uses your browser's localStorage to remember functional preferences on your device.

Synced to your account when you are signed in. While you are signed in, the Whatnot handle you link, the sellers and categories you follow (your watchlist), and the settings you change (such as alert preferences and goals) are saved to your account on our server, so they follow you to other devices. Signed out, they stay in this browser only. These are pulse_my_handle and pulse_follows below.

Local only. Everything else in the list below stays in your browser; it is not sent to us and is not shared with anyone. Your API key is sent only as the credential on your own API requests.

• pulse_key: your API key, if you have entered one for programmatic access, so you don't have to re-enter it. You set it yourself in the account panel; we never put it there from a link. It never leaves your browser except as the credential on your own API requests.
• pulse_theme: your light/dark theme preference.
• pulse_my_handle (synced when signed in), pulse_my_lane, pulse_my_category (local): the Whatnot handle and category you tell the dashboard are yours, so it opens on your numbers.
• pulse_follows (synced when signed in), pulse_compare_set (local): the sellers and categories you follow, and the ones you line up side by side on this browser.
• pulse_view, pulse_plan_more_open, pulse_taxonomy_v1, pulse_trialbanner_dismissed: whether you see the biggest shows as a list or a gallery, whether you keep Plan's detail open, a cached copy of the public category list, and whether you dismissed the trial banner.
• pulse_handle_synced, pulse_handle_refused: the handle this browser last saw linked to your account, and a handle Whatnot did not recognize, so the dashboard does not re-send either.
• pulse_heard_from_skipped, pulse_was_signed_in: that you skipped the "How did you find PULSE?" question, and that this browser had a signed-in session, so a signed-out reload offers "Sign back in".
• pulse_nav: whether this browser was signed in, on which plan, and when, as last seen by one of our public pages, so their header shows "Open My shop" or "Sign in" right away.

Clearing your browser's cookies and site storage removes all of the above.

3. How we use data

• to provide and maintain the Service and your account;
• to process payments and send billing-related notices (trial-ending, receipts, failed-payment) via Stripe and email;
• to prevent fraud and abuse (duplicate trials, signup floods, card reuse);
• to measure which marketing channels and pages bring us subscribers: we connect the first-touch source saved in your pulse_src cookie, and a hashed per-device identifier derived from your pulse_did cookie, to the email you use at checkout or when you create an account (together with the first page you landed on), and to whether that account becomes a trial or paying subscriber. This is first-party measurement only and is not shared with any advertising network;
• to send you optional product emails where they are enabled: a weekly digest of your own linked handle's recent viewership; alerts and post-show recaps by email if you use PULSE Pro without the app; during a free trial, what we measured on your own linked shows; a reminder to add your Whatnot handle if none is linked; a note before your plan renews if you have not used PULSE for two weeks; and the one email you asked for when a handle you asked us to track has its first report. Every such email carries a one-click unsubscribe, and you can turn each kind off in your account settings;
• to respond to support requests.

We do not sell your personal data.

4. Service providers

We share the minimum necessary data with providers that operate the Service, including Stripe (payments), Apple (purchases made inside the iOS app are sold and processed by Apple), Expo (push notification delivery for the mobile app, which in turn hands the message to Apple's push service), RevenueCat (in-app subscription management; it receives your device identifier and, once you sign in, your email address as the account key), Resend (email delivery), Hetzner (hosting) and Cloudflare (CDN and DNS). They process data on our behalf under their own terms.

Our web pages, including this one, load their display fonts from Google Fonts. When your browser fetches those fonts, Google receives your IP address and browser user-agent in order to serve them. Google Fonts sets no cookies, and we do not send Google any account, billing, or usage data; only the font files are requested.

We also use an internal operations alerting channel (a chat webhook) that notifies us of events we must act on: a new support ticket, a failed payment, a delivery failure. Those notifications can contain your email address and the text of a support message you sent us, so that we can answer you. Nothing from the market data or your saved settings is sent there, and it is not used for analytics or advertising.

Where your data is processed. Our server is in Finland (Hetzner, Helsinki), which is in the EEA. Your account, your billing records, your saved settings and our market data are stored and processed there. One thing is processed elsewhere, and we name it rather than imply a guarantee we cannot keep:

• The providers in section 4. Stripe, Apple, Expo, RevenueCat, Resend, Cloudflare and Google (Fonts) operate globally and may process data outside the EEA under their own terms. Cloudflare also serves our public pages from edge locations around the world.

So if you are in the United States, your account data is transferred to and processed in the EEA; and if you are in the EEA or the UK, it is processed in the EEA except in the case above.

5. Data retention

Account and billing records are retained for as long as your account is active and as required for legal, tax, and accounting purposes. Raw market-data snapshots that power our analytics are retained for approximately 14 days and then compacted into hourly per-category rollups and daily per-seller rollups, which are kept; the per-seller rollups carry the seller's public handle and back the public seller pages described below. This market data is keyed to public shows and sellers. None of it is keyed to your PULSE account. Other horizons we enforce automatically: support tickets are deleted 180 days after they are closed; interest-form leads and the record of emails we sent you, 12 months; tracking requests, 12 months (the email address on one is deleted once we send its one email, or after 60 days); first-party analytics (pageviews, automated visits and funnel events), 90 days; the record of the days you used PULSE while signed in, 13 months; mobile crash reports, 30 days. Support-chat logs are retained only as long as needed to operate and improve support and are then deleted or anonymized.

Free-trial fraud prevention. When a free trial is used we keep a non-reversible record that a trial was consumed: a salted, irreversible hash of the email address and the opaque card fingerprint Stripe derives (never the card number). This record is kept after an account is deleted, with the link to your account removed, so that deleting and re-creating an account cannot be used to take repeated free trials. It contains nothing readable and cannot be used to identify or contact you.

6. Your rights and deletion

You may request access to, correction of, or deletion of your personal data. You can delete your account (and the personal data associated with it) from within the Service, or by emailing us at support@pulsemetric.live. Deletion removes your account and its personal data, including your password, sign-in sessions and trusted-device records. The one exception is the non-reversible free-trial-prevention record described in section 5, which is retained without any link to your identity. Deleting your account also cancels a subscription billed through Stripe, immediately and without a refund of the unused part of the period (see the refund policy). It does not cancel a subscription bought through the App Store, which Apple bills; cancel that in your App Store subscription settings. Depending on where you live (e.g. the EEA/UK), you may have additional rights under the GDPR or similar laws; contact us to exercise them.

Public seller pages

PULSE publishes a page for Whatnot sellers who appear in Whatnot's public live feed, at pulsemetric.live/s/<handle>, together with share images built from it. Each page shows the seller's public handle and avatar and public show statistics as PULSE observed them: viewers, shows tracked, timing and the categories they run in, and, where Whatnot publishes them, follower and items-sold counts, rating and review count, and whether the account is verified. The sources are Whatnot's public live feed and, when someone opens a page we have not counted yet, that seller's public Whatnot profile, which we fetch at that moment. When a seller links their handle to a PULSE account with Pro access (a trial or a paid plan), we also read that public profile about every 2 minutes while they are live, and their public show recap and its share image show the figures from those reads once a show has enough of them. Otherwise nothing on these pages comes from a PULSE account, and a seller does not need one for a page to exist. We publish them as public information, processed for market intelligence.

Our posts and seller social handles. PULSE's own social media posts about the market name sellers by their public Whatnot handle, with the live or peak viewer numbers we observed. Where a seller has published a social media handle themselves, in their public Whatnot bio or on their own website, we record it, and once a person at PULSE has checked it we may mention that handle in the caption of a PULSE Instagram post, at most once a week per seller. We never mention a handle we have only guessed, and we do not tag sellers on Facebook or X. For this we keep the seller's public Whatnot bio, the handles found in it with where we found them (deleted once we have neither seen nor checked a handle for 13 months), and, for up to 13 months, a record of which sellers each of our posts named or mentioned, so that a removal request can be traced to past posts.

If you are the seller and do not want this page, email support@pulsemetric.live with your handle. No account is needed. Once we record your request the page stops being served immediately, and it leaves the seller directory, the sitemap and the seller search within a day. The share images stop being generated at once, but a copy already held by our content delivery network can be served for up to a day after that. Removal covers the seller page, its share images and the per-seller data our public interfaces return for that handle. It also stops our posts from naming or mentioning you, and deletes any social handles we hold for you. Your public shows continue to count toward market statistics, and your handle can still appear where we report the market rather than you: category rankings and category tables, and the comparison blocks on other sellers' pages. Tell us if you want those considered too and we will look at them case by case.

7. Security

Passwords are stored only as salted, memory-hard scrypt hashes; API keys, session and device-trust tokens, and one-time sign-in codes are stored only as one-way hashes, never in readable form. The raw API key is shown once at creation and delivered to you by email. Payment details stay with Stripe, IP addresses are stored in our database only in salted, irreversibly hashed form, and transport is encrypted (HTTPS). No method of storage or transmission is perfectly secure, but we take reasonable measures to protect your data.

8. Children

The Service is intended for businesses and adults; it is not directed to children and we do not knowingly collect data from them.

9. Changes

We may update this Policy; the "Last updated" date above reflects the latest version.

10. Contact

United Distribution Group LLC
support@pulsemetric.live
2232 Dell Range Blvd, Suite 303 #1595, Cheyenne, WY 82009, United States