Privacy Policy.

1. SCOPE AND ROLES

This Policy applies to personal information Jazbic processes in connection with the Services. Depending on the context, Jazbic may act in different privacy roles.

Jazbic as controller/business. For information used to operate our own business, such as account administration, security, support, legal compliance, service operations, and communications, Jazbic generally determines the purposes and means of processing.

Jazbic as processor/service provider. Business customers may use Jazbic to process information about their customers, prospects, contacts, opportunities, employees, vendors, and other business relationships. Where a business customer determines why and how that information is processed and applicable law recognizes a controller/processor or business/service-provider distinction, Jazbic generally processes that information on the customer's behalf and according to the customer's documented instructions, this Privacy Policy, our Terms of Service, and any applicable Data Processing Addendum.

If your information was entered into Jazbic by one of our business customers rather than directly by you, that customer may be the organization primarily responsible for responding to your privacy request. We may direct you to that customer or assist the customer as required by law.

2. INFORMATION WE COLLECT

2.1 Account and profile information

Name, work email address, company or organization, role, and other profile information you choose to provide.

Account identifiers, authentication status, login-related records, and security information needed to create and protect your account.

Preferences, settings, and information you choose to place in User Memory, Working Context, Company Memory, Customer Memory, or similar product features.

Passwords and authentication. For email-and-password accounts, Jazbic processes the password for authentication and stores a one-way password hash rather than the plaintext password. Jazbic also uses Firebase Authentication to support federated Google and Microsoft sign-in. Authentication credentials are used for account access and security and are not used for advertising or AI-generated sales assistance.

2.2 Customer, prospect, opportunity, and work information

Customer and prospect names, company names, business contact information, job titles, roles, and relationship information.

Opportunity and deal information, including opportunity fields, MEDDPICC-related information, deal health or assessment information, risks, next steps, commercial context, and other information a user chooses to record.

Notes, account history, customer context, prompts, chat messages, working context, saved prompts, and other information entered into the Services.

Files, screenshots, images, audio or voice input, transcripts, and other content that users upload or provide for analysis.

AI-generated summaries, analyses, recommendations, drafts, classifications, extracted information, and other output generated from user-provided or connected information.

2.3 Email and calendar information

If you choose to connect a supported Google or Microsoft account, Jazbic may access email and calendar information that you authorize us to access. The data accessed depends on the provider, the permissions you grant, and the feature you request.

Email content and metadata, which may include message bodies, subject lines, sender and recipient information, timestamps, thread information, and other message metadata needed to provide email-related features.

Calendar information, which may include event titles, dates and times, attendees, meeting details, and other event information needed to provide calendar-related context.

OAuth access tokens, refresh tokens, account identifiers, and related authorization data needed to maintain an authorized connection.

Jazbic does not currently persistently store Gmail attachments as part of its Gmail indexing functionality. If that practice changes, we will update this Policy before or when the change becomes applicable.

2.4 Information collected automatically

Internet Protocol (IP) address and network information.

Browser type, operating system, device type, language, referring URLs, and similar technical information.

Usage and diagnostic information, such as login timestamps, pages and features used, searches or actions performed, error logs, crash information, performance data, and system events.

On jazbic.com, after you consent to Analytics cookies, Google Analytics may collect page views, page URLs, referring URLs, interaction or event data, browser and device information, language, screen resolution, and a pseudonymous client identifier. Google may process network information such as an IP address in connection with Analytics; Google states that Google Analytics 4 does not log or store IP addresses.

Jazbic does not currently request precise GPS location or browser geolocation for ordinary use of the Services.

2.5 Support, security, and communications information

We collect information you provide when you contact support, report a problem, request deletion or access, communicate with us about security, participate in a product discussion, or otherwise communicate with Jazbic. We may also generate technical records related to authentication, rate limiting, abuse prevention, security events, and troubleshooting.

3. SENSITIVE AND REGULATED INFORMATION

Depending on jurisdiction and context, certain information processed through Jazbic may be considered sensitive personal information. This can include account login information and the contents of private email communications. Users may also choose to submit confidential business information or information about third parties.

Jazbic is not designed as a system for storing or processing highly regulated data such as payment-card numbers, Social Security numbers, government identification numbers, protected health information subject to HIPAA, biometric identifiers used to identify a person, or other specially regulated information unless Jazbic expressly agrees in writing to support that use. Please do not submit such information unless you have confirmed that the intended use is supported and lawful.

Jazbic does not use voice, images, or other uploaded content to create biometric identifiers or biometric templates for identity recognition.

4. SOURCES OF INFORMATION

We obtain personal information from the following sources:

Directly from users and business customers when they create accounts, enter data, upload content, configure memories or workspaces, or communicate with us.

From connected services authorized by the user, including Google and Microsoft email and calendar services.

From service providers that support authentication, AI processing, security, hosting, email delivery, abuse prevention, website analytics, and similar operations.

Automatically from browsers, devices, servers, and application activity when users interact with the Services.

From other users or business customers when they enter business contact or relationship information about customers, prospects, colleagues, vendors, or other individuals.

We do not currently purchase consumer profiles from data brokers for targeted advertising, and we do not use connected Google Workspace data for advertising or data brokerage.

5. HOW WE USE INFORMATION

We use personal information only for purposes that are reasonably related to operating, securing, supporting, and improving the Services or otherwise described in this Policy. These purposes include:

Creating, authenticating, maintaining, and securing user accounts.

Providing customer workspaces, notes, memories, opportunity management, context building, and other platform functionality.

Providing AI-generated summaries, analysis, recommendations, drafting assistance, search, classification, extraction, and other user-requested AI features.

Retrieving and processing authorized email and calendar information when needed for user-facing functionality.

Maintaining user-authorized third-party connections and managing OAuth tokens.

Responding to support inquiries and troubleshooting technical problems.

Detecting, investigating, preventing, and responding to fraud, abuse, unauthorized access, security incidents, and violations of our Terms.

Monitoring reliability, diagnosing errors, measuring product performance, and understanding usage trends so we can maintain and improve the Services.

Measuring traffic and interactions on jazbic.com through Google Analytics after Analytics-cookie consent, so we can understand website performance and improve the marketing site.

Sending administrative communications, including security notices and material changes to legal terms or policies.

Complying with applicable law, lawful process, contractual obligations, and enforcement of our rights.

We do not use Google Workspace data for targeted advertising, cross-context behavioral advertising, data brokerage, lending or creditworthiness decisions, or to create, train, or improve a general-purpose or shared AI model.

6. LEGAL BASES FOR PROCESSING

Where European Economic Area, United Kingdom, Swiss, or other law requires us to identify a legal basis, we rely on one or more of the following, depending on the processing activity:

Performance of a contract or steps requested before entering into a contract, including creating accounts and providing requested Services.

Legitimate interests, including securing the Services, preventing fraud and abuse, maintaining reliability, providing support, improving product functionality, and operating a business-to-business software service, where those interests are not overridden by applicable rights and interests.

Consent, including where a user authorizes a third-party integration or where consent is required for particular cookies or other processing.

Compliance with legal obligations, including tax, accounting, regulatory, law-enforcement, or litigation-related obligations.

Protection of vital interests where processing is genuinely necessary to protect life or physical safety.

Where we rely on consent, you may withdraw it at any time, although withdrawal does not affect processing already lawfully performed. Disconnecting a third-party account revokes future access through that connection but may not automatically delete all information previously processed or stored through the Services; deletion is addressed in Section 13.

7. AI FEATURES AND AI SERVICE PROVIDERS

Jazbic uses artificial intelligence and machine-learning services, including OpenAI, to provide AI-powered functionality. Depending on your request, relevant portions of your prompts, chat history, selected customer or opportunity context, notes, files, images, audio or voice input or transcripts, connected email or calendar information, and other content may be transmitted to an AI service provider so the provider can generate a response or otherwise perform the requested processing.

Jazbic does not use Customer Content, including connected email or calendar content, for the purpose of training or improving a general-purpose or shared artificial-intelligence model. We use business/API AI services under the provider terms and account settings applicable to Jazbic. We do not intentionally opt Customer Content into provider programs that use such content to train or improve general-purpose or shared models. If we ever offer an optional feature that materially changes this practice, we will provide a clear disclosure and obtain any consent required by law or applicable provider policy before enabling that use.

AI-generated output may contain errors, omissions, or inaccurate assumptions. Jazbic is designed as a productivity and decision-support tool. Users remain responsible for reviewing AI-generated output before relying on it, especially for legal, financial, employment, compliance, or other consequential decisions.

Some Jazbic AI features use persistent conversation state with OpenAI to maintain conversational continuity. OpenAI may retain conversation state, files, request data, or related service records according to the OpenAI service configuration, provider terms, and applicable data controls. Jazbic may also retain related prompts, chats, and AI outputs in its own systems. We use available provider deletion mechanisms as part of applicable account or privacy-deletion workflows, subject to technical, legal, backup, and provider limitations.

Jazbic does not use AI to make solely automated decisions about individuals that produce legal or similarly significant effects on those individuals as a product purpose. Deal assessments, MEDDPICC analysis, risk signals, and similar outputs are business-assistance features and should be reviewed by a human user.

8. GOOGLE WORKSPACE AND GOOGLE API DATA

Jazbic’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and applicable Google Workspace User Data and Developer Policy, including the Limited Use requirements.

8.1 Access and use

Jazbic requests Google permissions only for user-facing features that require the requested data.

Access begins only after the user authorizes the applicable Google connection and permissions.

Gmail data may be used for user-requested productivity features such as retrieving relevant messages, providing summaries, producing drafts, surfacing context, and other email-related assistance.

Google Calendar data may be retrieved to provide requested meeting and calendar context.

Google Workspace data is not used for advertising, data brokerage, creditworthiness, or other unrelated purposes.

8.2 Storage and retention of Google data

Jazbic may retrieve and persistently store selected Gmail messages associated with contacts or business context in a user's Jazbic workspace when that storage is needed to provide requested email-related and revenue-work functionality. Stored Gmail information may include message content, subject, sender and recipient information, dates, thread information, and related metadata.

Jazbic does not currently persistently download or store Gmail attachments as separate files as part of its Gmail synchronization functionality.

Google Calendar information is accessed when needed to provide calendar context and is not currently persistently stored by Jazbic as calendar-event records.

Disconnecting a Google account stops future API access through that connection and removes the active OAuth connection from Jazbic. Previously stored Gmail messages may remain as part of existing workspace context unless they are deleted through an available deletion process or a valid privacy request. We retain Google Workspace data only for permitted user-facing purposes and subject to applicable Google requirements.

OAuth access and refresh tokens are retained only while needed to maintain the authorized connection and are removed from active systems when the user disconnects the applicable Google account, subject to limited backup or security retention.

8.3 Transfers and human access

Relevant Google Workspace content may be transmitted to OpenAI or another approved service provider only when necessary to provide a user-facing feature requested by the user and subject to applicable provider terms and Limited Use restrictions.

Human access to Google Workspace content is restricted. Authorized Jazbic personnel may access specific content only where the user has affirmatively requested or authorized support involving that content, where reasonably necessary for security or abuse investigation, where data is appropriately aggregated or de-identified for internal operations, or where access is required by law.

8.4 Security and deletion

We use reasonable administrative, technical, and organizational safeguards designed to protect Google Workspace data, taking into account the nature of the information and the risks of the processing. These safeguards are reviewed as our systems and provider requirements evolve. Users may request deletion of Google-derived data by contacting privacy@jazbic.com. We will honor valid deletion requests in accordance with applicable law, applicable Google requirements, and our documented retention and backup processes.

9. MICROSOFT EMAIL AND CALENDAR DATA

If you connect Microsoft 365, Outlook, or another supported Microsoft account, Jazbic may access email and calendar information you authorize through Microsoft OAuth and APIs. Selected Microsoft email messages associated with contacts or business context in the user's Jazbic workspace may be persistently stored to provide email-related and revenue-work functionality. Microsoft Calendar information is accessed when needed for calendar context and is not currently persistently stored by Jazbic as calendar-event records. Authorization tokens are used to maintain the connection and are removed from active systems when the user disconnects the account. Disconnecting stops future API access but does not by itself necessarily erase Microsoft-derived email information previously stored in Jazbic. Previously stored Microsoft-derived content is subject to the deletion practices described in Section 13 and may be deleted through applicable account, workspace, or privacy-request workflows, subject to legal, security, backup, and provider limitations.

10. HOW WE DISCLOSE INFORMATION

We do not sell personal information for money. We disclose information only as described in this Policy, as requested or authorized by the user, or as required by law.

10.1 Service providers and subprocessors

Depending on the features used, our service providers may include:

OpenAI - AI processing for user-requested AI functionality.

Amazon Web Services (AWS) - cloud infrastructure, object storage, and backup storage, including Amazon S3.

Google and Firebase - Google OAuth, Gmail and Calendar APIs, federated authentication services, and Google reCAPTCHA for abuse prevention on authentication-related pages.

Google Analytics - website traffic and interaction measurement on jazbic.com after a visitor consents to Analytics cookies.

Microsoft - Microsoft OAuth and Microsoft 365 or Outlook email and calendar connectivity.

Email-delivery and other vendors that provide communications, security, or operational services reasonably necessary to operate Jazbic.

Our vendors may use subprocessors or process limited information for security, legal compliance, fraud prevention, and service administration under their applicable agreements. We do not represent that a vendor is prohibited from all independent processing where the vendor’s terms or applicable law permit it.

10.2 Legal and safety disclosures

We may disclose information if we reasonably believe disclosure is necessary to comply with law or valid legal process; respond to lawful requests by public authorities; protect the rights, property, or safety of Jazbic, our users, or others; investigate fraud, abuse, or security incidents; or establish, exercise, or defend legal claims.

10.3 Corporate transactions

Information may be disclosed or transferred in connection with a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar corporate transaction, subject to applicable law and, for Google Workspace data, any additional consent or provider-policy requirements that apply.

11. COOKIES AND SIMILAR TECHNOLOGIES

We use cookies, local storage, and similar technologies for authentication, session management, security, preferences, troubleshooting, basic site functionality, and, where you consent, website analytics. Additional details are provided in our Cookie Policy.

We use Google reCAPTCHA on certain authentication-related pages to help detect and prevent automated abuse. reCAPTCHA may process network, browser, device, and security-related signals, including IP address, under Google's applicable terms and privacy practices.

On jazbic.com only, we use Google Analytics to understand traffic and interactions with our marketing website. Google Analytics is not deployed in the Jazbic application at my.jazbic.com.

Google Analytics is configured to run only after a visitor consents to Analytics cookies. Google Signals, Google Analytics Advertising Features, and ads personalization are not enabled. We do not intentionally send email addresses, account identifiers, Customer Content, Gmail or Calendar content, or other Jazbic application content to Google Analytics.

Google Analytics may use first-party cookies including _ga and _ga_<container-id>. Google documents a default expiration of two years for these cookies. You can decline or withdraw consent for Analytics cookies through the cookie-consent controls we provide. See our Cookie Policy for additional details.

Where applicable law requires consent for non-essential cookies or similar technologies, we use an appropriate consent mechanism. Analytics cookies are not enabled on jazbic.com until you consent. You may later withdraw that consent through the cookie-preference controls we provide. Browser controls may also allow you to block or delete cookies, although doing so may affect functionality.

12. INTERNATIONAL DATA TRANSFERS

Jazbic is based in the United States, and our servers and operations are primarily located in the United States. Personal information may also be processed in countries where our service providers or their subprocessors operate.

Where applicable law requires a transfer mechanism for personal information transferred from the EEA, United Kingdom, Switzerland, or another jurisdiction, we will rely on an available lawful transfer mechanism, such as an adequacy decision, applicable data privacy framework, standard contractual clauses, contractual safeguards, or another legally recognized mechanism, as appropriate to the provider and transfer. We do not claim that a particular transfer mechanism applies to every transfer unless it is actually in place.

13. DATA RETENTION AND DELETION

We retain personal information only for as long as reasonably necessary for the purposes for which it was collected, to provide the Services, comply with legal obligations, resolve disputes, enforce agreements, protect security, and maintain appropriate business records. Retention varies by data category and context.

Account and profile information generally remains while an account is active and may be retained for a limited period afterward for closure, fraud prevention, legal, compliance, audit, or security purposes.

OAuth tokens are retained while the associated third-party connection remains authorized and are removed from active systems when the user disconnects the connection or the relevant account is deleted, subject to limited backup or security retention.

Connected email information may remain while needed to provide the applicable user-facing workspace functionality, subject to the provider-specific restrictions described above. Disconnecting an integration stops future provider access but does not necessarily delete email content already stored in the workspace. Calendar information is currently accessed on demand and is not persistently stored as calendar-event records.

Customer Content, notes, opportunities, memories, files, transcripts, and chat information may remain while the account or business relationship is active, unless deleted earlier by the user or customer, and may be deleted or de-identified after termination subject to backup, legal, and security requirements.

Usage, diagnostic, authentication, and security logs are retained for periods reasonably necessary for troubleshooting, fraud prevention, security monitoring, and operational purposes.

Google Analytics data is retained according to the settings of our Google Analytics property and Google's applicable retention rules. Google Analytics cookies may remain on a device for up to their configured expiration period unless they are deleted earlier. Withdrawing Analytics consent stops future Analytics-cookie use by Jazbic but does not retroactively delete information previously collected by Google Analytics.

Backups may temporarily retain deleted information until the applicable backup is overwritten, rotated, expired, or deleted in the ordinary course. Jazbic maintains database backups using AWS infrastructure, including Amazon S3, as part of its business-continuity practices.

To request deletion of personal information, email privacy@jazbic.com from the email address associated with your account or provide other information reasonably necessary to verify the request. Jazbic also provides in-product account or workspace deletion controls for applicable users. Deletion workflows remove applicable information from active systems, but the same information may remain temporarily in encrypted backups until those backups expire through normal rotation. Jazbic may retain limited audit information, such as an account email address or deletion record, where reasonably necessary to document the deletion request or comply with legal, security, fraud-prevention, dispute-resolution, or compliance obligations.

14. SECURITY

We maintain a risk-based information-security program with administrative, technical, and organizational safeguards designed to protect personal information against unauthorized access, use, disclosure, alteration, or loss. Safeguards are selected and maintained based on the nature of the Services, the sensitivity of the information, reasonably foreseeable risks, and the maturity of our systems.

Depending on the system and risk involved, safeguards may include encrypted network transport, authentication and authorization controls, multi-factor authentication for designated privileged accounts, restricted administrative access, credential and secrets-management controls, logging and monitoring, vulnerability and dependency-management practices, and backup and recovery controls. We use cloud infrastructure and storage services, including AWS and Amazon S3, for certain hosting, storage, or backup functions. The particular controls applied to a system may change as our architecture, providers, and risk profile evolve.

Access to production systems and administrative functions is limited to personnel or service accounts with a business need and is governed by access-control practices appropriate to the relevant system. We also maintain operational procedures intended to reduce the risk that secrets, authentication credentials, or other sensitive security information are unnecessarily exposed in logs or routine application output.

No security program can guarantee absolute security. Users are responsible for protecting their credentials, using appropriate organizational access controls, and notifying us promptly if they suspect unauthorized access.

15. BUSINESS CUSTOMERS AND CUSTOMER DATA

Business customers are responsible for determining whether they have the right and lawful basis to place third-party information into Jazbic, connect business email or calendar accounts, and instruct Jazbic to process that information. Business customers must provide legally required notices and obtain legally required permissions from their own contacts, employees, prospects, or customers.

Where Jazbic acts as a processor or service provider, we process Customer Data on the business customer's documented instructions, subject to this Privacy Policy, our Terms of Service, applicable law, and any applicable Data Processing Addendum. If a separate signed Data Processing Addendum conflicts with this Privacy Policy regarding processor obligations, the signed Data Processing Addendum will control for the processing it expressly governs.

16. YOUR PRIVACY RIGHTS

Depending on your location, our role, and applicable legal thresholds, you may have rights regarding personal information. These may include rights to:

Know or confirm whether we process your personal information.

Access personal information and obtain a copy.

Correct inaccurate personal information.

Delete personal information, subject to legal exceptions.

Obtain portable copies of certain information where applicable.

Object to or restrict certain processing where applicable.

Withdraw consent where processing is based on consent.

Opt out of certain sale, sharing, targeted advertising, or profiling practices where applicable.

Appeal a denial of a privacy-rights request where applicable.

Complain to an applicable data protection authority.

To exercise a privacy right, email privacy@jazbic.com. We may request information reasonably necessary to verify your identity, authority, and the scope of the request. Authorized agents may submit requests where permitted by law, subject to verification.

If we process information solely on behalf of a business customer, we may direct you to the customer or work with the customer to respond.

17. U.S. STATE PRIVACY DISCLOSURES

This section applies only to the extent a U.S. state comprehensive privacy law applies to Jazbic and to the relevant individual or processing activity. Nothing in this section is intended to state that Jazbic meets the applicability threshold of every state privacy law.

17.1 Categories of personal information

During the preceding 12 months, depending on product configuration and use, Jazbic may have collected or processed the following categories: identifiers; professional or employment-related information; commercial or business relationship information; Internet or other electronic network activity; account login information; contents of private communications; customer and prospect relationship information; and business assessments or inferences generated for user-facing revenue-work features.

Jazbic does not intentionally collect biometric identifiers for identification, precise GPS location for ordinary use, or sensitive personal information for the purpose of inferring personal characteristics.

17.2 Sale, sharing, and targeted advertising

Jazbic does not currently sell personal information for monetary consideration and does not currently share personal information for cross-context behavioral advertising or use personal information for targeted advertising as those terms are defined by applicable U.S. state privacy laws. If these practices change, we will update this Policy and provide any legally required notice and opt-out mechanism before or when the change becomes applicable.

17.3 Non-discrimination

Where required by law, we will not unlawfully discriminate against you for exercising an applicable privacy right.

18. CHILDREN AND MINORS

The Services are intended for business and professional users and are not directed to individuals under 18 years of age. You may not create or use a Jazbic account if you are under 18. If we learn that we collected personal information directly from a person under 18 in violation of this section, we will take reasonable steps to delete it.

19. CHANGES TO THIS POLICY

We may update this Privacy Policy from time to time to reflect changes to our Services, data-processing practices, legal requirements, or other operational needs. We will update the "Last updated" date when changes are made. If we make material changes, we will provide notice through the Services, by email, or by another appropriate method before the changes take effect where required by applicable law. If a change introduces processing for which applicable law requires consent, we will obtain the required consent before applying that processing to the affected personal information. We will not rely solely on a change to this Privacy Policy or continued use of the Services as consent where affirmative consent is required by applicable law.

20. CONTACT US

Jazbic LLC

Privacy: privacy@jazbic.com

22384 Pineapple Walk Dr

Boca Raton, FL 33433

United States

For general service or legal questions unrelated to privacy, contact admin@jazbic.com.