Effective Date: September 15, 2026
This Privacy Policy describes how Azeroth Inc. ("our," "we") collects, uses, and shares personal information. In particular, this Privacy Policy applies to:
Our website at www.jenova.ai as available to the general public (our "Website"). This Privacy Policy applies to visitors to our Website ("Visitors").
Our other online websites, applications, and services we operate that post this Privacy Policy ("Services"). As a central part of our Services, we enable individuals who sign on to our services ("Users") to interact with AI agents on our platform, create and use Agents, and connect their accounts to external, third-party applications and services ("Third-Party Tools"). For clarity, in the product interface these integrations may be labeled as "apps" or "app connections"; such in-product references to "apps" refer to Third-Party Tools for purposes of this Privacy Policy.
Our Jenova Agent API and related developer tools made available through Jenova's API endpoints and the Developer dashboard (www.jenova.ai/platform) (the "API Services"). The API Services enable developers ("API Developers" or "Developers") to integrate our AI agent capabilities into their own applications, services, or products, which are then used by the Developer's own end users ("End Users"). This Privacy Policy describes how we handle data submitted by API Developers and their End Users through the API Services.
Information We Collect
To provide our Website and Services, we may collect data by which Visitors and Users may be identified. We may also collect information about the devices and equipment you use to access our Website and Services, including usage data.
Information Provided Directly by You. If you are a Visitor, the information we collect from you may include contact information such as full name, email address, and other identifiers that may permit you to be contacted online. You may also provide us with other information when you communicate with our AI agent platform, including by uploading images, documents, or other multimedia content and files (your "Prompts").
Account Information. When you create a User account, you may sign in with email or via single sign-ons integrated with Google and Apple. For email sign-in, we collect your email address and authentication information (e.g., a salted/hashed password or magic-link/one-time-code tokens). For Google or Apple SSO, those providers may share certain data with us associated with you, including your name, email address, or other contact information. We do not have access to your account credentials with those SSO services.
API Developer Account Information. When you create an API Developer account on www.jenova.ai/platform, we collect your email address, phone number, account authentication information, and any other information you provide during registration or account management. We verify your phone number via SMS or voice verification code as part of the account activation process. We also generate and associate API Keys with your Developer account, which you use to authenticate API requests.
API Keys. API Developers are issued unique API Keys to authenticate and access the API Services. We store and associate these API Keys with Developer accounts. API Keys are used to identify the Developer making API requests and to track usage for billing and security purposes.
Data Submitted Through the API Services. When API Developers and their End Users use applications built with our API Services, we collect and process data submitted through API requests, including:
Prompts and Inputs: Text, documents, or other materials submitted by API Developers or their End Users for processing by our AI models.
Outputs: Responses generated by our AI models in response to API requests.
Conversation Data: Chat sessions, conversation history, memory entries, and uploaded files submitted through the API.
Agent Configuration Data: System instructions, knowledge bases, model selections, and other configuration settings for AI agents created through the API.
API Usage Data: Metadata about API requests, including timestamps, API endpoints accessed, request/response sizes, error logs, IP addresses, and usage metrics for billing and system monitoring.
End User Data and Authentication Credentials. When End Users of API Developer applications connect to Third-Party Tools (such as Gmail, Google Drive, Slack, or GitHub) through features enabled by the API Services:
We collect and store authentication credentials (such as OAuth tokens) that enable our AI to access the End User's external services on behalf of the End User, as directed by the API Developer's application.
These credentials are stored on Azeroth's infrastructure when the API Developer configures Third-Party Tool integrations through our platform (www.jenova.ai/platform).
We process data retrieved from End Users' connected Third-Party Tools (such as emails, documents, messages, or other content from external services) to generate responses and complete tasks as requested through the API Developer's application.
Developer Responsibility: API Developers are solely responsible for obtaining appropriate consents, authorizations, and disclosures from their End Users before enabling Third-Party Tool connections. API Developers must ensure their End Users understand what data will be accessed, how it will be used, and the risks involved. Azeroth relies on API Developers to act as the primary privacy contact and controller for their End Users.
Agent Data. When you create or use Agents, you may provide information within those agents, such as custom instructions, knowledge bases, or other data inputs. We store the custom system instructions and knowledge bases uploaded to Agents, but we do not manually access or view this data or use it for training, except when required for legal compliance, security purposes, or technical debugging. These materials may be processed by automated systems (including for safety review, analytics, and app operation). Primary user interactions are not reviewed by humans; any human access is limited to AI-generated, de-identified summaries for analytics and product improvement or to the limited exceptions above. In the event of system errors, limited access to this data may be granted to authorized personnel under strict access controls to resolve the issue effectively.
Global Memory Data. Our Services include an optional personalization feature called "Global Memory." When Global Memory is turned on, we may store user-approved data points you add or confirm (e.g., traits, preferences, profile details, and other relevant information) to deliver a more tailored experience. You can add, modify, or delete Global Memory entries by conversing directly with the AI in the chat interface. You can also turn Global Memory on or off at any time using a toggle in the chat interface. When Global Memory is turned off for a session: (i) that session will not reference Global Memory; and (ii) the content of that session will not be used to create or update your Global Memory. We may retain limited metadata (e.g., timestamps of updates) for security, troubleshooting, and audit purposes. Global Memory is not used to train our own AI models.
Third-Party Tool Data. When you connect a Third-Party Tool, you authorize us and the Tool to access and process data from your connected external services. This may include the content of your documents, emails, messages, or other data ("Third-Party Data") necessary for the AI to perform an action or formulate a response on your behalf. You are responsible for the data you authorize us to access and should only connect services containing data you are comfortable sharing under the terms of this policy. For clarity, in the product interface, Third-Party Tools (including MCP-based connections) may be labeled as "apps" or "app connections"; references to "apps" in-product are treated as Third-Party Tools under this Privacy Policy.
Chat History and Uploaded Files. We also store user chat history and files uploaded by users, whether to Jenova or to Agents. We do not use this data to train our own AI models. Primary user interactions are processed by automated systems to enable the service and to generate de-identified summaries and analytics for product improvement. Humans do not review raw interactions; any human access is limited to these AI-generated, de-identified summaries or when required for legal compliance, security purposes, or technical debugging. In cases where system errors occur, authorized internal personnel may access limited user data under strict access controls to investigate and resolve the issue. Azeroth may also use automated tools, including AI-assisted analytics, to analyze user behavior, usage patterns, and use cases to improve the Services. Such analysis is conducted under the same access controls and data handling commitments described in this Privacy Policy. Furthermore, Agent Creators cannot access or view the chat history or uploaded files of users who interact with their agents. For data submitted through the API Services: API Developers can access and manage their own API-generated data (including conversation history and uploaded files) through API endpoints and the Developer dashboard. API Developers cannot access data belonging to other Developers. End Users should contact the API Developer whose application they are using for questions about their data.
Group Chat Data. If you participate in a group chat, your messages, uploaded files, account display information, data returned through connected tools, and other chat activity may be visible to the owner and other members of that chat, including members added later. If you leave or are removed from a group chat, your prior messages and uploaded files may remain available in the chat and in copies created through sharing, export, or similar features. Group chats do not use Global Memory to personalize responses or create or update Global Memory entries.
Agent Metadata. For Agents available on the platform, we may collect limited metadata (e.g., which Agent you used, timestamps, feature flags) to operate, secure, and improve the platform. Unless you expressly direct otherwise, we do not share your personal chat content or uploaded files with Agent Creators. Agents created by Agent Creators are not editorially reviewed, endorsed, or supported by Azeroth. We use automated systems to review Agents for policy compliance; this process is not performed by humans. See "Agents: Privacy Considerations and Disclaimers" below for more details.
Information Collected Automatically. We may collect data regarding your use of our Website through other means. This data may include your IP address, the date and time you access our Website, and the pages and content you access during your visit, websites that you link to or from, whether you receive or open an email or other communication from us, and the links you click on within those emails. We may also collect information from your mobile device or your computer about how you interact with our Website, including the date of the visit, the time of arrival and length of visit to the Website, the type of device used and the operating system on that device, browser type, a list of files downloaded or pages viewed, your IP address, and any errors encountered. If you use our mobile application, we may additionally collect information about your location while using our application. This information helps us address customer support issues, provide you with a personalized experience, prevent fraudulent use of our services, and manage the Website we provide you, including gathering aggregated data about engagement. For the API Services, we automatically collect technical information about API requests, including IP addresses, timestamps, API endpoints accessed, request and response metadata, error logs, and usage patterns for billing, security monitoring, fraud prevention, and service improvement. Direct API requests made to Jenova's API endpoints do not load browser cookies or marketing pixels, but the consumer web app and Developer Platform, including www.jenova.ai/platform, may use cookies, pixels, analytics, attribution tools, error monitoring, and similar technologies as described below.
Except where required by applicable law, we do not respond to "do not track" signals or other mechanisms that provide consumers the ability to exercise choice regarding the collection of personally identifiable information about an individual consumer's online activities over time and across third-party websites or online services.
Cookies and Similar Technologies. We and our third-party service providers, such as Google Analytics, use cookies and similar technologies (like web beacons and pixels) to collect information automatically on the consumer web app and Developer Platform. A "cookie" is a small text file that a website stores on your device to help the site remember information about you.
We use these technologies for purposes such as:
Operating and providing our Services.
Authenticating you and remembering your settings and preferences.
Analyzing the performance of our Services and understanding how users interact with them.
Improving our Services and developing new features.
Google Analytics: We use Google Analytics to help us understand and analyze usage of our Services. Google Analytics uses cookies to collect information such as how often users visit the Services, what pages they visit, and what other sites they used prior to coming to our Services. To learn more about how Google uses data, visit Google's Privacy Policy. You can prevent the use of Google Analytics relating to your use of our Services by downloading and installing the browser plugin available via this link: https://tools.google.com/dlpage/gaoptout.
Your Choices: Most web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove or reject browser cookies. Please note that if you choose to remove or reject cookies, this could affect the availability and functionality of our Services.
To provide features powered by YouTube API Services, we collect the following data:
User information, including name and email address, provided during login using Google SSO.
User chat history, including search queries entered into the chat interface to fetch relevant YouTube video links.
Chat history, including YouTube-related queries, is stored beyond the session to provide continuity, improve personalization, and enhance the functionality of our Services. YouTube links and related source references returned by the YouTube API and stored within chat history may become unavailable, expire, be refreshed, or be removed from the product interface after 30 days. We may remove, refresh, or limit access to YouTube API data as required or permitted by applicable YouTube API Services policies.
Regulated Data and Compliance Disclaimer
The Services are not designed, intended, or certified for use as a storage or processing solution for data subject to specific regulatory handling requirements, including but not limited to Protected Health Information (PHI) under HIPAA, data subject to GLBA, FERPA, ITAR, EAR, payment card data subject to PCI-DSS, children's data requiring verifiable parental consent, or similar regulations, or data protected by attorney-client privilege (collectively, "Regulated Data").
You must not submit, upload, transmit, or process Regulated Data through the Services unless Azeroth has expressly agreed to such use in a separate written agreement signed by an authorized representative of Azeroth. The Services have not been audited or certified for compliance with HIPAA, SOC 2, ISO 27001, GDPR, PCI-DSS, FedRAMP, or any other regulatory or industry framework, and use of the Services does not by itself satisfy any specialized legal, contractual, or regulatory obligation.
If you submit Regulated Data to the Services without Azeroth's separate written agreement, you do so at your own sole risk and in violation of our Terms of Use. Azeroth is not responsible for any regulatory non-compliance, penalties, fines, or liability arising from your submission of Regulated Data.
API Developers are solely responsible for ensuring that their applications do not process Regulated Data through the API Services unless Azeroth has expressly agreed to such processing in a separate written agreement. Azeroth acts as a service provider and does not independently verify the regulatory classification of data submitted through the API Services.
How We Use Personal Information
We may use the data we gather to operate our business and for a variety of purposes, including the following:
To enhance, support, and manage our Website and Services, including to maintain, analyze, customize, and improve your experience in connection with our Website and Services. This includes using data to improve the functionality of the Jenova platform, the Agent Creation Feature, and the API Services.
For analytics and product improvement using automated AI systems that analyze usage patterns and chat history to generate de-identified summaries and insights. Primary user interactions are not reviewed by humans; any human access is limited to these AI-generated, de-identified summaries.
To communicate with you and provide you with information that you request from us.
To provide customer and technical support.
To monitor and enforce our contracts, legal terms, acceptable use or other policies or similar terms, including our Terms of Use and Usage Policy.
To comply with the law and satisfy our regulatory and compliance obligations. Additionally, to support compliance efforts on behalf of others and ourselves that support our provision of services.
To detect and prevent fraud and other prohibited, illicit, or illegal activity, and to protect the rights and interests of you, others, and ourselves.
To address existing or anticipated disputes.
To otherwise operate our business, including support for transactions impacting our company as a whole (such as mergers, acquisitions, or asset purchases).
To fulfill any other purpose for which you provide your information to us.
For other purposes permitted by law, described to you when you provide your information, or to which you consent.
Personalization via Global Memory: When Global Memory is turned on, we use your Global Memory entries to personalize responses and experiences across sessions. When Global Memory is turned off for a session, we will not reference Global Memory for that session and the session content will not be used to create or update your Global Memory. Global Memory may also be disabled automatically for group chats.
API Services Operations: For the API Services, we use the information we collect to: (a) authenticate API Developers and process API requests; (b) provide, maintain, and improve the API Services; (c) calculate usage and bill API Developers for Credits consumed; (d) monitor API usage for security, fraud detection, abuse prevention, and compliance with our Terms of Use and Usage Policy; (e) enforce rate limits and usage restrictions; (f) generate de-identified analytics and insights to improve the API Services; and (g) communicate with API Developers about their accounts, usage, billing, technical issues, and updates to the API Services.
As permitted by law, we may combine the information we gather about you in identifiable form, including information from third parties. We may use this information, for example, to improve and personalize our services, content, and advertising.
We do not use user data, including Prompts, Outputs, chat history, uploaded files, custom system instructions, or knowledge bases, to train our own AI models. This policy applies equally to data submitted through the API Services by API Developers and their End Users. Primary user interactions are not reviewed by humans. We may process your content using automated systems to support the Services and to generate de-identified summaries and analytics for product improvement. Any human access is limited to these AI-generated, de-identified outputs, or when required for legal compliance, security purposes, or technical debugging. We store, but do not manually access or view, the custom system instructions or knowledge bases uploaded to Agents or configured through the API Services for any other purpose, except in the limited circumstances described above. Similarly, we store user chat history and uploaded files (whether to Jenova, to Agents, or through the API Services) but do not use this data for training our models.
Jenova relies on third-party AI model providers and other suppliers to provide parts of the Services. Where available, we use commercial API channels, account settings, contractual commitments, or opt-outs intended to prevent customer content from being used to train those providers' models. Third-party providers may still process and retain information as needed to provide, secure, debug, monitor, comply with law, and prevent abuse of their services, and their handling of information is subject to their applicable terms and policies. Azeroth does not guarantee the independent conduct of third-party providers beyond the commitments Azeroth has actually obtained.
Notwithstanding the foregoing, the Services — including all Outputs generated by Agents and the API Services — do not constitute professional advice in any domain. Our collection and processing of data in medical, legal, financial, or other specialized domains does not create any professional-client relationship and does not create a professional obligation to safeguard such data under domain-specific regulatory standards (such as HIPAA for medical data, GLBA for financial data, or rules of professional conduct for legal data). Users and API Developers are solely responsible for the data they submit and for independently ensuring compliance with applicable regulatory requirements.
Data Processing for AI Agent and Third-Party Tool Integrations
When you authorize and use a Third-Party Tool through our AI Agent features, you instruct us to interact with that Tool on your behalf. For clarity, in the product interface these integrations (including MCP-based connections) may be labeled as "apps" or "app connections"; references to "apps" in-product are treated as Third-Party Tools for purposes of this Privacy Policy. This process involves the following data flow:
By using these features, you consent to the processing of your prompts and your Third-Party Data by our AI models, our underlying AI model providers, and the infrastructure of the Third-Party Tool provider.
Third-Party Tool Integrations via API Services: When an End User of an API Developer's application connects to a Third-Party Tool through the API Services, the data flow is as follows:
Developer Responsibilities: API Developers are solely responsible for: (a) obtaining appropriate consents and authorizations from their End Users before enabling Third-Party Tool connections; (b) disclosing to End Users what data will be accessed, processed, and shared when using Third-Party Tools; (c) ensuring End Users understand the data flow and privacy implications; (d) maintaining their own privacy policy that governs their relationship with End Users; and (e) complying with all applicable privacy and data protection laws. By using the API Services with Third-Party Tool functionality, API Developers represent that they have obtained all necessary consents from their End Users.
IMPORTANT NOTICE: AI Model Provider Data Processing
It is critical to understand how data processed via our AI Agent features, Third-Party Tools, and API Services is handled, as these features may require Jenova and its third-party providers to process Prompts, context, instructions, and data returned by connected tools in order to provide the requested functionality.
This provider processing is a fundamental condition of using the AI Agent features and Third-Party Tool integrations through the API Services. If you are not comfortable with this processing, you should not use these integrations. API Developers must disclose these data processing practices to their End Users and obtain appropriate consents.
This is particularly important for users who submit sensitive, personal, or confidential information to the Services. Data submitted through Third-Party Tool integrations — including data that may contain medical records, legal communications, financial information, or other sensitive content from your connected external services — may be processed by third-party AI model providers to provide, secure, debug, monitor, comply with law, and prevent abuse of their services. Azeroth does not guarantee the independent conduct of third-party providers beyond the commitments Azeroth has actually obtained.
API Developers must prominently disclose these data processing practices to their End Users, particularly where End Users may submit sensitive or personal data through the Developer's application. Failure to disclose constitutes a violation of the Terms of Use.
Use of YouTube API Services
We may use user chat history, including YouTube-related queries, for the following purposes:
To ensure continuity across sessions and provide users with access to past interactions.
To enhance and personalize the user experience.
To monitor and improve the functionality and performance of our Services.
Chat history is retained securely and may be anonymized or deleted upon user request, as described in the "Managing Your YouTube API Data" section. YouTube links and related source references stored within chat history may become unavailable, expire, be refreshed, or be removed from the product interface after 30 days.
Agents: Privacy Considerations and Disclaimers
Agents created by Agent Creators (including agents accessible at URLs such as www.jenova.ai/a/{custom agent}) are not editorially reviewed, endorsed, or supported by Azeroth. Interactions with Agents run on our infrastructure; however, unless you expressly direct otherwise, we do not share your personal chat content or uploaded files with Agent Creators. We may share aggregated or de-identified usage statistics about Agents. Agents may be described for specialized verticals (e.g., academic, medical, legal), but they do not provide professional advice and should not be used as a substitute for advice from qualified professionals. We recommend that you avoid submitting sensitive personal information to Agents. If you choose to share sensitive information, you do so at your own risk.
Azeroth does not monitor, review, or moderate user interactions with the Services in real time. Azeroth has no visibility into the content of individual conversations and cannot detect or respond to user emergencies, mental health disclosures, or safety concerns arising during interactions with the Services. Users who experience distress during interactions with any agent should discontinue use and contact qualified professionals or emergency services immediately.
Relationship Between API Developers, End Users, and Azeroth
When API Developers use the API Services to build applications for their End Users:
Developer as Controller: The API Developer is the data controller (or has a direct relationship with the data controller) for their End Users' personal information. The API Developer determines what data is collected from End Users, how it is used, and what functionalities are provided.
Azeroth as Service Provider: Azeroth acts as a service provider for the API Developer, processing End User data solely as instructed by the API Developer through API requests and in accordance with our Terms of Use and this Privacy Policy.
No Direct Relationship with End Users: Azeroth does not have a direct relationship with End Users of API Developer applications. End Users should contact the API Developer (whose application they are using) for questions about data collection, use, sharing, or deletion. API Developers are responsible for providing their own privacy notices, terms of service, and support to their End Users.
Developer Privacy Obligations: API Developers must: (a) maintain and display their own privacy policy that complies with applicable laws; (b) obtain all necessary consents from End Users for data collection and processing; (c) clearly disclose to End Users that their application uses AI-generated content and the limitations thereof; (d) disclose to End Users how data will be processed, including by Azeroth's AI models and underlying third-party model providers; (e) inform End Users about Third-Party Tool integrations and associated data flows; and (f) provide End Users with appropriate rights to access, correct, and delete their data.
Data Access and Deletion Requests from End Users: If an End User contacts Azeroth directly with a data access, correction, or deletion request, we will direct the End User to contact the API Developer whose application they used. Upon verified request from an API Developer, we will assist in fulfilling End User data requests in accordance with applicable law and our agreement with the Developer.
Data Isolation: Data submitted by each API Developer is isolated and accessible only to that Developer. API Developers cannot access other Developers' data or End User data from other applications.
Sensitive Data Responsibility: The API Developer, as the data controller for their End Users, is solely responsible for: (a) determining whether data submitted by End Users constitutes Regulated Data or sensitive personal information; (b) implementing appropriate safeguards, encryption, access controls, and regulatory compliance measures for such data before it is submitted to the API Services; (c) ensuring that submission of End User data to the API Services (and processing by Azeroth and its third-party providers) is permissible under all applicable privacy, data protection, and industry-specific regulations in all jurisdictions where the Developer operates; and (d) responding to regulatory inquiries, audits, or investigations concerning End User data. Azeroth processes data submitted through the API Services as instructed by the API Developer and does not independently classify, validate, or apply regulatory controls to such data.
How We Secure Personal Information
We are committed to maintaining administrative, technical, and physical measures designed to protect the security of your information. This includes using encryption for data in transit and at rest, and implementing strict access controls to limit who can view user data. For the API Services, we employ additional security measures including secure API authentication, rate limiting, API Key encryption, and monitoring for suspicious activity. Of course, despite these measures, no network or system is ever entirely secure, and we cannot guarantee the security of networks and systems that we operate or that are operated on our behalf.
International Data Transfers and Processing
Azeroth Inc. is based in the United States. All data collected through the Services — including personal information, Prompts, Outputs, uploaded files, chat history, Global Memory entries, Agent data, API Developer data, and End User data — is transferred to, stored on, and processed using infrastructure located in the United States and other jurisdictions where Azeroth's service providers (including cloud hosting and AI model providers) operate.
By using the Services, you explicitly and voluntarily consent to the transfer of your data to the United States and to processing in the United States, regardless of your country of residence. You acknowledge that the United States may not provide the same level of data protection as your home jurisdiction. If you do not consent to the transfer and processing of your data in the United States, you must not use the Services.
Azeroth has not certified under the EU-U.S. Data Privacy Framework or any similar cross-border data transfer program. Users outside the United States should review this Privacy Policy carefully and independently assess whether their use of the Services is consistent with local data protection requirements before using the Services.
Azeroth's privacy practices are governed by this Privacy Policy and applicable law. Azeroth Inc. is based in the United States and operates the Services from the United States. Users outside the United States are responsible for determining whether their use of the Services is consistent with the legal requirements applicable in their jurisdiction.
API Developers who make their applications available to End Users outside the United States are solely responsible for complying with all applicable data transfer, data protection, and privacy laws in those jurisdictions. Azeroth is not responsible for the API Developer's compliance with non-U.S. regulatory requirements.
How We Share Personal Information
We may share your information with third parties as reasonable to operate our business, to provide the Services to you and others, as permitted or required by law, or as directed or authorized by you. For example:
Affiliated Companies. We may share some or all of your information with our parent companies, subsidiaries, joint ventures, or other companies under common control with us.
AI Providers and Third-Party Tool Providers: When you authorize and use features that connect to Third-Party Tools, you are directing us to share your Prompts and relevant data with both the Third-Party Tool provider and our underlying AI model providers. The data handling practices of the Third-Party Tool provider are governed by their own privacy policy, which we strongly encourage you to review before authorizing the tool. When End Users of API Developer applications use Third-Party Tool integrations, data is shared with Third-Party Tool providers and our underlying AI model providers as described in this Privacy Policy. API Developers are responsible for disclosing these data flows to their End Users.
Payment processing companies, such as Stripe;
Cloud hosting and security service providers; and
Technical and customer support providers.
Google SSO: User-provided data during login is processed in accordance with Google's Privacy Policy.
YouTube API Services: Search queries are sent to the YouTube API to retrieve relevant video links. These queries may be stored as part of your chat history as described above. YouTube links and related source references included in chat history may become unavailable, expire, be refreshed, or be removed from the product interface after 30 days.
Agents and Creators. We do not sell or transfer your personal chat content or uploaded files to Agent Creators unless you explicitly authorize a disclosure (for example, by connecting an Agent to an external service or form that you control). We may share aggregated or de-identified statistics with Agent Creators to help them understand usage and quality. Agents created by Agent Creators are not editorially reviewed, endorsed, or supported by Azeroth.
API Developers and Their End Users. When you are an API Developer, you have access to the data submitted through your own API Keys and can retrieve this data through API endpoints and the Developer dashboard. You cannot access data belonging to other API Developers. As an API Developer, you are responsible for how you use, store, and share data obtained through the API Services, including End User data. You must maintain your own privacy policy governing your use of End User data and comply with all applicable privacy laws. We may share aggregated, de-identified usage statistics and analytics with API Developers about their API usage.
We do not share, store, or use any data beyond what is necessary to provide the requested services.
Professional Advisors, Law Enforcement and Regulators. We share your information with our professional advisors who provide legal, compliance, auditing, accounting, banking, insurance, consulting, or similar services, and with regulators, law enforcement, or government agencies to:
comply with our legal and regulatory obligations, including those compliance obligations of federal, state, or local regulators;
conduct audits and manage financial, insurance, or other matters;
protect our interests, property, or legal rights, or those of our customers or third parties;
respond to a subpoena, court order, or similar law enforcement request, or when we believe in good faith that the disclosure of personal information is necessary to prevent physical harm or financial loss, to report suspected illegal activity, or to investigate violations of this Privacy Policy or other applicable terms; and
for other legal purposes, such as to enforce our terms and conditions, or to exercise or defend legal claims.
Corporate Transaction. In the event of a corporate transaction, we may share your personal information with companies or other entities in connection with, or during the negotiation of, any merger, sale of company stock or assets, financing, acquisition, restructuring, divestiture, or dissolution of all or a portion of our business, or other similar event.
Other Disclosures. In addition to the above disclosures, we may disclose personal information in the event that we believe such disclosure is (i) necessary to provide our services or operate our business; (ii) in accordance with purposes we describe when you share it with us; (iii) permitted by law; or (iv) with your consent or at your direction.
What Choices Do I Have?
Update personal information. If you are a User or API Developer, you can update certain information that you have provided by logging into your account settings. As permitted by law, we may not accommodate a request to change information if we believe the change would violate any law or legal requirement, cause the information to be incorrect, or prevent the provision of our Services.
Manage Third-Party Tool Integrations. You can choose whether to connect or use any Third-Party Tool. You can review the permissions granted to, and disconnect, any previously authorized Tool at any time through your account settings. Disconnecting a Tool will prevent any future data flow between our Service and that Tool for your account. API Developers can manage Third-Party Tool configurations for their agents through the www.jenova.ai/platform dashboard. End Users of API Developer applications should contact the Developer to manage or disconnect Third-Party Tool integrations.
Manage Global Memory. You can turn Global Memory on/off at any time via a toggle in the chat interface. You can add, modify, or delete specific Global Memory entries by conversing directly with the AI in the chat interface. When Global Memory is off for a session, the session will not reference Global Memory and the session content will not be used to create or update your Global Memory. You may also request deletion of all Global Memory entries through the chat interface or by contacting [email protected].
API Developer Data Management. API Developers can access, retrieve, and delete data associated with their API account through API endpoints and the Developer dashboard at www.jenova.ai/platform. API Developers are responsible for implementing data deletion, access, and management functionality in their applications to respond to End User requests. Developers can delete conversation history, uploaded files, agent configurations, and other data associated with their API Keys.
End User Data Requests. If you are an End User of an application built by an API Developer using our API Services, and you wish to access, correct, or delete your personal information, please contact the API Developer whose application you are using. The API Developer is responsible for responding to your data requests. If you are unable to reach the API Developer, you may contact us at [email protected], and we will attempt to direct you to the appropriate Developer or, where required by law and technically feasible, assist with your request.
Managing Your YouTube API Data. You can manage your data related to YouTube API Services as follows:
Access Chat History: View your stored chat history, including search queries for YouTube API Services, through your account.
Delete Chat History: Request the deletion of specific entries or your entire chat history by contacting us at [email protected].
Expiration of YouTube Sources: YouTube links and related source references returned by the YouTube API and included in chat history may become unavailable, expire, be refreshed, or be removed from the product interface after 30 days. Users cannot request these links or source references to remain available in the product interface longer than this period.
Revoke Access: Revoke Jenova's access to your Google account at any time by visiting Google's security settings page.
Data Export and Portability. Except as expressly required by applicable United States law (such as the verified right of access under the California Consumer Privacy Act), Azeroth does not provide data export, bulk download, data portability, or data migration tools or functionality. You do not have a contractual right to download, extract, or receive copies of your data (including Prompts, Outputs, chat history, uploaded files, Global Memory entries, Agent configurations, or any other data associated with your account) in any particular format or through any self-service mechanism. You are solely responsible for maintaining your own independent copies of any data, content, or Outputs that are important to you. We recommend that you save copies of Outputs or content that you wish to retain, as we may delete data in accordance with our data retention policies.
Azeroth may, at its sole discretion, offer limited data access or export features from time to time, but such features may be modified, limited, or discontinued at any time without notice, and their availability does not create a contractual right to data export or portability.
We are not obligated to provide data access, portability, or download functionality beyond the rights and mechanisms required by applicable law.
Please note that revoking access may limit your ability to use features of our Services that rely on YouTube API Services. Deleting chat history may also affect your access to past interactions and personalized features.
Data Retention
We retain personal information for as long as necessary to fulfill the purposes for which it was collected, to provide our Services, to comply with legal obligations, to resolve disputes, and to enforce our agreements. Custom system instructions and knowledge bases for Agents are retained for as long as the agent exists, or until deleted by the user. User chat history and uploaded files are retained for as long as necessary to provide the Services, or until deleted by the user.
API Services Data Retention. For data submitted through the API Services: (a) conversation history, uploaded files, and other End User data are retained for as long as necessary to provide the API Services to the API Developer, or until deleted by the API Developer through API endpoints; (b) API usage logs and metadata are retained for billing, security, fraud prevention, and compliance purposes for a commercially reasonable period; (c) agent configurations and system instructions are retained for as long as the agent exists, or until deleted by the API Developer; and (d) API Developers are responsible for implementing appropriate data retention and deletion policies for their End Users' data in compliance with applicable law.
Global Memory Retention and Deletion. Global Memory entries persist until you modify or delete them, or until your account is closed. When you delete a Global Memory entry, it is removed from active systems within a commercially reasonable period. Residual copies may remain in system backups for a limited time consistent with our backup retention schedules, after which they are purged in the normal course of business. We may retain limited logs (e.g., timestamps of deletion) for security and audit purposes.
Inactive Account Deletion. We may deactivate or delete free (non-subscriber) accounts that have been inactive for an extended period. Generally, free accounts that have not been used for 90 days or more may be subject to deletion. The following accounts are not subject to automatic inactive account deletion: (a) accounts with an active paid subscription, while the subscription remains active; and (b) accounts with an activated API Developer account at www.jenova.ai/platform. When an inactive account is deleted, associated personal information and data (including chat history, uploaded files, Global Memory entries, Agent data, API Keys, and account information) will be deleted in accordance with our standard data deletion procedures. We may provide notice before deleting an inactive account, but are not obligated to do so. You are responsible for regularly accessing your account if you wish to maintain it and the associated data.
Children's Privacy
Our Services are not intended for individuals under the age of 18. We do not knowingly collect personal information from individuals under 18. If we become aware that we have collected personal information from an individual under 18, we will take steps to delete such information. These steps may include: (a) immediate account suspension or termination; (b) deletion of all personal information and content associated with the account; (c) reporting to the National Center for Missing & Exploited Children (NCMEC) if the minor was exposed to or involved in prohibited content, in compliance with 18 U.S.C. § 2258A; (d) notification of parents or legal guardians where required by applicable law and where contact information is available; (e) preservation of information required by law enforcement or as necessary for legal compliance; and (f) cooperation with law enforcement investigations. API Developers represent and warrant that they do not knowingly use the API Services to collect personal information from individuals under 18, and that they comply with all applicable laws protecting minors' privacy, including the Children's Online Privacy Protection Act (COPPA) where applicable.
API Developers represent and warrant that they do not knowingly allow individuals under 18 to use their applications built with the API Services. API Developers must implement appropriate age screening measures and must immediately notify Azeroth upon learning that a minor has accessed their application through the API Services.
Your California Privacy Rights
If you are a California resident, you may have certain rights under the California Consumer Privacy Act (CCPA). These rights may include the right to know what personal information we collect, use, disclose, and sell about you, the right to request deletion of your personal information, and the right to opt-out of the sale of your personal information. To exercise these rights, please contact us at [email protected]. If you are an End User of an API Developer's application and are a California resident, please contact the API Developer to exercise your CCPA rights, as the API Developer is the business that determines how your personal information is collected and used.
Updates to Our Privacy Policy
We may update this Privacy Policy from time to time in order to provide clarification or notice of changes to our practices. If we make changes, we will revise the Effective Date at the top of this Privacy Policy. Changes to this Privacy Policy will be effective once they are posted unless otherwise indicated. We may choose to notify you by email to the email address in our records. For API Developers, we may also provide notice of material changes through the www.jenova.ai/platform dashboard or via email to the email address associated with your API Developer account.
Contact Information
If you have any questions or concerns about this Privacy Policy or the privacy practices at Azeroth Inc., please contact us by emailing us at [email protected]. If you are an End User of an API Developer's application, please contact the API Developer directly for questions about your personal information. The API Developer's contact information should be available in their application or privacy policy.