01Who is responsible
ClientsFlow is developed by Smolanov Serhii. Privacy contact: smolanovsergey@gmail.com. This policy applies to the Android app com.clientflow.app, not future releases or third-party websites and services.
02Data processed
The app processes information entered by the user and operational records needed for its features. Records and settings are stored locally on the device.
ClientsFlow: workspace, client names and contacts (company, phone, email, Telegram, WhatsApp), notes, projects, tasks, deadlines, amounts, extras, recurring rules, payments and allocations, price and activity history. The app does not request card numbers or bank-account access.
03Purposes
Information supports record keeping, scheduling or project management, calculations, history, settings and backups. The current implementation has no registration, advertising SDKs, integrated analytics or upload of the working database to the developer's server.
04Files and backups
Exports are initiated through Android's system file or folder picker. JSON and CSV exports do not have additional app-level encryption: someone with file access can read the information. Choose a trusted storage location.
ClientsFlow can write backups to a selected folder, including an available Google Drive file provider. Automatic backup is off by default and enabled by the user. JSON includes history and soft-deleted records; rotation keeps the last seven app backups in the connected folder. Import replaces the database. Android automatic system backup is disabled.
05Device access and third parties
The app uses access granted to a selected file or folder. The inspected implementation does not access the address book, camera, microphone or location. If you choose cloud storage, its provider receives the file under its own terms; the app developer does not operate that storage.
Folder selection grants persistent access to that folder. The app does not use its own Google Drive API OAuth client. Disable automatic backups and disconnect the folder in settings to stop further copying.
06Retention and deletion
Local records remain until the user removes or clears app data. Archiving or hiding a record is not complete erasure. To remove the whole local database, use Android's Clear storage function or uninstall the app. Exported files, cloud backups and copies on other devices must be deleted separately.
07Security
Android limits access to the app's internal files. No additional app-provided encryption of databases or backups is claimed. Use a device lock, keep the OS updated and protect exported files. The developer has no remote access to your local database.
08Other people's and children's data
The app is a work tool for adult users. A user entering student, client or other personal information is responsible for a lawful basis, required notices and appropriate data minimisation. Requests about those records should first go to the teacher or organisation that entered them.
09Requests and your rights
Use the app and device settings to access, correct or remove local data. The developer cannot remotely change data they do not hold. Emailing smolanovsergey@gmail.com provides your sender address and voluntarily supplied message content for responding to your request. Such correspondence is kept only as necessary for support and applicable obligations. Do not send entire databases unnecessarily. Subject to applicable law, you may request access, correction, deletion or restriction of data provided to the developer and complain to a supervisory authority.
10Policy changes
The current revision date appears on this page. Before cloud accounts, analytics, payments or other processing are introduced, this policy must be updated. This version covers the inspected Android implementation and does not imply an iOS release.