Tidyslip Privacy Policy

Effective date: 4 November 2026 · Last updated: 4 November 2026 (version 0.6.1: before/after images in the free version) · Applies to the Tidyslip app for Android (com.tidyslip.app).

This policy explains what information the Tidyslip app handles, where it is stored and who can see it. In short: your jobs, customer details, photos and PDF reports stay on your device. The app has no accounts and no ads. When the app is online, it contacts our purchase service to check whether Pro is active. That check uses an anonymous ID, not your name or Google account, and never includes your jobs, customers or photos. If you leave the setting on, the app also sends crash reports and basic usage statistics to Google Firebase. These never include your jobs, customers, photos, business details or reports, and you can turn them off in Settings.

Who we are

Tidyslip is developed and published by Arda Türkoğlu, an individual developer based in Türkiye ("we", "us"). We are responsible for the app and for answering questions about this policy. You can reach us at turkogluarda0@gmail.com.

Data on your device

Everything you enter or add in Tidyslip is stored only in the app's private storage on your device:

We do not have a server for this data and we cannot see it. The app does not include this data in Android's automatic cloud backup.

Your jobs, customer details, photos and reports leave your device only when you choose to send them:

Data processed by service providers

Tidyslip offers a one-time in-app purchase ("Tidyslip Pro"). The first 3 report exports are free. Pro removes this limit and adds extra features described in the app, such as your logo and contact details on reports, client sign-off and saved checklists. Two service providers are involved:

If you never buy Pro: RevenueCat holds only the anonymous app user ID and the technical request information above, with no purchase attached. We cannot link that ID to you, your name, your Google account or your jobs.

You can see your anonymous ID in the app under Settings → Anonymous purchase ID, and copy it if you want to contact us about it.

The product information the app receives from RevenueCat can also include a setting that chooses between a few built-in wordings of the Pro screen; no extra information is sent for this. We use this information only to provide, verify and restore purchases and to see overall purchase numbers in the RevenueCat dashboard. We do not sell it and we do not use it for advertising. Communication with these services uses encrypted connections (HTTPS).

Crash reports and usage statistics (Google Firebase)

The app uses Google Firebase Crashlytics and Google Analytics for Firebase, provided by Google LLC, to find crashes and to understand, in aggregate, how the app is used (for example how many jobs and reports are created, how reports are shared, saved or printed and how often that fails, whether photos come from the camera or the gallery, which Pro tools are used, whether the app was opened from its home-screen shortcut, and how often the Pro screen is shown).

What is sent: crash details (the error message and where in the app's code it happened, the state of the app's threads, device model, Android version, free memory and disk space, app version, whether you have Pro, the name of the app screen that was open (such as "Home" or "Camera"), and the last few in-app events before the crash); reports of a few unexpected errors the app handles itself, such as an unexpected error during a purchase or when a report could not be created, saved or shared, which contain only the type of error and where in the app's code it happened; a list of in-app events with limited fixed values (such as "report sent", "share" or "save", "camera" or "gallery", which Pro tool was used, whether a sent report includes an issue, "free" or "pro"), and whether you use the free version or Pro as a property of this installation; for Pro tools such as client sign-off or the review link, only the fact that the tool was used is sent, never the signature, name or link; when you share a before/after image, only that the share screen opened, the image format (post or story) and the screen it was opened from, never the image; automatic events that Firebase records for every app (such as first open, session start, screens viewed, time in the app, app updates and crashes, and, if you buy Pro, the purchase event with the product and price); general device and app information (device model, Android version, app version, device language, and an approximate location such as the country or city, derived from the IP address); information Google Play may provide about how the app was installed (for example the store campaign, if any); and a Firebase installation ID and an Analytics instance ID created for this app installation.

What is never sent: your jobs, customer names or addresses, notes, photos, report contents, business details, sign-offs or review links. Usage events contain only fixed values, and the app does not add your content or file names to crash reports.

Firebase is not used for advertising; the advertising ID is not collected and ad personalization is disabled.

Your choice: in the EU, EEA, UK and Switzerland, and when the app can’t tell your region, crash reports and usage statistics stay off until you choose Allow on the first screen. Elsewhere this setting is on by default. You can change it at any time in Settings → Privacy → Share usage and crash data. The app tells Google Analytics your choice through Google’s consent settings (analytics storage allowed or denied); advertising storage and ad personalization are always set to denied. When you turn it off, the app stops sending crash reports and usage statistics, deletes crash reports and usage data that were not sent yet, and deletes the Firebase installation ID (if your phone is offline, this is completed the next time the app starts).

Where and how long: Google may process this information in the United States. Crashlytics keeps crash reports and their identifiers for 90 days. Google Analytics keeps event-level and installation-level data for 2 months; aggregated statistics that do not identify an installation may be kept longer. Google's handling is described in the Firebase privacy information and the Google Privacy Policy.

What we don't collect

Retention and deletion

Children

Tidyslip is a work tool for adults who run cleaning and similar service businesses. It is not directed at children, and we do not knowingly collect information from children. If you believe a child has contacted us, email us and we will delete that correspondence.

Changes

This policy describes the app as it works on the effective date above. If a future version changes what information is handled, we will update this page before that version is released and change the effective date. Significant changes will also be mentioned in the app's release notes.

Contact

Questions or requests about privacy: turkogluarda0@gmail.com
Developer: Arda Türkoğlu, Türkiye