Terms of Service

Terms of Service

Managed SaaS, closed source, EU-resident by default. Soft quotas and billing cap default-on so a traffic spike never becomes a five-figure invoice.

Last updated · 19 May 2026

01. Service description

Gurulu provides a managed SaaS Truth Layer for product analytics — event ingestion, identity resolution, event health, attribution, an event registry, SDKs, a CLI, an MCP server and a dashboard. Gurulu is offered exclusively as a managed service. We do not offer a customer-facing self-hosted distribution. Any orchestration tooling we publish is for our own operations, not a supported deployment model. The platform is closed source; our public NPM packages cover the SDKs, CLI and MCP server only.

02. Acceptable use

You agree not to: • Abuse the free tier (1 million events / month) by sharding workloads across multiple workspaces. • Track personally identifiable information without lawful basis or in violation of the consent model. • Reverse engineer, decompile or attempt to derive the source code of the closed-source platform components. • Use Gurulu to ingest data that violates applicable law (CSAM, sanctions, prohibited content). • Run penetration tests against shared infrastructure without prior written agreement. Violation may result in immediate suspension. We will warn and offer a 7-day cure period before terminating, except where the violation is egregious or unlawful.

03. Accounts & access

Authentication is via magic link (primary), Google OAuth or GitHub OAuth. There are no passwords. The workspace owner is responsible for managing seat access, RBAC roles, API key rotation and SSO configuration. You must keep your authentication factors secure. If a magic link is intercepted or an API key leaked, rotate it immediately from the dashboard or via the CLI. Gurulu is not liable for losses caused by compromised credentials you failed to rotate after discovery.

04. Pricing & billing

Gurulu offers two plans: Free and Pay-as-you-go. The Free plan is genuinely free — 2 million events / month, all features on, no credit card required, and it never expires. Pay-as-you-go is usage-based (usage-based, with volume discounts) with a soft quota and a billing cap default-on. When you reach 80% of your quota you receive a warning; when you reach 100% the billing cap blocks paid overage by default — events keep ingesting on a soft-degraded path until you raise the cap manually. Annual billing is discounted 20%. 30-day unconditional refund. If you are unhappy within the first 30 days of a paid plan, email billing@gurulu.io and we refund the full amount, no questions asked.

05. Data ownership

Customer event data — every event you send us — is yours. Gurulu acts as a sub-processor for that data, governed by the Data Processing Addendum. You can export your data at any time via the dashboard, the CLI or the API. We do not hold your data hostage. Gurulu owns the platform, the closed-source pipeline, the dashboards and the derived service telemetry. Aggregate, anonymized usage statistics may be used to improve the product.

06. Service availability

We target 99.9% uptime on the data plane (ingest) starting at the end of Phase 3. During the Phase 1 / Phase 2 beta period, we do not commit to an SLA — but we publish status updates and incident postmortems at /status. Planned maintenance is announced at least 72 hours in advance and scheduled during EU low-traffic windows when possible. Emergency maintenance may happen without notice if a security or stability issue requires it.

07. Termination

You can terminate your subscription at any time from the dashboard. After termination you have a 30-day grace window to export your data; after that, data is deleted on the next scheduled erasure run (subject to the 35-day backup retention and the 7-year audit log retention). We may terminate for cause if you breach these Terms — we will provide a 7-day cure period for material non-egregious breaches. For egregious breaches (abuse, unlawful content, security threat) termination is immediate.

08. Warranty disclaimer

Gurulu is provided 'as is' and 'as available'. To the maximum extent permitted by applicable law, we disclaim all implied warranties of merchantability, fitness for a particular purpose and non-infringement. We do not warrant that the service will be uninterrupted or error-free. Beta features (clearly labeled in the dashboard) are provided without any warranty.

09. Liability cap

To the maximum extent permitted by law, our aggregate liability under these Terms is capped at the amount you paid us in the twelve (12) months preceding the event giving rise to the claim. We are not liable for indirect, incidental, special, consequential or punitive damages, including lost profits or lost data, even if advised of their possibility. These caps do not apply to liability that cannot be excluded under applicable law (e.g. gross negligence, intentional misconduct, GDPR / KVKK statutory damages).

10. Governing law

These Terms are governed by the laws of Türkiye. Any dispute that cannot be resolved amicably will be submitted to the exclusive jurisdiction of the Istanbul Çağlayan courts. EU consumers retain the protection of their local mandatory consumer law. (Placeholder — final jurisdiction subject to legal review before public launch.)

11. Changes to these Terms

We may update these Terms as the product evolves. Material changes will be announced via email to workspace owners at least 30 days before they take effect, and the new version will be published at /terms with a revised 'Last updated' date. Continued use of the service after the effective date constitutes acceptance of the updated Terms.

Legal questions · legal@gurulu.io

Terms of Service — Gurulu