Privacy Policy

Introduction

Jensi ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use Jensi, our AI tool that turns requests from email, Slack, Teams and meetings into suggested tasks that people review and approve, and related services.

Information We Collect

Information You Provide

• Account Information: Name, email address, password, and organization details when you create an account.
• Project Data: Tasks, comments, files, and other content you create within Jensi.
• Communications: Messages you send through our platform, including emails synced from Gmail or Outlook for task creation, meeting recap and summary emails received in connected inboxes (for example from Fireflies, Zoom, or Gemini), and content from connected integrations such as Slack and Microsoft Teams.
• Meeting Assistant Data: When you enable the meeting assistant, we process meeting recordings, transcripts, speaker labels, attendee metadata, and meeting titles and times linked to scheduled events.
• Integration Data: Read-only Google Calendar event metadata (titles, times, attendees, and video meeting links) when you connect Google.
• Payment Information: Billing details processed through our secure payment provider (Stripe).

Information Collected Automatically

• Usage Data: How you interact with Jensi, including features used, pages visited, and actions taken.
• Device Information: Browser type, operating system, and device identifiers.
• Log Data: IP address, access times, and referring URLs.

How We Use Your Information

We use the information we collect to:

• Provide, maintain, and improve our services
• Process transactions and send related information
• Send administrative communications about your account
• Respond to your comments, questions, and support requests
• Improve the quality of our AI features. Authorized Jensi staff may review a limited sample of AI inputs and outputs for this, under strict access controls
• Monitor and analyze trends, usage, and activities
• Detect, investigate, and prevent fraudulent or unauthorized activities

Automated Features

Jensi uses automated processing to provide task creation, status updates, and project insights. When using these features:

• Your content is processed to provide automated task extraction and suggestions
• When enabled, the meeting assistant may join scheduled video calls you opt into, transcribe them, and propose tasks for your approval
• We store AI inputs and outputs, encrypted, to debug and improve the quality of these features
• We do not use your specific content to train general AI models
• Our AI provider (Amazon Web Services Bedrock) does not use your data to train its models
• You can opt out of specific AI features in your settings
• AI-generated content is clearly labeled within the platform

Google API Services

Jensi accesses Gmail (read-only), Google Calendar (read-only), and Google Drive (read-only) through Google's OAuth 2.0. Our use of data received from Google APIs is governed by the following practices:

• Email content is used to detect actionable work, including meeting recaps from third-party notetakers delivered to your inbox, and to propose tasks for approval within your organization.
• Calendar data is read only to show upcoming meetings, extract video meeting links, and attach schedule context to meeting-related activity. Jensi does not create, edit, or delete calendar events.
• Document content from Drive is used only when linked in emails you've received, to provide richer task context.
• OAuth credentials and synced Google data are encrypted at rest using symmetric encryption (Fernet).
• You can revoke Jensi's access to Google at any time in your Google Account settings; this revokes all access tokens and stops syncing.
• Jensi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Microsoft 365 Services

When you connect Microsoft 365, Jensi accesses Outlook mail (read-only) and, for organization admins who connect Teams, Microsoft Teams channel content needed to extract and propose work. Our practices include:

• Email content is used to detect actionable work and propose tasks for approval within your organization.
• Teams messages and threads are used only for channels you configure for monitoring, to propose tasks and post approval cards.
• OAuth credentials and synced Microsoft data are encrypted at rest using symmetric encryption (Fernet).
• You can revoke Jensi's access to Microsoft 365 at any time in your Microsoft account settings, and disconnect Teams at any time from Settings → Integrations; this revokes access tokens and stops syncing.

Atlassian Jira

When an organization connects Jira through Atlassian OAuth, Jensi syncs work between Jira and Jensi projects. Our practices include:

• What we access: Jira projects, issues, comments, and attachments that the connecting user can see. We also store the Atlassian account IDs, display names, and avatar URLs of Jira users who appear in synced issues and comments. Where Jira shares them, we store email addresses, and we use them only to match Jira people to workspace members.
• How we use it: To keep Jira and Jensi projects in sync in both directions, to show the Jira author on mirrored comments, and to match Jira people to workspace members. During project setup, the names and email addresses of unmatched Jira people may be sent to our AI provider (Amazon Web Services Bedrock) to suggest matches. These AI records are deleted within 4 days.
• Storage: OAuth credentials are encrypted at rest using symmetric encryption (Fernet). When Jensi posts a comment or an update to Jira, it shows the name of the Jensi author and can set the Jira assignee. We do not store Atlassian personal data in Jira entity properties.
• Personal data reporting: As Atlassian requires, we report the Atlassian account IDs we store to Atlassian at least once every 7 days. When Atlassian reports that an account is closed, we erase that person's account ID, avatar, and people mappings from Jensi, including history records, and we erase their name from the comments they wrote and from mentions that link to the account. When Atlassian reports that an account is updated, we refresh the name and avatar, or remove them if Jira no longer knows the account.
• Revoking access: When you unlink a project, we erase the Jira people data for that link. When you disconnect the Jira site, we erase this data for every link on the site, together with the connecting account ID. You can also revoke Jensi's access at any time in your Atlassian account settings, under Connected apps.

Information Sharing

We may share your information in the following circumstances:

• With Your Consent: When you explicitly authorize sharing
• Team Members: Project data is shared with members of your organization as configured
• Service Providers: With vendors who assist in providing our services, including hosting, analytics, payment processing (Stripe), AI processing (Amazon Web Services Bedrock), product analytics (PostHog, usage metadata only), website analytics (Google Analytics, see below), meeting assistant services (Nylas), recording storage (Amazon Web Services S3), and work management sync (Atlassian Jira)
• Legal Requirements: When required by law or to protect our rights
• Business Transfers: In connection with a merger, acquisition, or sale of assets

Cookies and Analytics

On our public website and on the signup and login pages, we use Google Analytics 4, a service from Google LLC, to learn how visitors find Jensi and which pages help them decide to sign up. We do not use it inside the Jensi app after you sign in, and we do not use it for advertising.

• What it collects: pages you view, the site or campaign that sent you (for example a UTM link), approximate location from your IP address, device and browser type, and a few actions such as clicking a signup button or signing up. Google Signals and ad personalization are turned off.
• Cookies: _ga and _ga_<ID>, which tell visits apart. They last up to 2 years unless you clear them.
• Retention: Google Analytics keeps event data for 14 months, then deletes it.
• Your choice: If you visit from the European Union, the European Economic Area, the United Kingdom or Switzerland, Google Analytics stays off until you select Accept in the cookie banner. To change your choice, use the Cookie settings link in the site footer. Anyone can also block Google Analytics with the Google Analytics opt-out browser add-on or by blocking cookies in the browser.

We also set two small items that do not track you: a jensi_region cookie (1 day) that records whether the cookie banner applies in your country, and a browser storage entry that remembers your banner choice. If you arrive from a campaign link, your browser also stores that link's campaign tags (such as utm_source) for up to 90 days, so we can tell which campaign led to a signup. Where the cookie banner applies, this happens only after you select Accept. Google processes analytics data under its privacy policy.

Data Security

We implement industry-standard security measures to protect your data, including:

• Encryption in transit (TLS 1.3) and at rest (AES-256 disk encryption, plus field-level encryption for sensitive content)
• Regular security audits and penetration testing
• Access controls and authentication requirements
• Only a small number of authorized Jensi staff can access customer content, for support and AI quality review
• Secure data centers operated by cloud infrastructure providers with SOC 2 Type II certification

For independent assessments (including Google CASA Tier 2) and more detail on how we protect customer data, see our Security page.

Data Retention

We retain your information for as long as your account is active or as needed to provide services.

When a workspace owner deletes a workspace, access ends immediately and we permanently erase the workspace's data, including its emails, tasks, projects, files, connected-account data and AI inputs and outputs. This cannot be undone. We keep one minimal deletion record: the workspace name and identifier, who deleted it, when, and the number of items erased. We keep it to prove the deletion and to handle billing and legal questions. Your subscription is cancelled when you delete a workspace, and unused time and credits are not refunded. Database backups can still hold the data for up to 14 days, then they are overwritten.

AI inputs and outputs are deleted after 90 days. Samples flagged during AI quality review are kept until they are reviewed and removed.

Your Rights

Depending on your location, you may have the right to:

• Access the personal information we hold about you
• Correct inaccurate information
• Delete your personal information
• Export your data in a portable format
• Opt out of certain data processing activities
• Withdraw consent where processing is based on consent

International Transfers

Your information may be transferred to and processed in countries other than your own. We ensure appropriate safeguards are in place, including Standard Contractual Clauses where required.

Children's Privacy

Jensi is not intended for children under 16 years of age. We do not knowingly collect personal information from children under 16.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by email or through a notice on our platform.

Contact Us

If you have questions about this Privacy Policy or our privacy practices, please contact us at:

• Email: hello@jensi.io