Privacy & Data Safety
Pretio Data and Privacy Information
Effective date: November 2, 2026 ยท Last reviewed: November 2, 2026
Pretio works without an account. If you choose to sign in (Pretio 1.4.6), your records are also stored in your account so they can sync across your phones. Pretio currently has no operational process for receiving and fulfilling individual requests to delete server-side records. The email below is for privacy questions; it is not a server-side deletion service.
Delete data stored on your device
Use Pretio's Delete All Data feature to remove products, saved prices, stores, shopping lists, and related records stored locally in the app. To confirm, type DELETE and wait for a short countdown. When you are signed in, Delete All Data also deletes your synced cloud data. Pretio never deletes your data automatically when you exceed a plan limit.
Delete your account (Pretio 1.4.6)
You can delete your account from the Account page. Deleted accounts can be recovered within 30 days. Individual items you delete can be restored from Recently Deleted.
Backups
Backups are manual. Before destructive actions Pretio asks whether you want to back up your data first.
In Pretio v1.4.4, Photo Product identification sends a locally compressed image to Google Gemini through Firebase AI Logic when you choose to identify a product. Photos are not stored in Pretio's saved product records, but external service provider retention may apply. Deleting local Pretio data does not erase any data retained by Google. For details, see the Privacy Policy.
Ask a privacy question
For questions about Pretio's data practices, email pretio.support@maxqstudio.dev. Do not send passwords, payment-card details, or Google Play purchase tokens. The email route has not been verified as a server-data deletion process, and Pretio cannot promise deletion of server-side records in response.
What may not be attributable to one person
- Earlier Pretio versions stored Product Insight reports and product profiles in shared caches keyed by product and market, not by a Pretio account. Version 1.4.4 does not write its AI responses to those shared caches.
- Some request-activity records contain a barcode and time but no account identity.
- Request-rate records use a hash of a random installation ID and expire automatically.
- Purchase-entitlement records use a one-way hash of a Google Play purchase token and support purchase verification, restore, and fraud prevention.
Legacy Product Insight cache records are shared or request-scoped and have no Pretio account identifier. Detailed per-call Gemini diagnostic records are written only in the Tester project, not Production. Production operational logs are separate from those Tester diagnostics. Request activity records contain a barcode and time, not an installation identity. Rate-limit records use a one-way hash of a random installation ID that the current app does not show to users. Purchase-entitlement records are keyed by a one-way hash of a Google Play purchase token, and the current source has no automatic TTL for them. These structures cannot currently be matched reliably to one person using an email address or order ID. Legacy shared product information may also be used by other Pretio users and is not deleted for one installation.
Some request-rate records and barcode-activity records have TTL expiry settings, but Firestore deletion is asynchronous. Cache freshness periods are not deletion periods. Detailed per-call Gemini diagnostic records are written only in the Tester project, not Production. Production Cloud Functions also emit operational event and error logs to Cloud Logging; their retention depends on the Production logging configuration, which has not been verified here. The previous Production backend did not define a deletion or maximum-retention period for legacy shared Product Insight caches or purchase-entitlement records. Pretio therefore does not claim that all server-side data is deleted on request or within 90 days.
