Terms of Service

1Agreement

1.1These Terms govern your access to and use of the Service. By creating an account, accessing the Service, or clicking to accept, you agree to them. If you accept on behalf of an organisation, you represent that you are authorised to bind it, and “you” means that organisation.

1.2If we and you have signed a separate written agreement or Order Form covering the Service, that agreement prevails over these Terms to the extent of any conflict.

1.3Order of precedence: (a) a signed Order Form or Enterprise Agreement; (b) Schedule B (Data Processing Addendum); (c) these Terms; (d) any policy or documentation referenced here.

2Definitions

• Organisation — the top-level billing entity. One subscription, one invoice, and one pooled quota shared across every Project within it.
• Project — a product or system within an Organisation. Holds its own data, identities and access map.
• Space — a working copy of a feature within a Project, used by a developer or team.
• Release Workspace — the production environment of a Project, into which Spaces are promoted.
• User — an individual authorised by you to access the Service under your Organisation.
• Customer Data — all data, content and materials you or your Users submit to, or generate within, the Service, including data belonging to your own end users.
• Plan — the subscription tier you select. The quotas, runtime guards and commitments of each Plan are published on the pricing page and incorporated into these Terms by reference.
• Quota — a published numeric limit on a Plan. Quotas fall into three classes, defined in §4.
• AI Tokens — units of large-language-model input and output consumed through the Service.
• Marketplace — the API Bay facility by which you may offer paid access to APIs you publish.
• Hosted Service — Minimal operated by us on our own cloud infrastructure, in the region you select.
• Self-Hosted Deployment — Minimal licensed to you and installed and operated by you on infrastructure you control. Governed by §3.
• Licence Telemetry — the records a Self-Hosted Deployment reports to our licence server, itemised at Privacy §3.9. It is the only data that reaches us from a Self-Hosted Deployment.

Where these Terms say “the Service” without qualification they mean both the Hosted Service and a Self-Hosted Deployment. Where a clause applies to only one of them, it says which.

3Accounts, Users and Security

3.1You must provide accurate registration information and keep it current.

3.2Users are not licensed individually. Paid Plans permit an unlimited number of Users within your Organisation. The Free Plan is limited to the number of Users published for that Plan.

3.3You are responsible for all activity under your Organisation, for the acts and omissions of your Users, and for maintaining the confidentiality of credentials and API keys.

3.4You must notify us without undue delay via our contact page on becoming aware of any unauthorised access to your Organisation.

3.5You must be at least 18 years old, or the age of majority in your jurisdiction, to hold an account. The Service is not directed at children, and you must not knowingly submit the personal data of a child through the Service except as permitted by Schedule B and applicable law.

Self-Hosted Deployments

3.6Licence grant. A Self-Hosted Deployment is licensed, not sold: a non-exclusive, non-transferable right to install and run Minimal on infrastructure you control, for the term and within the licensed units you have paid for. The licence does not permit sublicensing, resale, or operating Minimal as a service for third parties without a separate written agreement.

3.7Licence validation and IP whitelisting. The deployment reports Licence Telemetry to our licence server and validates against the IP addresses you have registered. You are responsible for keeping that whitelist current; an instance reporting from an unregistered address will not validate. Defeating, blocking or falsifying licence validation is a material breach, and so is running more licensed units than you have paid for.

3.8What stays with you. On a Self-Hosted Deployment you operate the infrastructure, the database, the backups, the network boundary, the patching and the availability. The uptime commitments in §7 do not apply — we do not operate the environment and cannot be measured on it. Support is advisory.

3.9We hold no standing access. We have no persistent credential into your environment. Where you ask for help, you grant access for a stated purpose and a bounded period, and you can revoke it at any moment. We take no copy of your data in the course of support unless you send us one.

4Plans, Quotas and Runtime Guards

4.1Quotas are published per Plan and fall into three classes:

(a) Cost dials

Metered. Database storage, network (ingress and egress combined), API requests, AI Tokens and, where applicable, agent-hours or query volume. Exceeding a cost dial does not interrupt the Service; it is billed at the published overage rate under §6.

(b) Runtime guards

Hard ceilings, enforced at the operating-system level. Maximum run or request duration, CPU cap, memory cap and concurrency. These are never billed and cannot be exceeded. A process that reaches a guard is terminated and the event is written to your audit trail.

(c) Packaging limits

Hard counts. Projects, Spaces, MCP tools, applications, agents, workflows and similar. These are never billed. To exceed one, you upgrade your Plan.

Pooling and fair use

4.2Quotas are pooled at the Organisation level, not per Project. Creating an additional Project draws on the allowance you already hold; it does not create a new charge.

4.3Fair use. Where a Plan describes a resource as unmetered, that description is subject to the fair-use figure published for that Plan. If your usage is materially and persistently above it, we will contact you to agree a Plan change. We will not levy an unpublished charge, and we will not suspend the Service, without first giving you written notice and a reasonable opportunity to respond.

4.4We may change published Quotas prospectively under §18. A reduction of a Quota on a Plan you already hold takes effect only at your next renewal.

5AI Tokens

Model vendor selection

5.1Where you consume AI Tokens through the Service, Littlebit selects the underlying model vendor and model. This is not a per-Plan option and may change; we will not make a change that materially degrades output quality without notice.

Bring your own key

5.2You may instead supply your own model-provider credentials. Where you do, AI Tokens are not metered and not charged by us. You are responsible for your agreement with, and all fees payable to, that provider, and for the lawfulness of the data you send it.

5.3Where we supply the model, prompts and completions are transmitted to the model vendor as a sub-processor. The current list is at Schedule C, mirrored at Privacy Schedule C, and forms part of Schedule B.

5.4We do not train models on Customer Data, and we do not permit our model vendors to do so. Where a vendor’s default terms would permit training, we contract out of it.

6Fees, Overages and Payment

6.1Subscription fees are billed monthly or annually in advance, per the Plan you select.

Overages

6.2Overages are billed monthly in arrears at the rates published for your Plan. All overage rates are published before they can be incurred. We will not introduce a charge that was not published at the time the usage occurred.

6.3Fees are exclusive of taxes. You are responsible for all applicable taxes other than taxes on our income. Where required, GST will be added at the prevailing rate.

6.4Invoices are due on receipt unless an Order Form states otherwise. We may suspend the Service for non-payment on 14 days’ written notice, and will restore it promptly on payment.

Refunds and price changes

6.5Refunds. Subscription fees are non-refundable except where required by law, or where we terminate for convenience under §14.3, in which case we refund the unused portion pro rata.

6.6Price changes apply from your next renewal and require 30 days’ notice under §18. Prices in a signed Order Form are fixed for its term.

7Availability

Availability target — Plans below Scale

7.1We operate to an availability objective of 99.9% per calendar month and publish incident history at status.littlebit.in. This is an operational target, not a service level agreement. It carries no service credits and no other contractual remedy.

Service Level Agreement — Scale and above

7.2If Availability in a calendar month falls below 99.5%, you may claim a service credit against that month’s subscription fee:

Exclusions and claims

7.3Availability means the percentage of minutes in the calendar month during which the Service was reachable, excluding Excluded Downtime.

7.4Excluded Downtime means downtime caused by: scheduled maintenance notified at least 24 hours in advance; emergency maintenance necessary for security or stability; your configuration, code or content; your Users; third-party services or networks not under our control, including our infrastructure providers to the extent of their own failure; suspension permitted under these Terms; and events outside our reasonable control.

7.5Claims must be submitted via our contact page within 30 days of the end of the affected month, with the times and nature of the unavailability. Service credits are your sole and exclusive remedy for any failure to meet the commitment in §7.2. Credits are applied against future fees, are not redeemable for cash, and are capped in aggregate at 50% of the fees paid for the affected month.

Why the commitment is set where it is

7.6Availability composes in series across every critical dependency. Our infrastructure providers commit 99.9% per server per month, and their remedy is a credit capped at that server’s own charge. A downstream commitment of 99.9% would require every layer we add — database, application, deployment and patching — to be 100.0000% available, which is not attainable. We publish the figure we can meet.

8Dormancy, Archival, Export and Deletion

8.1This section applies to Free Plan Projects only. A Project on a paid Plan is never flagged and never archived, however inactive it is, for as long as the Plan is paid.

8.2Activity means any interaction with a Project: an API request, a sign-in, a deployment, a query, or the exercise of any right under §10. Any single such event resets the periods in this section.

Flagging — 1 month

8.3After one month without Activity we display a notice in the product and send you an email. Nothing is throttled, paused, degraded or interrupted. The Project continues to operate exactly as before.

Archival — 4 months

8.4After four months without Activity we archive the Project. Compute resources are released and the Project is converted to a portable export: schema, data and configuration in open, documented formats with a manifest.

Download and restoration

8.5Download is guaranteed. For as long as an archive exists, you may download it free of charge, without limit, self-service, and without contacting us. We will not require a request, a ticket, a payment, or any other condition.

8.6Restoration is offered but not guaranteed. We will attempt to restore an archived Project into a running Project at your request, subject to available capacity at that time. We do not warrant that restoration will be available, and failure to restore is not a breach of these Terms. The remedy in every case is §8.5.

Deletion and notices

8.7Deletion — 16 months. Twelve months after archival, the archive is permanently deleted.

8.8Notices. We will send at least six notices across this lifecycle: seven days before flagging; at flagging; seven days before archival; at archival, stating the exact deletion date and the download link; six months into the archive period; and thirty days before deletion, to your primary and any recovery address. Each notice states the date of the next step.

Retention rationale

8.9The sixteen-month period is set to exceed the minimum retention required of a data fiduciary under Rule 8(3) of India’s Digital Personal Data Protection Rules 2025, while remaining no longer than necessary for the purpose of enabling recovery of an inactive Project. It is recorded in our privacy notice under Article 13(2)(a) UK/EU GDPR.

8.10Nothing in this section limits your right to delete a Project, or to require deletion of personal data, at any time under §10 and Schedule B.

9Roles under Data Protection Law

9.1Two distinct roles apply and they must not be conflated.

(a) Account data

In respect of the personal data of you and your Users — registration details, billing information, authentication and support correspondence — Littlebit is the controller (UK/EU GDPR) and the Data Fiduciary (DPDP Act 2023). Our processing is described in our privacy notice at Privacy Policy.

(b) Customer Data

In respect of personal data contained in Customer Data — including the personal data of your own end users — you are the controller / Data Fiduciary and Littlebit is the processor / Data Processor. We process it only on your documented instructions, on the terms in Schedule B (Data Processing Addendum).

(c) Which model you are on changes our role

On the Hosted Service we process Customer Data as processor on your instruction, and Schedule B governs it. On a Self-Hosted Deployment we process no Customer Data at all: we are the controller of account data and of Licence Telemetry, and nothing else reaches us. Schedule B is therefore not engaged by a Self-Hosted Deployment, and signing one for it would misdescribe what happens.

Archival is not erasure

9.2Archival is a suspension of processing, not an erasure. Archiving a Project under §8 does not discharge, and does not purport to discharge, any obligation you owe your own end users. You remain responsible for your own retention schedule.

9.3You may require erasure at any time. On your instruction we will delete Customer Data earlier than the periods in §8, subject only to retention we are required by law to maintain. The sixteen-month period in §8.7 is a processor retention limit that you accept on registration; it is a maximum, not a commitment to retain.

9.4We will not access Customer Data except as necessary to provide, secure or support the Service, to comply with law, or on your instruction.

10Your Rights over Personal Data

10.1Access, correction, portability and erasure requests are free of charge, self-service where technically possible, and are never gated behind a payment, a support ticket, or a Plan. This applies whether the Service is live, flagged, archived, suspended or terminated.

10.2We provide the first copy of personal data free of charge in a commonly used, machine-readable electronic format. Where you request further copies, we may charge a reasonable fee based on the administrative cost of providing them, disclosed to you in advance — and we will not do so where a request is neither manifestly unfounded nor excessive.

10.3We will not provide a slower, partial or lower-quality response to any request because you declined to purchase anything.

10.4We publish at Privacy §17 the means of making a request — email privacy@littlebit.in — the identifier we require to identify you, and the period within which we will respond, which will not exceed 30 days for rights requests and 90 days for grievances.

10.5Where we act as processor, we will forward any request we receive from your end users to you without undue delay and assist you in responding, as set out in Schedule B.

11Security and Incidents

11.1We will maintain appropriate technical and organisational measures, described in our privacy policy, including encryption in transit and at rest, access control, tenant isolation, and audit logging of privileged operations.

11.2We will notify you without undue delay, and in any event within 72 hours, of becoming aware of a personal data breach affecting Customer Data, with the information you reasonably require to meet your own notification obligations.

11.3You are responsible for the security of your own code, configuration, credentials and access policies, and for the identities and permissions you define within the Service.

12API Bay Marketplace

What publishing costs

12.1Publishing is priced in two lines, and neither is a share of your revenue. Parking is flat monthly rent for the capacity your dataset occupies, at the tier rate published on the pricing page and incorporated by Schedule A; your footprint counts tables, views, materialized views and indices, and you may sit up to 10% over your tier for one week without consequence. Traffic is metered per request served, at the published rate, from the first request. Both are netted off your earnings before payout under §12.4.

12.2If you stop paying. Your endpoints go read-only for thirty days and we notify the people subscribed to them. Parking owed is netted from your earnings first. Nothing is switched off before that window closes.

Your price, and what we take from it

12.3You set the price and you keep all of it. Any price at or above the published floor, changed with thirty days notice to the people already calling your endpoints. We take 0% commission, at any scale — this is a term of these Terms, not a rate, and it does not change with your plan. The floor exists only to cover the traffic meter in §12.1; set your price there and your data is effectively donated. Where you offer paid access, Littlebit acts as merchant of record for the transaction with the person using your data: we collect payment, remit applicable taxes, and pay you.

12.4Settlement. Payouts run monthly once your balance reaches the minimum published on the pricing page, or accumulate until you instruct otherwise. The statement is earnings less traffic, less parking, less the payment rail’s transfer fee — passed through at cost, itemised, and never marked up. Indian tax deducted at source under s. 194-O at 1% is deposited against your PAN. You remain responsible for your own tax obligations on amounts received.

12.5Refunds and chargebacks are debited against your next settlement. You retain authority to issue refunds to the people using your data.

What you warrant

12.6You warrant that you hold all rights necessary to license the data and functionality you publish; that it does not infringe any third party’s rights; and that its publication complies with all applicable law, including data protection law where it contains personal data.

12.7We may remove a listing that breaches §13, is subject to a credible third-party complaint, or that we are required by law to remove. We will tell you why, and restore it if the issue is resolved.

13Acceptable Use

13.1You must not use the Service to: break any law; infringe intellectual property or privacy rights; transmit malware; attempt to gain unauthorised access to any system; interfere with or degrade the Service or another customer’s use of it; circumvent any Quota, runtime guard, rate limit or billing mechanism; or resell the Service other than through the Marketplace.

13.2You must not artificially generate activity for the purpose of preventing a Project being flagged or archived under §8. The periods in §8 are deliberately long so that this is unnecessary.

13.3You must not submit to the Service any special category personal data, payment card data, or data subject to sector-specific regulation, unless we have agreed in writing that the Service is suitable for it.

14Suspension and Termination

14.1You may terminate at any time from within the product. Termination takes effect at the end of your current billing period. We do not require notice, a call, or an explanation.

14.2We may suspend the Service immediately where necessary to prevent material harm to the Service, to other customers, or to a third party; where required by law; or for non-payment under §6.4. We will tell you the reason, and limit the suspension in scope and duration to what is necessary.

14.3We may terminate for convenience on 60 days’ written notice, refunding unused prepaid fees pro rata.

14.4Either party may terminate for material breach not cured within 30 days of written notice.

14.5On termination, you may export Customer Data for 90 days. We will delete Customer Data at the end of that period, save for backups deleted on their ordinary cycle and data we are required by law to retain. We will not withhold your data pending payment of any sum.

14.6Sections 6 (accrued fees), 9, 10, 14.5, 15, 16, 17, 19 and 20 survive termination.

15Warranties and Disclaimers

15.1Each party warrants that it has authority to enter into these Terms.

15.2We warrant that we will provide the Service with reasonable skill and care and in accordance with its documentation.

15.3Except as expressly stated, the Service is provided “as is”. We disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement, to the fullest extent permitted by law.

15.4We do not warrant that the Service will be uninterrupted or error-free. Availability is addressed exclusively in §7.

15.5AI output. Output generated by a large language model may be inaccurate, incomplete or unsuitable. You are responsible for reviewing it before relying on it, and for any decision taken on the basis of it.

16Limitation of Liability

16.1Neither party excludes liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any liability that cannot lawfully be excluded.

16.2Neither party is liable for indirect, incidental, special or consequential loss, or for loss of profit, revenue, goodwill or anticipated savings, however arising.

16.3Our total liability is one quarter of fees, and it is paid as credit. Subject to §16.1 and §16.4, our total aggregate liability to you for all claims arising out of or in connection with these Terms is limited to the fees attributable to the calendar quarter in which the event giving rise to the claim occurred — one quarter of the fees payable for the subscription term then current, apportioned, whether you were billed monthly or annually and whenever the invoice fell due — and is satisfied by the issue of service credit. Where a claim involves more than one event, the quarter of the earliest of them applies. On a Plan carrying no fees the amount is nil, and on a Self-Hosted Deployment §16.8 applies instead. Service credits issued under §7.5 count towards this limit and do not stack on top of it. Your aggregate liability to us is limited to the same amount, save for the matters in §16.4; the credit mechanism in this clause applies only to our liability to you, and your liability is payable in money.

16.4The cap in §16.3 does not apply to your obligations under §6 (fees), §13 (acceptable use) or §17 (indemnity), or to either party’s breach of confidentiality. Those liabilities are payable in money, not credit, and the credit mechanism in §16.3 has no application to them.

16.5Loss of Customer Data. Subject to §16.1, our liability for loss or corruption of Customer Data is limited to using reasonable endeavours to restore it from our most recent backup. You are responsible for maintaining your own copies — §8.5 exists so that this is always possible.

16.6How credit works. Service credit is applied against fees that fall due after it is issued, is not redeemable for cash, and is not transferable. It does not expire while your Organisation remains active. Where the agreement has ended, or will end before the credit can be used, we pay the equivalent amount in money instead — a remedy you cannot use is not a remedy.

16.7We cannot promise you more than our infrastructure providers promise us. The Hosted Service runs on third-party cloud infrastructure named in Schedule C. Our commitments to you are bounded by the commitments those providers make to us. Where loss or unavailability is caused by the failure of such a provider, our liability is limited to passing through to you whatever remedy we obtain from them, and such downtime is Excluded Downtime under §7.4. This clause does not limit our liability for our own failure to provide the Service with reasonable skill and care under §15.2.

16.8Self-Hosted Deployments — the environment is yours. You operate the infrastructure, the database, the network, the backups, the patching and the availability, as set out in §3.8. We accept no liability for the operation, availability, performance or security of that environment, or for loss of data held in it. Our liability is limited to the software itself performing in accordance with its documentation, and is capped on the same basis as §16.3 against the licence fees attributable to the quarter in which the event occurred — one quarter of the fees payable for the licence term then current, apportioned.

16.9If this allocation of risk does not suit you, there are two routes and we would rather you took one than signed unhappily. Take the Self-Hosted Deployment and hold the whole stack yourself, or negotiate an Order Form, which ranks above these Terms under §1.3. What we will not do is commit to a remedy we cannot fund from what the Service earns.

17Indemnity

17.1We will defend you against a third-party claim that the Service, used in accordance with these Terms, infringes that party’s intellectual property rights, and will pay damages finally awarded, provided you notify us promptly, give us control of the defence, and cooperate.

17.2You will defend us against a third-party claim arising from Customer Data, from your Marketplace listings, or from your breach of §13, on the same conditions.

18Changes to These Terms

18.1We may change these Terms. For any change that materially and adversely affects you, we will give at least 30 days’ notice by email and in the product before it takes effect.

18.2If you object to a material adverse change, you may terminate under §14.1 before it takes effect and we will refund unused prepaid fees pro rata. Continued use after the effective date constitutes acceptance.

18.3Changes required by law, or to address a security risk, may take effect immediately; we will tell you as soon as practicable.

18.4We maintain a public changelog of these Terms in the changelog.

19Governing Law and Disputes

19.1These Terms are governed by the laws of India.

19.2The courts at Coimbatore, Tamil Nadu, India have exclusive jurisdiction, save that either party may seek injunctive relief in any court of competent jurisdiction.

19.3Nothing in this section deprives a consumer of the protection of mandatory provisions of the law of their country of habitual residence.

20General

20.1Entire agreement. These Terms, with their Schedules and any Order Form, are the entire agreement between us on their subject matter.

20.2Assignment. Neither party may assign without the other’s consent, except to a successor in a merger or sale of substantially all assets.

20.3Severability. If a provision is held unenforceable, the remainder stands.

20.4No waiver. Failure to enforce a provision is not a waiver of it.

20.5Publicity. We will not use your name or logo as a reference without your prior written consent.

20.6Force majeure. Neither party is liable for failure caused by an event beyond its reasonable control, provided it takes reasonable steps to mitigate.

20.7Notices to us: legal@littlebit.in, or by post to the address above. To you: the email address on your Organisation.

ASchedule A — Plans, Quotas and Rates

Incorporated by reference from the pricing page, which is the source of record. Each Plan publishes: cost dials with their overage rates; runtime guards; packaging limits; and the availability and dormancy commitments in §7 and §8. API Bay rates are incorporated the same way — the parking tiers, the traffic meter, the price floor and the payout minimum referred to in §12 are published at pricing.html#api-bay. No figure appears in the body of these Terms unless it is a commitment rather than a price: notice periods, grace windows, availability percentages, service credit percentages, the 0% commission, and statutory rates.

BSchedule B — Data Processing Addendum

Available on request, signed per customer. Email legal@littlebit.in and we will send the current addendum for signature; it is not yet published as a standing document. Until one is signed, §1.3 is read as if paragraph (b) were omitted, so these Terms and the Privacy Policy govern, and nothing in this schedule reduces what they commit us to. The addendum covers: subject matter, duration, nature and purpose; categories of data subject and personal data; processing only on documented instruction; personnel confidentiality; Article 32 security measures; sub-processor list, notice and objection rights; assistance with data subject requests (§10.5); assistance with DPIAs and breach notification (§11.2); deletion or return on termination (§14.5); audit and information rights; the §8.7 sixteen-month processor retention limit and the customer’s right to require earlier erasure (§9.3); international transfers — EU/UK Standard Contractual Clauses and UK Addendum, plus the DPDP Act position on transfers outside India; and the DPDP-specific requirement that a Data Fiduciary can cause its Data Processor to erase (s. 8(7)(b)).

CSchedule C — Sub-processors

This schedule is the same list as Privacy Schedule C, which is maintained as the single source so the two cannot drift. It names every sub-processor engaged today.

Not yet engaged or not yet published: model vendor, payment processing, email delivery, and monitoring and support tooling. Until a name appears here we will give it to you in writing within five working days of a request to the privacy contact, and no sub-processor in a new category is engaged without notice and your right to object under Privacy §7.1.

A Self-Hosted Deployment has no sub-processors. Nothing in this table touches it; only Licence Telemetry reaches us, and we share it with nobody.