How we handle personal data

Privacy notice

Who is responsible for your data, what this website records and only with your consent, how and why we contact people we have not met, what happens when you book a call, and how to use your rights. It does not cover client work, which runs under the data agreement we sign with each client before work starts.

Applies to
This website, and the messages we send to people we have not met.
Last updated
29 October 2026

Who is responsible

The controller

Controller
The registered business is Jagatbhai Viplavbhai Patel, trading as Mirai360 (sole proprietorship, India). Shivang Patel leads every engagement.
Postal address
404 Galaxy Mall, Nehru Nagar, Ambawadi, Ahmedabad, Gujarat 380015, India
Who answers
Shivang Patel answers every question about this notice.
UK and EU representatives
Being appointed. We will name our UK representative (UK GDPR Article 27) and our EU representative (EU GDPR Article 27) here, with how to reach them, once they are appointed. Until then, contact us directly.
Client work
Not covered by this notice. It runs under the data agreement we sign with each client before work starts.

On this website

When you visit this website

Apart from our two free tools and the message form in the Get in touch section of our home page, this website has no forms. Elsewhere it does not ask for your name or email address, and it does not record what you type.

Nothing optional runs until you choose

The first time you visit, a banner asks whether we may use our analytics and the Meta Pixel. You choose each one separately: Accept all allows both, Decline all allows neither, and Manage choices lets you tick one and choose Save choices. Until you allow a tool, it does not run: nothing is stored in your browser for it, no record of your visit is sent to our analytics, and the Pixel's code is not fetched. If you choose Decline all, that stays true on every page you open. The site works the same either way.

Without asking, the site stores only your choice itself, in your browser's storage for this site, so that the banner does not ask again on every page.

What our hosting provider logs

With each request, our hosting provider logs your IP address (the number that identifies your internet connection), your browser type, the address you opened, including any reference code or campaign tags in it, and the time, as any web server does. Google Cloud keeps these logs for 30 days. Our lawful basis is legitimate interests: keeping the site running and secure.

What our analytics records, if you accept

Our own analytics service receives a short record each time you open a page, and each time you click a booking link, an email link or a link to another page on this site. It also receives one when you run the AI-readiness check, give your email address to see its full report, finish the bottleneck finder's questions, give your name and email to see its full result, or send a message from the Get in touch section of our home page. Each record holds:

  • a random visitor ID, which your browser keeps in its storage for this site until you clear it;
  • a random visit ID, which your browser keeps only until you close the tab;
  • the page address, including anything added to the end of it, the page title and the page you came from;
  • the campaign tags in the link you followed, if it had any, which say which ad, post or message sent you;
  • the reference code in the link you followed, if it came from one of our messages (see If we contacted you);
  • for a click, which link it was and where it leads;
  • for the AI-readiness check, which tool it was and your website's score;
  • for the bottleneck finder, which tool it was and, once you finish the questions, its result: whether AI fits the task and whether you are ready to start;
  • for a message, which of the form's four topics you chose;
  • the time, and whether this is your first visit.

Analytics records do not hold your answers to the bottleneck finder, the website address you checked, your message, your name or your email address. Those reach us only when you send them through the tool or the form, as described in When you use our free tools or contact form.

These IDs are kept in your browser's storage, not in cookies. Once our analytics has read the reference code and campaign tags, the page removes them from the address bar, before the Meta Pixel can load, so they are not sent to Meta or copied if you share the link.

Our analytics service is our own software. It runs in Google Cloud's Mumbai region, in India, on a server and database we also use for another product of ours, and each record is marked as coming from this site. The records are stored in MongoDB Atlas, a database service. Our analytics does not pass them to Meta or to any other advertiser.

Why, and on what basis

We use these records to count visits, see which pages people read, learn which links and messages bring people here, and count how often our free tools are used and what results they give. Our lawful basis is your consent, which you give for each tool on its own.

Other ways to switch it off

  • If your browser sends a Global Privacy Control or Do Not Track signal, we treat it as Decline all: neither our analytics nor the Pixel runs, and the banner does not appear.
  • Opening any page with ?analytics=off at the end of the address, for example mirai360.ai/?analytics=off, does the same, and your browser remembers it for this site. Open a page with ?analytics=on to remove it.
  • Turning off JavaScript for this site stops our analytics and the Meta Pixel altogether.

Advertising

The Meta Pixel, and your choice

Meta is the company behind Facebook and Instagram. The Pixel loads only after you allow Meta advertising in the banner, with Accept all or by ticking it under Manage choices. Until then, and if you do not allow it, its code is not fetched and nothing is sent to Meta.

What the Pixel sends, if you accept

The Pixel loads from connect.facebook.net and sends Meta a page view each time you open a page on this site.

The Pixel also sends Meta one event called Lead when you give us your email address in one of three places: when you give your name and email to see your full bottleneck finder result, when you ask to see the full AI-readiness report, and when you send a message from the Get in touch section of our home page. The Lead event names which of the three it was. It does not carry your name, your email address, your answers, your score, your topic or your message. Meta is not told when you run the AI-readiness check or finish the bottleneck finder without giving us your email address, and it is never told when you book a call.

With each page view and each Lead event, Meta receives your IP address, your browser details, the page address and the page you came from. Meta's automatic collection of button clicks and page details is switched off on this site. Meta can store its own identifiers in your browser, cookies called _fbp and _fbc, and can link the visit to a Facebook or Instagram account. The Pixel reports to a Meta advertising account we first set up for an earlier product of ours, which has closed.

Why, and on what basis

We use the Pixel to measure our ads and to show ads to people who have visited this site. Our lawful basis is your consent. We and Meta are joint controllers for collecting this data on our site and sending it to Meta. What Meta does with it after that is up to Meta, under its own privacy policy, at facebook.com/privacy/policy.

How to change your choice

Use Cookie choices at the foot of any page to open the banner again. If you later choose Decline all, our analytics sends no further records, a Pixel already loaded on the page is told to stop, and the page deletes the _fbp and _fbc cookies this site holds. To remove the visitor ID our analytics stored, clear this site's data in your browser. That also clears your choice, so the banner asks again.

You can also turn off ads based on your activity in your Meta account's ad preferences.

Free tools

When you use our free tools or contact form

Our two free tools, the AI-readiness check and the bottleneck finder, and the message form in the Get in touch section of our home page are the only places on this website where you type anything in.

The contact form

If you send a message, we receive what you chose it is about, your name, your work email address, your company if you give it, and your message.

The AI-readiness check

When you enter a website address, we send that address, and nothing else, to Ora (ora.ai), an independent service that checks how well AI agents can use a website. Ora visits the site's public pages to score them, and may keep the score, as it does for any site it checks. We keep the result on our server so that we can show you the full report.

The score appears straight away. To see the full report, you give us your email address, and your company name if you choose. We keep them with the website you checked, its score and the time. We show you the report and email it to the address you gave, as a PDF, from our Google Workspace mailbox. A copy of that email comes to us, so we know who asked.

The bottleneck finder

Your answers stay in your browser while you go through the questions, and your result is worked out there. Whether AI fits the task shows straight away, and nothing is sent to us for that. To see the rest of the result, you give us your name and your work email address, and your company if you choose. We then receive them with your answers and your result. Our server works the result out again from your answers and emails it to the address you gave, as a PDF, from our Google Workspace mailbox. A copy of that email comes to us, so we know who asked. We keep what you sent so that we can answer if you write back.

Checking an email address

When you give us an email address in any of these three places, our server looks up its domain, the part after the @, in the internet's public directory of domain names (DNS), to check that the domain can receive email. Only the domain is looked up, never the whole address, and no email is sent to check it. If the domain cannot receive email, we ask you to check the address. We keep a note with what you sent of whether the lookup got an answer.

Why, and on what basis

We use what you send to email you the result or report you asked for, to reply to you, to understand what you asked about, and to write to you once about your report or answers. We email a result to the same address at most once an hour per tool. Our lawful basis is legitimate interests: answering a business that asked us something. You can tell us to stop at any time, and we will not write to you again.

What we do not keep

The tools themselves do not store your IP address; our hosting provider logs it with each request, as for every page (see When you visit this website). A hidden field that only automated programs fill in is used to drop spam. If you allowed analytics in the banner, it also records that you used a tool, without your answers, your name or your email address (see When you visit this website). If you allowed Meta advertising, the Pixel tells Meta when you give your email to see your full bottleneck finder result, ask to see a full AI-readiness report or send a message, without those details either (see The Meta Pixel).

How long we keep it

We keep what you sent for 12 months from your last contact with us, then delete it. You can ask us to delete it sooner, at the address at the top of this page.

Calls

When you book a call

Booking links open Calendly's own website, which runs our booking calendar. Nothing from Calendly loads on this site.

When you book, Calendly collects the details you enter, such as your name, your email address and anything you tell us about the call, and passes them to us. We use them to hold the call and prepare for it. Our lawful basis is taking the steps you asked for before any agreement. Calendly handles your details under its own privacy notice (opens in a new tab).

If you accepted our analytics, it records that you clicked a booking link. It does not record whether you went on to book, and nothing about your booking is sent to Meta.

Outreach

If we contacted you

We contact owners, directors and managers at companies we have not met, about work we think is relevant to their company. Most are at manufacturing companies in India. We also write to leaders of online clinics and digital pharmacies in the UK and Europe. We send these messages in batches, to many companies at a time. If you received one, this section is for you.

How we contact people

  • Through a business messaging app run by Meta, to a mobile number listed for your business. Most of our messages to companies in India are sent this way.
  • By email, sent through Google Workspace. An email can carry a one-page PDF we wrote about your company, built from public information such as published customer reviews.
  • On LinkedIn: a connection request and, if you accept it, a message.
  • Sometimes by phone, on a number listed for your business.
  • If you filled in a form on one of our ads on Facebook or Instagram, or messaged us first, we reply through the messaging app or by email.

Where your details came from

  • public business listings, such as Google Maps;
  • your company's website, press releases, published research papers and public records, such as Companies House and domain-registration records;
  • professional profiles, such as LinkedIn;
  • business-contact data providers, such as Apollo.io;
  • a form you filled in on one of our ads, or a message you sent us.

Where no work email address is published, we may work out a likely one from the format your company uses for other staff.

What we keep

  • your name, job title and company;
  • the business phone number, email address or LinkedIn profile we used;
  • which messages we sent, when, and whether you replied;
  • our correspondence with you, and notes on what you told us;
  • the reference code in the links we sent you.

Links in our messages

A link in one of our messages can carry a reference code that is unique to you. If you open it and allow analytics in the banner, our analytics records the code with your visit. The code belongs to the person we wrote to: if our message was forwarded and someone else opens the link, their visit is recorded against that person. That links the visit, the pages you read in it and any booking link you click to you, as the person we wrote to. We use this to see which messages lead people to read about our work or ask for a call. If you do not allow analytics, it records nothing, and the visit is not linked to you. The address you opened, with the code in it, still appears in our hosting provider's logs for 30 days, as described in When you visit this website.

Why, and on what basis

We use your details to contact you about that work and to follow up a few times, and for nothing else. Our lawful basis is legitimate interests: reaching businesses we may be able to help. If you asked us to contact you, through a form or a message, we rely on that request. Linking a website visit to you relies on your consent in the banner.

How to object or opt out

  • Reply "stop" to any message, or email us at the address at the top of this page, and we will not contact you again.
  • You can object to our use of your details at any time, including for direct marketing. If you do, we stop.
  • You can ask what we hold about you, or ask us to delete it, at the same address.
  • To stop a visit being linked to you, choose Decline all in the banner, or change your choice with Cookie choices at the foot of any page.

How long we keep it

We keep your record while we are in contact with you, or may still follow up about the same work. If you ask us to stop, we mark your record so that you are not contacted again. If you ask us to delete your details, we delete them, and the analytics records linked to your reference code with them. We keep only your name and the number or address we used, on a do-not-contact list, so that we never write to you again.

Sharing

Who else sees your data

  • Our own analytics service: receives the records described in When you visit this website, only if you allow analytics. It does not pass them to any advertiser.
  • Google: hosts this website, our free tools, our contact form and our analytics service in Google Cloud's Mumbai region, in India, keeps the server logs, and runs our email on Google Workspace.
  • Ora (ora.ai): receives the website address you enter in the AI-readiness check, and nothing else, as described in When you use our free tools or contact form.
  • MongoDB: holds our analytics records in its Atlas database service.
  • Calendly: runs bookings, when you open a booking link.
  • Meta: receives Pixel data only if you allow Meta advertising, as described in The Meta Pixel. Meta also runs the messaging app we use for outreach, which carries our messages to business phone numbers, and the ad forms on Facebook and Instagram, as described in If we contacted you.
  • LinkedIn: carries the connection requests and messages we send there.

This website loads no fonts, scripts or images from other companies. The one exception is the Meta Pixel, after you accept it.

We do not sell personal data.

We work from India, and our analytics service runs there. If you are in the UK or the EU, your data is handled outside the UK and the EU. The safeguard for that is listed in What we are still putting in place.

Google, MongoDB, Calendly, LinkedIn, Ora and Meta may also process data in other countries, including the United States. Each says in its own terms where it processes data and how it protects data sent abroad.

Your rights

Your rights

Under UK GDPR and EU GDPR, you can ask us to:

  • tell you what we hold about you and give you a copy;
  • correct anything that is wrong;
  • delete it;
  • stop or limit how we use it;
  • give it to you in a format you can move elsewhere.

You can object to our use of legitimate interests at any time. You can always object to direct marketing, and we will stop. You can withdraw your consent to our analytics and the Meta Pixel at any time with Cookie choices, as described in The Meta Pixel.

Email us at the address at the top of this page. We answer within one month.

If you are in India, you can make the same requests at the same address, and we answer within the same month.

If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk if you are in the UK, or to the data protection authority where you live or work if you are in the EU.

We update this notice when what the site or our outreach does changes, and change the date at the top.

Still in progress

What we are still putting in place

This notice is in force. These items are still being put in place, and each will be stated here when it is.

UK and EU representatives
Being appointed. We will name our UK representative (UK GDPR Article 27) and our EU representative (EU GDPR Article 27) here, with how to reach them, once they are appointed. Until then, contact us directly.
Safeguard for UK and EU data handled in India
Being put in place with our UK data protection adviser. Ask us at the address at the top of this page how your data is protected today.
Where our analytics database sits
The records are held in MongoDB Atlas. We are confirming which country its servers are in.
Indian data protection law
We are confirming with our adviser which duties under India's Digital Personal Data Protection Act 2023 and its Rules apply to us, and from when. Until then, anyone, wherever they are, can make the requests in Your rights at the same address.

Ask what we hold about you, or ask us to delete it.