Privacy Policy for TidyPepple
Last updated: 14 October 2026
This privacy policy explains how personal data is processed when you use TidyPepple (“the App”) and this website. TidyPepple is an installable web app (progressive web app, “PWA”) for task management that runs in your browser. There is also an Android app for direct download that shows the same web app (see section 7).
In case of doubt, the German version of this privacy policy prevails.
1. Data controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Frank Röseler
c/o POSTFLEX PFX-656-694
Emsdettener Straße 10
48268 Greven
Germany
Email: tidypepple@roeslr.com
2. Principle: local first, encrypted otherwise
TidyPepple is a local-first app. Everything you enter (tasks, notes, projects, contexts, attachments) is stored and processed on your device or in your browser.
- Without the optional sync, your content never leaves the device. There is then no user account, no sign-in and no registration.
- With sync, your content is end-to-end encrypted on your device before it is transmitted. Neither the controller nor the hosting provider can read it (see section 5).
- There is no tracking, no analysis of individual users' behaviour and no advertising. No cookies are set for analytics or advertising. We only count, anonymously, how many devices start the App per day (see section 4).
- The App's source code is public under the AGPL-3.0 licence: https://github.com/MelBourbon/tidypepple. You can verify the processing described here there. This privacy policy covers tidypepple.com and app.tidypepple.com. Anyone running their own instance of TidyPepple is responsible for the processing in that instance.
3. Data stored on your device or in your browser
For the App to work, the following is stored locally in your browser or in the
Android app's own storage (technically in IndexedDB, localStorage,
sessionStorage and the service worker cache):
- your tasks with title, notes, status, dates, contexts and attachments,
- technical data for sync (device ID, timestamps, list of changes not yet sent),
- settings such as language, text size, sorting and filters,
- whether the App runs in the browser or in the Android app, and in the Android app, which update notice you have dismissed,
- if you use sync: the unlocked key of your vault as a non-exportable key object of the browser or WebView, and your sign-in session,
- the App files themselves, so the App starts offline.
This data stays on your device. You can delete it at any time by deleting tasks in the App, clearing the site data for TidyPepple in your browser or the Android app's storage, or uninstalling the App. Under *Settings → Data* you can export your tasks as a JSON file.
Legal basis: Art. 6(1)(b) GDPR (providing the features you use) and § 25(2) no. 2 TDDDG (storage on the device that is strictly necessary).
4. Server log files when the website and App are loaded
The website and the App are delivered as static files by a web server. As with any website, connection data is processed in server log files when they are requested:
- IP address of the requesting device,
- date and time of access,
- name of the requested file and amount of data transferred,
- status code, referring page (referrer), browser and operating system.
This data is needed to deliver the website and the App and to keep the server stable and secure. It is not combined with other data sources.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and reliable delivery).
The hosting provider, acting as processor under Art. 28 GDPR, is netcup GmbH, Emmy-Noether-Straße 10, 76185 Karlsruhe, Germany. A data processing agreement is in place. Server log files are deleted automatically after 30 days.
Counting App starts. So that we know how many devices use the App, the App
sends a short request to our web server (/beacon) each time it starts. It only
contains whether the App is installed or running in the browser, whether it runs in
the Android app, the App version, plus whether sync is used (local only, account without sync,
syncing). The App assigns no device identifier for this and stores
nothing on your device for it; no content is transmitted.
When the request arrives, the IP address and browser identifier are processed – as with any request. They go into a separate log file that is normally evaluated and deleted automatically within one hour at the latest. In doing so, the IP address and browser identifier are combined with a random value generated anew each day into a one-way hash. Its only purpose is to count several starts of the same device on the same day once. The random value is deleted at the end of the day; after that only daily totals remain (e.g. "120 devices, 80 of them installed"). This does not allow us to identify individual persons, and the data is not combined with any other data.
The App uses the same route to report that it was installed and when a
programming error occurs. Besides the version and display mode, an error ping
only contains where the error occurred (e.g. on start-up) and its technical type
(e.g. TypeError), never the error message, as it could contain content. Only
a few errors are reported per session.
If you do not want to be counted, you can block requests to /beacon, e.g. with
a content blocker; the App keeps working unchanged.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in knowing how widely the App and its versions are used in order to plan development and operation).
5. Optional sync
Sync between several devices is an optional, paid feature. Data is only transmitted to a server if you set it up.
Sign-in. You sign in with your email address and receive a sign-in link by email. No password is stored. This processes your email address, a user ID and sign-in times.
Encrypted content. Your tasks and attachments are encrypted on your device with a key only you hold (AES-256-GCM), which is protected by your passphrase or recovery key. The server stores encrypted records only. Titles, notes, contexts, file names and file contents are not readable by the controller or the hosting provider. Your passphrase and recovery key never leave your device.
Technically visible metadata. For syncing, the following is unencrypted on the server: random record IDs, times of changes, the number of records, whether a record was deleted, and the number and size of attachments.
API access (MCP). With the sync subscription you can create API tokens in the app, through which the TidyPepple MCP server, AI assistants or your own scripts access your tasks. For each token the server stores a name you choose, its permission (read or read and write), a hash of the token, your key wrapped with the token, and the times it was created and last used. The server cannot open the wrapped key; decryption happens only on the computer running the MCP server. A revoked token is deleted together with these details. Important: if you connect an AI assistant from another provider (e.g. Claude by Anthropic), that provider receives whatever content the assistant retrieves. You initiate this transfer yourself; the respective provider is responsible for processing it under its own privacy policy.
Provider. Sign-in, database and file storage are operated by Supabase, Inc. (USA) as processor. The data is stored in a data centre in the European Union. A data processing agreement including the EU Standard Contractual Clauses for any access from third countries is in place.
Sending emails. Supabase sends sign-in and confirmation links through the email service Resend, operated by Plus Five Five, Inc. (USA), as processor. This processes your email address, the content of the respective email (the sign-in or confirmation link) and delivery details (time, delivery status). A data processing agreement including the EU Standard Contractual Clauses is in place with Resend; as Resend is a US provider, data may be transferred to the USA. The content of your tasks is never sent this way.
Retention. Deleted records are reduced to an empty marker after 90 days. All other data is kept until you ask for your account to be deleted (see section 11); it also stays retrievable after a subscription ends, so no data is lost.
Legal basis: Art. 6(1)(b) GDPR (performance of the sync contract).
6. Buying the sync subscription via Lemon Squeezy
Purchase and payment of the sync subscription are handled by Lemon Squeezy, operated by Lemon Squeezy, LLC, USA. You are redirected to Lemon Squeezy's checkout page for this. Lemon Squeezy acts as the seller (Merchant of Record) and payment processor and processes the data arising during the order (e.g. name, email address, payment and billing data) as an independent controller in accordance with its own privacy policy: https://www.lemonsqueezy.com/privacy
If you are already signed in, the App passes your user ID and email address to the checkout page so the subscription can be linked to your account. Lemon Squeezy then informs the controller of the subscription status (email address from the order, order and subscription IDs, status, end of term). The controller does not receive full payment details.
As Lemon Squeezy is a US provider, data may be transferred to the USA. Lemon Squeezy relies on appropriate safeguards under Art. 44 et seq. GDPR (including Standard Contractual Clauses).
Legal basis: Art. 6(1)(b) GDPR (performance of the purchase contract) and Art. 6(1)(c) GDPR (retention obligations under tax and commercial law).
7. Android app
Distribution. The Android app is offered for download directly on this website at https://tidypepple.com/en/android/, not through an app store. Downloading it only involves the server log data described in section 4.
How it works. The Android app is a shell: it shows the web app from app.tidypepple.com in its own view (Android System WebView). Everything in sections 2 to 6 about the web app therefore applies to the app as well. The data listed in section 3 is stored in the app's own storage instead of the browser. You delete it by clearing the app's storage in the Android settings or by uninstalling the app. The app itself collects no additional data and contains no Google services, analytics or advertising libraries. The app's data is excluded from Android backup (Google account) and from transfer to a new device; back up via sync or the JSON export.
Opening attachments and saving files. When you open an attachment in the Android app, the app stores it unencrypted in a dedicated folder in the app's cache and hands it to an app of your choice for viewing. That app is then responsible for any further processing. The folder is emptied when you open the next attachment and deleted together with the app's storage. Exported files are saved only to the location you choose in the "Save as" dialog.
Update notice. So that you learn about updates, the app fetches the file
tidypepple.com/android/version.json at startup and then at most every six hours, and
compares the version number in it with the installed one. This only involves the server
log data described in section 4; the app sends no further information.
Buying the sync subscription in the Android app. In the Android app, too, you buy the subscription through Lemon Squeezy. The order page opens in your browser; section 6 applies.
Legal basis: Art. 6(1)(b) GDPR (providing the app and the features you use) and Art. 6(1)(f) GDPR (legitimate interest in pointing out updates).
8. Contact by email
If you email us, we process the data you send (name, email address, content of the message) solely to handle your request.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in answering enquiries) or Art. 6(1)(b) GDPR if the enquiry relates to a purchase.
9. Feedback and bug reports via GitHub
For bug reports, ideas and questions we use the public issues of the repository on GitHub: https://github.com/MelBourbon/tidypepple/issues. The feedback link on this website, *Settings → Feedback* in the App and “Report the problem” on the App's error page lead there. These are plain links; GitHub is only loaded when you click one of them.
GitHub is operated by GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA. Writing an issue requires a GitHub account. Whatever you post there is visible to everyone, together with your user name. GitHub is an independent controller for the processing on GitHub; its privacy statement applies: https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement. Data may be transferred to the USA in the process; GitHub is certified under the EU-US Data Privacy Framework.
“Report the problem” on the App's error page opens a new issue with pre-filled text: App version, platform, the App page you were on, plus the error message and the first lines of the technical stack trace. It contains no content from your tasks. You see the text before submitting, can edit or shorten it, and nothing is sent automatically.
Please do not report security vulnerabilities publicly, but by email (see section 8).
We read and reply to your posts there in order to fix bugs and develop the App further.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in handling bug reports and suggestions).
10. No third-party content on the website
This website loads no fonts, scripts or other content from third-party servers. There are no analytics tools, no social media plugins and no embedded videos.
11. Your rights
Subject to the statutory requirements, you have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR), data portability (Art. 20 GDPR) and objection (Art. 21 GDPR).
You can view, export and delete locally stored data yourself at any time in the App, through your browser settings or in the Android settings. To delete your sync account including all encrypted data, an email to the address above is sufficient.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The competent authority is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.
12. Changes to this privacy policy
This privacy policy may be updated to reflect changes in the law or in the App's features. The current version published on this website applies.