Effective April 9, 2026 · Last updated April 9, 2026
Inflatic ("the Service," "the App," "the Website") is a mobile application and web service that displays inflation-related data, pricing trends, and purchasing-power estimates. The Service is provided on an as-is, best-effort basis. It is intended for general informational purposes only and does not constitute financial, investment, or economic advice.
Inflatic is operated by Inflatic ("we," "us," "our"). References to "you" or "the user" mean any individual who installs, opens, or otherwise uses the App or visits the Website.
By tapping or clicking "Accept and Continue" on first use, you agree to these Terms. There is no option to use the Service without accepting. If you do not agree, do not use the Service.
We may update these Terms from time to time. If we make material changes, we will notify you through the App or Website (for example, by requiring re-acceptance). Continued use after notification constitutes acceptance of the revised Terms.
The Service is available to users aged 13 and older. We do not knowingly collect information from children under 13.
When in use, the Service contacts our servers to retrieve current inflation and pricing data. The Service uses pre-provisioned authentication tokens to authorize access. In the mobile App, these tokens are platform-specific and embedded into the application binary at build time — they are not obtained or refreshed at runtime. They are signed, per-platform credentials with a defined expiration period. If a bundled token expires or is revoked, the App will be unable to retrieve data until an updated build is distributed. On the Website, tokens may be provisioned or managed differently depending on the access method. In either case, the Service does not dynamically negotiate or rotate tokens during normal operation unless explicitly designed to do so.
The Service is provided for personal, non-commercial informational use. You agree not to reverse-engineer, decompile, or attempt to extract source code or authentication credentials from the Service; use automated systems to scrape, crawl, or overload the Service; redistribute, sublicense, or resell access to the Service or its data; or interfere with the normal operation of the Service or its infrastructure.
Inflatic is designed to minimize data collection. We do not collect personal information such as names, email addresses, phone numbers, or physical addresses. We do not require account creation or login. The data we do collect is limited to what is described in this section and is used solely for operational measurement.
After you accept these Terms on first use, the Service sends a one-time install event to our servers. This event includes your platform (iOS, Android, or web) and the app or client version. It does not include any device identifier or installation identifier. This event is used to measure aggregate install counts and platform distribution. If your device is not connected to the internet at the time of acceptance, the install event may be queued for delivery when connectivity is restored. If delivery is not possible, the install event may not be recorded. Install and usage measurements may therefore be incomplete due to connectivity conditions.
Separately from the install event, the Service performs a daily active usage check. On each calendar day that the Service is used (after Terms have been accepted), the Service generates or retrieves a locally stored anonymous installation identifier. This identifier is a random value generated entirely on your device or browser using a local random number generator. It is not a system advertising identifier (such as IDFA or GAID), and it is not derived from any personal or device-level information. The identifier is stored locally on your device or in your browser and persists across sessions. It is not generated or assigned by our servers — it is created and stored locally. Once per calendar day, the Service sends this identifier along with your platform to our servers. This daily ping is used to measure aggregate daily active usage and platform trends. It is a separate event from the install event described above, with a different payload and different timing.
We do not collect your name, email address, phone number, or physical address. We do not use system-level advertising identifiers (IDFA, GAID) or cross-app tracking identifiers. We do not collect location data, contacts, photos, or other device content. We do not use third-party analytics SDKs (such as Segment, Amplitude, Mixpanel, Firebase Analytics, or Sentry). All tracking is first-party only, sent to our own servers at api.inflatic.com.
Our servers and network infrastructure may use third-party providers, including Cloudflare, for content delivery, DDoS protection, and related services. These providers may process network-level metadata (such as IP addresses) as part of normal traffic routing. We do not control or direct these providers to collect personal information on our behalf beyond what is inherent in network traffic handling.
The Service may use different authentication tokens for different platforms (iOS, Android, and web). This means that platform identification may be built into the authentication mechanism at the token level. These tokens are used solely for authorizing access to our data API and do not carry or transmit personal information.
The Service contacts our servers to retrieve updated data in the following situations: immediately when the App is opened or the Website is loaded; when you manually refresh; and periodically during active sessions at approximately four-to-five-minute intervals via a continuous background polling cycle. This periodic polling runs for the duration of the session regardless of user interaction. It is not limited to moments when the Service is actively opened or resumed — it continues as long as the session is active.
The Service caches the most recent successfully retrieved data payload to persistent local storage (on-device storage in the App, or browser storage on the Website). This cached data survives app restarts, device reboots, and browser refreshes. If the Service is unable to reach our servers (due to network unavailability, timeout, or server error), it will display the last successfully cached data along with a timestamp indicating when that data was last updated. If no cached data exists (for example, on a first use with no network connectivity), the Service will display an explicit offline or no-data state rather than showing placeholder or synthetic information. Cached data is stored unencrypted in local storage. The cache contains only the data payload and freshness metadata — it does not contain personal information.
We do not sell, rent, or share any collected information with third parties for advertising, marketing, or profiling purposes.
The anonymous installation identifier stored locally persists until you uninstall the App, clear the App's storage, or clear your browser data (on the Website). Server-side, daily ping data may be processed (for example, hashed with the date) before storage so that the raw identifier is not retained in our systems. We retain aggregated operational data (install counts, daily active usage counts, platform distribution) indefinitely for trend analysis.
We use reasonable administrative, technical, and organizational measures designed to protect the Service and the limited information we handle. In the mobile App, authentication tokens and the installation identifier are currently stored in standard on-device storage (AsyncStorage), which is not encrypted at rest. We are evaluating migration to encrypted on-device storage (such as Expo SecureStore) for future releases. Bundled authentication tokens in the App are embedded as string literals in the app binary, which provides limited protection through standard code obfuscation but is not equivalent to encrypted storage. On the Website, tokens and identifiers are stored in standard browser storage mechanisms, which are similarly not encrypted at rest.
Inflatic presents inflation and pricing data sourced from third-party providers and public data sets. We make reasonable efforts to display accurate, current information, but we do not guarantee the accuracy, completeness, or timeliness of any data shown. Data may be delayed, estimated, or subject to revision by its original sources.
Inflatic's data collection began on March 17, 2026. Stable, reliable datapoints did not appear in the dataset until approximately March 20, 2026. As a result, historical views covering periods before that date — including the 30-day view during the initial weeks of availability — may display incomplete, sparse, or visually irregular data. This is expected behavior reflecting the true state of the dataset, not a bug or data error. Historical coverage will naturally fill in as the dataset matures over time.
Nothing in the Service constitutes financial, investment, legal, or tax advice. Do not make financial decisions based solely on information presented in the Service.
On first use or when cached data is not available, the Service displays a loading state (skeleton UI) while retrieving data from our servers. During this loading period, no data values are displayed. The Service does not show synthetic, placeholder, or estimated data as if it were real. Data is displayed only after a successful response from our servers or from a previously cached real data payload.
We do not knowingly present synthetic or fabricated data as genuine underlying source data. Internal placeholder values may exist in the app codebase for development and testing purposes, but these are not surfaced to users during normal operation.
The Service relies on third-party data sources that we do not control. These sources may change their data formats, availability, pricing, or terms without notice. We are not responsible for interruptions, inaccuracies, or discontinuations originating from third-party data providers.
We do not guarantee uninterrupted availability of the Service. The Service may be unavailable due to server maintenance, network issues, third-party provider outages, or other factors. Because the mobile App uses build-time-embedded authentication tokens with a defined expiration period, the App will cease to function for data retrieval when those tokens expire unless an updated build is distributed. We will make reasonable efforts to distribute updated builds and maintain service continuity across all platforms before any token expiration.
Inflatic may rely on third-party infrastructure providers (such as cloud hosting, CDN, and DNS services) for normal operation. Disruptions to these providers may affect Service availability. We are not responsible for outages or performance degradation caused by third-party infrastructure.
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR FREE OF HARMFUL COMPONENTS.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL INFLATIC, ITS OFFICERS, DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, WHETHER INCURRED DIRECTLY OR INDIRECTLY, OR ANY LOSS OF DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM YOUR USE OF OR INABILITY TO USE THE SERVICE.
These Terms are governed by and construed in accordance with applicable law, without regard to conflict-of-law principles.
If any provision of these Terms is found to be unenforceable, the remaining provisions will continue in full force and effect.
These Terms constitute the entire agreement between you and Inflatic regarding the Service and supersede any prior agreements.
If you have questions about these Terms or the Service, you may contact us at [email protected].