Privacy Policy

Tavemir stores the finance records you create on your device, requires no Tavemir account and does not operate an app backend that collects those records. Google Play Billing separately processes purchase history and diagnostics; Google ML Kit may process device/app information and usage metrics, as explained below.

1. Publisher and contact

Tavemir is published and controlled by TURGAY YÜKSEL in Türkiye. Privacy and support enquiries can be sent to dasguardcore.notify@gmail.com.

2. Data used on your device

Tavemir stores the budgets, expenses, transactions, debts, receivables, reminders, notes and similar finance records you enter locally on your device unless you explicitly export or share them. It uses these records to provide the features you choose:

Data	Purpose
Budgets and categories	Compare monthly category limits with your recorded spending.
Accounts and transactions	Calculate balances, income, expenses, cash flow and category summaries.
Reminders and dates	Track bills, rent, subscriptions, cards, loans and vehicle obligations.
Debts, receivables and business contacts	Organize records and linked due dates you enter.
Preferences and app-lock values	Remember language, currency, theme and protect app access.
Premium entitlement metadata	Remember the selected plan and a one-way purchase fingerprint for bounded offline continuity. Raw purchase tokens are not added to finance exports or backups.

Smart Entry and document processing

In versions that include Smart Entry, selected or shared text and images are processed on your device. Suggestions become financial records only after your review and confirmation. Temporary image copies may be kept in private app storage; your original file is not modified. Canceling a preview or stopping recognition does not necessarily discard the current draft or its temporary source: the source may remain available while you review, crop or retry that draft. Cleanup of the temporary copy is requested when the source is released, including after saving or discarding the draft. Files left after an interruption or incomplete cleanup are checked for deletion at a later app start; immediate deletion is not guaranteed.

Separately from document content, Google ML Kit may transmit technical device/app information, installation identifiers and usage/performance metrics to Google. Google uses these ML Kit metrics for performance and usage analysis, debugging, service maintenance and improvement, and detecting misuse or abuse. Google describes this processing in its ML Kit Terms & Privacy and Android data disclosure. This is separate from the Google Play Billing processing described below. Deleting local records does not mean that Google's technical records have also been deleted.

Camera input uses a separate camera app, and choosing an existing image uses Android's document picker. Tavemir does not add broad storage or camera permission for this workflow. Review the proposed amount, date, currency and account before saving; document recognition is not a guarantee of financial accuracy.

Local trial record

The trial record is stored locally, separately from financial records. It contains start/end and last-observed times, a used flag and notice preferences. It is not sent to a new analytics service and is excluded from the financial JSON backup. Importing that backup does not start, reset or extend a trial. With no Tavemir account/server/device fingerprint, one trial per person cannot be guaranteed across reinstalling, deleting app data or different devices. Existing Google Play Billing/SDK processing is separate and remains described in this policy.

Local purchase diagnostics and optional JSON file (+19)

For troubleshooting purchases, restoration and Premium access, Tavemir 1.0.0+19 keeps a limited technical record in application-process memory. It holds up to 256 recent events; older events are discarded as the buffer fills. This memory record is lost when the application process ends. Leaving a screen or putting the app in the background does not necessarily end that process. Tavemir does not automatically save this record to a file or send it to the publisher or support.

The record can contain event names, sequence numbers and UTC times; session-local operation/query identifiers and their relationships; product type and product ID; actual and upper-layer Billing response codes, returned record counts and attempt numbers; purchase-processing stage and status; a true/false indication that a purchase token is present; filter acceptance or rejection reasons; and the resolved plan, access state and action. It can also record connection, retry, timeout, cancellation and ignored-late-response events.

This limited record and its JSON export do not contain the raw purchase token, a token hash or purchase fingerprint, order IDs, account information, financial records, raw purchase objects or the provider's free-text debug message. Product IDs and purchase/access states can be present; the file is not a finance backup.

If you choose Save purchase diagnostics as JSON in About Tavemir, Tavemir takes a snapshot before opening Android's file-location picker. The JSON also includes the app version name/code and the UTC export time. You choose where to save it, or cancel. Saving does not automatically send the file to anyone. The saved copy remains separate from the process-memory record: ending the process or clearing Tavemir data is not a substitute for deleting that file from its chosen location. Delete the exported file and any copies separately when no longer needed.

This Tavemir-local record and optional export are separate from Google Play Billing and its internal DataTransport processing described below. The temporary lifetime of Tavemir's in-memory record and the lack of automatic sending of that record do not mean that Google's separate diagnostic or purchase processing is temporary, disabled or deleted.

3. Collection and sharing

Tavemir has no Tavemir account, advertising SDK, independent analytics SDK, bank connection or finance-record sync backend. The app does not automatically transmit your finance records to the publisher or to Google Play Billing.

Finance data can leave your device when you explicitly export or share a PDF, CSV, text or backup file. The destination you select then processes that copy under its own terms.

Google Play Billing may connect when Tavemir starts, even if you do not start a new purchase. It queries available Premium products, purchase eligibility and current ownership. It also restores purchases and processes and acknowledges purchases when those actions occur. Premium is optional; Free features remain available without purchasing.

Google Play Billing and its internal DataTransport diagnostic pipeline may send Google technical Billing/API connection diagnostics, relevant app metadata, device-software metadata and network metadata. Billing also processes purchase history and entitlement information with Google. Diagnostics help Google analyze Billing operation; purchase processing supports app functionality, fraud prevention, security and compliance. These Billing-related diagnostics and purchase transfers use HTTPS/TLS encryption.

Tavemir does not receive or store your card number, CVV or Google account password. It may receive a Play purchase token and transaction state to verify Premium access and acknowledge a purchase. The raw token is not sent to a DasGuard Core backend, included in finance exports or backups, or retained as a raw persistent finance record. Tavemir may locally retain the plan/access state, last verification time and a one-way token-derived purchase fingerprint for bounded offline access.

In Google Play's Data Safety classification, Billing diagnostics and purchase history are collected but not shared, because Google processes them as a platform service provider. This classification does not mean that no information is sent to Google. Google's processing is also described in Google's Privacy Policy.

Billing diagnostics are required, not processed only ephemerally, and used for Analytics. Purchase history is optional because Premium purchases are optional; it is not processed only ephemerally and is used for App functionality and Fraud prevention, security and compliance. Neither category is classified as shared under the accepted Google Play service-provider classification; technical transfers to Google still occur.

You choose the calendar month, expense category and increase or decrease percentage. Tavemir applies that percentage to the recorded category spending to show a hypothetical amount, not achieved savings or a recommended target. There is no default advice percentage, personalized spending recommendation or financial-health rating. Period totals, comparisons and other record-based calculations and forecasts remain available.

4. Permissions and device services

Notifications: used to show reminders you schedule. Android marks reminder content private and can substitute generic lock-screen text when your system privacy setting hides sensitive content.
Boot completed: used to restore locally scheduled reminders after a device restart or app update.
Google Play Billing: used to query products and ownership, including at startup, and to purchase, acknowledge, restore or manage optional Premium access.
Biometrics: when enabled, authentication is performed by the operating system; Tavemir does not receive your biometric template.

Tavemir does not request location, contacts, microphone, camera, phone, SMS or advertising permissions in its Android release manifest.

5. Security and backup

The optional PIN is stored as a salted, computationally expensive derived value rather than plain text. When launch locking is enabled, Tavemir also re-locks after 30 seconds in the background. The PIN and supported device biometrics protect app access; they do not encrypt local records or exported files. Android system backup is disabled for Tavemir app data. Files you explicitly export are readable by anyone or any service you share them with, so choose destinations carefully.

6. Retention, correction and deletion

To delete a Tavemir record, use its edit/delete controls in the app. To remove all local Tavemir data, open Android Settings > Apps > Tavemir > Storage and clear app data, or uninstall Tavemir; Android labels may vary. Export a backup first only if you want to retain a separate copy. Losing or canceling Premium never deletes those finance records. Minimal local entitlement metadata can be replaced or removed when Play ownership is reconciled, app data is cleared, or the app is uninstalled. Tavemir has no server account to delete. A file you exported must be deleted from its destination separately.

Clearing or uninstalling Tavemir does not automatically delete Google's purchase or diagnostic records. Tavemir has no app account or developer backend to delete. For applicable Google-held data, use Google Account Data & privacy, Google Play personalization and history controls or Google's Privacy Help Center to manage data or request deletion as available. Deleting Play activity is not the same as deleting purchased items or purchase-entitlement records. Google may retain records for legal, accounting, security or fraud-prevention reasons. Tavemir cannot delete Google's diagnostic records for you and makes no automatic 90-day deletion promise.

Review access is a locally verified Premium access grant, not a Tavemir account or a Google Play purchase. It can be removed on the Review access screen. No reviewer access code is published in this policy.

7. Children

Tavemir is a general personal-finance organization tool and is not designed or marketed for children. The app does not knowingly collect children's data through a Tavemir backend because no such backend exists.

8. Your rights

You control local records directly in the app. For privacy questions or rights that cannot be exercised locally, contact the publisher at the address above. Applicable rights depend on your location.

9. Changes

If Tavemir's data practices or features materially change, this policy and the Google Play Data safety disclosure must be updated before the changed release is distributed.