Privacy Policy

PRIVACY POLICY FireAPI is committed to protecting the privacy and personal information of its users. This Privacy Policy outlines how information is collected, used, disclosed, and secured when individuals interact with FireAPI through its website or use any of its API-related services. FireAPI provides both public API hosting and enterprise-level API management tools (collectively referred to as the "Services"). This document also explains how user data is managed in compliance with data protection obligations concerning Personally Identifiable Information (PII). Users are advised to review this Privacy Policy regularly to stay informed about how their information is handled and to ensure they are comfortable with the practices described. FireAPI may revise this Privacy Policy from time to time. Any such changes will be reflected by updating the "Last Updated" date at the top of the page. In some cases, FireAPI may also notify users of significant changes through other means such as emails or on-site notices. By continuing to use the Services after changes have been made, users are deemed to have accepted the revised policy. If users do not agree to the changes, they are advised to stop using the Services and delete their accounts if applicable. FireAPI provides two core offerings: its public Developer Hub and its Enterprise API Hub. The Enterprise API Hub allows organizations to manage internal and external APIs, supporting integrations with various API gateways, analytics dashboards, and team collaboration features. This platform allows organizations to monitor API performance, usage trends, and service reliability through detailed metrics. The public Developer Hub enables developers to publish, test, and subscribe to APIs. It functions as a central platform for discovering APIs and managing API consumption, both by individuals and teams. FireAPI collects certain user data through both platforms to facilitate these services, improve system performance, and maintain account integrity. FireAPI may collect personal information through direct user input, automated tracking systems, and integrations with third-party platforms. Information users provide voluntarily includes names, email addresses, usernames, contact numbers, organization names, job titles, API configuration preferences, profile details, and support requests. This information is often collected during account registration, profile updates, support conversations, participation in events, or application for employment. Automatically collected data includes IP addresses, browser types and versions, device information, access dates and times, visited URLs within the platform, referring links, and language preferences. FireAPI uses cookies and related tracking technologies to analyze usage patterns, store user settings, maintain secure sessions, and customize user experiences. Some cookies may be stored by third-party services, particularly if users log in through third-party providers or interact with social widgets. Device-level data may include hardware model numbers, unique device identifiers, operating system details, and connection logs. These are used to improve compatibility, troubleshoot issues, and optimize the Service experience. FireAPI may also receive data from third-party services, such as social logins or API publishing partners. Such data is handled in accordance with this Privacy Policy and subject to the user's privacy settings on those third-party platforms. FireAPI uses collected information for several operational and administrative purposes. These include account creation and authentication, transaction processing, content delivery, platform optimization, customer support, system maintenance, technical alerts, and API monitoring. Communication with users may include updates about platform features, system outages, service changes, promotional content, newsletters, and event invitations. FireAPI also uses personal data to analyze platform usage trends, generate analytics reports, improve interface performance, and prevent misuse of the Services. FireAPI may combine data collected from different sources to offer a more integrated experience. For example, information from support conversations may be linked to usage data to better address user issues. In certain cases, FireAPI may send users system-generated push notifications regarding updates, new features, or support reminders. Device and identification data is collected for this purpose. FireAPI offers optional integrations with third-party applications. These may include services such as payment processors, API gateways, developer tools, or cloud hosting platforms. The use of third-party applications is governed by their own privacy policies, and users should review them before enabling such integrations. FireAPI is not responsible for data handling by these third parties. In some circumstances, FireAPI may disclose user information. This includes situations where disclosure is necessary to comply with legal obligations, enforce FireAPI's terms and policies, detect or prevent fraud, respond to emergencies, or protect the safety of individuals. Disclosure may also occur if FireAPI is involved in a business transaction such as a merger, asset transfer, or acquisition. In these cases, user data may be transferred to the successor entity under continued privacy safeguards. FireAPI may share aggregated or anonymized data with partners or researchers. This data does not contain personally identifiable information and is used for purposes such as statistical analysis, product development, and market research. FireAPI takes steps to ensure that aggregated data cannot be traced back to individual users. Security is a priority for FireAPI. The company implements industry-standard measures to prevent unauthorized access, data breaches, and misuse of information. Personal data is stored on secure servers in access-controlled environments. Account access is protected by passwords, which should be kept confidential by users. FireAPI strongly encourages users to log out after each session and to avoid sharing account credentials. Any suspected security breach should be reported immediately to support@fireapi.io. Users have the ability to review, update, or delete their personal information at any time by logging into their accounts or contacting FireAPI at support@fireapi.io. Users who no longer wish to maintain their accounts may request deactivation. FireAPI may retain certain information for legal compliance, dispute resolution, backup retention, or fraud prevention purposes. In some cases, archived data may be retained temporarily before being deleted or anonymized. FireAPI retains user data only as long as necessary to fulfill the purposes described in this Privacy Policy. When data is no longer needed, it is securely deleted or anonymized. If users want to inquire about what personal information FireAPI holds, they can send a request to support@fireapi.io. FireAPI aims to respond to such requests within thirty days, subject to verification of identity and scope of request. Users may opt out of promotional emails by clicking unsubscribe links in those messages or by contacting support@fireapi.io. Even if users opt out of promotional communications, FireAPI may still send essential messages related to account security, system functionality, service availability, or transactional notices. Cookies and similar technologies are used by FireAPI to store preferences, authenticate users, enhance functionality, and analyze user engagement. A cookie is a small text file placed in the user's browser or device to remember session activity and preferences. FireAPI uses both session cookies, which expire after the browser is closed, and persistent cookies, which remain until deleted manually or upon expiration. Disabling cookies may result in reduced functionality on the FireAPI website or platform. Security cookies help prevent unauthorized logins and other threats. Analytical cookies track usage trends and site performance. Functional cookies personalize the user interface and support smoother navigation. Third-party cookies may be installed by services such as analytics tools, login providers, or embedded social media content. These cookies are subject to the third party's data practices and should be reviewed individually. Users may control cookies through their browser settings. Most browsers allow for blocking or deleting cookies on a per-site basis. Adjusting these settings may limit access to some FireAPI features or require additional authentication for each session. Instructions for managing cookies are available in browser support documentation. FireAPI supports third-party sign-in options, such as OpenID, GitHub, or Google authentication. These providers verify identity and allow users to sign in without creating a separate FireAPI password. Certain basic profile information such as email, name, and avatar may be shared with FireAPI at login. Users can revoke access to their FireAPI accounts through their identity provider at any time. Social media features may be present on the FireAPI platform, such as buttons for sharing content. These features may collect user data including IP address and page views and may store cookies for performance. These services are operated either by FireAPI or by external vendors and are governed by their respective privacy policies. FireAPI may offer community forums, discussion threads, or blog comment sections. Any information shared in these public areas is visible to other users and may be indexed by search engines. Users are advised not to post sensitive or private information in public areas. Requests to remove forum content or testimonials can be made by contacting support@fireapi.io. FireAPI will attempt to honor such requests unless retention is required by platform policy or legal obligation. FireAPI may publish testimonials or endorsements from satisfied users. These testimonials may include names or profile images, with prior consent from the individual. Testimonials may be edited for clarity or length but will not misrepresent the user's opinion. FireAPI may include links to external websites for additional tools, documentation, or partnership offerings. Once users leave the FireAPI website, their activity is governed by the privacy policies of the destination site. FireAPI is not responsible for the content, terms, or privacy practices of any third-party websites. FireAPI's services are not intended for use by individuals under the age of 13. FireAPI does not knowingly collect information from children. If a parent or guardian becomes aware that a child has submitted personal data to FireAPI, they should contact support@fireapi.io so that appropriate action can be taken to remove the information and disable any associated accounts. If users have concerns, complaints, or questions about this Privacy Policy or FireAPI's handling of personal information, they should contact the company directly at support@fireapi.io. FireAPI aims to address all concerns promptly and respectfully and may follow up for additional clarification if needed. This Privacy Policy represents the complete understanding between users and FireAPI with respect to the handling of personal information. By using the Services, users agree to the terms described herein.