Your information

Privacy policy

Last updated: 15 September 2026

This policy covers the Quitpod app, including quitpod.app. Nicholas Holden operates Quitpod and is responsible for its handling of personal information. Contact support@quitpod.app with privacy questions or requests.

Google sign-in and your account

If you choose Google sign-in, Google provides your account identifier, name, email address, email verification status and profile picture. Supabase Auth stores this identity and manages your sign-in session. We use it to recognise your account, show your signed-in status and administer your AI allowance and purchases.

Quitpod requests only basic sign-in permissions: OpenID, email and profile. We do not request Gmail, Drive, calendar or contacts access. Your Google password is not shared with Quitpod. Your Google identity and profile are not included in AI prompts; your email may be supplied to Stripe when you open payment checkout.

We do not sell Google user data, use it for advertising or use it to train AI models. Quitpod's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can revoke Google access in your Google account connections; this does not itself delete your Quitpod account or local notes.

Book bookmarks across devices

When signed in, Quitpod saves your place in each book chapter or section in Supabase, linked to your account. We store the chapter or section identifier, text position, a revision identifier and the server update time. Bookmarks are used to resume reading across your devices and are not included in AI prompts. No chapter text or private notes are uploaded as part of bookmark sync.

Bookmarks also remain cached on your device for offline reading, separately for each account. Existing device bookmarks are imported into the first account used after this feature is enabled. If another device has already changed a bookmark, the newer server version takes precedence over an older offline edit. Guest reading remains local to the device. Clearing local data removes the device copies; signed-in bookmarks can be downloaded again. Account deletion removes the server bookmarks.

What stays on your device

The app saves your preferences, consent choice, quit plan, course progress, conversations, journal and private journey notes in local device or browser storage. These records are not encrypted by the app. They are kept separately for each signed-in account, so signing out hides your records from the next person using the same device or browser profile. Records made before you first signed in become that account's. Anyone who can sign in as you, or who uses the app without signing in, may be able to read the records held for them.

Use Settings → Clear all data on this device to remove these local records, or clear the site's storage in your browser. Do this separately on each device you have used. Clearing local data does not delete your server account, reset your free allowance or cancel a payment plan. The saved support context described below is not a full app backup and does not restore app chats, task answers or private notes.

Daily check-in reminders

A daily reminder is optional and off unless you turn it on. In the installed Android or iPhone app it is scheduled by your phone, and nothing about it leaves the device. In a browser it is delivered by your browser's own push service, which needs a delivery address, so we store one record for that browser: the push address your browser issued, the two keys needed to encrypt to it, the time you chose and your time zone.

That record is not linked to your account, and contains no name, email address, phone number, saved focus or anything about your quitting. The reminder itself says only that a check-in is waiting; it never contains your saved focus, a health detail or any claim about what you have done. We keep a record of when a reminder was last delivered so the app can tell you if reminders have stopped reaching you.

Turning the reminder off deletes the record, and so does clearing the site's storage. We also delete it if your browser tells us the subscription no longer exists, if reminders repeatedly fail to send, if a first reminder is never confirmed within seven days, or after ninety days without a delivered reminder. Delivery depends on your device and operating system settings, and your browser's push service handles the message in transit.

Saved quit context

When you agree to AI sharing while signed in, Quitpod saves an account snapshot of your quit profile (name, reason, trigger, spending and quit date), quit-plan answers and approach, whether the app takes you to be vaping, and course progress (current stage/page, task counts and latest check values). Changes sync while the app is open and connected; offline changes retry later. Your quit profile and plan, including the quitting status choice and quit date, also load on your other signed-in devices after the same agreement. Course summaries support replies but do not restore task history or course position on another device. The latest successfully synced snapshot supports conversations on your linked WhatsApp number. It is not live observation or verified abstinence. Book bookmarks already sync separately and show saved reading places, not proof that a chapter is finished.

These fields are stored in Supabase under your verified account, with a schema version, update time and consent version. No app chats, journal entries, private task answers or journey notes are included. We retain this context until you withdraw AI sharing or delete your account. Turning off AI sharing clears the saved context and Quitpod’s WhatsApp chat memory once connected; the app shows if that clear must retry. A content-free revision marker prevents old uploads recreating the data. Book bookmarks remain until account deletion. Service backups may keep earlier copies for their normal backup period. Later categories of synced information will be described before collection.

Offline use and updates

To let Quitpod reopen offline, your browser also downloads a local copy of the app, book, fonts and images. This public-file cache is separate from your personal records and excludes account, AI and payment responses. App updates replace public files without clearing your saved plan or notes.

When you choose AI

The opening notice explains AI sharing and saved account context. Choosing “I understand, let’s begin” enables them; choosing “Continue without AI” leaves sharing off. If you choose AI later, we ask for your agreement then. You can change sharing in Settings. To generate a reply, Quitpod sends your message, recent conversation and relevant saved quit-plan answers through our Supabase API to OpenRouter and the model provider it routes to. This includes what vaping does for you, your reasons for stopping, environment changes, support people, withdrawal preparation and slip plan, alongside your quitting approach and date. Shared context can include your buddy focus, a selected journey step or activity, and a trigger moment and reported outcome you choose to discuss. Requested AI readings and check-ins also use this context.

Private journal entries, task answers and private journey notes are excluded from these requests. Anything you copy into a conversation becomes part of the shared conversation. Please avoid sharing information you do not want processed by an AI provider, or private information about other people.

Messages about nicotine use, cravings or wellbeing may reveal health information. We use your consent for optional AI sharing, including your explicit consent to process health information you choose to share for replies. You can withdraw that consent in Settings by turning off “Allow AI message sharing”. This stops future AI sharing; it does not undo processing already carried out. The free tools remain available.

Our AI provider is OpenRouter, which routes requests to the model provider selected by Quitpod. Requests exclude providers that permit training on submitted data. This is not a guarantee of zero retention: OpenRouter and model providers have their own operational and abuse-prevention practices. See OpenRouter's privacy policy, its provider data policies.

For web-app conversations, Quitpod's account database stores AI request identifiers, timestamps, request status and credit balances, not the text of your conversations. The API processes conversation text to produce a response; the app saves delivered replies locally.

WhatsApp support

Optional WhatsApp support is for adults with a verified account connection. WhatsApp sends Quitpod your phone number, message identifier, timestamp and message text so we can reply. The first reply explains AI sharing; no message is sent to an AI provider until you tap “I agree” or reply AGREE after seeing that notice. This includes explicit consent to process health information you choose to share. Only typed messages are supported for support conversations; consent buttons are also available.

Unlike the web-app chat, WhatsApp support keeps recent conversation and an AI-written summary in Supabase so follow-up messages have context. Messages waiting for a reply are temporarily queued there. Processed queue entries retain message identifiers and delivery-attempt metadata, with their text removed. Conversation and delivery records are removed after seven days of inactivity; routine service backups may retain earlier copies for their normal backup period. WhatsApp and AI providers have their own retention practices. Phone numbers are not included in AI requests.

Reply STOP to withdraw AI-sharing consent, cancel queued replies and clear Quitpod's active conversation memory. Reply RESET to clear that memory while keeping your existing consent, or START to request support again. These commands do not delete messages from your WhatsApp account, Meta's systems, AI-provider records or backups. WhatsApp chat events are not sent to our optional usage analytics. Contact support@quitpod.app for help with your information.

To receive AI replies, connect your WhatsApp number from your signed-in app account, send the connection message through WhatsApp, and confirm the number in the app. Quitpod stores the verified phone-to-account link until you disconnect it or delete the account. Connection requests expire after ten minutes. Following the WhatsApp agreement, support can use your saved quit context and book bookmarks from the same account as your credits. App chats, journals and private task notes are not copied into WhatsApp. Disconnecting clears Quitpod's WhatsApp chat memory; your account context remains for the app. STOP and RESET clear WhatsApp chat memory, not your saved app context or bookmarks.

Each AI reply uses one request from your account's shared free and paid balance. Linking, consent and control commands use no credits. We store the request identifier and delivery status to prevent duplicate charges and refund failed replies. A credit is returned if delivery is not confirmed within thirty minutes. STOP clears memory and consent; it keeps your number linked so you can return with START. Use Disconnect WhatsApp in account settings to remove that link.

Optional usage analytics

Analytics is off until you choose “Allow analytics”. With your separate, explicit consent, Quitpod sends basic usage events to PostHog Cloud EU to understand which features are used, whether AI replies arrive, and how well the website loads and responds, and diagnose problems using masked web session recordings and error reports. Saying no does not limit the app. You can change your choice using “Share usage analytics” in Settings.

Events describe app visits, clicks on public controls, the main screen opened, opening support, starting the journey, completing a practice, advancing a lesson, and AI requests, replies, failures or cancellations. They include a timestamp, a random analytics reference, platform, app version, consent version, test or production status and, for AI requests, chat or insight type and a broad reply-time band. We do not send messages, journals, private notes, account identifiers, names, emails, private trigger descriptions, precise location, full page addresses or advertising identifiers. Quit-plan answers are also excluded.

On the website, we also collect page views and departures, visit and page references, visit length, scrolling, browser name and version, operating system, device type and screen size. Screen events identify general app tabs (path, talk or practices). Browser page addresses describe the website page being viewed. Referrers contain only the originating website address, without its page path. URL queries, fragments, search terms and advertising click IDs are excluded. Performance measurements cover loading, responsiveness and visual stability (FCP, LCP, INP and CLS); they do not include page text, images or the contents of interactions.

On the website and installed web app, masked session recordings show public interface text, layout, navigation, scrolling and pointer interactions. Form inputs are masked. Displayed chats, AI replies, private quit-plan answers, notes and account details are blocked before transmission. Images, drawings, embedded content, console logs and network request or response bodies are excluded. Error reports include the error type, app build and code location; free-text error messages, local variables and URL queries are removed. Failed AI requests also produce a generic error report without the request or reply.

The analytics reference is stored locally and is separate from your sign-in and AI identities. It lets us recognise repeat use from the same installation or browser. This is pseudonymous information, not anonymous information: using a vaping support app can itself reveal information about your health. Your explicit analytics consent covers that use. Analytics requests pass through a Quitpod subdomain using PostHog's managed Cloudflare proxy to PostHog's EU service. Cloudflare processes this traffic at its network edge, which may be outside the EU. PostHog receives the network address needed to deliver requests; our configuration discards client IP addresses from stored events. For consenting web visits, PostHog uses the IP address to estimate location, such as country, region and city. This is approximate network location; we do not request GPS or device location permission. Native app analytics does not include location, session recordings or automatic error reports.

Turning analytics off stops future collection and discards unsent events and recordings. It does not delete data already received by PostHog. Your reference remains visible in Settings so you can request access or deletion using the link there or by emailing support@quitpod.app. Save the reference before clearing local data; clearing it removes our way to locate these records using that device. Account deletion alone does not locate analytics recorded under a separate reference.

Analytics is stored in PostHog's EU region. The project's current plan lists a twelve-month event-retention window, but PostHog has not yet enabled automatic expiry for this project. Records therefore remain until deleted; we cannot currently promise automatic removal after twelve months. Session recordings have a separate 30-day retention setting. You can request deletion earlier. See PostHog's event-retention explanation and privacy policy.

Payments, support and service logs

When you buy AI access, Stripe handles checkout and payment details. Quitpod stores the account and payment references, credit allocation and, where applicable, subscription information needed to fulfil the purchase and manage billing. We do not receive or store your full card number. See Stripe's privacy policy.

If you email support, we receive your email address, message and any information you include. Hosting and authentication providers may also process IP addresses, browser information, request times, sign-in events and error information to operate and secure the service.

Providers and international processing

We use Cloudflare to host the website, Supabase for authentication, the API and account records, Google for sign-in, OpenRouter and its model providers for AI, Stripe for payments, and PostHog Cloud EU for optional usage analytics. They receive information needed for those functions. We may disclose information when legally required or necessary to investigate fraud or protect the service and its users.

These providers may process information outside your country, including in the United States. Their processing locations and protections depend on the service used. Contact us for information about the applicable arrangements and international-transfer safeguards. More information is available in Cloudflare's, Supabase's and Google's privacy policies.

Why we use information and how long we keep it

We use account and billing information to provide the service you request and fulfil purchases. Optional AI sharing and optional analytics each rely on separate consent, including explicit consent where the information reveals health information. Service security, fraud prevention and responding to support requests serve our legitimate interests in running a reliable app. Where necessary, we retain financial records to meet legal obligations.

Local records stay until you delete them or your device or browser removes them. Account and allowance records remain while you use the account. On a deletion request, we remove information we no longer need; limited payment, fraud-prevention or dispute records may need to remain for applicable legal requirements or outstanding claims. Provider logs, backups and AI processing records are subject to each provider's retention arrangements. We do not promise that signing out immediately deletes records.

Your choices and rights

Email support@quitpod.app to request account deletion, access to your server-held data, a correction or other help with your information. We may need to verify that the request comes from the account holder. We cannot read or remotely erase notes stored only in your browser.

Depending on the applicable law, you may have rights to access, correct, delete, restrict processing or receive a portable copy of your information. You can withdraw consent for future AI sharing or analytics at any time in Settings, using their separate controls.

You can object to processing based on our legitimate interests. Contact us using the email above and explain your request.

You can complain to your local data protection authority. In the UK, contact the Information Commissioner's Office. Quitpod does not use AI to make decisions about you that have legal or similarly significant effects.

Cookies, age and changes

Quitpod uses necessary local storage for sign-in, preferences and saved app data, including your analytics consent choice. An optional analytics reference is created only when you agree. Our analytics integration does not use cookies or persistent event queues. After consent, the website uses tab-scoped session storage to group visits across reloads; this is cleared when you withdraw consent. We do not include advertising trackers. Linked sign-in and payment services apply their own cookie policies.

Quitpod is intended for adults aged 18 and over. If you believe a child has shared personal information with us, contact us so we can address it.

We will update this page when our data handling changes, show a new date and provide an additional notice when a material change requires it.