Before public release
DevTracker is in development. This page describes the implemented preview; individual services become available after account configuration and verification. No public App Store release date is announced. DevTracker is a working name.
Scope and operator
This policy applies to DevTracker and its product, support and policy pages. Other Sunlight apps have separate policies. Sunlight provides DevTracker; the legal operator is identified on the Publisher Information page.
Information you provide
A cloud account uses your email address and account identifier. You may save project names, app identifiers, website domains and provider connections. Provider credentials are encrypted on the backend. Session credentials are stored in the iOS Keychain.
Connected reports
With your authorization, DevTracker reads reporting data from the services you connect. It stores aggregate revenue, proceeds, subscription, advertising, traffic and search metrics, together with source scope, currencies, reporting dates and freshness.
Some provider API responses include customer or payment details that the reporting adapters process transiently to calculate aggregates. Customer names, customer emails, card details and individual payment records are not retained as reporting records.
DevTracker purchases
When Pro purchasing is configured, Apple processes the payment. DevTracker verifies signed purchase information and retains the original transaction identifier, subscription product, expiry, revocation status, signature date and store environment linked to your DevTracker account. A purchase uses an account token to bind it to that account. Signing into a different DevTracker account or connecting the same provider does not transfer the purchase. DevTracker does not receive your Apple payment-card details.
How information is used
Information is used to authenticate you, display your reports, maintain connections, enforce plan limits, verify purchases and provide requested support. Google API data is used for your reporting features, not advertising profiles, data sales or training general-purpose AI models. The current app preview contains no advertising or third-party usage-analytics SDK.
Google API data and your permission
DevTracker’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. You grant the relevant reporting permission through Google’s authorization page. Google tokens are exchanged on the backend; refresh tokens are stored encrypted and are not returned to the app.
Disconnect a source in DevTracker to remove its stored connection credential and report. You can also revoke access in your Google account connections. Revoking Google access alone does not delete your DevTracker account or previously saved reports.
Free allowances and abuse prevention
DevTracker verifies your provider account and selected product, app, stream, property or site. Connected services may use different emails from your DevTracker login. The backend uses provider account identifiers and keyed identity hashes to prevent an additional DevTracker account, new API key or reconnection from claiming another Free project for the same verified identity. Google connections request the OpenID account identifier alongside reporting access, without requesting email or profile scopes for this purpose. Verification uses the identities available from each provider, such as RevenueCat project, Stripe account, Lemon Squeezy user/store and Paddle seller IDs. Independent provider identities cannot reliably identify one human.
Confirmed allowance records remain while the account and project are active, including after a source disconnect. After project or account deletion, limited pseudonymous allowance records expire 180 days after last use and are removed by scheduled maintenance. Unfinished reservations expire after ten minutes. Usage counters and expired source leases are removed after eight days. These limited records contain no email addresses, passwords, API keys or financial reports. Maintenance runs hourly; infrastructure backup expiry is separate.
Owner-scoped opaque account/scope identifiers also help detect overlapping selections in combined revenue views. They do not grant access to another user’s reports. Reporting usage counters and source leases protect capacity and prevent connection changes from resetting cooldowns. Account recovery requires verification; accounts are never automatically merged because they connect the same service. Use password recovery or contact support if your original account is inaccessible.
Storage and service providers
Supabase provides authentication, database storage and server functions. Provider credentials and Google refresh tokens are encrypted on the backend. Authorized reporting operations enforce ownership, source scopes, usage and response-size limits. This website adds no advertising trackers or analytics scripts.
The optional reporting-currency view requests public historical rates from Frankfurter. Currency codes, dates and normal network information such as the request IP reach that service. Financial amounts, provider credentials and your DevTracker account identifier are not included in rate requests. Public rates are cached on the device for 24 hours. Conversion dates and original amounts remain visible; reference conversion is not a settlement or payout report.
Operational records and network information
Account-linked request counts, transfer-byte counts, source-check timestamps and bounded error codes support security, fair-use limits and troubleshooting. They are not a record of every screen you view or a third-party advertising profile. Hosting, authentication and connected services also receive network information needed to serve requests, such as an IP address, request time and technical request metadata. Infrastructure can retain security and diagnostic logs according to its service configuration. Contact support with questions about technical records and retention.
Your reports can include aggregate country, platform, app-version, advertising and audience breakdowns from your own provider properties. These are business reports, rather than permission to access this iPhone’s location, contacts, photos or other apps. The current app does not request those device permissions. DevTracker does not sell your connected data or use it to track you across other companies’ apps and websites.
On your devices
The app caches account-owned reports on your device. Dashboard preferences, source selections, automatic-refresh preference and goals are local to that account and clear on sign-out. These preferences do not automatically sync between devices. Revenue masking hides displayed monetary values and clears the pinned widget; exports contain the original numbers.
Widgets show the explicitly pinned value, report period and last check. Daily reminders and goal notifications are local. Goals require fresh, complete data with compatible units, currency, dates and country/version filters. Demo and marketing figures are fictional.
Optional monitoring, inbox and push
Scheduled monitoring starts disabled. If you enable it, the server checks authorized, active sources within persisted provider, import and byte budgets. It retains compact comparison windows, quiet hours, threshold rules, daily/weekly digest preferences and inbox events. Missing, stale or partial data is disclosed; compatible comparisons are required and repeated alerts are suppressed. Rolling windows can overlap and are labelled. Dashboard country/version filters do not narrow whole-source monitoring.
The inbox retains at most 100 events for 30 days; two compact monitoring windows per source expire after 30 days without use. If Apple push is configured later and you enable notifications, an installation identifier, environment-specific token hash and encrypted device token are linked to your account for delivery. Up to five registrations expire after 90 days without renewal. Lock-screen push payloads contain no revenue amounts or provider/source names. Device tokens are removed on monitoring disablement and cleared through account controls. Push delivery is currently unavailable and unverified; inbox updates do not require it.
Retention and deletion
Your workspace is retained while your account is active. Disconnecting a provider deletes its stored credential, saved report and monitoring baseline. Previously generated inbox data can remain for up to 30 days, hidden from the ordinary inbox when its source is disconnected; it can appear in an explicit retained-account export. Deleting a project removes its connections and reports. In-app account deletion removes your authentication account and its owned workspace, projects, connections, reports, monitoring preferences/baselines/inbox events, device registrations and subscription record. The limited abuse-prevention records described above are retained separately until expiry.
Local report caches, goals and pinned widget data are cleared on sign-out or in-app deletion. Infrastructure backups may retain deleted records until those backups expire. Technical logs and support correspondence may remain for security, resolving requests, disputes or applicable legal requirements. Apple and connected providers retain their own records under their own policies.
Your controls
Export report CSVs, readable summaries or retained cloud account data from the account export screen. The explicit retained-data export can include reports retained from an earlier plan without unlocking those reports in the current dashboard. It excludes provider credentials, OAuth/push tokens and private abuse-prevention hashes. Downloads use a protected temporary file that is removed when you leave the export screen. Available data is paged at request time rather than a frozen backup; deleted data cannot be recovered. Normal transfer limits can apply; contact support if an export cannot complete.
You can disable monitoring, disconnect sources, revoke provider access, clear widgets, change notification permission or delete your account. See Account & data deletion. Deletion or uninstalling does not cancel an Apple subscription. Contact support for access, correction or other privacy requests.
Contact Sunlight
For DevTracker support or privacy requests, email devsunlightpvt@gmail.com. Never send passwords, API keys, private keys, authentication codes or customer details.
The service is provided by Sunlight. The legal operator and location are listed in Publisher Information.