Last updated: April 16, 2026

TRIMSY Privacy Policy

This Privacy Policy explains how the current Android release of TRIMSY (the "App") handles information. This text is based on the verified production variant in the codebase as of April 16, 2026.

Overview

TRIMSY is used for product photography, receipt and document capture, local media organization, storage planning, watermark/logo handling, and related utility features. The current production app uses Google Sign-In with Firebase Authentication, TRIMSY cloud sync, Firebase Messaging for optional marketing notifications, Google AdMob, Google's User Messaging Platform for ad consent, and Google Play Billing subscriptions.

Information We Process

• Google Sign-In and Firebase Authentication data if you choose to sign in, including your Google account email address, display name, Google sign-in token, and Firebase UID.
• Product photos, scanned receipts, imported document images, watermark files, logo files, thumbnails, categories, storage layouts, settings, onboarding state, consent state, and related metadata that you create or save in the App.
• Ad-related device data required by Google AdMob and Google's consent tools, including the advertising ID (AD_ID), device identifiers, network information, IP-based signals, and consent state.
• Google Play Billing purchase and subscription state for the App's paid tiers.
• If you explicitly opt in to promotional notifications, Firebase Cloud Messaging topic-subscription state needed to deliver those optional campaign messages.

Camera and Document Scanning

The camera permission is used only to let you take product photos and capture or scan receipts and other documents inside the App. The App also lets you import receipt or document images from your device instead of using the camera.

How We Use Information

• To sign you in with Google and keep your app data separated per signed-in account or guest session.
• To save, organize, watermark, preview, export, upload, restore, and sync photos, receipts, storage layouts, categories, settings, and related metadata.
• To show banner ads and rewarded ads in the free tier through Google AdMob after consent requirements are handled.
• To process, acknowledge, and restore paid subscription tiers through Google Play Billing.
• To store local settings such as language, grid preferences, storage data, onboarding progress, and monetization state.
• If you opt in, to send promotional notifications about discounts, launch campaigns, subscription-related offers, and relevant product updates.

Promotional Notifications

Promotional notifications are optional and are shown in the App with a startup or onboarding choice before they are activated. These notifications may include discounts, time-limited offers, launch campaigns, subscription-related offers, or relevant product updates. Delivery uses Firebase Cloud Messaging.

If the App shows a startup or onboarding consent message for promotional notifications, that option may appear enabled by default, but you can review it and turn it off before accepting. Promotional notifications are activated only after you complete that consent step. If you turn the option off before accepting, you will not receive promotional campaign notifications. If you later disable the promotional notifications toggle in the App, future campaign notifications should stop after the device unsubscribes from the promotional topic. This promotional opt-in is separate from essential service, security, or account-related notifications if those are added in a future release.

Google Sign-In, Firebase, and Cloud Sync

Google Sign-In is optional. You can continue in guest mode. If you sign in, the App uses Google Sign-In and Firebase Authentication for authentication and account scoping. Signed-in paid tiers can also use active TRIMSY cloud sync. In that flow, the App can upload and restore product photos, receipt images, logo files, watermark assets, thumbnails, categories, storage layouts, settings snapshots, onboarding state, consent state, and related metadata through TRIMSY backend services built on Firebase and Google-hosted infrastructure.

Advertising

The free tier uses Google AdMob for banner ads and rewarded ads. The App declares and uses the Google advertising ID permission (`AD_ID`) for AdMob. Google may process the advertising ID, device or other identifiers, network information, IP-based signals, consent information, and related ad-delivery or fraud-prevention data according to Google's policies. Ad consent choices are handled with Google's User Messaging Platform.

Purchases

The App offers paid subscription tiers through Google Play Billing. Purchase processing is handled by Google Play Billing. The App stores resulting entitlement state locally so that paid features can be restored and enforced on the device.

Photos, Media, and Local Storage

The App stores product photos, receipt images, document scans, logo files, watermark templates, storage layouts, categories, counters, and settings locally on the device. Product photos are saved in app-managed storage and can also be exported to public Pictures or Documents folders depending on your settings. Receipt imports and scanned documents are stored locally in app-managed storage. If you use a signed-in paid tier with cloud sync enabled, selected media and synced account data can also be uploaded to TRIMSY cloud services for restore and cross-install recovery.

Backend, Cloud Sync, and PC Sync

The current TRIMSY Android release includes active backend cloud sync for signed-in paid tiers. That sync can upload and restore media files and selected structured user data. PC-sync hooks are still not the primary active sync path in this release.

Analytics, Crash Logs, and Diagnostics

The verified standalone app code does not integrate Firebase Analytics or Firebase Crashlytics. The app's cloud diagnostics hook is currently a no-op. Google services used by the App, such as AdMob, Firebase Authentication, and Google Play Billing, may still generate their own operational, security, billing, or service diagnostics under Google's policies.

Third-Party Processing and Sharing

We do not sell your personal information. Data is shared with third parties only when needed to operate the features you use:

• Google Sign-In and Firebase Authentication for optional sign-in.
• Google AdMob and Google's consent platform for advertising in the free tier.
• Google Play Billing for the Pro purchase flow.
• Firebase Cloud Messaging for optional promotional notification delivery if you choose to opt in.

Android Backup

The current Android manifest allows system backup. Depending on your device and Google backup settings, some locally stored app data may be included in Android backup and restore handled by the platform. If you need a strict no-backup posture before publication, this behavior must be disabled in the app build.

Your Choices and Deletion

• You can use the App in guest mode instead of Google Sign-In.
• You can manage ad consent choices through the in-app privacy options form when Google requires it.
• You can review the promotional-notification choice during startup or onboarding if that prompt is shown, and you can turn it off before accepting even if it appears enabled by default.
• You can turn promotional notifications on or off later in the App settings. Turning them off stops future promotional campaign notifications after the device unsubscribes.
• You can choose whether or not to subscribe to a paid tier.
• You can sign out, clear app storage, delete exported files, or uninstall the App to remove local data from the device.
• If you want signed-in account or cloud data removed from backend systems, please use the developer privacy contact listed in the store listing or any published deletion-request page linked there. Support-handled backend deletion tooling exists, but no in-app self-service deletion endpoint is verified in this release.

Children's Privacy

The App is not intended for children under the age required by applicable law to provide consent on their own.

Changes to This Policy

This Privacy Policy may be updated from time to time. The latest version will be made available at the published policy URL.

Contact

For privacy-related questions or deletion requests, please use the developer contact details provided in the Google Play listing for TRIMSY.