Privacy Policy

Last Updated: November 18, 2026

1. Information We Collect

Jenner Analytics Ltd. collects information to provide and improve our services. The types of information we collect include:

  • Personal Information: Name, email address, and contact details you provide when creating an account or contacting us
  • Technical Data: Your IP address, the browser and device details your browser sends with each request (its "user agent"), and how you interact with our Platform
  • API Keys: If you integrate third-party AI services into our web Platform, we securely store your API keys. (In the Jenner for macOS app from the Mac App Store, any keys you enter stay in your device's local Keychain and are never transmitted to us — see Section 10.)
  • Usage Data: Information about how you use the Platform, including features accessed and time spent
  • Usage Analytics: We collect language-feature telemetry: the names of procedures, statements, and options used (e.g., "PROC ARIMA", "ESTIMATE", "METHOD"). Each record is linked to the account that ran the code, so it is personal data rather than anonymous data. We never collect variable names, dataset names, data values, file paths, or code content. Usage Analytics is a setting for each organization; its starting state may depend on where the organization is located, and an organization administrator can switch it on or off at any time in Settings.
  • How You Heard About Us (optional): When you sign up or buy, we may ask "How did you hear about Jenner?" Answering is optional and is never required to sign up or buy. If you answer, we store your answer with your account, together with any text you type under "Other". We also send it to PostHog as part of your account's analytics profile, and show it to the Jenner team in an internal Slack notification of new sign-ups (see Section 3). Please do not put personal or sensitive information in the "Other" text box.
  • Workspace Activity Counts: Your web workspace counts how many notebook cells you run and how many of them end in an error. In Jenner Studio, it counts how many programs and tasks you run, how many of those runs end in an error, how many of them are runs of the built-in sample project, and how many imports and saves you make. In both, it counts how long you are active. Active time counts the time the tab is on screen within a minute of a key press, a pointer press or a cell run, or, in Jenner Studio, a run, an import or a save; we never record which key was pressed. These counts never carry the code, data, output or content of any cell. Jenner Studio's counts never carry code, data, output or file contents, or the name of any file or project. We also record when you were last active in Jenner Studio, and the dates you first reach a few milestones, such as your first cell run, your fifth Jenner Studio run or your first import. Only web workspaces count activity: the Jenner apps for Windows, Linux and macOS report no activity counts. We record any of this only while your help-email setting is on and your organization's Usage Analytics setting is on, so nothing is recorded for organizations where Usage Analytics is off; what was recorded before is kept as Section 6 describes. We use this information to choose which help emails to send you, and, if you have agreed to receive product news, which product-news emails to send you, and to see whether those emails help. We also use it to decide when to send account emails, such as trial-credit reminders, and how to word them, and to hold emails back while you are active in a workspace.
  • Email Records: Your choices about help emails and product news, when you made them, and how. If you sign up after October 13, 2026, we also record whether the product-news box was shown to you ticked or unticked, and the wording shown. We record which of our onboarding, help and product-news emails we have sent you, when, and in which language. If our email provider reports that an email to an address of yours bounced, was rejected, or was reported as spam, we record that address and the reason.
  • Sign-in Records: Each time someone tries to sign in to an account on our Platform, we record the email address entered; whether the attempt succeeded and, if not, why; how the sign-in was made (for example a password, a passkey, a two-factor code, a link sent to your email, or Google, GitHub or Microsoft); the IP address and user agent; and the country and time zone of that IP address, which we look up in a location database kept on our own servers, so your IP address is not sent to anyone for this. When you sign in or sign up — through our forms, an emailed sign-in link, or with Google, GitHub or Microsoft — we also record the languages and time zone your browser reports. We keep a record of a failed attempt even when no account exists for the email address entered.
  • Download and Licence Records: When you download Jenner or retrieve a License Key, we record which file or licence it was, when, and the IP address and user agent of the request. When an installed copy of Jenner uses its licence to check for or download an update, we record the licence serial number, the version or file involved, the IP address, and the client details it sends. We also use whether and when you downloaded the Jenner trial, whether you have started or completed a purchase, and whether a licence has been issued to your email address, to choose which help emails and, if you have agreed to receive product news, which product-news emails to send you.
  • IP Address Location: We look up the approximate location of an IP address (country, region, city, postcode, map coordinates and time zone) in a location database kept on our own servers, so the address is not sent to anyone for this. We do this to choose whether the product-news box on our sign-up form starts ticked; to save the country and time zone of the IP address with each sign-in record; and to show the approximate location of sign-ins and sessions on account security pages.
  • Records of Accepting Our Terms and Policies: When you accept or acknowledge one of our legal documents, we record which version, when, the email address on your account, your IP address and user agent, and the wording you agreed to. When you accept one of our terms, or acknowledge a policy at sign-up, we email you a copy of that record.
  • Feedback and Enquiries: When you send us feedback or a bug report, we record your message, the page you were on, your email address, IP address and user agent, and any screenshot or recording you attach. When you send us a sales enquiry, we record the details you enter, including any phone number and the time zone your browser reports, together with your IP address and user agent.
  • Platform Edition Usage Reports: If your organization uses Jenner inside its own Databricks workspace or Snowflake account (a "Platform Edition"), Jenner counts the people who use it there each month, so that the organization can be charged for each active user. To do this, it records to the minute when each person runs programs with Jenner there. It counts each person by a scrambled code made from their user name, never by their name or email address. On Databricks, the app sends us those counts and codes. On Snowflake, they stay in your organization's account, and Snowflake bills the charge. Section 11 describes who counts as active and what is kept where.

2. How We Use Your Information

We use the collected information to:

  • Provide, maintain, and improve our services
  • Process your requests and fulfill service obligations
  • Send important account notifications and updates, such as confirming your email address, confirming a purchase and how to set it up, and telling you about changes to this policy
  • Enforce our Terms of Use and other agreements
  • Analyze usage patterns to enhance user experience
  • Measure which advertising brought people to us
  • Understand which channels bring us customers, so we can decide where to spend on marketing
  • Enable interactive features and personalization
  • Respond to customer support inquiries
  • Remind organization owners when trial credits are running low or about to expire (switched off with Recharge Reminders on the Billing page)
  • Send you help emails about getting started and installing, chosen from how you have used the Platform (for example, whether you have run a notebook cell or a Jenner Studio program, or which product you downloaded)
  • Send you product news and use cases by email, if you have agreed to receive them, chosen from how you have used the Platform (for example, whether you have run notebook cells or Jenner Studio programs on several days, or downloaded the trial without buying a licence)
  • Keep accounts and the Platform secure: spot and investigate sign-in attempts that may not be yours, and show you, and the administrators of your organization, the sign-in history of an account
  • Deliver the software and licences you are entitled to, detect and respond to a desktop licence being used beyond what our Platform Terms allow, and answer licence and billing questions
  • Count the active users of a Platform Edition, charge the organization for them, warn its owners when it nears a limit they set, and check that its usage reporting is complete, as our Terms of Service allow (see Section 11)

Our legal bases under the UK GDPR and the EU GDPR:

  • To provide your account and the services you asked for, including account emails: this is necessary for our contract with you (Article 6(1)(b)).
  • To keep accounts and the Platform secure and to detect and respond to licences being used beyond what they were sold for, using Sign-in Records and Download and Licence Records: our legitimate interests (Article 6(1)(f)).
  • To learn which features are used, and to choose and send help emails: our legitimate interests in improving the Platform and helping you get started (Article 6(1)(f)). You can object as described in Section 4.
  • To send you product news, and to choose which to send from how you have used the Platform: your consent if you signed up from the European Economic Area or another country where the law requires consent; otherwise our legitimate interests (Article 6(1)(f)). Either way you can stop it at any time, free of charge.
  • To keep records of what you accepted: our legitimate interests in being able to show which terms applied to you (Article 6(1)(f)).
  • To count the active users of a Platform Edition, charge the organization for them and check its usage reporting: our legitimate interests in charging for the use of Jenner as agreed with the organization, and in checking that what is charged is right (Article 6(1)(f)).
  • Advertising measurement that uses cookies or identifiers: your consent through our cookie banner, as our Cookie Notice explains.

We also turn the information described in this policy into statistics: for example, how many sign-ins came from each country each day, or how many people downloaded each version. These statistics describe groups of at least 10 people and cannot be used to identify anyone, so we may keep them indefinitely. The information they are made from is kept only for the periods in Section 6.

3. Information Sharing and Disclosure

Jenner Analytics may disclose your information in the following circumstances:

  • Service Providers: We may share information with trusted third-party contractors and service providers who assist in operating our Platform
  • Legal Requirements: When required by law, regulation, legal process, or governmental request
  • With Your Consent: For purposes disclosed at the time of collection or with your explicit permission
  • Business Transfers: In connection with a merger, acquisition, or sale of assets
  • Your Organization: If you belong to an organization on our Platform and its owners or administrators turn on login statistics, they can see how many times members of that organization have signed in, how many attempts failed, and when each member last signed in, and they can delete those records for their organization. A sign-in you make without choosing a specific organization may count toward more than one organization you belong to. Separately, an owner or administrator of an organization you belong to can look up a member's individual sign-in attempts in more detail — including the IP address, approximate location and device for each one — for account-security purposes. The organization's audit log also records when you sign in through that organization's own sign-in page, and the method used.

We do not sell your personal information to third parties.

The service providers we use on our web Platform are listed below. This list does not apply to the Jenner for macOS app, whether from the Mac App Store or as a direct download, which embeds no third-party analytics or advertising — see Section 10.

  • PostHog (European Union) — product analytics. Usage events, page addresses (including, when you follow a link in one of our emails, which email it was), and, once you sign in, your account identifier, name, and organization. If you answer "How did you hear about Jenner?", PostHog also receives your answer, including any text you typed under "Other", as part of your account's analytics profile.
  • Honeybadger (United States) — error monitoring. Technical diagnostics when something goes wrong, including the page address and browser information.
  • LinkedIn (United States / Ireland) — advertising measurement, via the LinkedIn Insight Tag. Loads only if you accept cookies on our banner.
  • Google Ads (United States / Ireland) — advertising measurement, via the Google Ads tag. The tag loads on every page, but until you accept cookies on our banner it stores nothing and sends no identifier that could single you out. If you accept, it sends Google which of our ads your visit followed and, when you sign up, a one-way scrambled form of your email address so that sign-up can be matched to the ad. Google receives the scrambled value, never the address itself.
  • Paddle (United Kingdom) — payment processing and merchant of record for web subscriptions and desktop licences. Loads on our pricing and billing pages and whenever you start a purchase. On the pricing and billing pages it shows prices including the tax for your country, which Paddle works out from your IP address. Paddle is also merchant of record for Jenner on Databricks. For it, Paddle receives our identifiers for your organization and its workspaces, each workspace's Databricks number and, each month, the number of active users charged in each workspace, with the workspace's display name or number. It receives none of the scrambled codes described in Section 11.
  • YouTube (United States) — hosting for the videos on our website. Nothing is sent to YouTube or Google unless you click play.
  • Google reCAPTCHA (United States) — bot and abuse protection for our contact form and our legal document download. The script loads as soon as a page carrying one of them opens, for everyone who opens it and before you interact with anything, and sends Google your IP address, browser information, and interaction signals. Those pages are our home page, the product and service pages that end in a contact form, our legal documents page, and, if an email verification link has expired, the page offering to send a new one. It does not load on our other sign-up or sign-in pages.
  • Google, GitHub and Microsoft — sign-in providers. If you choose one of them to sign in, that provider authenticates you and gives us your name, email address and profile picture, which your browser then loads from that provider's servers.
  • Mailtrap — delivers the emails we send you: account emails, help emails and product news, and the Jenner on Databricks invitations and usage warnings described in Section 11. It receives your email address and each email's content, which can include your name, your organization's name, your credit balance and trial dates, details of a purchase, and, in the confirmation of a legal document you accepted, your IP address. It also delivers to our team the messages you send through our contact form. It tells us when an email to your address bounced, was rejected or was reported as spam, or when you unsubscribed through it.
  • Slack (United States) — internal notifications to our team when someone signs up, downloads Jenner, sends feedback or makes a sales enquiry. These include your name and email address and, for a sign-up notification, how you signed up and, if you gave one, your answer to "How did you hear about Jenner?", including any text you typed under "Other".
  • GitHub (United States) — our issue tracker. When you send feedback or a bug report, we copy it there, including your email address, the page you were on, and your browser's user agent.
  • Amazon Web Services and Hetzner — hosting and infrastructure for the Platform itself.

See our Cookie Notice for what each of these stores in your browser and how to control it.

4. Your Privacy Rights

You have the following rights regarding your personal data:

  • Access: Request access to the personal data we hold about you
  • Correction: Request correction of inaccurate or incomplete data
  • Erasure: Request deletion of your personal data
  • Object: Object to our use of your data where we rely on our legitimate interests (see Section 2), including Usage Analytics, Workspace Activity Counts and help emails. You can always object to direct marketing, and we will then stop.
  • Portability: Request transfer of your data to another service
  • Withdraw Consent: Withdraw previously given consent at any time, including consent to product news
  • Unsubscribe: Every help email and every product-news email has an unsubscribe link, and you can switch help emails and product news on or off on your profile page. Switching off help emails also stops Workspace Activity Counts. Organization owners can switch off trial-credit reminders with Recharge Reminders on the Billing page. Other account emails are not affected, because we need them to run your account.

You can download a copy of much of your account information from your account profile page, including your sign-in history, your email choices and the help emails we sent you, and your workspace activity counts. In most cases you can delete your account there too. If you sign in only with Google, GitHub or Microsoft, set a password first. If you own an organization that has other members, transfer ownership or remove them first. To exercise any of these rights, or to ask about sign-in attempts made with your email address when it had no account with us, please contact us at [email protected].

5. Data Security

We implement appropriate technical and organizational measures to protect your personal information:

  • Secure servers protected by firewalls
  • SSL/TLS encryption for data transmission
  • Encrypted storage of sensitive information including API keys
  • Regular security audits and updates
  • Access controls and authentication requirements

While we strive to protect your data, no method of transmission over the internet is 100% secure. We cannot guarantee absolute security.

6. Data Retention

We keep personal information only as long as we need it for the purposes in this policy. For the records below we have set fixed periods, and a job on our servers applies them automatically every day:

  • Sign-in Records: deleted 24 months after the attempt.
  • Failed sign-in attempts for an email address that has no account with us: deleted after 6 months.
  • Session records (the IP address and user agent of each browser you are signed in on): deleted 24 months after the session ends.
  • IP address locations: deleted 24 months after we look them up.
  • Download and Licence Records: the IP address and user or client agent are deleted after 24 months. The record of which file or licence was involved, and when, is kept in our audit trail, from which entries cannot be deleted; we remove the personal details from it as described in this section. We keep it for 6 years after the licence ends, because we need it to show which licences were issued and used.
  • Usage Analytics: deleted 24 months after it is collected. Organization administrators can request immediate deletion at any time via the Features settings page or by contacting [email protected].
  • Workspace Activity Counts: totals for each browser tab are deleted 2 days after the tab last reports, and daily totals 90 days after the day. We keep, while your account exists, the dates you first reached a few milestones and when you were last active in Jenner Studio.
  • Email Records and records of accepting our terms and policies: kept while your account exists.
  • Feedback, bug reports and sales enquiries: the IP address and user agent are deleted 24 months after you send them.
  • Licences you bought: the licensee name and email address on a licence are kept after you delete your account, for 6 years after the licence ends, because the licence was issued to that name.
  • Jenner on Databricks records: we erase the scrambled user codes from Databricks usage reports and progress snapshots 13 full months after the end of the month they cover; the counts and the bills are kept. We have not set a fixed period for the rest of these records: usage counts, bills, invitations, purchase requests, licence records and the email addresses described in Section 11. They belong to your organization's licence, so deleting your own account does not delete them.

When you delete your account, we delete straight away your sign-in records (including failed attempts made with your email address), session records, usage analytics, email records, workspace activity counts and records of accepting our terms and policies. We also remove your email address, account identifier, IP address and user agent from our audit trail. IP addresses and client details recorded when an installed copy of Jenner checks for or downloads updates carry no account identifier, so they are deleted on the 24-month schedule above.

Our own server logs, which can include IP addresses and email addresses, are kept for 30 days. Deleted data can remain in our database backups for up to 7 months, until those backups expire.

7. Children's Privacy

Our Platform is not intended for individuals under 18 years of age. We do not knowingly collect personal information from children. If we become aware that we have collected data from a child, we will promptly delete it.

8. International Data Transfers

Your information may be transferred to and processed in countries other than your country of residence. We are established in the United Kingdom, and our analytics data is held in the European Union. Some of the service providers listed in Section 3 — Honeybadger, LinkedIn, YouTube, Google Ads, Google reCAPTCHA, Slack, GitHub, and the sign-in providers — process data in the United States.

Where personal data leaves the UK or the European Economic Area, we rely on the transfer safeguards set out in each provider's data processing terms. You can ask us which safeguards apply to a particular provider by writing to [email protected].

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we make a material change, we will post the updated policy on our Platform, update the "Last Updated" date, show a notice about the change in the Platform until you dismiss it, and email account holders about significant changes. The updated policy applies from its "Last Updated" date. A change to this policy never counts as your consent to anything that needs your consent, such as product news; we ask you for that separately.

10. Jenner for macOS App

In addition to our web Platform, we offer Jenner for macOS, a desktop application distributed through the Mac App Store and also offered as a direct download (a .pkg installer) from our Platform. This section describes how that application handles your information. Where a point applies to only one of the two, it says so. The app is designed to keep your work on your own device:

  • On-Device Storage Only: The Mac App Store app stores a small amount of data locally on your device: a reference (security-scoped bookmark) to the workspace folder you grant it access to, and your subscription or trial status. This data is kept locally in the app's macOS Keychain and/or UserDefaults on your device and is not transmitted to us. We do not use this data to track you, and the app does not include any user-tracking functionality.
  • No Third-Party Analytics or Advertising: Neither the Mac App Store app nor the direct download embeds third-party analytics, advertising, or tracking SDKs.
  • No Activity Counts: Neither the Mac App Store app nor the direct download reports Workspace Activity Counts (see Section 1); only web workspaces count activity.
  • On-Device Processing: The app runs a local JupyterLab server on a loopback address (127.0.0.1) on your computer. Your notebooks and the data you analyze are processed locally on your device and are not transmitted to us. Some features you can choose to run will, however, send data to — or fetch data from — an external service that you select: for example, an AI/LLM procedure that sends your prompts or data to the third-party AI provider you configure, a cloud-storage procedure that reads or writes your own storage bucket, an HTTP request to a URL you specify, or a database or data-API connection you open. In each of these cases the data travels directly between your device and the service you chose, using any credentials you supply — it does not pass through us.
  • Your Credentials Stay on Your Device: Any API keys or service credentials you enter in the Mac App Store app (for example, an AI provider key or cloud-storage access keys) are stored locally in your device's macOS Keychain and are used only to connect you to the third-party service you chose. They are not transmitted to us.
  • Subscriptions via Apple: In the Mac App Store app, subscriptions are handled by Apple through StoreKit and the App Store. Apple processes your payment for the Mac App Store app; that app does not collect or store your payment information. Apple's handling of that data is governed by Apple's privacy policy.
  • The Direct Download: If you buy Jenner for macOS on our Platform instead, you buy a one-time licence, as for Windows and Linux. Paddle processes your payment as merchant of record (see Section 3). The .pkg installer and later versions of it are downloaded from our release server, and we keep the download and licence records described in Section 1. Your License Key is a file saved on your Mac. The app sends it to our release server only when it checks for or downloads an update, to show the copy is licensed (see Section 1).
  • Credentials in the Direct Download: The direct download does not store your API keys or service credentials. It reads them from environment variables or configuration files that you create on your Mac, uses them only to connect to the service you chose, and does not send them to us.

11. Jenner Platform Edition (Databricks and Snowflake)

A Platform Edition of Jenner runs inside a Databricks workspace or a Snowflake account that your organization holds under its own agreement with Databricks or Snowflake. Your organization decides who in that account may use Jenner, and is responsible for them under our Terms of Service. Your programs and data stay in that account. This section describes the information a Platform Edition keeps there to count active users, and the information it sends to us or to the platform.

  • Who Counts as Active: A person counts as active in a calendar month (in UTC) only when their first and last counted runs that month are more than 24 hours 6 minutes apart, so one day of use is never charged. A service identity counts as active from its first counted run in the month. A counted run is a program that Jenner carries out, whether it ends cleanly, with warnings or with an error in the program itself. These do not count: runs that Jenner refuses, for example because the user limit has been reached or no valid licence allows them; runs that fail on Jenner's side, such as a crash, a failure to start, a run that is stopped, a run that writes no log or a run whose outputs cannot be saved; cancelled runs; and opening or browsing the Jenner Studio app without running a program.
  • Scrambled Codes Instead of Names: Jenner turns the user name of each person it counts (on Databricks, usually their email address) into a scrambled code, using a secret key it creates in your organization's account. On Databricks, it keeps the key and, for each code, the first and last minute in each hour in which it had a counted run, in a storage volume in your organization's workspace. On Snowflake, it keeps the key and, for each code counted in a month, the minute of its first and last counted run that month, in the app's own tables in your organization's account. The key never leaves your organization's account, so we cannot tell from a code whose it is. Anyone who can read the key can check whether a code belongs to a particular person, so the codes are personal data, not anonymous data.
  • What Stays in Your Organization's Account: On Databricks, the app's People page shows administrators which people are active. It works this out inside the workspace, from the names and email addresses of the members of the Jenner access group, which it reads from Databricks, and the email addresses of people who have opened the app or been invited from it, which it keeps in the workspace. These names and addresses are not sent to us, except for invitations as described below. Once 13 full months have passed since a month ended, the app deletes its record of that month's runs, and its copy of that month's report, at its next regular maintenance run (the app runs one every hour while it is running, and a daily job runs one); it keeps the key. On Snowflake, the app keeps a record of each run in your organization's account, including the user name of the person who ran it, and saves each run's program, log and listing in a folder named after that user on your organization's own stage; the app does not delete those folders. Once 13 full months have passed since a month ended, the Snowflake app deletes its record of that month's runs and the codes it counted, when the next program run started with the app's run procedure finishes; it keeps the key.
  • What Jenner on Databricks Sends Us: When the app is installed, it sends us the workspace's number and address, its cloud provider and the app's version. Each month it sends us a usage report: the number of active people, active service identities and both together, the scrambled code of each one counted, the workspace's number and address, the licence serial number, the month, the version of the active-user rule, an identifier of the key (not the key itself) and the version of Jenner's software. During the month it sends the same figures so far, at most once an hour. These reports carry no names, email addresses, programs, data, table names or file paths. We use the codes to count a person once when they use Jenner in more than one of your organization's workspaces that share one key, and to check the counts.
  • Administrators' Actions on Databricks: When an administrator starts a purchase from the app, it sends us their email address, and we keep it with the request. When an administrator invites people from the app's People page, it sends us the email addresses they type, the administrator's email address and the app's web address. Owners and administrators of your organization can also invite people from their Jenner account. We email each invited person an invitation that names who invited them and the workspace, and we keep the invited address, who invited them, when, and whether the invitation was withdrawn. We use an invited address only to send that invitation and to show your organization its list of invitations.
  • Licence and Usage Warnings: The License Key that the app downloads names your organization and an owner's email address, and anyone who can use Jenner in the workspace can read it. Owners and administrators of your organization can set a limit on the number of active users in a workspace. Jenner then names an owner's email address, as the person to contact, to anyone in the workspace who is turned away because the limit has been reached. When the month's count reaches 80% of the limit, we email your organization's owners and billing contact with the count and the limit; the email names none of the people counted.
  • Billing: We bill Jenner on Databricks ourselves from the usage reports, through Paddle (see Section 3). Databricks does not bill it and sends us no billing information about it. On Snowflake, Snowflake bills the active-user charge on your organization's Snowflake invoice through the Snowflake Marketplace. For each active user each month, the app sends Snowflake one billing event, as soon as the user counts as active, carrying the month, the user's scrambled code, whether it is a person or a service identity, and the version of the active-user rule; it never carries a name. Snowflake's handling of that information is governed by Snowflake's privacy policy. The Snowflake app sends nothing to us directly.
  • Why We Use It: We use this information to charge your organization for its active users, to warn its owners when it nears its limit, and to check that its usage reporting is complete and accurate, as our Terms of Service allow. We do not use it for help emails, product news or advertising.

12. Contact Us

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

Jenner Analytics Ltd.
66 Paul Street, London, England, EC2A 4NA
Email: [email protected]