Hot Fire · Internal company application
Privacy Policy
Hot Fire is a company-operated, internal Google Ads management and analytics application. It is used by authorized company personnel to manage Google Ads accounts for which the company has appropriate access. This Privacy Policy explains what information Hot Fire accesses, why it uses that information, where it stores it, when information may be disclosed, and how to request deletion.
1. Who operates Hot Fire and why
Hot Fire provides a simplified internal interface for Google Ads campaign creation and updates, budget management, pausing or resuming campaigns, and advertising performance analysis. Hot Fire is not a public advertising management service and does not offer open user registration. Privacy-related inquiries can be sent to [email protected].
2. Google authorization and data accessed
When an authorized user connects a Google Ads account, Hot Fire uses Google OAuth 2.0 authorization and the Google Ads API to access only the advertising accounts and resources that the user's Google permissions and granted API access allow. Depending on the requested operation and data availability, these resources include:
- Google Ads customer/account identifiers, account names, and account configuration;
- Campaigns, ad groups, ads, status, targeting and other advertising settings;
- Campaign budgets and related spending settings;
- Advertising performance metrics such as impressions, clicks, costs, and conversion data, where available;
- OAuth authorization data, including access tokens and refresh tokens, needed to maintain the authorized Google Ads connection; and
- Operational information generated by authorized actions in Hot Fire, such as the requested account, operation and result.
Hot Fire does not use Google Ads authorization to read Gmail messages, Google Drive files, or unrelated personal Google account content. Google Ads access can allow both reading and changing eligible advertising resources; authorized users should review the Google authorization screen before granting consent.
3. How Google Ads data is used
Hot Fire uses the information described above for the following internal business functions:
- Displaying authorized Google Ads accounts, campaigns, settings, and performance reports;
- Analyzing campaign results and supporting internal advertising reporting;
- Creating and updating campaigns and advertising settings at the direction of authorized personnel;
- Adjusting budgets or pausing and resuming eligible campaigns at the direction of authorized personnel; and
- Maintaining the Google Ads API connection, operating the application, and investigating operational errors or security issues.
Google Ads data accessed by Hot Fire is not used to build unrelated consumer profiles, is not sold as a data product, and is not used for AI-generated non-consensual intimate imagery or similar prohibited purposes. Hot Fire is not an AI imagery-generation application.
4. Where and how information is stored
OAuth credentials: OAuth tokens used to access authorized Google Ads accounts are stored on servers managed by the company so that Hot Fire can maintain the authorized connection and make permitted API requests.
Google Ads data: Google Ads account, campaign, and performance information retrieved for internal management and analysis is stored in a database operated as part of the company's application infrastructure.
These systems are operated on company-managed servers. Access is intended for the application's authorized personnel and the technical components required to operate the service. Technical logs or temporary processing data may also arise from using the application; their specific contents and retention depend on the actual server configuration.
5. Sharing and disclosure
Hot Fire is designed for the company's own internal Google Ads operations. It does not offer Google Ads data for sale, does not distribute that data publicly, and does not provide an external advertising-management service to unrelated customers.
Information may be available to authorized company personnel as necessary for the purposes described above, and is transmitted to Google through the Google Ads API as necessary to carry out authorized requests. If supporting infrastructure providers process information on the company's behalf, their involvement must be consistent with the purposes described here and applicable safeguards. Information may also be disclosed where required by applicable law.
6. Data retention and deletion requests
Hot Fire retains stored Google Ads information and OAuth credentials for the company's internal advertising management, reporting, and authorized operational needs. Retention depends on the ongoing need for the connection or information and on applicable business or legal requirements. This policy does not state a fixed retention period because a single verified period has not been established for all data categories.
An authorized user may request that stored Google Ads information or the application's stored OAuth authorization credentials be reviewed or deleted by emailing [email protected]. Include the relevant Google Ads account identifier and the nature of the request, but do not send OAuth tokens or passwords. The company may need to verify the requester's authorization and identify any data that must be retained for applicable legal or operational reasons before taking action.
Removing a connection or deleting records from Hot Fire does not itself delete the underlying Google Ads account or advertising data held by Google.
7. Revoking Google OAuth access
Users may revoke the Google authorization granted to Hot Fire in their Google Account connections settings. Revocation prevents Hot Fire from obtaining further access under that authorization, but it does not automatically erase copies of Google Ads information or tokens already stored by Hot Fire. To request deletion of stored information, contact [email protected] separately.
8. Security and permitted use
Hot Fire is intended for restricted internal use on company-managed infrastructure. The company is responsible for limiting access to authorized personnel, protecting stored OAuth credentials and advertising data, and keeping its implementation consistent with this policy and applicable Google API requirements. No method of electronic storage or transmission can be guaranteed completely secure.
Use of information obtained through Google APIs is subject to the applicable Google API Services User Data Policy, including Limited Use requirements where applicable. Hot Fire uses such information only for the disclosed internal advertising-management purposes.
9. Updates to this policy
We may update this policy to reflect changes to Hot Fire's actual data-handling practices or applicable requirements. The current version and its effective update date will be published at https://kwpslw.com/privacy.html. When changes materially affect the handling of authorized users' Google information, affected users will be informed as appropriate before that information is used for a materially different purpose.
10. Contact
For questions about privacy, access to stored information, OAuth authorization, or deletion requests, email [email protected].
Hot Fire is an independently operated internal application. It is not a Google product and is not affiliated with or endorsed by Google.