Extended Cookies & Privacy Consent

We use cookies to analyze marketing traffic, monitor system errors, and track conversion events. Hashed/anonymized IPs are used by default unless you accept full tracking.

F
FormsDB Engine Back to Home
Legal Governance & Trust

Terms of Service

Version 2.4 • Last updated June 25, 2026 • Isolated Database Sandbox Architecture

Document Outline

Key Takeaways

✓ 100% File Isolation: Separate physical SQLite containers per tenant. No mixed storage.
✓ GDPR & CCPA Compliant: Zero tracking telemetry, instant self-service database purges.
✓ Zero-Bloat Footprint: Fast load times, system font stacks, zero analytics scripts.

Terms of Service

Effective Date: June 25, 2026

Welcome to FormsDB. By accessing our platform, website, API gateway, or sandbox simulators, you agree to comply with and be bound by the following Terms of Service.

1. Credit Economy & FSR Calculations

FormsDB operates under a dynamic credit economy model:

  • Calculated Submission Cost: Every form submission consumes credits based on field complexity (FSR).
  • Base Rate: A baseline routing credit rate applies to every connection.
  • Top-up & Depletion: When your balance drops below the threshold, the system automatically locks inputs into encrypted tables until a top-up is triggered.

2. Tenant Isolation & Use of Platform

  • You are solely responsible for the configuration and payloads submitted to your workspace endpoint.
  • You agree not to abuse the API gateway or simulate malicious high-volume request attacks.
  • FormsDB reserves the right to lock connections that repeatedly violate rate-limiting middleware boundaries.

3. Storage SLA & Security

  • We maintain a 99.9% uptime SLA for workspace SQLite file mounts.
  • Files are isolated, preventing cross-tenant read/write exploits.
  • In the event of subscription termination, all isolated database containers will be scheduled for permanent deletion.

4. Disclaimers and Limitations

  • The platform is provided "as is" and "as available".
  • FormsDB is not liable for data loss due to workspace secret exposure or client-side integration failures.