Privacy policy

Last updated November 10, 2026. About 18 minutes to read.

SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India. CIN U62013GJ2023PTC146272.

Contents

This is how smalBlu handles personal data and the data in your cloud. We wrote it for the person who has to decide whether to connect a cloud account to us, so it says what we read, what we never read, and what our AI does with it.

1Who we are and what this covers

1.1

"smalBlu", "we" and "us" mean SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India. Our corporate identity number is U62013GJ2023PTC146272.

1.2

This policy covers smalblu.ai, the emails and calls that come from it, the free cloud review, and the smalBlu service.

1.3

For customers, our contract and data processing terms sit alongside this policy. If they conflict on how customer data is handled, the contract wins.

1.4

This policy does not cover websites we link to, or your cloud provider. They have their own terms.

2Two kinds of data

2.1

Visitor data is what we receive when someone uses our website, fills in a form, books a call or writes to us. For this data we decide why and how it is used. Under the law we are the data fiduciary (India) or the controller (EU and UK).

2.2

Customer data is what we receive from a cloud account you connect to us, and what we create from it, such as recommendations and logs. Most of it describes machines, not people. Where it does contain personal data, you decide why it is processed and we act on your instructions. You are the data fiduciary or controller, and we are your data processor.

2.3

Account data is the names, work emails and roles of the people who use the service, approve changes or receive invoices. We treat it like visitor data.

3If you visit our website

3.1

Forms. When you use a form we receive your name, work email, company, your message, and anything else you choose to enter, such as your rough monthly cloud spend. We use this to reply and to prepare your review or quote.

3.2

Booking a call. Calls are booked through Calendly. Calendly receives your name, email, chosen time and any answers you give, and shares them with us. We use them to run the call.

3.3

Server logs. Our hosting company records each request to the site: IP address, browser, page, time and the page you came from. We use these logs to keep the site running and to spot abuse.

3.4

Email. If you write to us, we keep the conversation so we can reply and follow it up.

3.5

Analytics. We do not run analytics on the site today. A8 If we add it, we will name the tool here first, and choose one that works without following you across other websites.

3.6

Marketing. We email you only about what you asked for. If we want to send anything else, we will ask, or give you a clear way to say no. Every such email has a way to stop them.

3.7

Links to AI assistants. Some of our pages may offer a link that opens an AI assistant with a question already typed in. If you use it, your question goes to that assistant under its own terms, and we receive nothing back.

4Cookies

4.1

Our website is built to work without tracking cookies. We do not use advertising cookies, retargeting pixels, session recording or data brokers. A9

4.2

If the site needs a cookie to do its job, such as keeping a form secure, we will list it here with its purpose and how long it lasts. Today that list is empty. A9

4.3

If we embed the Calendly booking page in our site, Calendly may set its own cookies when you open it. Our plan is to link to Calendly rather than embed it, so those cookies apply only once you are on its page. A9

4.4

If we ever add a cookie that is not strictly necessary, we will ask you first where the law requires it, and you can say no without losing access to anything.

5If you connect your cloud

5.1

To connect, you create a role in your own cloud account using a policy we provide. We use that role to read your account. We do not ask for your root login, your passwords or long-lived keys. A1

5.2

We start read-only. That applies to the free cloud review and to the first stage of every customer account.

5.3

We ask for the least access that does the job. The policy is written out so that you can read it before you create the role, change it, or run it past your security team.

5.4

You stay in control. This table shows what you control and how each one starts.

What you controlHow it startsWhat it means
Access levelRead-onlyWe can look. We cannot change anything until you give us a separate role for changes. A14
Rules for automatic changesOffNothing runs on its own until you write a rule that allows it.
Model training on your dataOff, with no switchCustomer data does not train AI models. There is no setting that turns this on. A3
Disconnecting usYours at any timeDelete the role in your account and our access ends at once. Nothing on our side can stop that.

6What we read

6.1

We read the following from the accounts you connect: A2

  • Inventory and settings: resource IDs, names, tags, types, sizes, regions, versions, and how resources connect to each other.
  • Usage and performance numbers: CPU, memory, disk, network, connection counts, query counts and durations, and GPU utilization.
  • Cost and billing: cost and usage reports, line items, reserved capacity, savings plans and credits.
  • Change and health events: when a resource was created, resized, restarted or failed.
  • Account structure: account IDs, account names and how they are organized.
6.2

This is metadata, but metadata can still point to a person. A database called adam-test, a tag holding an email address, or a change event carrying a username is personal data. We treat it as personal data, and we ask you not to put secrets or sensitive details in names and tags.

7What we do not read

7.1

We do not read: A1 A2

  • the contents of your databases, including rows, documents and values
  • the contents of your storage objects, disk volumes, snapshots and backups
  • secrets, private keys, and the values of environment variables and startup scripts
  • what is in memory, or the content of network traffic
  • the content of your application logs
  • records about your own customers
7.2

Permissions enforce this. The role in section leaves out the permissions that would allow any of this, such as reading a storage object or decrypting a value. A1

7.3

Query text. Some database performance tools return the text of a query, and that text can contain real values. We do not request it. We read counts and durations. A2

7.4

How to check us. The role's policy is in your account, so you can read exactly what it allows. Every call the role makes is recorded in your own AWS CloudTrail. Management calls are recorded by default, and you can turn on data events if you want proof that object reads never happen.

7.5

If a future part of the service needs more than section describes, such as logs or traces, we will say so here first. It will stay off until you turn it on for your account. A2

7.6

This table sets out the line, layer by layer.

WhereWe readWe never read
ComputeInstance type, size, region, tags, CPU, memory and disk use, running hoursWhat is in memory, disk contents, startup scripts, environment variables
StorageBucket and volume names, size, tier, object counts, last access dates, lifecycle rulesThe files themselves, volume and snapshot contents, backups
NetworkingLoad balancers, gateways, routes, security group rules, data transfer volumesThe content of any traffic, packets or payloads
DatabaseEngine, version, instance size, connections, query counts and durations, storage usedRows, documents, values, query text, stored credentials
Billing and accountCost lines, reserved capacity, savings plans, credits, account names and IDsYour payment details at AWS, your AWS root login

8Changes and the action log

8.1

If you want smalBlu to apply changes, you give us a second role with its own limited permissions. It is separate from the read-only role, so you can remove it without disconnecting us. A14

8.2

A change goes ahead only if it fits a rule you set or a person on your team approves it. Everything else waits.

8.3

Each action is written to a log: what changed, when, why, what the simulation predicted, which rule or person allowed it, and the result. The log contains the names of the people who approved changes.

8.4

You can read and export this log at any time. A12

8.5

Applying a change does not give us access to the contents listed in section . The change role is limited to managing resources. A14

9What our AI does with your data

9.1

What the AI does. It reads the metadata in section , finds waste and risk, works out a fix, simulates the effect, and writes a recommendation with its reasons. Where your rules allow, it starts the change.

9.2

What goes in. Only metadata from section , and only what the task needs. The contents listed in section cannot go in, because we do not have them.

9.3

Training. Customer data does not train AI models. That covers our own models and anyone else's, and it covers fine-tuning. We do not use one customer's data to produce results for another. A3

9.4

Outside AI models. Some of this work may run on AI models hosted by other companies. When it does, the provider receives only what that request needs, under contract terms that forbid training on it and limit how long it is kept. A4

9.5

Numbers we do keep. We keep totals that cannot identify you or your infrastructure, such as how much cloud spend we have scanned in all or how many engineering hours were returned. These totals never train a model. A3

9.6

Mistakes. AI can be wrong. That is why changes are simulated first, why they need your rule or your approval, and why our engineers stand behind them. A5

9.7

No decisions about people. The AI decides about servers. It makes no decisions about individuals and does not build profiles of them.

9.8

If this changes. We will not start using customer data for training. If we ever wanted to, it would need your written agreement first, and a new version of this policy.

This table follows one recommendation from start to finish.

StepWhat happensWhat is kept
ReadOur role reads metadata from your account.The metadata, in storage reserved for your account.
ReasonThe AI works out what to change, using only that metadata.The recommendation and its reasons. Outside models keep nothing beyond their contract limit. A4
SimulateWe estimate the effect before anything moves.The simulation result.
ApproveYour rule or your team decides.Who or what allowed it.
Apply and logThe change runs and is recorded.An entry in your action log.
DeleteWhen you leave, we delete it.Nothing beyond section .

10Who at smalBlu can see it

10.1

smalBlu is AI and engineers working together, so people on our team can see customer data. They may do so only to run the service: to check a recommendation, investigate a problem, apply a change or answer your support request. A5

10.2

Access is limited to named engineers who need it, and each access is logged. A5

10.3

Everyone with access is bound by confidentiality duties in writing. A5

10.4

We do not look at customer data for curiosity, marketing or sales. If we want to use your results in a case study, we ask you first.

11Companies that handle data for us

11.1

These companies handle data for us. Each is bound by contract to use it only to provide its service to us. A8

CompanyWhat it does for usWhat it receives
VercelHosts our websiteWebsite requests, including IP address
CloudflareAnswers DNS lookups for our domainDomain lookups. Website traffic does not pass through it.
ResendSends form messages and emailsName, email address and message
CalendlyBooks callsName, email address, chosen time and your answers
11.2

We do not use a website analytics company today. A8

11.3

We will update this list before we add a company that handles customer data, and tell customers 30 days ahead so they can object. See section .

12Other times data may be shared

12.1

We do not sell personal data, and we do not share it for advertising.

12.2

The law. We disclose data if a law, court or government authority in a place that has power over us requires it. We check that the request is valid, disclose only what is required and, unless the law forbids it, tell the customer first.

12.3

Protecting people and the service. We may use or disclose data where needed to stop fraud or a security attack, or to make or defend a legal claim.

12.4

Sale of the company. If smalBlu is merged or sold, data may pass to the new owner. It stays under this policy until customers have had notice of any change, as section requires.

12.5

With your agreement. We share data in any other case only if you ask us to.

13What we keep, why and for how long

13.1

This table is complete. If we start holding something new, it goes here first.

DataWho it is aboutWhy we hold itKept forWho sees itLegal ground (EU and UK)
Form entriesVisitorsTo reply and prepare your review or quote24 months after last contact A13Our team, ResendSteps before a contract, legitimate interests
Booking detailsVisitorsTo run the call24 months after last contact A13Our team, CalendlySteps before a contract
Server logsVisitorsTo keep the site running and secureUp to 12 months A13Engineers, VercelLegitimate interests
Emails with usVisitorsTo reply and keep a record24 months after last contact A13Our teamLegitimate interests
Cloud metadataCustomersTo run the serviceContract, then 30 days. Backups 60 days. A6Named engineers, our AI, listed vendorsYour instructions, under contract
Free review metadataCustomersTo produce your review30 days after the review ends A6Named engineers, our AIYour instructions, under contract
Recommendations and simulationsCustomersTo show what we found and whyContract, then 30 days. Backups 60 days. A6Your team, named engineersYour instructions, under contract
Action logCustomersA record of every changeContract, then 12 months A12Your team, named engineersYour instructions, legal claims
Account contactsCustomersLogins, approvals and noticesContract, then 12 months A13Your team, our teamContract
Access and security logsBothTo detect and investigate misuseAt least 12 months, as Indian law requires A13Named engineersLegal obligation, legitimate interests
Invoices and contractsCustomersTax and company law8 yearsFinance team, advisersLegal obligation

14Deleting your data

14.1

End of a contract. You remove our roles. We stop reading your account at once. Within 30 days we delete your cloud metadata, recommendations and simulations. Backups age out within 60 days. A6

14.2

What stays longer. The action log stays for 12 months so that both of us can answer questions about past changes. Invoices and contracts stay for as long as tax and company law require. Security logs stay for the period in section . A12

14.3

Copy first. You can export your action log and your findings before the end date. A12

14.4

Free cloud review. If you do not go ahead, we delete what we read within 30 days of the end of the review. A6

14.5

Earlier deletion. You can ask us to delete customer data sooner. We will, unless the law requires us to keep it. We will confirm in writing when it is done.

14.6

Totals. The totals in section are not deleted, because they cannot identify you.

15Security

15.1

We protect data with encryption in transit and at rest, least-privilege access, multi-factor login for staff, separate storage for each customer, and logging of staff access. A10

15.2

SOC 2 and ISO 27001 are in progress. We do not hold either certificate today, and nothing in this policy claims that we do. When that changes we will update this section and offer the reports to customers.

15.3

Nothing in this policy claims certification under any privacy law. We describe what we do, and the laws we work to follow, so that you can judge it.

15.4

No system is perfectly secure. You help by limiting who can edit the roles you gave us, and by telling us at once if you think they have been misused.

16If something goes wrong

16.1

If we confirm a security incident that affects customer data, we will tell the affected customers within 48 hours, and keep updating them until it is closed. A11

16.2

The notice will say what happened, what data was involved, what we have done and what you may need to do. If we do not yet know something, we will say so.

16.3

We will also report to regulators and tell affected people as the law requires. In India that includes CERT-In and, once the DPDP duties apply, the Data Protection Board of India and the individuals affected.

16.4

A customer that is the data fiduciary or controller for the data remains responsible for its own notices, and we will give it the information it needs.

17Where data is stored and sent

17.1

Our engineers work from India. If they view customer data, that counts as a transfer to India.

17.2

Website vendors in section may process data in the United States and other countries.

17.3

From the EU and UK. India does not have an EU or UK adequacy decision. For these transfers we use the European Commission's standard contractual clauses and the UK addendum, or another lawful method. You can ask us for a copy.

17.4

From India. The DPDP Act allows transfers outside India unless the government restricts a particular country. We will follow any such restriction.

18Your rights in India

18.1

India's Digital Personal Data Protection Act 2023 and the Rules of 2025 come into force in phases. Most duties on businesses begin around May 2027. Until then, the Information Technology Act 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011 apply. We are writing this policy for both.

18.2

Now. You can review the information you gave us, correct it, and withdraw any consent you gave. If you withdraw consent, we may be unable to provide what depended on it.

18.3

Once the DPDP duties apply. You can also ask for a summary of your personal data and how it is processed, ask who we shared it with, ask us to erase it, raise a grievance with us, and nominate someone to exercise your rights if you die or cannot act.

18.4

We give notice and, where required, ask for your consent in clear language. You can ask for this policy's notice in any language listed in the Eighth Schedule to the Constitution of India once that duty applies.

19Your rights in the EU and UK

19.1

If the EU or UK GDPR applies to our handling of your data, you can ask us to give you a copy of it, correct it, delete it, limit how we use it, or send it to you or another company in a common format. You can object to our use of it based on legitimate interests, and to direct marketing at any time.

19.2

Where we rely on consent, you can withdraw it at any time.

19.3

We reply within one month. You can also complain to your local data protection authority.

19.4

If you are in the EU or the UK, write to us at hello@smalblu.ai about any of these rights.

19.5

This section describes rights the law gives you. It is not a claim that smalBlu is certified under GDPR.

20Your rights in California

20.1

We do not sell personal information or share it for cross-context advertising, and we have not done so in the past 12 months. We do not use sensitive personal information to infer things about people.

20.2

smalBlu may be below the size at which the California Consumer Privacy Act applies. We offer these rights to California residents anyway: to know what we collect and why, to correct it, to delete it, and to be free from worse treatment for asking. An authorized agent may ask for you.

20.3

The categories we collect are identifiers and contact details, internet activity on our website, and professional details such as your company and role. Sections and give the sources, purposes and retention periods.

20.4

Because we run no ad trackers, a Global Privacy Control signal has nothing to stop on our website today. If that changes, we will honor it.

20.5

This section describes rights the law gives you. It is not a claim of compliance certification.

21Complaints and the Grievance Officer

21.1

Our Grievance Officer is Sharuya. Reach them at hello@smalblu.ai or by post at the address in section .

21.2

We acknowledge a complaint within 7 days and aim to resolve it within 30 days. That is within both the one month allowed by the 2011 Rules and the 90 days allowed under the DPDP framework.

21.3

To use any right in this policy, write to the same address. We may need to confirm who you are, and we ask only for what we need to do that.

21.4

If personal data reached us through a customer, such as a name in a resource tag, we will pass your request to that customer and help it respond.

21.5

You can also complain to a regulator: the Data Protection Board of India once it takes complaints, or your local authority in the EU or UK.

22Children

22.1

Our website and service are for businesses and are not meant for anyone under 18. We do not knowingly collect their data, and we do not track or target them.

22.2

If you believe a child has given us personal data, write to us and we will delete it.

23Changes to this policy

23.1

Each version has a number and a date, and past versions stay available.

23.2

If a change matters to customers, we will email them at least 30 days before it applies. Website visitors will see the new date and a short note on what changed.

23.3

A change cannot give us more rights over data we already hold unless you agree. Section applies to training.

24Data processing summary

24.1

This summary is for customers. The full data processing agreement (DPA) forms part of the contract. Ask us for a copy at hello@smalblu.ai.

PointSummary
RolesYou are the data fiduciary or controller. smalBlu is your data processor.
What we processCloud metadata that may contain personal data, such as names in tags, usernames in change events and approver names.
Whose dataYour staff, contractors, and anyone named in your resources.
WhyOnly to provide the service, on your documented instructions.
How longFor the contract, then as section says.
TrainingNot used to train AI models, ours or anyone else's. A3
StaffNamed engineers, bound to confidentiality, with access logged. A5
SubprocessorsListed in section . 30 days' notice of a new one, and you may object.
SecurityAs section says.
IncidentsNotice within 48 hours of confirming an incident. A11
Your requestsWe help you answer requests from individuals and regulators.
AuditsWe answer reasonable security questions and share reports once we have them.
TransfersAs section says, with standard contractual clauses where needed.
End of contractReturn and deletion as section says.

25Contact

25.1

General questions: hello@smalblu.ai.

25.2

Privacy requests and complaints: hello@smalblu.ai, for the attention of Sharuya, our Grievance Officer.

25.3

Post: SmalBlu Technologies Private Limited, E-603, Iscon Platinum, Nr Bopal Cross Road, Bopal, Ahmedabad, Daskroi, Gujarat 380058, India.