GoldSense Privacy Policy

Effective date: 2026-09-09

This Privacy Policy explains how GoldSense ("we", "our", or "us") collects, uses, and shares information when you use the GoldSense mobile application (the "App") on Android and iOS.

Summary

• The App does not require account sign-up and does not ask you to register a name, email address, or phone number. Any names, ID numbers or phone numbers you enter in a sale record stay in your local records.
• Portfolio data, settings, and alerts are stored locally on your device.
• Price data is fetched from our proxy using MetalPriceAPI, with optional direct Yahoo Finance requests. Exchange rates come from public currency APIs. Network providers receive ordinary connection metadata, such as your IP address.
• In-app purchases are processed by Apple App Store (iOS) or Google Play (Android) and managed via RevenueCat for entitlement verification. We never receive or store your payment details.
• If the App crashes, a technical crash report is sent to Sentry, our crash-reporting processor, in its European Union data region. It describes the error and the device; it never contains your portfolio. See "Crash Reporting" below.
• We do not serve ads. We do not use advertising or usage-analytics SDKs. Price requests, widget refreshes, RevenueCat purchase checks, and Sentry crash/session reporting can occur automatically.

Information We Collect

• Device-local data: portfolio items, transactions, alerts, photos you attach to portfolio items, and settings — all saved in local storage (SQLite / Shared Preferences). This data stays on your device unless you choose to export or share it.
• Crash reports: In release builds, if the App crashes or hits a serious internal error it could not recover from, the App sends a crash report to Sentry. Exactly what a report contains, and what is deliberately left out, is described under "Crash Reporting". Development builds send nothing.
• Purchase information: For Premium upgrades, RevenueCat receives an anonymous user identifier and the purchase receipt from Apple or Google in order to validate your entitlement. We do not receive your Apple ID, Google account, or full payment details.

How We Use Information

• Provide core functionality: track prices, manage portfolios, set alerts, and display widgets.
• Process in-app purchases: validate Premium status through RevenueCat using the platform receipt.
• Fix defects: crash reports are used only to find and fix errors in the App.

Crash Reporting

GoldSense stores your holdings locally, so crash reporting is designed to tell us that something broke and where in the App's code — not what you were doing, and not what you own.

What triggers a report. A report is sent when the App crashes (an unhandled error in the App's code or, rarely, in native platform code), or when the App catches a serious internal error it could not fully recover from (for example, a failure to open its local database). In addition, each time the App starts, the reporting library sends a short session record (start time, duration, app version, whether the session ended in a crash, and the installation identifier described below) that is used to calculate a crash-free rate. Reporting is enabled in release builds, including release builds installed outside the stores.

What a report contains.

• The error type and message, and a stack trace of the App's own code (which functions were running when it failed).
• The App's version and build number, and the version of the reporting library.
• Device details: manufacturer, brand and model, CPU architecture, screen size and density, orientation, total and free memory, total and free storage, battery level and charging state, whether the device was online and the connection type (Wi-Fi or cellular), time zone, language and locale, boot time, and (on Android) whether the device is rooted.
• Operating system name, version and build, and whether the device was in light or dark mode.
• App state at the time: foreground or background, memory used by the App, and the list of software libraries the App is built from.
• A random installation identifier, generated by the reporting library the first time the App runs and stored in the App's private storage. It is not derived from your device's hardware, SIM, or advertising identifiers; it is not linked to your name, email address, or any account; and it is discarded when you uninstall the App. Its only use is to count how many installations a defect affects.

What is deliberately excluded.

• No portfolio data, transactions, prices, photos, names, ID numbers, or phone numbers. If a database error message contains an SQL statement or its values, the message is cut off at that point before it leaves the device.
• No file system paths (on both platforms these embed the device's account name); they are replaced with a placeholder before sending.
• No IP address in the report (the reporting library's "send default personal information" option is off), and no device name.
• No screenshots, no screen recordings, and no view hierarchy.
• No "breadcrumbs" — the trail of screens visited and buttons tapped that crash reporters normally record. They are discarded on the device and never transmitted.
• No performance tracing and no usage analytics.

Reports travel over an encrypted HTTPS connection. Like any web server, Sentry's infrastructure sees the connection's IP address while delivering the request, but the App does not include it in the report and it is not shown to us.

Where it goes. Reports are sent to Sentry (Functional Software, Inc.), which processes them on our behalf as a data processor, in Sentry's European Union data region. Sentry's privacy practices are described at https://sentry.io/privacy/.

Retention. Crash reports are retained by Sentry for its standard error-event retention period (30 or 90 days depending on the Sentry plan, at the time of writing; see https://docs.sentry.io/security-legal-pii/security/data-retention-periods/), after which they can no longer be accessed. They are not used for any other purpose, are not sold, and are never used for advertising or profiling.

Your choices. This version of the App has no in-app switch to turn crash reporting off; the only way to avoid it is not to use the App. You can ask us to delete crash reports at the contact address below. Because a report carries no personal identifier, please tell us the device model and the approximate date and time of the crash so that we can locate it.

Data Storage and Retention

• On-device storage: Your portfolio and settings are stored locally on your device. You can delete the App to remove this data.
• RevenueCat: Stores an anonymous user ID and purchase history to enable subscription management and restore-purchases functionality. RevenueCat's privacy practices are described at https://www.revenuecat.com/privacy.
• Sentry: Stores crash reports and session records as described under "Crash Reporting", for the retention period described there.

Data Sharing

• Third-party price providers: To fetch prices, the App and its widgets make requests to our proxy at goldsense-proxy.vercel.app, which uses MetalPriceAPI. The App can also make direct Yahoo Finance requests. Exchange rates are fetched from open.er-api.com and api.frankfurter.dev. These providers may process your IP address and standard network metadata to serve content.
• App stores and billing: Apple App Store (iOS) and Google Play (Android) process in-app purchases. RevenueCat receives the platform receipt for validation.
• Crash reporting: Sentry receives crash reports and session records as described under "Crash Reporting". Sentry acts as our processor and does not use them for its own purposes.
• Legal: We may disclose information if required by law.

Permissions

• Network access: required to fetch prices, verify purchases, and send crash reports.
• Notifications: used to deliver local price alerts you configure.
• Widgets: display prices and, when available, portfolio totals on your home screen. Aggregate metal quantities, premiums and cost basis are shared locally with the widget so it can recalculate totals without opening the App. These holdings values are not included in price requests. The operating system controls refresh timing; it may delay or suspend updates.
• Camera: used to take photos of your precious metals items for your portfolio. Photos are stored locally on your device.
• Photo Library: used to select and save images of your portfolio items. Images remain on your device.
• We do not request microphone, location, contacts, or calendar permissions.

Children's Privacy

The App is not directed to children under 13. We do not knowingly collect personal information from children.

Security

We use industry-standard HTTPS for network communications and follow least-permissions principles. However, no method of transmission or storage is 100% secure.

Your Choices

• Manage alerts and widgets in the App's settings.
• Export your local data using Data Management in Settings. Delete holdings in the portfolio, or remove the App to remove its local data. Copies you previously exported or backed up are separate and must be managed by you.
• Manage or cancel a Premium subscription at any time via your Apple ID subscriptions or Google Play subscriptions settings.
• Restore past purchases via Settings → Premium → Restore Purchases.
• Ask us to delete crash reports (see "Crash Reporting").

International Transfers

Requests to price providers, our proxy, and RevenueCat may be routed through servers outside your country. Crash reports are stored in Sentry's European Union data region. By using the App, you consent to such transfers.

Changes to This Policy

We may update this Policy from time to time. Material changes will be reflected in an updated effective date.

Contact Us

If you have questions about this Policy, contact: three.minutes.electro@gmail.com