Privacy Policy
What this policy covers
PipeAlert monitors public retailer product listing pages for pipe tobacco stock levels and pushes an alert when a watched blend comes back in stock. This policy explains what data the service holds and what happens to it.
What we collect
- Email address. What the alert signup form asks for. It identifies your subscription, and it is how you get your ntfy topic back if you change phones or clear your browser. We also use it to contact you about the service.
- ntfy topic name. If you enable phone alerts we store the topic you are using, so we know where to deliver. This is a delivery address, not a device identifier.
- Which blends you watch. Needed to decide what to send you.
- Aggregate page analytics. Page views and referrers, in aggregate. Used to understand whether the site works.
- Purchase records. The order number, amount, currency and item for a completed subscription. Used to measure how many visitors become subscribers. Covered in detail under cookies and analytics below.
What we do not collect
- No card details ever reach us. Stripe takes the payment and holds the card; we receive only an email address, a subscription id and the status of the subscription.
- No advertising identifiers, no cross-site tracking pixels, no data broker feeds.
- No precise location. We do not ask for it and the site does not read it.
- No contact lists, no address book access.
- No data from your retailer accounts. We never ask for your Smokingpipes or any other shop login.
Cookies and analytics
The site has no login, so it sets no login cookie.
We use two analytics tools. Neither is used to build a profile of you across other sites.
Cloudflare Web Analytics measures page views and referrers only. It is cookieless and does not fingerprint visitors.
Google Analytics 4 is loaded through Google Tag Manager as the page loads. It does not store the IP address your browser sends. It measures page views and the interaction events Google Analytics collects by default, such as scrolls, outbound link clicks and video plays.
It also sends one event of our own. When a purchase completes, the confirmation page at /thanks pushes a single purchase event into the Google Tag Manager data layer, carrying the order number, the amount, the currency and the item bought. That page pushes it only after our server has re-checked the checkout with Stripe and found it finished with nothing left owing, so the record describes a completed sale rather than a visit. Reaching /thanks without a finished checkout behind it sends nothing. The purpose is to measure how many visitors become subscribers.
The purchase event carries no name, no email address and no other personal identifier. The order number in it is Stripe's checkout session id, which identifies the transaction rather than you.
Google Analytics sets a first-party cookie in your browser so it can tell a return visit from a new one. That cookie is not an advertising cookie and it is not used to follow you to other sites.
We run no advertising tags, no remarketing, no ad platform conversion tracking and no cross-site tracking pixels.
Analytics loads without a consent banner today. If we introduce advertising or cross-site tracking cookies, we will ask for your consent before setting them and update this policy first.
Who else sees your data
A small number of processors, each limited to what their job requires:
- Cloudflare hosts the site and the database.
- Stripe takes the payment, holds the card details and sends the receipts. We never see a card number.
- Our email provider delivers mail such as the reply that contains your ntfy topic.
- ntfy.sh delivers notifications to your phone.
Topic names on ntfy.sh are not secret from other ntfy users. Public topics can be read and posted to by anyone who knows the name, and the name is the only credential. We generate ours at random and do not publish them. Do not rely on a topic name to carry anything private.
We do not sell, rent or share personal data with anyone else. We do not transfer it to data brokers or advertisers. We will disclose data if legally compelled, and we will tell you when we are allowed to.
How long we keep it
We keep your email address and topic name until you ask us to delete them, and then we delete the signup record within 30 days. Billing records are different: Stripe keeps the payment history it is legally required to keep, and we keep the subscription id and its status for as long as the subscription exists. Monitoring history that is not tied to an individual is kept indefinitely as part of the public stock record.
Your choices
- Access and export. Write to us and we will send you what we hold. It is a short list.
- Correction. Write to us and we will fix it.
- Deletion. Write to us and we will delete your signup record and its data. No retention creep.
- Stop alerts by removing the topic in the ntfy app. That works immediately and needs no request to us.
We answer these requests within 30 days, usually much faster.
Security
Data is encrypted in transit. Access to the production database is limited to the operator. We do not have a security team, and we will not claim to be unhackable. If a breach affects your data, we will tell you what happened and what was exposed.
Children
The service is for adults of legal smoking age in their jurisdiction. It is not directed at anyone under 21 in the United States, and we do not knowingly hold data from minors. If you believe a minor has an account, write to us and we will remove it.
Changes
If this policy changes in a way that matters, we will email account holders before the change takes effect. The effective date at the top always reflects the current version.
Contact
pengtengpt3337@agent.qq.com
Operated by 2fermat · 2543 Borax Dr, Santa Clara, CA 95051