Effective October 15, 2026. This policy is provided by Blip, LLC. It is not legal advice.
Blip is a trading-card market tool offered by Blip, LLC. This policy describes the marketing website and the application. The marketing website is the public site that introduces Blip. The application is the signed-in product. It is in a closed beta, and the marketing site does not create an account or open the application. Login and Get Started on the marketing site go to a Coming Soon page.
The marketing site is hosted on Webflow. Account signup is not open on this site. The Contact page has a form for questions and feedback. The form accepts a message only when sending is turned on. While sending is turned off, that form does not deliver or store a message, and Mailgun is not used for it. When sending is turned on, Webflow's form storage is not used for that form. How a message is handled once sending is on is described under The contact form. Site settings reviewed for this policy show Webflow data collection turned off and no Google tag IDs. One site script is applied, and it updates the copyright year in the footer. It is not an analytics tag. This policy does not claim that the published host sets no cookies. Webflow's own platform cookies were not inspected.
When the application is used, sign-in is handled by Auth0. Blip stores an Auth0 subject identifier and can store the email address Auth0 provides. The application keeps its own user id. After an account is approved, a person can set a display name, a generated avatar style, a time zone, and email preferences. Blip does not use its own cookies for application sign-in. It stores session data in browser local storage. Auth0 may use cookies on Auth0's login domain. A closed-beta approval flag controls whether a signed-in person can enter the application. Passwords are entered with Auth0. This policy does not claim that Blip stores passwords.
The application stores portfolios, portfolio entries, watchlists, alert subscriptions a person creates, and related records, including prices and notes they enter. Those records are scoped to the account. Community profile fields and a leaderboard preference exist. New accounts are set so the leaderboard and community discovery stay off until the person turns them on.
The application can store trading-card images a person uploads, including images used for a grading-risk review. Image files are stored in Amazon S3 under a path scoped to the account. The database stores image metadata. A separate card-identify action can accept an image for a lookup and is documented as not saving that image. This policy does not describe every image endpoint.
Grading-risk results are advisory and probabilistic. Blip is not a professional grading company and does not guarantee a grade from PSA, BGS, CGC, SGC, or any other grading provider. The application stores the assessment for the account, including a predicted range and a confidence figure. A person can record a later grade outcome, including optional notes. Where a written explanation is generated, structured assessment fields, not the card image, are sent to OpenAI. In the application reviewed, that explanation is available on a Pro account. The text is advisory, does not change the numeric result, and is not listed as a feature on this marketing site. The current design does not send images to OpenAI.
Prices, comparable sales, ROI figures, and trend lists come from market data and calculations. CardHedge is used for market lookups. SportsCardsPro is used for some card search. In the design reviewed for this policy, those providers receive card identifiers or search terms, not an account profile. Market figures, including ROI figures, are estimates. They are not a promise of a sale price, a profit, or a future return.
The application has Free and Pro tiers. The marketing site currently shows Free at $0 per month and Pro at $12.99 per month. The checkout amount is set in Paddle. A yearly price and a trial are not offered on the marketing site and are not stated in this policy. Blip stores a Paddle customer identifier and subscription status. In the design reviewed, card numbers are not stored in Blip's database. Stripe is not the current billing provider in that design. Renewal, cancellation, and refund rules are not stated in this policy.
Auth0 sends identity-verification email. Mailgun is the provider for Blip product email, including a beta-approval notice and a support request from a signed-in user. Optional newsletter and product-update email default to off. When the marketing contact form is accepting messages, Mailgun also delivers those messages, as described under The contact form. While sending is turned off, Mailgun does not process that form. Privacy requests can be sent to privacy@blipapp.com.
When the form on the Contact page is accepting messages, Blip receives the name, email address, and message you type. The form accepts a message only when sending is turned on. While sending is turned off, the form does not deliver or store a message.
When sending is turned on, the form uses Cloudflare Turnstile to check that a message comes from a person. The widget runs in Cloudflare's managed mode. For that check, Cloudflare receives signals from your browser, including your IP address, a TLS fingerprint, your User-Agent, the site key, and the page origin. Blip's service also sends your IP address with the check. Cloudflare handles that information under its Turnstile Privacy Addendum at https://www.cloudflare.com/turnstile-privacy-policy/ and its privacy policy. This policy does not claim that the Turnstile host sets no cookies.
When sending is turned on, the entry goes to a Blip service on Cloudflare Workers. The service emails it through Mailgun, in the United States, to a Blip mailbox. The email shows the time in UTC, the name, the email address, and the message. The email address is the reply address. The service does not put the IP address in that email. Webflow does not store submissions for this form. The form script does not store the message in the browser.
To limit repeated messages, the service keeps short-lived records when it processes a submission. Those records hold one-way hashes of the IP address and email address, hashes that can confirm a particular email and message, a count of recent attempts, and the result of an attempt. A separate count covers all visitors together and is not tied to one person. A hash of an IP address, an email address, or a message is not anonymous. The service is built to drop a counter one hour after the first counted attempt in that window, and to drop a message record ten minutes after it is recorded. That ten minutes starts again when the attempt finishes. Expired records are removed on a schedule and again when a later attempt is checked. If the schedule does not run, they remain until that later check. Cloudflare can restore this storage to a point in the past 30 days, so a deleted hash can remain recoverable during that period. This policy does not promise that every Cloudflare copy is gone after 30 days. The message text is not written to that storage.
The service's own log records the result of an attempt, not the name, email address, or message. Cloudflare keeps those logs, and a technical trace of the request, for 7 days on the plan this service uses. The trace includes request details such as the time, the path, and general network information. This policy does not claim that a successful delivery leaves the message out of that trace.
Do not include passwords, payment card numbers, or government identification numbers in the form.
Blip keeps a delivered contact-form email in its mailbox for 12 months from the date it is received. Blip can delete that email sooner after a verified request to privacy@blipapp.com, unless Blip must keep it to meet a legal or similar retention obligation. Deleting an email from the mailbox is a manual step. It is not an automated purge. Mailgun keeps its own copy under Mailgun's plan and the sending domain's settings. This policy does not state how long Mailgun keeps that copy.
On the application, sign-in state is kept in local storage, and Auth0 may set cookies on its own domain. The application can emit first-party product events in the browser. In the code reviewed, those events are not sent to a third-party analytics service. The marketing site has no Google tag and no custom analytics script in the settings reviewed. A cookie list, a consent banner, and a retention period for usage data are not stated in this policy.
These providers are used for the application, based on the code and documentation reviewed on October 14, 2026: Auth0 for sign-in, Amazon S3 for uploaded images, Supabase for the database, Render for application hosting, Paddle for subscription billing, Mailgun for product email, OpenAI for a written explanation of a grading-risk result on a Pro account, and CardHedge and SportsCardsPro for market data. The marketing site is hosted by Webflow. When the contact form is accepting messages, Cloudflare provides the contact-form security check and the service that receives those messages, and Mailgun delivers them. For that check, Cloudflare also receives the browser signals described under The contact form. Blip does not choose those signals. Blip sends each provider the information described for that provider's role, so the provider can perform that work. This list is not a contract, and it can change. This policy does not include a sale, advertising-sharing, or do-not-sell statement. Those decisions are not made here.
In the design reviewed, account, portfolio, image, grading-risk, and alert-subscription records remain until an operator deletes the account. This policy does not promise how long they are kept, how quickly they are removed, or that deletion is certified. Self-serve download and self-serve deletion are not available. Planned time limits for some alert events, audit rows, and ingestion logs are written down and are not enforced. Those plans are not a public retention promise until they are approved. This policy does not state how long backups are kept. A contact-form email in Blip's mailbox is kept for 12 months, as described under The contact form. That period does not set how long other records, Mailgun's own copy, or Cloudflare logs are kept.
Access to account data is limited to the signed-in user, with operator access for administration. The application is built to avoid logging passwords, raw sign-in tokens, email addresses in free text, and raw grading-model payloads. This policy does not claim a certification, an audit, or that a breach cannot happen.
A person can correct profile and preference fields in the application after the account is approved. Optional email categories can be turned off there. A full export, and deletion of an account, are manual operator steps. There is no self-serve request form. Questions and requests about personal information can be sent to privacy@blipapp.com. A request to delete a contact-form email is handled manually after the request is verified. Blip can delete that email before the end of the 12-month mailbox period, unless a legal or similar obligation requires Blip to keep it. This policy does not set a response timeline, and it does not state region-specific privacy rights.
The application is not designed to collect information from children. A minimum age is not set in this policy.
This policy is effective October 15, 2026. If it changes, Blip will update this page and the effective date.
Blip, LLC's mailing address is 221 N. Central Ave, #283, Medford, OR 97501. Privacy requests can be sent to privacy@blipapp.com. The support request inside the application is available only to a signed-in user. The marketing contact form is on the Contact page. It accepts a message only when sending is turned on. While sending is turned off, the form does not deliver or store a message. Sending a message does not guarantee a response.