Privacy Policy
What we collect when you create an account on pulseapp.mldeep.io and use the Pulse demo, who it reaches, how long we keep it, and how to have it removed.
Last updated
1. Who is responsible
MLDeep Systems (OPC) Private Limited (“MLDeep”, “we”), registered at E1203, Sukhwani Skylines, Bhumkar Das Ghugre Rd, Wakad, Pune 411057, decides how the data described here is used. For anything in this policy, including a request to see, correct or delete your data, write to info@mldeep.io.
Our Grievance Officer is Anmol Parimoo. You can reach them at info@mldeep.io or by post at the address above.
2. What we collect
Your account. When you sign up, our sign-in provider, Clerk, records your email address, your password (which we never see), your name if you give it, and the time you accepted these terms and this policy. If you belong to an organisation in your account, we read its name to pre-fill your company.
The onboarding form. Before you reach the demo, we ask for your role, full name, phone number, city, country, company, company size and industry. Your country is pre-filled from the approximate location of your connection, and you can change it. We store your answers with your account, along with a record of the consent you gave: its exact wording, its version and when you gave it. While you fill the form in, a draft is saved with your account and in your browser, so you can pick up where you left off.
Requests you send us. If you ask about a plan, we keep what you chose (tier, modules, number of projects, billing) and any note you add, with your account. PostHog records the plans you build and the plan you ask for, and, for a request, what that plan costs at our list price, whether or not the page showed it to you.
How you use the site and the demo. We measure this from your first visit, including the sign-up and onboarding pages. Our analytics provider, PostHog, records the pages you view, where you click, the actions you take, how fast pages load and any errors you run into, and links them to your account, your email address and your company once you sign in, including what you did before signing in. It also records how you move through pages, with what you type into form fields, and the lines that show your name and email, masked. Your name, phone number and city are never sent to PostHog.
Questions you ask Pulse. When you type a question into Ask, we send Google’s Vertex AI, in its Mumbai region, your question, the page and view you asked from, and the names of the figures, filters and periods Pulse can use, so it can work out which figure you mean. To write the one-line summary of a trend, we also send that answer’s figures. Google does not use any of it to train its models. In its answer cache, Pulse keeps the plan it made and the answer, but not your question’s text, until its server restarts, so the same question is answered faster.
Your Ask conversations. When you are signed in, we keep each question you ask, the page you asked it on, the plan Pulse made and the answer it showed you, as a conversation under your account, in Supabase in Mumbai. In the product, only you see your conversations. When you ask a follow-up, we also send Vertex AI the earlier questions of that conversation and the plans Pulse made for them, never their figures. Every conversation is kept for audit, including any you delete: deleting one takes it off your list, and the people who operate the service can still read it.
Your daily allowance. A count of the questions your account asked Pulse today, kept against your account ID for 7 days, to enforce the daily allowance. It is stored in Supabase in Mumbai and holds no question text.
Alert discussions. When your organisation uses alert threads, we keep what you write and do on an alert: your comments and replies (and the earlier wording of any comment you edit), the emoji reactions you add to a comment and each time you add or remove one, when you acknowledge, assign, start or close an alert and any note you add, who in your organisation is assigned to it, which part of the alert a comment was started from, and which comment the assignee or owner marked as the team’s conclusion, by whom and when. Each entry carries your name and account ID, and everyone in your organisation can see it. We also record which alert pages you open and when, to show you what is unread and to keep a record your organisation’s admins can review.
Alert discussions and AI. Nothing from an alert’s discussion is sent to an AI model: not its comments or replies, not the names of the people who wrote them or moved the alert, and not the notes left with status changes. The team conclusion shown on an alert is a comment a person marked, in their own words. Summaries an earlier version of Pulse wrote from a discussion stay stored with it and are no longer shown.
Your organisation’s workspace. When we run Vantresi on your organisation’s own data, we store the figures we work out from it (totals, rates and the alerts they raise) with Supabase, our database processor. The people and customers behind those figures appear in it only as hashed or masked keys, never by name, email address or phone number. Only members of your organisation in Clerk, signed in with it as their active organisation, can open it, and we use that membership for nothing else. When a member asks Pulse or Veyra a question on your organisation’s workspace, it is answered from those stored figures, and we send Gemini on Vertex AI, in our own Google Cloud project in its Mumbai region, the question, the page it was asked from, the names of the figures, filters and periods it can use with the values it can filter by (people only as masked keys), and, to write a trend’s one-line summary, that answer’s figures. For a follow-up, we also send the earlier questions of that conversation and the plans Pulse made for them, never their figures. Each such question counts against that member’s daily allowance, and Google does not use any of it to train its models. We do nothing else with the stored figures. Comments, assignees and status on your organisation’s workspace alerts are alert discussions, kept as described above and stored per organisation: access to them is limited to your organisation’s members and the people who operate the service. PostHog measures your use of the workspace’s alert pages as it does every other page you open signed in, linked to your account ID and email address. When a member pauses or resumes one of your organisation’s agents, we keep their name, account ID, the time and the reason they gave with your workspace’s figures, so the pause is on record for your organisation. When a member downloads or emails the workspace’s Summary as a PDF or Excel file, we read their name and email address from Clerk and print them, with the date and time, on that file, so a copy shows who took it; our log of the download keeps their account ID, not their name or email address. When an admin publishes your organisation’s monthly workbook or rolls back to an earlier one, we keep their name, email address, account ID and the time with your workspace’s figures, and show their name in its list of loads, so each change is on record. The workbook itself is read to work out the figures and is not kept; we keep its file name and a fingerprint of its contents, to recognise the same file if it is sent again.
Emails you ask us to send. If you send a brief to someone from the demo, we use the address you enter to send that one email, and do not keep it.
Technical data. Our host, Vercel, processes the technical details of each request (such as your IP address and browser) to serve the site and keep it secure. Our error logs can include your account ID, but not your contact details.
3. What we use it for
- to create and secure your account, and let you sign in;
- to show you the demo in the version that fits your role and industry;
- to answer the questions you ask Pulse, with AI;
- to contact you about Pulse using the details you gave, as the consent you ticked says;
- to let your organisation discuss and track alerts, and keep a tamper-evident record of who did what;
- to show your organisation’s figures and alerts to its members, and no one else;
- to understand how the demo is used, so we can improve it;
- to answer requests you send us, and to keep the service secure.
4. Who receives it
We do not sell your data, and we do not share it with anyone for their own advertising. It reaches only the services that run Pulse for us, each for the purpose below:
- Clerk: your account, sign-in and onboarding answers.
- PostHog: usage analytics and session recordings.
- Brevo: sends your welcome email, and the email that tells our team you have signed up or sent a request, which includes the details you gave.
- Vercel: hosts the site.
- Supabase: stores alert discussions and their history, in its Mumbai region. It also stores your organisation’s workspace figures, your Ask conversations and the count behind your daily question allowance.
- Google Cloud (Vertex AI): works out which figure a question you ask Pulse is about, and writes trend summaries, in its Mumbai region, without using any of it to train its models.
Apart from alert discussions in Supabase and Google Cloud’s Vertex AI, both in Mumbai, these services may process data outside India, including in the United States. We may also disclose data where the law requires it.
5. Cookies and browser storage
- Clerk sets the cookies that keep you signed in.
pulse_onboardedandpulse_guidedcarry you from the onboarding form into the demo. Each lasts ten minutes.pulse_org_checkedholds your account ID for 12 hours, to record that you belong to no organisation with its own workspace, so you are not asked again on every page.pulse-alert-panelremembers whether you keep an alert’s discussion panel open. It holdsopenorclosedand nothing else, and lasts a year.- PostHog stores an identifier in a cookie, shared across mldeep.io sites, and in your browser’s local storage.
- Your browser’s storage also holds the onboarding draft and a few display preferences. They stay on your device, and clearing your browser’s site data removes them.
6. Withdrawing consent
The box you tick on the onboarding form is your consent to be contacted about Pulse. You can withdraw it, or ask us to stop measuring your use of the site and delete what analytics has recorded about you, at any time by writing to info@mldeep.io. Withdrawing does not affect what was done before.
7. How long we keep it
We keep your account and onboarding details while your account is open. When you ask us to delete your data, we delete your account, your onboarding answers and requests, and your analytics profile, except where the law requires us to keep something.
Alert discussions and their history are your organisation’s record. We keep them while your organisation uses Pulse, and they cannot be edited after the fact, so your name stays on what you wrote or did there. The record of which alert pages you opened is deleted after the period your organisation’s admins choose, one year unless they change it.
Your organisation’s workspace figures are kept while your organisation uses Vantresi, and deleted on request.
Your Ask conversations are kept as a record of what Pulse answered, including those you delete from your list. If you ask us to erase your data, we go through that record with you.
8. Your rights
Under India’s Digital Personal Data Protection Act, 2023, you can ask us for a summary of the data we hold about you, have it corrected or completed, have it erased, nominate someone to exercise these rights for you, and have a grievance answered. Write to info@mldeep.io. If you are not satisfied with our answer, you can complain to the Data Protection Board of India.
9. Children
Pulse is a business product, and accounts are for people aged 18 or over.
10. Changes to this policy
The date at the top says when this policy last changed. If a change affects how we use data you have already given us, we will tell you before it takes effect. The Terms of Service refer to this policy.