Terms of Service

1. What QubicDB is

QubicDB helps you create and manage database instances through a web control plane. You connect your apps with credentials, TLS where offered, and IP allowlists you control.

Supported engines may include PostgreSQL, MariaDB, MongoDB, and Redis. Plans decide engine access, database counts, storage, isolation (shared or dedicated), backup access, and support expectations.

Using QubicDB does not transfer ownership of our software, brand, or infrastructure-you receive a limited right to use the service under your active plan.

2. Agreement

By creating an account and accepting these Terms of Service, you agree to this agreement and our Privacy Policy. If you use QubicDB for a school group, startup, or organization, you confirm that you are allowed to accept these terms for that group.

Please read these terms before storing important project data. Learning and early projects are welcome; free and lower-cost plans are not positioned as enterprise production commitments with contractual uptime guarantees.

3. Accounts, login, and settings

You must sign in with a supported social identity provider (such as Google or GitHub) and use a verified email address. You are responsible for activity under your account and for keeping your provider login secure.

In account settings you can review your profile, linked login providers, plan snapshot, accepted legal documents, and active sign-in sessions. You may revoke individual sessions or revoke other sessions while keeping the current browser signed in. Keep at least one linked login method so you can still sign in.

Please do not create many accounts to bypass plan limits. Tim QubicDB may request additional verification, slow down signups, or decline service when automated or unfair account creation is detected.

4. Plans, quotas, and fair use

Each plan shows limits in the product, such as how many databases you may run, storage allowances, engine options, isolation mode, and whether backups are available. Capacity on shared plans is shared with other users.

Paid plans may appear as Coming soon until billing is enabled. Listing a paid plan does not create a purchase obligation until checkout is available and you complete it.

Tim QubicDB may adjust limits, features, or availability so the service stays healthy. Free and entry-level resources are intended for study, portfolios, prototypes, demos, and small non-critical apps. For important work, keep your own export or backup outside QubicDB.

If storage or other metered usage exceeds your plan, Tim QubicDB may warn you, throttle features, or suspend the affected database or account until usage returns within limits or you change plans.

5. Databases, isolation, connections, and security controls

You own the content you store in your databases. You choose what to store and must keep it lawful and appropriate for the plan and environment you use.

Shared isolation means multiple tenants may share platform capacity with logical separation. Dedicated isolation means your database may run with reserved capacity sized to plan resource limits. Isolation is shown in the product for each engine on your plan.

You manage database credentials, password resets, IP allowlists, and application security. Concurrent client connections may be limited per database role; the dashboard may show recent connection and storage samples so you can stay within plan limits.

We recommend keeping highly sensitive records-such as payment card details, government identity numbers, or health data-off free or shared plans unless you accept the limits of that environment and can rotate credentials when needed. Export or copy important data regularly. Data may not remain available after account closure, safety actions, maintenance, overage suspension, archival, or service changes.

6. Backups

Backup create and restore features are available only when your active plan enables them. Free and other plans without backup access require you to export data yourself.

Even when backups are enabled, they are an operational aid-not a guarantee of complete recovery for every failure mode. Keep your own copies of work that matters.

7. Status page and operational labels

QubicDB may publish a public or authenticated status page with uptime and health information for platform services. Status information is informational and best-effort. It is not a service-level agreement (SLA), warranty, or promise of uninterrupted service.

Operational labels such as a server name or instance code may appear in the product or status views to help you identify where a database runs. Those labels do not expose your database contents.

8. Support

Signed-in users may open support tickets in the product to report provisioning, connection, plan, or account issues. Support on the free plan is best-effort and may be limited.

Paid plans may describe different support expectations in the product or plan materials when those plans are active for purchase.

9. Acceptable use

Use QubicDB only for lawful purposes. Respect other users who share this platform with you.

Please do not attempt unauthorized access; disrupt the platform or other tenants; interfere with security or availability; mine cryptocurrency; run spam or harmful automation; host illegal content; overload the service; or bypass plan limits, connection limits, allowlists, abuse controls, or session controls.

Tim QubicDB may review operational signals (such as unusual traffic, repeated failed access, connection spikes, or resource usage) and apply abuse policies (including temporary blocks) to keep the platform stable. This is not permission to use your private application content for advertising.

10. Enforcement and safety actions

To protect the community and Tim QubicDB, we may warn, slow, restrict, suspend, archive, or close accounts or databases that appear abusive, unsafe, long inactive, over plan limits, or in breach of these terms.

In urgent cases-such as clear security risk, illegal content reports, or activity that harms other users-Tim QubicDB may act first and share more detail afterward when practical.

If access is removed for safety, overage, archival, or capacity reasons, free-tier and shared-plan data may not be kept indefinitely. Where reasonable, Tim QubicDB will try to give notice before planned removals that are not emergency safety actions.

11. Availability

Tim QubicDB works to keep the service useful and online, but availability on free and shared plans is best-effort. Maintenance, provider issues, capacity limits, or server health problems may interrupt service without a formal uptime guarantee.

12. Intellectual property

QubicDB branding, product UI, documentation, and platform code remain the property of Tim QubicDB. Your database contents remain yours.

You grant Tim QubicDB a limited license to host, process, collect operational metrics, back up (if enabled for your plan), and secure your service data only as needed to operate and protect QubicDB.

13. Disclaimers and limitation of liability

To the fullest extent permitted by law, QubicDB and Tim QubicDB provide the service without warranties of merchantability, fitness for a particular purpose, uninterrupted access, or error-free operation.

Because shared capacity and best-effort status reporting can vary, temporary interruption, incomplete recovery, or delayed metrics can happen. Keep your own copies of work that matters to you.

To the maximum extent allowed by law, QubicDB and Tim QubicDB are not liable for indirect, incidental, special, or consequential damages arising from use of the service, including lost profits, unavailable project data, or business interruption-even if we were told such issues were possible.

Where liability cannot be fully excluded, total liability is limited to the greater of (a) the amount you paid us for the service in the three months before the claim, or (b) zero if you used only the free plan. Your main remedy is to stop using the service or move your data elsewhere.

14. Indemnity

To the extent permitted by law, you agree to defend and hold harmless QubicDB and Tim QubicDB from claims, damages, and costs arising from your content, your misuse of the service, or your violation of these terms or applicable law.

15. Changes and contact

Tim QubicDB may update these terms by publishing a new version. For material changes, we may ask you to review and accept the updated document in the product before continuing with restricted actions. Accepted versions appear in your account settings.

If a section is found unenforceable, the rest still applies. Questions about these terms can be sent through in-product support or the contact channels listed on the QubicDB website.