Privacy Policy

Life Inventory: MyVault  |  Effective date: October 18, 2026  |  Last updated: October 18, 2026

At a glance. Your inventory, receipt records, product photos and receipt files are stored on your device. The current App does not automatically upload or synchronize this content to our Firebase database or file storage. Online services remain necessary for account access, account administration, subscription verification and, for eligible Free users of the ad-supported iOS version, advertising. You control any backups or reports you choose to save or share.

1. Who We Are and Scope

This Privacy Policy explains how Mehmet Kaan Yılmam ("we," "our," or "us") handles personal information in connection with Life Inventory: MyVault (the "App"), support requests and associated online services. The App may display the shorter name "Life Inventory." Contact us at studiolabss0@gmail.com.

This Policy describes the updated App with on-device inventory storage, on-device receipt text recognition, user-created backups and AdMob advertising. It does not mean that every older installed version used the same storage model. Removing cloud inventory storage from the current App does not, by itself, erase information previously submitted through an older version; account deletion and privacy requests are described below.

2. Information We Handle

2.1 Account, sign-in and pending registration

Firebase Authentication, operated by Google, handles account creation, email verification, password reset, email/password sign-in and Sign in with Apple. Account information includes your email address, profile name, account identifier, sign-in provider and verification status. Authentication providers may also process IP addresses, device or browser information, authentication tokens and security events. Apple's Hide My Email option may provide a relay address instead of your personal email address.

Firebase handles password authentication. We do not maintain a separate server database of plaintext account passwords, and we do not receive your Apple ID password. To let you finish email registration after closing the App, the App temporarily saves your selected registration credentials in device-protected secure storage and stores matching registration metadata locally. Pending drafts are checked for a 24-hour validity period when accessed and are cleared when registration is completed, cancelled or an expired or invalid draft is detected. Session credentials may also remain in platform-protected storage to keep you signed in. Do not send passwords or verification links to support.

2.2 Inventory and receipt records stored on your device

The App stores your item names, brands, models, categories, purchase amounts and currencies, purchase dates, warranty dates, return deadlines, merchant names, receipt records and item/receipt associations in an account-associated local database on your device. It also stores local settings and metadata needed for features such as custom categories, reminders, backup status and feature limits.

Signing in associates the local inventory with your account; it does not automatically synchronize that inventory between devices. We do not receive the contents of your current local inventory through normal inventory use. Purchase details and documents can reveal personal or financial information, so include only what you need.

2.3 Photos, documents and on-device receipt scanning

When you take or select a product photo, receipt image or receipt PDF, the App saves its own copy in its private storage on your device. It uses these files for viewing, linking to records and features you request. The current App does not upload these files to Firebase Cloud Storage.

When you scan a supported receipt image, Google ML Kit recognizes text on your device. The App extracts editable suggestions, such as merchant details, dates, totals and item information. The current scanning flow does not send the image or recognized receipt text to our server or to a cloud OCR or generative AI service. ML Kit may separately process technical SDK, device, usage and diagnostic information as described in its privacy documentation; on-device text recognition does not mean that every SDK operates without technical data processing.

Receipts can contain names, addresses, payment-card fragments or other sensitive details. Review the files you choose and the results before saving or sharing them. The App does not provide automated financial, legal, insurance or warranty advice.

2.4 Backups, restoration, reports and sharing

You can create a ZIP backup containing local inventory and receipt records, categories, attached photos and files, backup timestamps and an account-associated marker used to match the backup during restoration. The backup does not include your account password. Restoring a backup requires the account that created it and adds eligible missing records and files to that device; it does not provide continuous cloud synchronization.

You select the backup destination through your device's file interface. A destination may be local storage, iCloud Drive or another file provider you choose. PDF and CSV reports and other files you export or share are also processed according to the destination and recipients you select. These actions can send your content outside the App, even though the App itself does not provide cloud inventory storage.

ZIP backups are not password-protected or encrypted by the App. Account matching during restoration is not encryption. Protect your saved copies and choose trusted storage and sharing services. Copies outside the App remain under your control or the destination provider's policies.

2.5 Subscriptions and limited backend account records

Apple processes iOS subscription payments. RevenueCat helps verify purchases, restore subscriptions and determine whether Pro access is active. Relevant data may include your App account identifier, purchase receipts or transaction identifiers, purchased products, subscription and renewal status, entitlement information and technical information needed to provide this service. We do not receive your full payment-card details.

Although inventory content is local, our Firebase backend still handles account administration, subscription-status synchronization, limited records of whether certain subscription offers have been presented, account-deletion operations and registration-abuse protection. Cloud Firestore is used for these limited backend records, not as the current App's inventory or receipt-file storage. Local inventory contents are not sent to RevenueCat to verify Pro access.

2.6 Technical information, security and abuse prevention

Online service providers may process account identifiers, IP addresses, app and operating-system versions, request times, authentication and subscription events, and error or service logs to operate and secure their services. Registration protection uses short-lived keyed hashes of network addresses and event identifiers, with event times, to identify bursts of account creation. The dedicated rate-limit records do not contain raw IP addresses, email addresses or user account IDs; the underlying authentication and infrastructure services may process those data separately.

Rate-limit events are considered within windows of up to one hour, and expired records are eligible for scheduled cleanup. This does not guarantee that every infrastructure log or provider record is deleted within one hour. Hashing security signals does not necessarily make them anonymous.

2.7 Advertising and privacy choices

In the ad-supported iOS version, eligible Free users may see Google AdMob interstitial ads after a completed product or receipt save. Pro users are not shown these ads. The App requests non-personalized ads and does not provide your inventory contents, receipt text, photos, account name or email address to AdMob for ad targeting.

Google's advertising SDK may process IP addresses and approximate location inferred from them, device or app identifiers, ad impressions, ad interactions, product-interaction information, and crash, performance and other diagnostic data. These data may be used to deliver and measure advertising, limit frequency, prevent fraud, and operate, analyze and improve advertising services. Non-personalized advertising still involves data processing.

Google's User Messaging Platform (UMP) manages applicable consent messages and privacy choices. The App requests ads only when UMP reports that it may do so. It stores the time of the last displayed interstitial on your device to enforce an interval of at least two minutes between ads. The current implementation does not request App Tracking Transparency authorization to access Apple's advertising identifier (IDFA), and iOS same-app key is disabled. These settings do not mean that the advertising SDK processes no identifiers or technical data.

Where required by the consent platform, you can revisit your choices at Profile > Ad privacy choices. You can report an inappropriate ad at Profile > Report an ad or email us. The App does not require you to grant tracking authorization to use its core features.

2.8 Permissions, notifications and support

Camera access is used when you choose to photograph an item or receipt. Photo-library and file-picker access let you select the specific images, documents or backups you want to use. Notification permission enables optional local warranty and return reminders. Reminder dates, notification settings and scheduled notifications are managed on your device. You can change permissions in device settings; declining an optional permission may limit the corresponding feature.

We do not request precise device location, contacts or microphone access for these features. Approximate location inferred by an advertising or infrastructure provider from an IP address is separate from device location permission.

If you contact support or report an ad, we receive the email address you use, your message and any attachments you choose to send. Share only the information necessary to explain the issue.

3. How We Use Information

We do not sell your local inventory records or receipt contents to advertisers or use those contents to target ads. We do not send receipt images or recognized text to a generative AI service in the current App. These statements do not exclude the separate technical and advertising data processing described in Section 2.7.

4. Legal Bases Where Applicable

Where applicable data protection law requires a legal basis, we rely on performing our agreement with you for account and subscription services, legitimate interests for proportionate security, fraud prevention and service reliability, compliance with legal obligations, and consent where required. We rely on consent for advertising-related storage, access to device information or other processing where the law requires it. Optional permissions and user-directed sharing are requested through the relevant App or platform controls.

You may withdraw consent using available privacy controls without affecting processing lawfully completed before withdrawal. Certain online account data is necessary for account-based access and purchase verification. This does not make your locally stored inventory a cloud-hosted inventory.

5. Service Providers and Data Sharing

Relevant providers and recipients include:

Providers may act as processors or independent controllers depending on the service and circumstances. We may also disclose information where necessary to comply with law, protect rights and safety, investigate abuse, or complete a lawful business transfer with applicable safeguards. We cannot transfer local inventory content that we have not received.

6. Storage Locations and International Transfers

Your current inventory database and attached files reside in the App's storage on your device. Their location can change if you export them, create a backup or use operating-system backup or device-transfer services. The App's local storage model does not prevent copies from being stored by a cloud file or backup provider you enable.

Online account, backend, subscription, advertising and support information is processed separately. Firebase Authentication processes account data in the United States; other providers may process data in the United States or other countries where they operate. Backend account functions are configured in a United States region. Where international transfers require safeguards, the applicable service terms and legally required transfer mechanisms govern that processing. This Policy does not promise that all online service data stays in your country.

7. Security

We use account authentication, account-scoped local storage, platform-protected credential storage, server-side authorization for online account operations, input and file validation, and encrypted transport supported by our providers. The App's local inventory database and ZIP backups are not protected by a separate App-provided encryption password; the security of local data also depends on your device's operating system, passcode and backup settings.

No system guarantees absolute security or recovery. Keep your device and credentials secure, update your software, protect exported files and maintain your own backups. Deleting a record is not a guarantee of forensic erasure from device storage, provider backups or copies held elsewhere.

8. Retention, Deletion and Backups

8.1 Local records and files

Local records remain on the device until you delete them, complete the App's account-deletion flow on that device, or they are removed through operating-system controls. Signing out does not by itself erase the local inventory. Removing the App may remove its private files, but copies can remain in system backups, shared storage or external services. Reinstalling or signing in on another device does not automatically recover your local inventory; restoration depends on an available compatible backup and the originating account.

When you delete an item or receipt, the App removes the local record and attempts to remove its associated private attachment. Files originally selected from your photo library or file provider are separate copies and are not deleted from their original location. Files that cannot be removed immediately may remain until subsequent account-data cleanup.

8.2 Account deletion and online records

Use Profile > Delete account to request account deletion. Reauthentication may be required. The flow requests removal of your Firebase account and associated backend account data and clears the account's local inventory and attachments on the device completing the flow. Backend cleanup also covers account-associated inventory or files retained from older cloud-storage versions where present. If deletion fails or is interrupted, follow the App's retry instructions or contact us; local cleanup may not have completed.

Account deletion on one device cannot remotely erase local files on another device or copies you exported or shared. Remove those copies separately. Certain security, deletion-status, support, purchase, tax or other legally required records may remain for legitimate operational or legal purposes. Authentication-provider backups, infrastructure logs, advertising records and subscription-platform records may follow their providers' retention and deletion practices; we do not promise immediate deletion from every backup.

Deleting your account or uninstalling the App does not cancel an App Store subscription. Cancel it through your Apple account subscription settings. Purchasing Pro stops future in-app ad displays but does not automatically erase information already processed by advertising providers.

8.3 User-created backups and exports

You control the ZIP backups, PDF and CSV reports, shared attachments and other copies saved outside the App. Deleting a record or account does not delete these copies, revoke access already granted to recipients or remove independent provider backups. You must manage their retention and deletion with the relevant service. The App does not operate an automatic cloud inventory backup or synchronization service.

9. Your Privacy Rights and Choices

Depending on your location and applicable law, you may have rights to access, correct, delete, restrict or object to processing, obtain a portable copy, withdraw consent, or opt out of certain advertising-related uses, sales or sharing of personal information where those rights apply. You may also complain to the relevant data protection authority and, where applicable, appeal a privacy-request decision by contacting us. We will not discriminate against you for exercising applicable privacy rights.

Contact studiolabss0@gmail.com to make a request. We may need reasonable identity verification and will respond within applicable legal timeframes. Because local inventory contents are held on your device, we generally cannot retrieve them remotely; use the App's editing, deletion, backup and available report-export tools to manage your local copies. These tools do not limit any additional rights you have by law.

Use Profile > Ad privacy choices when available to review or change advertising choices provided by Google's consent platform, including applicable regional opt-outs. Where this entry point is required by the platform, it is displayed in the App. Use device settings to change permissions and platform backup preferences. To report an inappropriate ad, use Profile > Report an ad or contact support.

10. Children

The App is intended for general personal inventory management and is not directed to children under 13 or a higher minimum age applicable in their jurisdiction. We do not knowingly solicit personal information from children who cannot lawfully provide it. If you believe a child has provided information improperly, contact us so we can review the matter and take appropriate action. Parents and guardians should supervise use where appropriate.

11. External Links and Third-Party Services

Links to subscription settings, legal information, support resources, advertisements or other services may open content operated by third parties. A third-party destination or recipient handles information under its own policies. Review those policies before submitting information, saving backups to a service or sharing documents.

12. Changes to This Policy

We may update this Policy when the App's features, storage model, providers or legal obligations change. We will update the date above and provide additional notice or seek consent where required before introducing materially different processing. This version replaces the earlier description of cloud-hosted inventory for the updated App; it does not assert that historical data or independently held copies have already been deleted.

13. Contact

Privacy and support inquiries: studiolabss0@gmail.com
Operator: Mehmet Kaan Yılmam