Effective 18 November 2026

Privacy policy

Your account syncs selected habit IDs, names, categories and archived status. After you agree to tracking sync, it also syncs check-in dates, habit IDs, check-in/slip status and streak values; the account server can read those fields. Mood ratings, reflection text, journal entries, Urge Replay sequences and intervention notes, personal notes, habit-frequency answers, and optional typical amount, time and cost estimates stay on each device and are excluded from ordinary account tracking sync. Urge Replay suggestions are calculated on-device from repeated reported contexts, are not proven causes, and are never sent to cloud AI. On a later consented tracking sync, previously stored account mood fields are removed. An optional recovery-phrase copy is encrypted on your device before upload and includes habit labels, check-in dates/status, Plus Home title/cover, and device-only frequency/personalization details; old encrypted copies may retain previously included private fields until synced again or deleted. Optional Android app-time and website-domain summaries are separate opt-ins. Eligible iPhone users may opt into automatic weekly Screen Time challenge scores; only the weekly change is sent, and this requires Apple’s extra entitlement and EU eligibility. Other iPhone users can enter averages manually. Grow Together stores daily step totals and source; leaderboards use anonymous member handles and never show real names, email addresses or habit types. The desktop challenge display is static and makes no live data or account connection. We do not sell, rent or share personal data for advertising, or willingly give it to unrelated people. Account details, community posts, challenge contributions, private community-block preferences, messages, data-rights requests, organisation enquiries and purchase records are separate and use the limited service providers described below. There is no in-app AI feature, profile-photo upload or general file-upload service.

Optional encrypted diary sync

Habit names and categories are stored in your signed-in Prune account and can be read by Prune. After you consent, check-in dates, checked-in/slipped status, and streak values are also stored in the account and readable by Prune. Mood ratings, reflections, Urge Replay notes, journal text, and notes stay on each device only and are excluded from new syncs. The optional recovery-phrase copy is separate: new copies include habit labels and categories, check-in dates and status, and Plus Home title and cover, encrypted on your device before upload. Older encrypted copies may still contain moods or private text until you confirm a replacement or delete them. The phrase is never sent to Prune.

Optional website visit analytics

Separately from diary sync, Prune Plus members can turn on website analytics in the Analytics section. The paired browser extension keeps a rolling 30-day count locally, encrypted in that browser profile. When you sync, only the top five domain names and visit counts are encrypted on your device with your recovery phrase before upload. Prune does not receive or save that phrase and cannot read the synced totals. Page URLs, titles, search terms and page contents are not collected. Use the same phrase on each device; if you lose it, Prune cannot recover the encrypted totals. Turning the feature off deletes the encrypted account copy and clears local counts in the connected browser; account deletion also removes the account record. If the browser is unavailable, the account copy can still be deleted, but local tracking must be turned off in that browser.

Anonymous exit surveys

If you choose to answer after cancelling a store subscription or before deleting your account, Prune sends one selected reason category without your name, email, account ID, habit details, or written response. Prune stores only combined counts by reason and survey trigger for product improvement. The totals are available only to the verified owner account, and an individual answer cannot be removed later because it is not linked to an account. Hosting providers may process technical connection details to deliver and protect the request.

Optional weekly community challenges

If you submit a weekly challenge score, Prune stores your account ID, selected challenge category, week start, one aggregate score, its source and the time you agreed to share it. Android calculates screen-time change on your phone from selected apps; only the change in minutes per day is sent. Eligible iPhone users can opt into automatic Screen Time sharing: on iOS 26.4 or later, after Apple's separate data-access entitlement and permission, Prune reads only the device's total usage locally and shares one weekly change when the user opens Prune after a completed week. Apple limits this automatic access to devices in the EU using an EU-region Apple Account; it is not available in the UK. Other iPhone users can enter the two weekly averages manually, and only their difference is sent. Smoking and drinking support challenges send only a weekly step total from Apple Health or Health Connect; steps do not prove a change in smoking or drinking. Other members see an anonymous ranking label, not your name, email or account ID. The chosen challenge category is known to Prune and identifies the group you joined. Your profile badge is private; the leaderboard may mark a winning anonymous row. You can turn off automatic sharing or delete all your challenge scores and badges from Profile & settings, or by deleting your account.

Private challenge starting average

The screen-time starting average is stored only in this phone's encrypted Prune data. Android also keeps the selected app IDs on that phone so it can compare the same apps; those IDs are not uploaded for the challenge. Eligible iPhone users' Screen Time is read locally; app names and daily records are not uploaded. The server receives only the weekly change after the user opts into submitting scores or automatic sharing. A user-created encrypted backup may include the starting average.

Community blocking

If you block a community member, Prune stores a private account-to-account block record to hide each other’s forum posts and prevent replies between the two accounts. Your blocked-member list uses anonymous controls rather than showing account IDs or revealing the identity behind an anonymous post. You can unblock members at any time. Account deletion removes block records where your account is either the blocker or the blocked member.

How information is collected

You enter a profile name and confirm that you are at least 18 before creating an account. You choose your habit names and which are active or archived; habit IDs, names, categories and archived status sync with your account. Before tracking history is first synced, you must agree to send check-in date, habit ID, checked-in/slipped status and streak values. Mood ratings, reflection text, journals and personal notes remain local. Your chosen sign-in provider supplies account information to Clerk. Purchases are collected through the payment provider or app store, not through a Prune card-entry form. Device permissions provide optional local protection and usage information. Hosting and sign-in providers receive technical information needed to handle requests, such as IP address, browser/device details, session cookies and operational logs.

Private data on your device

Mood ratings, check-in reflection text, journal entries, Urge Replay sequences and intervention notes, unblock reflections, personal notes, personal motivation, daily goals, focus-session state, bedtime preferences, reminder questions and answers, word and website lists, and app-limit preferences remain encrypted locally and are not included in new account tracking sync. Urge Replay’s repeated-context suggestions are on-device associations, not proven causes, and replay content is never sent to cloud AI. Check-in dates, habit IDs, statuses and streak values sync only after consent. Habit IDs, names, categories and archived status sync separately to the account. The optional recovery-phrase copy is encrypted on your device and includes habit labels, check-in dates/status and Plus Home title/cover; it excludes moods and private text. Older encrypted copies may still include those fields until synced again with your phrase or deleted. Each browser stores its local tracker in IndexedDB using AES-GCM, with its non-exportable encryption key in that browser profile; clearing browser storage may make local history unavailable. Optional iPhone per-app reports remain on-device. On Android, an opt-in uploads selected app IDs/names, today’s total and weekly average; Plus members may separately sync up to 30 daily date/usage totals for selected apps. Detailed usage events and unselected apps are not uploaded. iPhone Screen Time reports remain on the phone. Optional encrypted website analytics sends only the top five domain names and visit counts; page URLs, titles, search terms and page content are not collected.

Account and profile information

Clerk processes sign-in credentials, account email, sign-in method and session information. Google or Apple processes sign-in only when chosen. Prune’s server stores your account ID, profile name, confirmation that you are at least 18, selected habit IDs/names/categories/archived status and tracking fields after consent: check-in date, habit ID, status, best streak and streak-at-slip. Mood ratings are not included in new account tracking state. We do not collect a date of birth. These records provide your account and sync the selected habit list and agreed tracking history.

Images, uploads and storage

Prune no longer offers profile pictures. There is no general file-upload endpoint and no public Prune upload bucket. Private homepage covers are stored locally by default and may be included in the optional recovery-phrase encrypted account copy. Backup imports and exports are processed locally; Prune does not retain exported files. Exported files remain under your control and should be deleted from wherever you save or share them.

Optional bank statement spend check

The free website spend checker reads a CSV statement only in your browser to estimate possible gambling, alcohol and vaping merchant totals. The file and its transactions are not sent to Prune, saved, or included in account sync. Merchant matching can be wrong, and refunds or unrelated purchases can affect totals; review the rows and use a statement you are comfortable opening in your browser.

Optional nearby pause places

Prune Plus can use foreground location only after you choose to save a trigger place and grant your phone permission. Prune checks only while the app is open, rounds the saved coordinates, stores them in your encrypted on-device data, and does not send or sync them to Prune. There is no background or continuous location tracking. Remove saved places from the Tempted screen. If you create an optional encrypted backup, it may include those saved places.

Community posts, replies and reports

Community posts and replies are text only. When you confirm publication, Prune stores your text, topic, author account ID, anonymity choice, thread relationship and time, and shows it to other forum members. Anonymous posting hides your name from other members, not from the service operator. Please do not post information you want to keep private. While you draft a post, the app or browser may match a short list of crisis-related phrases locally to show a support reminder. This simple keyword check is not AI, is not monitored, may miss context, does not alert staff, and does not send or separately store your draft. Your post is uploaded only if you review and confirm it. Report actions are available on other members’ posts and replies. Reports store the post ID, reporter account ID and report time for moderation; reporter identities are not shown to forum members or in the moderator review interface. Deleting a reply removes it. Deleting a thread-starter replaces its text with a deletion marker so others’ replies remain; that marker currently retains its account association until account deletion. Reports for the deleted post are removed. Organisations do not receive members’ habit activity.

Organisation enquiries

If you submit the organisation form on the website, Prune stores your name, email address, optional phone number, organisation, optional message and submission time in its server database so the publisher can review and respond. The record is matched by the email you enter and is not linked to a Clerk account ID. To request removal sooner, email prunehealth.life@gmail.com from the same contact address and include the organisation name and approximate submission date; the publisher will find and manually remove it from the private in-app inbox. It is automatically deleted 90 days after submission. Do not include private habit notes.

Website support messages

If you use the Support form, Prune stores the name you choose to provide, email address, selected topic, message, status and submission/update times in its server database. The record is matched by the email you enter and is not linked to a Clerk account ID. To request removal, email prunehealth.life@gmail.com from that same address and include the topic and approximate submission date. The publisher locates it in the private in-app inbox, marks it resolved as part of handling the removal request, and deletes it. It has no automatic expiry. Messages are not sent to an AI service; there is no automatic email notification or promised response time. Please do not send passwords, sign-in codes, card details or private habit notes.

Newsletter signups

If you sign up for Prune updates on the website, your email address is stored in the publisher’s private website inbox so the publisher can follow up about Prune news. It is not linked to a Clerk account ID and this form does not send automated newsletter emails or confirmation emails. The signup has no automatic expiry; contact the publisher from the same email address to request its removal.

Privacy requests

Signed-in users can submit a general privacy question from the in-app Privacy request form. Prune stores the account ID, verified sign-in email, request category and message, plus the status and reply. The request is visible to the submitting account and the verified publisher; the sign-in email is shown only to the publisher. Replies appear in the app and are not emailed. Do not include passwords, sign-in codes or private habit notes. Requests are not sent to AI. They have no automatic expiry; the publisher can remove a request after it is resolved. Deleting an account also removes that account’s privacy requests.

Data-rights requests

Signed-in users can submit access, correction or deletion requests from Profile & settings → Privacy → Data requests and check their status there. Prune stores the account ID, request type, optional message and status. These request records do not include your encrypted on-device habit history or your sign-in email. For help or to make a request if you cannot sign in, contact prunehealth.life@gmail.com. This public contact address does not grant access to the private inbox; only the configured verified primary sign-in account can list or manage requests in the app, and the server checks this permission for every owner action. Completed requests are automatically deleted one year after completion; account deletion also removes that account’s requests.

Payments and purchases

New website Prune Plus checkout and website contributions are paused. Existing website subscriptions started before checkout was paused may continue to renew until canceled; signed-in members can manage or cancel them from the website account. Stripe handled past website Plus purchases and contributions and may retain payment records under its own policy. If and when native mobile store products are released, Apple App Store and Google Play will process those in-app purchases, including any one-time lifetime and monthly products made available there. RevenueCat receives the signed-in Prune account identifier from the mobile app to link store entitlement information for restore and Plus access checks; the native store purchase flow has not yet been verified in a signed release. Prune does not receive full card numbers. The Stripe webhook remains in place to process legacy website purchase, subscription and refund events; it does not store raw webhook payloads in Prune's PostgreSQL database. The connected Stripe account is also used by another service; Prune processes only matching Prune events. Earlier webhook versions may have copied Stripe records before this change; older records may remain. Apple, Google, Stripe and RevenueCat retain payment or store records under their own policies. The website may request the signed-in account's Plus status to apply habit limits; this request does not include tracker contents.

Purposes and legal grounds

We use account data to provide and secure your account, community text to provide the forum you choose to use, reports and short-lived in-memory rate limits to prevent abuse, enquiry and privacy-message or data-rights-request information to answer you, and purchase records to verify payment and access. Where UK/EU data-protection law applies, these activities rely on providing the service you request, legitimate interests in security and moderation, consent for optional permissions where required, and legal obligations where applicable. We do not use private habit data for marketing, advertising, profiling or automated decisions. Optional features can be declined without losing the core private trackers.

Service providers and sharing

We do not sell or rent personal data, use data brokers, serve ads, share it for third-party marketing, or voluntarily hand it to unrelated people or organisations. Limited processing is provided by Clerk (sign-in and account security), Google or Apple (only your chosen sign-in), Replit (website/API hosting and the configured PostgreSQL database, plus website analytics if enabled), Stripe (legacy website subscriptions and past website payments; new website checkout is paused), RevenueCat (intended mobile store entitlement processing when native store billing is released), Apple App Store or Google Play (mobile billing and distribution when available), and Cloudflare (only if you enable DNS protection). The account database stores selected habits and, after consent, check-in and streak fields; moods, reflections, journal text and notes are excluded from new tracking sync. Community text is shared with members only when you choose to publish it. We may need to disclose information where legally required. Providers have their own privacy practices and may process information in other countries; the publisher must confirm applicable international-transfer safeguards before launch.

Website analytics, cookies and fonts

The native mobile app has no advertising, analytics or crash-reporting SDK. Authentication uses essential session storage/cookies managed by Clerk. Replit Project Analytics is off until enabled in Publishing settings for the published download website. If enabled, it processes page views and traffic information such as visit sources, top pages, countries, browsers and devices, including IP-based traffic data. Replit Project Analytics does not record session replays, clicks or keystrokes. The app contains no separate session-replay or keystroke-recording service. Custom checkout-return analytics send only an outcome category, not account IDs or habit data. Older checkout-return URLs may briefly include a Stripe session ID and, if page-view analytics are enabled, that URL may be processed by Replit. Website fonts are served from Prune’s own website rather than requested from Google Fonts.

AI

Prune currently has no in-app AI or generative-model feature and does not send account, community or habit data to an AI service as part of its features. Urge Replay suggestions use on-device repeated-context rules, are not proven causes, and do not send replay text to an AI service. Word filtering uses local matching rules, not AI. If an AI feature is introduced, its data use and provider will be disclosed before it is enabled, with consent where required.

Permissions and protection

Optional check-in notifications are scheduled on your device and can be declined or turned off. Prune Word Guard uses nearby text locally to apply your selected word rules; it does not store, log or send what you type to Prune’s server. Turning on Face ID or fingerprint requires a separate in-app confirmation before the device authentication prompt; the device handles biometric matching and Prune does not receive face or fingerprint data. On iOS, Allow Full Access shares encrypted rules and exceptions locally between Prune and its keyboard; the keyboard has no network code. The Android release includes the optional keyboard and optional selected-app boundaries. Before opening Android Accessibility or Usage access settings, Prune shows a separate in-app disclosure and asks you to agree. Accessibility access is used to notice the foreground app name only for apps you selected, so Prune can apply your chosen pause or time limit; it does not read screen contents, web-page text, messages, typed words, passwords, notifications or taps. Android’s Usage access is device-wide: Prune requests local app-use summaries, immediately discards records for apps you did not select, and uses only selected apps’ times to show the on-device report and enforce your daily limits. The system app picker may display launchable app names so you can choose targets. Selected app names and boundary settings are encrypted on the device. Android app-time sync is a separate choice: if enabled, Prune uploads selected app names and today’s and seven-day-average totals to the signed-in account for display on the website. It does not upload detailed usage events or records for apps not selected. Turning off sync deletes the account’s current snapshot; without sync, usage data stays on the device. On iOS, Screen Time reports remain inside Apple’s report extension and are not uploaded. Usage access and app-time sync are optional, can be declined or revoked, and are not needed for the private tracker. Android users may optionally configure the device's built-in Private DNS to family.cloudflare-dns.com for Cloudflare Families category filtering; this is not a Prune VPN, requires Android 9 or later, and does not apply Prune's custom blocked-site list. Cloudflare receives domain lookups and network connection information, including the source IP address; Prune does not receive or retain those queries. The user can change Private DNS in Android Settings, and the setting may remain after the app is removed. iOS uses DNS-over-HTTPS with certificate and hostname verification after the user's consent when included in an Apple-signed build with the required entitlement. Optional browser extensions request website access to filter supported text fields, hide matching Google results and block adult/personal domains locally. Pairing sends selected rules and exceptions directly from signed-in Prune to the extension in that browser; they are encrypted in that browser profile. Typing, search terms, visited domains, account IDs and rules are not sent by the extension to Prune. Adult-site rules are a bundled snapshot, not a live lookup; personal domains may be requested by the browser before a local redirect. Chrome/Edge and Firefox packages are unsigned previews; Safari requires Mac/Xcode packaging and signing. You can decline or revoke permissions in system or browser settings. No filter can guarantee blocking every harmful site or term.

Browser NSFW filtering

If you enable the paired desktop-browser extension, it checks social websites locally for clear NSFW or sensitive-content labels and hides matching post cards. It does not send page text or labels to Prune. It cannot identify unlabelled content, guarantee detection, or inspect content inside native social-media apps.

Security

The published website uses HTTPS. The API’s remote PostgreSQL connections are configured in code to use TLS with certificate and hostname verification; this describes protection in transit only. Prune does not claim that the hosted database is encrypted at rest because that has not been verified from the provider’s documentation and production settings. Phone activity is encrypted in app storage, and its key is held in the device’s secure system store. Browser tracker entries are encrypted with Web Crypto AES-GCM before they are stored in IndexedDB; the non-exportable key stays in the same browser profile, so this is local protection rather than protection from compromised website code or a compromised browser/device. Clerk handles sign-in passwords and authentication; Prune does not store users’ passwords. Server-side account records and community text are readable by Prune’s server while needed to provide those features, and published community text is visible to members. Private API requests are authenticated and checked against the signed-in account by the server. Prune does not use a public bucket for user uploads. Hosting and identity providers may process IP addresses to deliver and secure their services; Prune does not include IP addresses in its API responses or request logs. Data can be present in readable form while a service is processing it, so Prune cannot promise that no plaintext ever exists. No storage or transmission method is completely risk-free.

Retention and deletion

Profile & settings → Privacy contains two separate controls. “Delete all my data” clears this phone’s private records, protection preferences, encryption key and scheduled Prune reminders; it does not close your account. “Delete my account” permanently removes the Clerk sign-in account and its custom image, Prune profile, reports, privacy requests, data-rights requests and your community text. It does not erase local phone or browser tracker history. Clear browser data first in the signed-in website tracker under Settings → Delete browser data if you want to erase that browser’s local copy; use the phone app’s separate “Delete all my data” control for phone records. Thread markers remain without your account ID so other people’s replies are preserved. Completed data-rights requests are automatically deleted one year after completion; open requests are removed when their account is deleted. Website support messages and organisation enquiries are not linked to a Clerk account and are not removed by account deletion. They are matched by the email entered on the form and kept in the private inbox. Organisation enquiries are automatically deleted 90 days after submission; website support messages have no set automatic deletion date. To request earlier removal, email prunehealth.life@gmail.com from that same address with the message type and approximate submission date; the publisher marks an open support message resolved as needed, then deletes it as part of handling the request. Provider payment/security records and operational backups may remain under the provider’s retention policies or legal obligations; account deletion does not refund or transfer purchases. Prune does not retain uploaded backup or homepage-image files on a server.

Your choices and rights

You can change your display name, choose whether to publish community text, delete your posts, decline optional permissions, export a password-protected local backup, clear device records or delete your account. Signed-in users can submit access, correction or deletion requests from Profile & settings → Privacy → Data requests and check their status there. Former users and people who cannot sign in can email prunehealth.life@gmail.com or use the public Support form; messages appear in the publisher’s private in-app inbox but do not trigger an automatic email notification or response-time promise. Depending on your location, you may also have rights to restrict or object to processing, obtain a portable copy, or complain to a data-protection regulator such as the UK Information Commissioner’s Office.

External links and children

Support links and website checkout open external services with their own privacy practices. Prune does not attach your private habit activity to those links. Prune is intended for adults aged 18 and over; account creation asks you to confirm that you are at least 18, and the server requires that confirmation before enabling the account profile and community access. This is an age declaration, not identity-document verification. Prune is not designed for children.

Optional website filtering

If you enable website filtering, DNS domain lookups are processed by Cloudflare Families, which supplies adult-content and malware category filtering. Cloudflare receives the requested domain names and network connection information, including the source IP address, needed to answer these lookups; Prune does not receive a history of the domains you visit. This feature does not inspect webpage text, encrypted search terms or messages, and filtering is not guaranteed. On Android 9 or later, you manually set Android Private DNS to family.cloudflare-dns.com; this uses Android’s system setting, not a Prune VPN, and does not apply Prune’s custom blocked-site list. To stop it, change Private DNS to Automatic or another provider in Android Settings. The setting is controlled by Android and may remain after Prune is removed. On iOS, Prune configures an encrypted DNS profile after your separate consent; it requires an Apple-signed build with the relevant Network Extension entitlement. DNS may be bypassed by browser Secure DNS, another VPN, custom resolvers or direct IP access. See Cloudflare’s privacy policy for its handling of DNS queries.

Grow Together step challenge

If you choose “Sync today’s steps”, Prune asks Apple Health or Android Health Connect for permission and reads only the cumulative step count for the current day. Detailed health records are not uploaded. When you submit, Prune’s account database stores your account ID, date, step total, which health source was used and your leaderboard name preference. Your steps contribute to the shared challenge total. Your individual total is shown on the leaderboard under your profile name only while you have opted in; otherwise it is shown without your name. Step readings come from your phone and are not independently verified by Prune. This feature is optional and separate from your private habit tracker. You can refuse or revoke health permission in your phone settings; revoking it stops future reads but does not delete totals already submitted. Account deletion removes your challenge entries.

Onboarding frequency answers

During setup or when adding a habit, you may be asked how often it happens. Your selected frequency answers are stored in encrypted app data on your device and are not sent to your Prune account or included in account tracking sync. You can choose “Prefer not to say.” If you create an encrypted backup yourself, the answers are included in that user-controlled backup.

Habit personalization details

You may optionally add a typical amount, weekly frequency, time per day, and cost for a habit so its tools and estimates are more relevant. These details are stored in the encrypted private app data on your device and are not included in ordinary account tracking sync. If you create an encrypted recovery backup, they are included in that user-controlled encrypted backup. You can change or remove these details in Settings.

Changes

The effective date will be updated when this policy changes. Material changes to how personal data is used will be explained before the relevant feature is enabled.

Publisher and contact

Publisher: Yunus Garip. Public contact for privacy and data requests: prunehealth.life@gmail.com. Signed-in users can submit access, correction or deletion requests from Profile & settings → Privacy → Data requests and track their status there. The public email is for contacting the publisher; it does not grant access to the private in-app request inbox, which is managed only by the configured verified sign-in account. Signed-in users can also send a general privacy message from Profile & settings → Privacy. Anyone can use the Support form on the Prune website. Website support and organisation messages are matched using the email address submitted on the form, not linked to a Clerk account ID. To request removal, contact prunehealth.life@gmail.com from that same address and include the message type, topic or organisation, and approximate submission date. The publisher locates and manually removes the record from the private app inbox; for a support message, the publisher marks it resolved as part of handling the request, then removes it. Organisation enquiries are automatically deleted 90 days after submission. Website support messages have no set automatic deletion date. There is no automatic email notification or response-time promise.

This policy should be reviewed against the final app, provider settings and store disclosures before public release.

Optional support

Help keep Prune free and independent.

Prune is free and independently made. Website payments and contributions are paused. Prune Plus purchases are available inside the Prune app through the app store.