Legal

Privacy Policy

Last updated: November 2026

Introduction

Tomorrow Central (“we”, “our”, or “us”) is a product of itmtb Technologies. Tomorrow Central is a self-serve console of tools for infrastructure, tech, and AI agents. This Privacy Policy explains what information we collect, how we use and protect it, and the choices you have. By using Tomorrow Central, you agree to the practices described here.

Information we collect

Account data: When you register, we collect your first name, last name, email address, and country of residence. Authentication is handled through Amazon Cognito.

Connected accounts: To run certain tools you connect a cloud account (for example, AWS). We do this using a scoped, cross-account role that you create and can revoke at any time — we assume the role to obtain short-lived credentials only for the duration of a run. We do not store your long-lived cloud credentials, unless a specific tool explicitly states otherwise at the point of connection. We retain connection metadata (such as the role identifier and external ID) so you can re-run tools.

Tool inputs and results: When you run a tool, we store the inputs you provide and the results the tool produces (for example, a cost scan's findings about your own infrastructure). This data is stored on our infrastructure as part of the core product functionality so you can review, re-run, and act on it.

Usage data: We record how you use the platform — which tools you open, runs you start, and associated counts — to operate the service, enforce limits, and improve our tools.

Search: If you use Search, we store the catalogue and website pages you import so we can search them. When someone searches on your search box or search link, we record what they typed, the results shown, their IP address and an anonymous session identifier, to answer the search, protect it from abuse and show you your search statistics. These raw search records are deleted after 90 days; after that only aggregated counts remain.

Technical data: We automatically collect IP addresses, browser and device information, and log data for security monitoring and debugging. Our service logs, which include IP address and browser details, are kept for 60 days. Security records of account actions (for example, sign-ins refused or keys created) keep the IP address and browser details for longer, as part of your account's security history.

Analytics (only if you accept): See “Analytics” below.

How we use your information

We use your information to:

  • Operate, maintain, and improve the Tomorrow Central platform and its tools
  • Run the tools you request against the accounts you connect
  • Enforce usage limits and, where applicable, calculate charges
  • Send transactional emails (account verification, password reset)
  • Monitor for security threats and abuse
  • Comply with legal and regulatory obligations

We do not use your data for advertising, and we do not sell your personal information.

Website Growth Ops and your Google data

Website Growth Ops reads your website's search and visitor data from Google so it can show it to you and find what to improve. It only does this after an admin of your organization connects a Google account and grants permission on Google's own consent screen, and only for a website your organization has verified with us.

What we ask Google for (read-only):

  • Google Search Console (read-only): the list of properties you can access, to find the one for your verified website, and that property's search performance — for each day, page, search query and device type: clicks, impressions, click-through rate and average position.
  • Google Analytics (read-only): the list of accounts, properties and web streams you can access, to find the one for your verified website, and these figures from that property:
    • visits, for each day, landing page, channel and device type: sessions, engaged sessions and engagement time;
    • the events your website counts as conversions (the ones you choose, or the property's key events), for each day, landing page, channel and device type: how many;
    • visits from AI assistants, for each landing page and assistant: how many;
    • views of your website's “page not found” page, for each day, the address that was asked for and the page the visitor came from: how many. When the visitor came from another website, we keep only that website's name, not the rest of its address. We never keep anything after a “?” or “#” in any address, and we do not keep page titles;
    • visits and conversions for each hour of the last few days, in your property's time zone: how many;
    • the names of the events your property received, and how many of each (for example “page_view” or “form_start”), so we can tell you which measurements are switched off;
    • what visitors searched for using your website's own search box, and how often, over the last few months. Before we keep a search, we remove email addresses, phone numbers and long numbers from it, and we keep only searches made at least a few times; rarer ones are counted, not kept;
    • how many visitors started and how many sent the forms on each page of your website, for each day;
    • how many times each page of your website was viewed, for each day and device type, with the time visitors spent on it, and, over the last few months, which of your own pages visitors came from before each page. When a visitor came from another website, we keep nothing about that website;
    • for a few steps on the way to what your website is for (for example a service page, the contact page, a form, a conversion), how many visitors reached each step, by device type and channel, and which page they went to next;
    • visits, engaged visits and conversions for each browser, operating system and device type; for each country, language and new or returning visitor; and for each source, campaign and landing page;
    • for each page of your website: how many visitors scrolled to the bottom, which other websites visitors clicked through to (the website's name only) and which files they downloaded (the file's name only);
    • if your website sells online: for each day and product, how many were viewed, added to a cart, checked out and bought, and the revenue; and for each landing page, visits, purchases and revenue. Product names are kept as your shop sends them.

To recognise your website's “page not found” page, our crawler asks your website, once each time it reads it, for an address that does not exist, and reads that page's title. Our crawler runs no scripts, so this request never shows up in your analytics.

We never change anything in your Google accounts, and we do not read any other Google data (no email, files, contacts or calendar).

What we keep: those figures for the website you chose, for up to the history your plan allows (300 days on the free plan), and a Google refresh token so the data can update by itself. The refresh token is encrypted with a dedicated key held by our cloud provider, can be decrypted only by Website Growth Ops on our servers, and is never shown on any page, returned by any API or written to any log. Short-lived access tokens are held in memory only.

How we use it: only to provide Website Growth Ops to you and your organization — showing your data, finding pages and searches that are underperforming, and suggesting improvements. We do not use it for advertising, we do not sell it, and we do not use it to train AI models. People at itmtb Technologies do not read it unless you ask us to (for example, for support), it is needed for security, or the law requires it.

Who else sees it: our hosting provider stores it, in India. When you or an agent you have authorised asks the Tomorrow Central assistant about your website, the data needed for the answer is sent to the AI model provider that runs the assistant, only to produce that answer and under terms that do not allow it to be used for training. When you ask Website Growth Ops to draft a suggested change (for example, a new page title), the page's text and the search data needed for that draft are sent to the same provider, only to produce the draft and under the same terms; drafts are made only when you ask, and every number in a finding comes from our own calculations, never from the model. To see what Google shows for a few of your most important searches, those search terms (never your traffic figures) are sent to a search-results provider, which returns the public results; we look up at most your plan's monthly number of searches, and these results are deleted with your Search Console data. To find links from other websites to yours (for example, links that point at a page you have removed), your website's address is sent to a backlink data provider, which returns the public links it knows; nothing else about your website or its visitors is sent. To see which websites AI assistants cite for your website's topics, questions about those topics (written from your website's searches and names, never its traffic figures or its visitors' data) are sent to AI assistant providers, which answer with their sources; we ask at most your plan's monthly number of questions. An agent you connect over MCP receives only what the permissions you gave it allow.

Disconnecting and deletion: your Google connection is managed in Tomorrow Central's Connectors, where an admin can pause or disconnect it at any time; you can also remove our access from your Google Account (myaccount.google.com/permissions). When an admin disconnects, Connectors revokes the token at Google and deletes it, and Website Growth Ops deletes the Search Console and Analytics data it stored through that connection, and the analyses and findings built from it, all at once. Pausing stops updates and keeps the data. If you remove our access in your Google Account instead, updates stop and the connection shows as needing to be reconnected; the data already stored stays until an admin disconnects. Either way, figures older than your plan's history window are deleted automatically.

Tomorrow Central's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Analytics

We use Google Analytics to see how far people get on the site — for example, whether they start signing up or create their first search project — so we can fix where people get stuck. It runs only if you choose “Accept” on the banner. Until you choose, and if you choose “Decline”, Google Analytics is not loaded and nothing is sent to Google.

What we send is limited to the pages you visit (with account and project identifiers removed from the address) and a short list of steps such as “sign-up started”. We never send your name, email address, organisation, search text, website address or any identifier of your data. To change your choice, clear this site's data in your browser and you will be asked again.

Multi-tenant isolation

Tomorrow Central is multi-tenant. Your account, connected accounts, tool inputs, and results are logically isolated per tenant. Other tenants cannot access your data, and your data is never exposed to another tenant.

Programmatic and agent access (MCP)

Every tool can be used two ways: through our web console, and programmatically over the Model Context Protocol (MCP) so your AI agents can call it. To enable this, you issue API keys that you can revoke at any time.

Runs initiated by an agent are treated exactly like runs you start yourself — the same tenant isolation, the same retention, and the same scoped, revocable access to any connected account. We store the API keys you issue and log programmatic access for security and abuse monitoring. You are responsible for safeguarding the API keys you create and for activity performed with them.

The MCP endpoint also offers two optional tools an agent can use to send us free text: one for reporting what was missing or broken, and one for rating a result. We store what an agent writes there for 400 days and read it to decide what to build and fix. An agent may describe a problem in its own words, including quoting what you asked it to do, so please do not include credentials, personal data or confidential material in anything sent through those tools. Nothing else on the endpoint depends on them, and we never reply to that channel.

Aggregated and anonymised data

We may create aggregated and anonymised data derived from tool usage to understand, benchmark, and improve our tools. This data does not identify you or your organisation, is never sold, and is never used to expose one tenant's information to another.

Data retention

We retain your tool inputs, results, and connection metadata until you delete them or close your account — except where longer retention is required to meet legal or regulatory obligations. When you delete a result, connection, or your account, the associated data is removed from active systems, subject to routine backup cycles.

Data storage, location, and security

Your data is hosted in India, unless a specific tool explicitly states a different region. We use industry-standard security practices including encryption in transit (TLS), encryption at rest, and access controls.

You sign in through Amazon Cognito. Your session is then kept in an encrypted cookie that only our server can read (httpOnly, Secure) — scripts on the page cannot. It refreshes while you stay signed in and is cleared when you sign out.

While we take reasonable precautions, no system is completely secure. We encourage you to use a strong, unique password and to scope connected roles to the minimum access a tool needs.

Sub-processors and sharing

We do not sell, trade, or rent your personal information. We share data only with sub-processors that help us operate the platform, under appropriate data-processing terms:

  • Amazon Web Services (AWS) — cloud hosting and infrastructure (India region), Amazon Cognito for authentication, and Amazon SES for transactional email
  • Google (Google Analytics) — site analytics, only if you accept analytics on the banner
  • Google — the source of your website data in Website Growth Ops, only after your admin connects it
  • An AI model provider — runs the Tomorrow Central assistant, for the answers you ask for, and drafts the suggested changes you ask Website Growth Ops for; it may not use your data for training
  • A search-results provider — looks up public Google results for a few of your search terms, for Website Growth Ops
  • AI assistant providers — answer questions about your website's topics, with their sources, so Website Growth Ops can see which websites they cite; no traffic figures or visitor data are sent
  • A backlink data provider — looks up public links to your website's pages; only your website's addresses are sent, for Website Growth Ops

We keep this list current as our sub-processors change. We may also disclose information to law enforcement when required by applicable law or to protect our rights.

Business customers who need a Data Processing Agreement (DPA) can request one at support@tomorrowcentral.io.

Your rights

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

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Delete your tool results, connections, or your entire account and associated data
  • Export your data in a portable format
  • Revoke a connected account's role at any time, from your side, to cut off our access

To exercise these rights, contact us at support@tomorrowcentral.io.

Cookies

We use an essential cookie to maintain your session (httpOnly, Secure, SameSite=Lax). If you accept analytics, Google Analytics sets its own cookies to count visits; if you decline, it sets none. We do not use advertising cookies. You can disable cookies in your browser settings, but this will prevent you from staying signed in.

Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version here and revise the “last updated” date; where changes are material, we will provide additional notice.

Contact

If you have questions about this Privacy Policy, contact us at support@tomorrowcentral.io.