nolapse is published by singlethreadapps, the trade name of an independent developer established in Portugal, European Union ("the Developer", "we"). The data controller is Carlos Santos, trading as singlethreadapps.
Contact for any privacy matter: support@getnolapse.app
This Privacy Policy applies to the nolapse mobile application for iOS and Android ("the App") and to the website getnolapse.app ("the Website"). It is provided in accordance with the General Data Protection Regulation (GDPR — Regulation (EU) 2016/679) and other applicable law.
The App was built around one principle: your data stays on your device. There are no user accounts, no backend that stores your usage, no analytics and no advertising.
Everything you enter or generate in the App — check-ins, filter outcomes, impulse history, risk windows, statistics and settings — is created and stored locally on your device. The App does not send it to the Developer or to any third party. The Developer cannot see what you log, how often you use the filter or how much you estimate not spending.
The only personal data processed outside your device relates to subscriptions (Section 4.1), support requests you choose to send (Section 4.2) and the normal operation of the Website (Section 4.3).
The following data is stored only on your device and is not transmitted by the App:
| Data | Purpose |
|---|---|
| Check-ins — intensity, trigger, estimated spend | Filter evaluation and history |
| Filter outcomes, cooldowns and timestamps | Applying the decision for each window; impact tracking |
| Impulse history (full log in Pro) | History, patterns, monthly report |
| Risk windows — days and time blocks | Filter calibration and local notifications |
| Session reports — whether you played and the amount you declare | Money not spent; declared sessions shown separately |
| Statistics — impulses interrupted, resistance rate | Dashboard |
| Settings — language, currency, notifications, cooldown, Pro filter parameters | App configuration |
Reminders (for example at the start of a risk window or at the end of a cooldown) are scheduled locally by the App on your device. No push service or server is involved. You can turn them off in the App or in your device settings.
When you generate a report or export your history, the file is created on your device. If you share it through your device's share menu, it goes only to the destination you choose.
Depending on your device settings, your operating system may include app data in device backups (for example, Android backup to your Google account, or iCloud or computer backups on iOS). These backups are created and managed by Google or Apple under your account and their terms. The Developer has no access to them. If you do not want App data included, change your device's backup settings.
You can permanently delete all local data at any time in the App (Settings → Delete Profile) or by uninstalling the App. Copies held in device backups are managed through your Google or Apple account.
Pro is purchased through the Apple App Store or Google Play. Payments are processed by Apple or Google; the Developer never receives your payment card details.
To verify whether Pro is active, the App uses RevenueCat. RevenueCat processes: a random, anonymous app user ID generated by the App; your nolapse purchase history (product, purchase and renewal dates, subscription status); store transaction identifiers; and technical data needed to communicate with its servers, such as IP address, device model, operating system and app version, country or locale and currency. The App does not send RevenueCat your name, email address or any usage data. RevenueCat also uses this subscription data to give the Developer aggregated statistics (for example, the number of active subscriptions and revenue), which do not identify you.
Access codes: if you redeem an access code we have given you (for example as a tester or store reviewer), the App checks it on your device and then identifies itself to RevenueCat with the app user ID linked to that code instead of a random one. The code itself is not sent. Several people may share the same code, so the ID does not identify you.
The app stores also make transaction records available to the Developer (for example order identifiers, product, country and amounts) for accounting and support.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR) and compliance with legal obligations, such as accounting and tax records (Art. 6(1)(c) GDPR).
If you use the contact form on the Website or email us, we process your name, email address, the topic and the content of your message, and any other information you choose to include, in order to reply. Form messages are delivered to our support mailbox by email. Please avoid sharing more about your gambling behaviour than your request requires.
Legal basis: our legitimate interest in answering your request and, where it concerns your subscription, performance of a contract (Art. 6(1)(f) and 6(1)(b) GDPR).
The Website does not use cookies, analytics or advertising, and does not load resources from third-party servers (fonts are served from our own server). Like any website, our hosting provider records standard server logs (IP address, date and time, page requested, browser type) for security and operation. To prevent abuse, the contact form keeps a pseudonymised (hashed) form of your IP address for up to one hour.
Legal basis: our legitimate interest in operating and securing the Website (Art. 6(1)(f) GDPR).
We do not sell personal data, do not share it for advertising and do not use it for profiling.
Information about gambling behaviour may be sensitive. The App is designed so that the Developer never receives it: check-ins, triggers, spending estimates, outcomes and history are not transmitted by the App and are not accessible to the Developer.
The Developer only receives such information if you choose to include it in a support request.
Under the GDPR you have the following rights regarding personal data processed by the Developer:
To exercise them, contact support@getnolapse.app. We aim to respond within one month.
Because the App has no accounts and the Developer cannot see data stored on your device, that data cannot be linked to you by the Developer (Art. 11 GDPR). You can view, export and delete it yourself directly in the App. For subscription records, please include your store order ID so we can locate them.
You may also lodge a complaint with the supervisory authority of your country of residence or, in Portugal, with the CNPD (cnpd.pt).
Communication with RevenueCat and with the Website is encrypted (HTTPS/TLS). Access to the support mailbox is restricted to the Developer. Data stored by the App is kept in the App's private storage, protected by your operating system; we recommend protecting your device with a screen lock.
RevenueCat processes data in the United States. Such transfers are covered by the safeguards provided for in Chapter V of the GDPR, namely the European Commission's Standard Contractual Clauses included in RevenueCat's data processing terms or, where applicable, an adequacy decision. Apple and Google transfer data under their own terms.
Neither the App nor the Website uses cookies, advertising identifiers, analytics tools or tracking across apps and websites. RevenueCat's anonymous app user ID is used only to verify subscription status and to produce the aggregated subscription statistics described in Section 4.1, never for advertising or profiling.
The App and the Website are intended exclusively for adults aged 18 or over. We do not knowingly process personal data of minors.
We may update this Policy. Material changes will be announced on the Website and, where possible, through an App update or the store listing, at least 15 days before they take effect, unless a shorter period is required for legal or security reasons. The version and effective date are shown at the top of this page.