Timastra Ad Revenue
Timastra Ad Revenue — Privacy policy
An independent Android dashboard for estimated AdMob reports, with encrypted local storage and synthetic demo mode. The app is in internal and closed testing; purchase availability depends on the installed build and Google Play eligibility.
Effective and last updated: .
Who provides this app
Timastra Ad Revenue is provided by Timastra LLC. See our company details. Privacy questions can be sent to support@timastra.com.
This policy explains the app’s data use, including optional features and differences between supported platforms.
Optional read-only Google connection
Demo mode uses synthetic data and does not connect to AdMob. If you choose to connect, Google asks you to select an account and authorize the admob.readonly scope. The app reads publisher identifiers, account/reporting settings, app and ad-unit inventory, and estimated revenue, impressions, clicks, requests and related report metrics. It uses this information for your dashboard, filters, widgets, goals and alerts. It cannot change ads, payment settings or payout details. Estimates can change and are not settled payments. Timastra Ad Revenue is independent and is not affiliated with Google.
Where reporting data goes
Reports are requested directly between the device and Google. Google account labels and report data are kept locally; they are not sent to a Timastra reporting server or to RevenueCat. Google access tokens are used in device memory, not exported to billing services. Google processes authorization and API requests under its own policies. Timastra Ad Revenue’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data or use it for advertising or model training.
Encrypted local records and retention
Account labels, inventory, reports, preferences, saved views, goals, alert rules, delivery history and widget bindings are stored in encrypted device databases. Database keys are protected by Android Keystore. Demo and connected workspaces are separate. Android cloud backup of app data is disabled. Report caches are bounded and may be evicted; clearing report cache keeps preferences, rules, saved configurations and purchase access. Local preferences and configurations remain until you remove or reset them, clear app storage or uninstall. Losing the device key may require an explicit local reset; there is no Timastra cloud copy of reports or local settings to restore.
Widgets, notifications and exports
Widgets and notifications can expose information outside the app. Amount-hiding controls are available; Android and launcher settings affect lock-screen visibility and background execution. Refresh and alert delivery are best-effort rather than guaranteed live reporting. CSV and personal-data exports are created only when you request them and choose a destination with Android’s save picker. Exports may contain financial information and are not protected by the app’s database encryption after export. You control their storage, sharing and deletion.
Optional Google Play purchases
Builds configured with RevenueCat contact RevenueCat to check subscription access and load the product catalogue, even while new-purchase checkout is disabled. RevenueCat receives an app-generated anonymous billing identifier and necessary app/device/network metadata; purchase receipts/tokens, product identifiers and subscription state are processed when available. If purchases are enabled, Google Play processes payment and RevenueCat verifies purchase ownership and Pro access. Anonymous identifiers are pseudonymous: purchase records can still be associated with an installation or store transaction. The app does not deliberately attach your Google reporting identity, Google account email, Google tokens or AdMob reports to that billing identifier, and does not receive card details. Google Play and RevenueCat retain transaction records under their own policies and applicable requirements. Local deletion does not erase their records or cancel renewal. Some testing builds keep new-purchase checkout disabled. When checkout is available, the installed app and Google Play show the actual purchase terms before confirmation.
Advertising, diagnostics and support
This version has no advertising SDK, third-party analytics or crash-reporting SDK, and automatic advertising/device identifier collection by the billing SDK is disabled. A diagnostics export contains app version and an error category; sending it to support is your choice. Do not send Google tokens, passwords, purchase tokens, private databases or full revenue reports. The app is intended for authorized publisher account holders, not children.
Provider privacy references
Retention and deletion
Use Data & privacy to clear report cache or disconnect a Google connection. Disconnect removes that connection’s local inventory, reports, rules and saved settings and leaves its widgets unavailable. It does not delete your AdMob account or cancel a purchase. Where offered, request Google revocation when disconnecting, or manage app access in your Google account. Reset local data, Android Clear storage or uninstall removes this app’s local records; these actions are irreversible unless you separately retained an export. Delete exported files at their chosen destinations and any copies you shared. Google Play and RevenueCat transaction records are separate; contact support@timastra.com for help locating a billing-data deletion request without sharing tokens or card information. There is no separate Timastra reporting account to delete.
View deletion instructions and request help.
Support messages and your privacy choices
If you contact us, we receive your email address, message and any attachments you choose to send. We use them to respond, troubleshoot and handle privacy requests. Email and hosting providers process these communications and ordinary connection information. We retain correspondence as needed to resolve the request and meet applicable recordkeeping obligations; you may request deletion of correspondence.
You may request access, correction, export or deletion of personal information we hold, or raise an objection or withdraw consent where applicable. Local-only records must be managed on your device because we do not hold a remote copy. Optional device permissions can be revoked in system settings. Service providers may process data outside your country under their own policies; security also depends on your device and any destinations you choose for exports.
Contact and policy changes
Email support@timastra.com for Timastra Ad Revenue privacy questions. Include the app name and enough non-sensitive information to identify your request. Never send passwords, authentication codes, recovery keys or private health, financial or photo backups. We may need to verify ownership before releasing or deleting hosted records.
Material changes to the app's data practices will be reflected in this policy with an updated date and in the app where appropriate. Visiting this page is also covered by our website privacy policy.