Privacy Policy · Ali Sabet

This is the honest version of what happens to your data on sabet.com. I'd rather you know exactly what I collect and why than read something vague. Plain English first; the legal framing is in the Terms of Service.

1. What we collect

Account data — email address, handle, display name, and the optional bio, collection story, location, social handles, website and profile photo you add yourself.
Phone number — asked for when you add a shipping address or check out, so the carrier (and I) can reach you about a delivery. Optional.
Shipping address — name, street, city, state/region, postal code, country. Required to bid (winners are charged and shipped automatically) and to buy anything physical. Stored on your account and snapshotted onto each order.
Payment data — Stripe collects your card directly. Sabet stores a Stripe customer ID, the card brand and last four digits so you can see what's on file. Full card numbers never touch our servers.
Auth data — sign-in is handled by Clerk. Sabet receives a stable user ID and your email; passwords and passkeys stay with Clerk.
Provenance + ownership — when you own, verify, transfer or are issued a certificate for a piece, that is recorded in the public ownership chain. Intentionally public (shown as “Private collector” when your profile is private).
Content you post — feed posts, forum threads and replies, comments, messages, images you upload.
Activity — bids, orders, drop subscriptions, giveaway and draw entries, club memberships, Aura points, and the emails we send you (delivery, opens and clicks, so I can see what's working).
Giveaway entries — alongside the entry itself we keep a salted hash of your IP address (not the IP) to spot duplicate entries. The hash can't be turned back into an address.
Approximate location — Vercel's edge tells us the city and country a request came from. We use it to prefill the location on your profile (you can change it), to place giveaway entrants on the map, and to decide which privacy notice to show you. We don't store precise coordinates.
Push notifications — if you turn them on, we store the browser's push subscription endpoint and keys plus the device's user-agent string so we can deliver alerts and clean up dead subscriptions.
First-touch attribution — on your first visit we note where you came from (utm source and campaign, the referring site, the page you landed on, and whether the link came from Facebook, Instagram, Google or TikTok). If you sign up, that source is stamped on your account so I can tell which channels bring collectors.
Referrals — if you arrive through a member's share link, we record who referred you (they earn Aura when you place a first bid).
Presence sessions — a random first-party session id (the sb_session cookie, 30 days) and the page you are on, so drop pages can show “X people watching” and I can see live traffic. Tied to your account when you're signed in; rows are pruned after 35 days. While you are signed in on the home or live page, your handle and avatar can appear to other visitors as “here now”, unless your profile is private.
Consent and opt-out records — when you tick the box that lets us charge a saved card, confirm you are 18 or older, or subscribe to email, we store what you agreed to, when, on which page, and a salted hash of your connection (never the IP itself). If someone who is not a member asks us to stop emailing them, we keep that address on a do-not-email list so we can honor it.
Reports and blocks — if you report a member or a conversation, we store the report and the studio may read the conversation you reported. If you block someone we store that you did, so the block keeps working; they are not notified.
Duplicate-account checks — to keep prizes and giveaways fair we compare a salted connection hash between entries, and ask Stripe whether two accounts share the same card. We don't store the card fingerprint.
Operational logs — IP address, request paths and error traces, kept by Vercel and Sentry for security and debugging. Error reports are scrubbed of email addresses, phone numbers and payment identifiers, and of cookies and request headers, before they are sent to Sentry.

2. What we don't collect

Card numbers, CVCs or bank details (Stripe holds those).
Government IDs — there is no KYC here.
Sensitive demographics (race, religion, health). No use for them.
Precise GPS location.

3. Why we collect it

Run your account, show your collection, charge auction wins and ship what you buy.
Issue and verify certificates of authenticity and keep the provenance chain honest.
Send transactional email (receipts, outbid alerts, shipping) and, unless you opt out, news from the studio.
Measure which ads and posts actually bring collectors, so the studio's money goes where it works.
Investigate fraud, duplicate giveaway entries, theft claims and terms violations.

4. Analytics and advertising measurement

This is the part most privacy pages bury, so here it is plainly. Sabet runs two third-party measurement tools:

Meta Pixel + Conversions API — the Pixel runs in your browser and sets the _fbp / _fbc cookies. When you buy, join a club or enter a giveaway, our server also sends Meta a Conversions API event containing a hashed (SHA-256) version of your email, your IP address and browser user-agent, and the order value — so Meta can tell which ads led to a sale. Meta may use this to measure and improve ad delivery. Meta's privacy policy.
Google Analytics 4 (+ Measurement Protocol) — page views and events in your browser (the _ga cookies), plus server-side purchase events sent through the Measurement Protocol with the same anonymous client id. Google's privacy policy.

Your control. In the EU, EEA, UK, Switzerland and California — and whenever we can't tell where you are — neither tool loads, and no server-side event about you is sent to Meta or Google, until you accept the notice that appears on your first visit. If your browser sends a Global Privacy Control signal we treat it as “no” everywhere. Elsewhere they load by default and you can turn them off at any time using the link in the footer of every page. Your choice is stored in the sb_consent cookie for one year and, if you are signed in, on your account too. Turning tracking off after it was on tells both tools to stop, deletes their cookies from this browser, and no further event is sent. We only ever send them the address of the page without anything after the “?”, and they are not used at all on unsubscribe and confirmation links, in messages, or in the studio's admin. When a purchase is charged while you are not on the site (an auction closing, a club renewal), nothing is sent if your account has an opt-out on file, if we have no choice on record and you are in one of the opt-in regions above, or if we don't know your region. Videos are embedded with YouTube's privacy-enhanced player; an embedded video may still set cookies when it loads. Live and auto-playing video loads only after you have accepted where consent is required (or tap the video to play it); elsewhere it loads with the page unless you have opted out.

5. Who we share it with

These are the services that run the platform. Each sees only what it needs:

Clerk — sign-in. Email, password/passkey, profile basics. Their privacy policy.
Stripe — payments. Card details, billing and shipping address, transaction metadata. Their privacy policy.
Resend — email delivery. Recipient address and message body; reports opens, clicks and bounces back to us. Their privacy policy.
Klaviyo — email marketing. Email, name, handle, when and how you joined, your last bid date, whether you have an address and phone on file, and purchase stats (pieces owned, lifetime spend, club tier, Aura) so studio news can be segmented sensibly. Opting out of marketing here suppresses you there too. Their privacy policy.
Meta — advertising measurement — see section 4. Their privacy policy.
Google Analytics — site analytics — see section 4. Their privacy policy.
Printful — prints and club canvases. Receives your name, shipping address and, where the carrier needs them, phone and email for each print order. Their privacy policy.
ShipStation — shipping labels for pieces that ship from the studio. Receives name, address and order contents. Their privacy policy.
Shopify — the apparel store at sabet.love and gift cards. Order data moves between the two stores so a purchase there can be fulfilled or credited here. Their privacy policy.
Anthropic — the AI model behind three studio tools: screening member posts and comments as they are published (and hiding the ones that break the rules), drafting replies to support emails the studio pastes in, and answering the studio's own questions about site activity. It receives the text involved. It is not used to make decisions about you and, under its terms for business customers, does not train on this data. Their privacy policy.
YouTube — the privacy-enhanced video player (youtube-nocookie.com) for the studio's films and live streams. It may set cookies when a video loads — see section 4. Their privacy policy.
Sentry — error monitoring. Stack traces and request context. Email addresses, phone numbers, payment identifiers, link tokens, cookies and request headers are removed before a report is sent. Their privacy policy.
Cloudflare Turnstile — bot protection on the sign-in and sign-up forms, run by Clerk. It sees your IP address and browser signals to decide whether you are a person. Their privacy policy.
Browser push services (Apple, Google Firebase Cloud Messaging, Mozilla) — if you turn on notifications, alerts travel through the push service built into your browser or phone. It receives the encrypted alert and your device's push address. Their privacy policy.
Vercel — hosting, edge geolocation, image storage for uploads. Their privacy policy.
Neon — the Postgres database. Their privacy policy.
Upstash — Redis for rate limiting and short-lived caches (keys are ids, not personal data). Their privacy policy.

We don't sell your data to data brokers. Sharing hashed identifiers with Meta and Google for ad measurement can count as “sharing” under California law, which is why the opt-out in section 6 exists. Beyond the vendors above, the only time data leaves Sabet is in response to a valid legal request.

6. Do Not Sell or Share

California residents (and anyone else) can opt out of the ad-measurement sharing described in section 4 at any time: . That link is in the footer of every page, including the sign-in pages and your signed-in account pages. It stops Meta Pixel and Google Analytics from loading (and deletes their cookies if they were already there), stops our attribution cookies from being set, and is remembered for a year in this browser. If you are signed in it is also saved on your account, so purchases charged while you are away are never reported to Meta or Google either. It does not affect the cookies you need to stay signed in or check out. Browser cookies are per device, so repeat it on each device you use. We don't discriminate against anyone who opts out.

7. Cookies

Clerk session cookies (__session, __client_uat and related) — keep you signed in. Strictly necessary.
sb_session — random presence id, 30 days. Powers “people watching” counts and live traffic. First-party, functional.
sb_consent — your tracking choice, 1 year.
sb_src and sb_ref — first-touch source and the member who referred you, 30 days. Not set when you have opted out, or before you accept where consent is required.
sb_amp — set only when you open a friend’s giveaway link, so that friend receives the entry the giveaway rules promise them. It holds the giveaway and the friend’s member number, is never shared with anyone, and expires after 30 days. It is part of how the giveaway works, not advertising.
_ga, _ga_* — Google Analytics. _fbp, _fbc — Meta Pixel. Only when tracking is allowed.

8. Public vs. private data

Sabet is a transparent collector platform. By default your handle, display name, bio, photo, owned pieces and ownership records are public. You can make your profile private from /settings at any time; the provenance chain stays intact but shows “Private collector” instead of your handle.

9. Your rights and how to use them

See and correct your data — most of it is on your profile and /settings. Email for a complete export.
Delete your account — self-serve at Settings → Delete account. It closes the account and wipes your profile: email, name, handle, phone, saved address, socials, saved card and Stripe customer, attribution, your login, push subscriptions and sessions. Here is what is kept, and why. Ownership records, bids, orders and certificates stay in the ledger under “Deleted user”, because the chain of custody on every piece has to survive its owners. Each past order keeps the name, shipping address and phone it shipped to, and the studio keeps its record of the emails it sent you, because tax, accounting and payment-dispute rules require business records to be kept for several years. Things you published — posts, comments, love notes and their photos — stay up without your name unless you ask for them to come down. Records of consents you gave (such as the authorization to charge a saved card) are kept as proof. Copies that already went to the companies that ship, print and process payments for us (section 5) stay with them under their own retention rules; we can't delete inside their systems, but we do tell our email marketing tool to stop contacting you. You can also email support@sabet.com and I'll do it for you within 30 days.
Stop marketing email — every studio email has a one-click unsubscribe link at the bottom, or flip “News & updates” off in settings. Transactional email (receipts, outbid alerts, shipping) keeps running.
Opt out of ad measurement — section 6.

California (CCPA/CPRA), EU/UK (GDPR) and other regional rights apply where you live — access, correction, deletion, portability, objection, and no discrimination for using them. Email support@sabet.com to exercise any of them; I aim to reply within 5 business days.

10. Retention

Account data lasts as long as your account does. Presence sessions are pruned after 35 days; attribution cookies expire after 30. Order, payment and certificate records are kept for as long as the provenance ledger exists, as described above. The record of emails we sent (address, subject, delivery and open events) and consent records are kept for as long as the business needs them as proof. Copyright takedown notices, and our correspondence about them, are kept on file. Logs are kept for 30 days unless tied to a security incident.

11. Children

Sabet is for adults — you must be 18 to hold an account. If we learn we've collected data from someone under 13, we'll delete it.

12. Security

All traffic is HTTPS. Payment data is tokenized by Stripe. Database backups are encrypted at rest. Admin access is restricted by role and every admin action is logged. No platform is impenetrable; we follow industry practice and patch promptly. Security reports: /security.

13. Changes

When our practices change, this page changes and the date at the top moves. Material changes get a notice on the site and an email to active accounts.

14. Contact

Questions, requests, complaints — email support@sabet.com. Sabet Brands, Inc. (Sabet Studio), Irvine, California, USA.