This English version is a reference translation. The Japanese version is the authoritative text and prevails in the event of any discrepancy.
These Terms of Service ("Terms") set out the conditions of the contract between the operator of the database monitoring service Scandock (the "Service"), being the business listed on our Company page ("we" or "us"), and the business that uses the Service (the "Customer").
The Service continuously observes databases whose connections the Customer has registered, and uses AI to design what to monitor, judge anomalies, investigate causes, and propose remediation actions the Customer has registered in advance. The following provisions reflect the nature of a service that works against production databases.
When registering an account, the Customer agrees to these Terms and the Privacy Policy and confirms that it uses the Service as a business. We record the date and time of that agreement and the version of these Terms agreed to.
The demo published on our website shows fictional data only inside your browser and does not handle any Customer Data.
The Service is provided only to companies and sole proprietors using it for their business. It may not be used as a consumer.
Anyone applying for the Service represents and warrants that the Customer is a business, that it uses the Service for business purposes, and that they have the authority to agree to these Terms on behalf of the Customer.
The Customer represents and warrants that it has legitimate authority to connect to the databases it registers for monitoring and investigation and to create read-only users on them. Before registering a database managed by a third party, the Customer must obtain that third party's consent.
A contract for the Service is formed between the Customer and us for each project on the Service. Monitoring targets, memory, actions, and billing are all managed per project.
The project owner manages the contract, billing, and members on behalf of the Customer. Projects have owner, admin, member, and viewer roles, and permissions are limited by role.
Members invited to a project use the Service on behalf of the Customer. Actions taken by members are deemed actions of the Customer, and the Customer is responsible for ensuring its members comply with these Terms.
The Customer is responsible for managing accounts and credentials. We are not liable for damage caused by inadequate management.
If information the Customer has registered (such as the project name, members' email addresses, or billing details) changes, the Customer will update it on the Service without delay.
We may send the Customer notices necessary for operating the Service, and it may not be possible to opt out of them.
Connection strings the Customer registers are stored encrypted, and their plaintext is never written to logs, screens, API responses, or AI inputs. If a connection string with write privileges (an "admin connection") is registered, we automatically create a read-only user for monitoring and investigation and use only that user from then on. Admin connections are kept encrypted and used only to create and drop the read-only user and to run actions the Customer has registered to run on the admin connection.
Queries generated by the AI for monitoring and investigation run through the read-only connection and are limited to single read-only statements appropriate to the database type (SELECT, EXPLAIN, and so on). Writes to the target database happen only through actions the Customer has registered in advance.
The Customer may register Cloudflare D1 databases of Cloudflare, Inc. through authorization via Cloudflare OAuth. In that case, we access the registered database through the Cloudflare API using only the read permissions granted by the authorization. Although the authorization is granted per Cloudflare account, we do not use databases other than the registered one for monitoring or investigation. The Customer may revoke the authorization on Cloudflare at any time, after which connections relying on it can no longer be monitored.
The Customer may register Google BigQuery data of Google LLC through authorization via Google OAuth. In that case, we run queries through the Google API in the Google Cloud project the Customer selects, using only the BigQuery read permission granted by the authorization. BigQuery charges arising from these queries are billed to that project and borne by the Customer (we cap the data billed per query). Although the authorization extends to the data the authorizing Google account can access, we run monitoring and investigation queries only in the registered project. The Customer may revoke the authorization at any time from their Google Account settings, after which connections relying on it can no longer be monitored.
Because the Service runs queries against the target database, it increases load on it. The Customer can set and stop the monitoring interval and content, and judges the effect of that load at its own responsibility. We are not liable for performance degradation or failures of the target database caused by monitoring queries.
The Customer can connect a database that is not exposed to the internet through Cloudflare Tunnel, provided by Cloudflare, Inc. In that case, we create a tunnel for the Customer and register the database address the Customer enters in the tunnel's configuration. We also create hostnames leading to the tunnel on a dedicated domain we manage, and use Cloudflare Access to reject connections from anyone other than us.
The Customer is responsible for installing, updating, and stopping the connector (cloudflared) in its environment, for managing the token used to start it, and for protecting the network between the connector and the database. Traffic between the connector and the database is not encrypted by the Service.
When a tunnel or project is deleted, we delete the tunnel and its DNS records on Cloudflare. The Customer will stop and remove the connector in its own environment.
The Service can run only actions the Customer has registered in advance. Actions that use the admin connection always require the Customer's approval before they run. Other actions (including running read-only queries and sending notifications or creating records in integrated services) also require approval by default, and run without approval only when the project owner has enabled automatic execution for them.
Approving actions and enabling automatic execution are the Customer's decisions. The Customer is responsible for the content of registered actions, the results of running approved or automatically executed actions (including records created in integrated services), and preparing ways to roll them back. We are not liable for data changes, data loss, or other results of running actions.
Monitoring design, anomaly judgment, cause investigation, and action proposals in the Service are produced by automated processing using large language models. They may contain errors and do not guarantee that anomalies will be detected. Both missed detections and false positives can occur.
Anomalies the AI judges to be false positives may be closed as incidents without notifying the Customer. The AI also records, updates, and deletes facts learned during investigations and conversations as the project's memory and uses them in later judgments. The Customer can review closed incidents and memory on the Service, and can edit and delete memory.
The Service supports the Customer's monitoring and operations; it does not replace them. Final judgments and responses are the Customer's responsibility. Our liability for results caused by a notification not being sent, or by an incorrect notification or proposal, due to errors in AI judgments or memory is as set out in Article 15.
In these Terms, "Customer Data" means connection strings, schema information of target databases, values returned by monitoring queries, queries run for investigation and their results, records of AI judgments and investigations, conversation history, memory, and instructions and other information the Customer enters into the Service.
The Customer remains responsible for managing the target databases and the data in them while using the Service. We handle Customer Data on the Customer's behalf and use it only to provide the Service. We do not use it for any other purpose (including analysis to improve our services or training AI models).
To the extent necessary to provide the Service, we entrust processing of Customer Data to external providers ("Sub-processors"). Sub-processors and their countries are listed in the Privacy Policy. We require Sub-processors to apply security equivalent to these Terms, and we notify the Customer in advance on the Service or by its registered email address before adding or changing a Sub-processor.
We take security measures to prevent leakage, loss, or damage of Customer Data, as described on our Security page and in the Privacy Policy. If the Customer, as the entrusting party, makes a reasonable request to supervise us (such as answering a security checklist), we provide the necessary information to the extent it does not compromise the security of the Service.
If we become aware of leakage, loss, or damage of Customer Data, or the risk of it, we notify the Customer without delay and work to investigate the cause, prevent further harm, and prevent recurrence. We also provide information and cooperation the Customer needs to make reports or notify individuals under applicable laws.
If the monitoring targets include personal information or other sensitive information, the Customer is responsible for complying with applicable laws and contractual obligations regarding its handling. The Customer can adjust the scope of monitoring through monitor item settings.
Monitor item value history and audit logs are deleted daily once they exceed the period set by the plan. For projects without an active contract, the period of their previous plan applies for 30 days after the contract ends, and the shortest plan's period applies after that. AI judgment history is deleted after 30 days. Incidents, investigation records, conversation history, memory, and action records are kept without a set period until the Customer deletes the connection, conversation, memory, or project.
When a connection is deleted, we delete its monitor items, incidents, and investigation records. When a project is deleted, we delete that project's Customer Data, except information we are required by law to retain (such as billing records). Deleted data may remain in Sub-processors' backups for a certain period.
The Customer and we will treat as confidential any non-public technical or business information disclosed by the other party in connection with the Service, and Customer Data ("Confidential Information"); will not use it for purposes other than providing or using the Service; and will not disclose it to third parties without the other party's prior consent.
Notwithstanding the preceding paragraph, we may disclose Confidential Information to the Sub-processors described in Article 7 to the extent necessary, after imposing obligations equivalent to this Article on them. Either party may also disclose Confidential Information to the extent necessary under laws or orders of courts or government agencies.
Confidential Information does not include information that was public when disclosed, became public after disclosure through no fault of the recipient, was already held by the recipient when disclosed, was obtained from a third party with legitimate authority without a confidentiality obligation, or was independently developed by the recipient without using the Confidential Information.
Intellectual property rights in the Service and its software, documents, and screens belong to us or to those who have licensed them to us. These Terms do not license those rights to the Customer beyond the right to use the Service in accordance with these Terms.
Rights in Customer Data, and in monitor items, queries, investigation conclusions, memory, and other output the Service generates for the Customer, belong to the Customer, except those belonging to us or third parties. We may use them to the extent necessary to provide the Service.
If the Customer gives us opinions or requests about the Service, we may freely use them to improve the Service. This does not include Customer Data or Confidential Information.
We do not guarantee availability, response times, or other service levels of the Service. However, if we and the Customer separately agree on service levels in writing (for example, in an individual Enterprise plan contract), that agreement applies.
The Service is paid. Fees and limits for each plan, and usage-based fees for exceeding limits, are as displayed on the Service. Displayed prices exclude tax. Consumption tax is charged separately in accordance with the law, based on the billing details entered at sign-up (it may not be charged to businesses outside Japan).
Payment is by credit card (Stripe). Annual subscriptions may also be paid by bank transfer against an invoice. The Customer may choose monthly or annual billing (annual billing only for plans that offer it). For credit card payment, the first payment is charged at sign-up, and the subscription then renews and is charged automatically from that date, every month for monthly billing and every year for annual billing. For invoice payment, we issue an invoice at sign-up (or at the end of the trial, if any) and at each annual renewal, and the Customer shall pay by transfer to the account stated on the invoice by its due date (30 days after issue). Bank transfer fees are borne by the Customer. If payment is not confirmed by the due date, the subscription ceases to be active. If a promotion code we issue is applied, fees are discounted according to the code's conditions. Payment methods for the Enterprise plan are set out in the individual contract.
The Starter and Business plans include a free trial, for the number of days displayed on the Service, on a project's first subscription only. When subscribing by credit card, a credit card is required to start a trial. Unless the Customer cancels by the end of the trial, the subscription automatically converts to a paid contract on the day after the trial ends and is billed under the chosen billing interval and payment method. No fees are charged if the Customer cancels during the trial. During the trial, monitor items cannot be added and automatic investigations cannot be run beyond the plan's limits.
Database connections and members cannot be added beyond the plan's limits. If monitor items exceed the plan's limit, a usage fee is charged at the plan's unit price, prorated by the number of items over the limit and the period; if automatic investigations exceed the plan's limit, a usage fee is charged per investigation. Usage fees are billed monthly, including on annual contracts. The automatic investigations included in a plan are counted per month (on annual contracts, per one-month period from the start date) as the number of incidents opened in that period, including those the AI closed as false positives.
Projects without an active contract (including when a payment has failed and the contract is no longer active) are not monitored, judged, or investigated.
When upgrading to a higher plan, the difference is charged at that time. When downgrading to a lower plan, the difference is credited to subsequent invoices. Changes between monthly and annual billing take effect at the end of the current billing period.
Due to the nature of the service, fees for periods already provided are not refunded, including on a prorated basis if the Customer cancels mid-period. This does not apply where laws provide otherwise or where we could not provide the Service for reasons attributable to us.
We may change fees and plan contents. We will notify the Customer at least 30 days before the effective date, and changes apply to renewals on or after that date.
Interfering with the Service, accessing it by unspecified means, probing for vulnerabilities, reverse engineering, scraping, registering databases without authority, registering an IP address one has no authority over as a tunnel target, using the Service to infringe others' rights, and violating laws are prohibited.
We may change, add, or discontinue features of the Service, and temporarily suspend it for maintenance or incident response. For significant changes, we will notify the Customer in advance where possible. If we discontinue the entire Service, we will notify the Customer at least 30 days before the end date.
The Customer may cancel the contract at any time. Cancellation takes effect at the end of the current billing period (for annual contracts, the annual term); the Customer can use the Service until then, and the subscription will not renew. Cancellation during a free trial takes effect at the end of the trial.
After the contract ends, the Customer can delete its projects and account. Until a project is deleted, its Customer Data is retained as set out in Article 7. The sole owner of a project with other members cannot delete their account until they transfer ownership or delete the project. Before deleting a project, the Customer should save any information it can obtain from the Service (such as audit log CSV exports) as needed.
We may suspend use of the Service if the Customer violates these Terms, fails to pay fees, or we otherwise determine there is an obstacle to operating the Service. If a violation is not remedied within a reasonable period, we may terminate the contract. In urgent cases, we may suspend without prior notice.
Articles 3 through 9, Article 11 (regarding unpaid fees), Articles 14 through 16, and Articles 18 and 19 survive the end of the contract.
We are not liable for failure to perform obligations under these Terms due to natural disasters, war, terrorism, epidemics, the enactment or amendment of laws, orders of public authorities, failures of communication lines or power, failures of external providers we use (such as AI model, infrastructure, database, and payment providers), or other causes beyond our reasonable control.
The Service is provided "as is", and we make no warranty of any kind, express or implied, regarding its completeness, accuracy, fitness for a particular purpose, or detection of anomalies in monitoring targets.
We are not liable for indirect, incidental, special, or consequential damages, lost profits, or data loss arising from use of the Service. Where we are liable for damages, our total liability is limited to the total fees the Customer actually paid us in the 12 months before the damage occurred.
The preceding paragraph and other provisions of these Terms excluding our liability do not apply to damage caused by our intent or gross negligence.
The Customer and we each represent and warrant that neither they nor their officers are an organized crime group, a member of one, a person for whom five years have not passed since ceasing to be a member, a quasi-member, a company related to such a group, a corporate racketeer, a racketeer disguised as a social or political movement, a specialized intellectual crime group, or any equivalent person ("Antisocial Forces"), and that they have no socially reprehensible relationship with Antisocial Forces.
The Customer and we each covenant that they will not, themselves or through third parties, make violent demands, make unreasonable demands beyond legal responsibility, use threatening words or violence in connection with transactions, damage the other party's credibility or obstruct its business by spreading rumors, fraud, or force, or engage in any equivalent conduct.
If the other party breaches either of the preceding two paragraphs, the Customer or we may terminate the contract immediately upon notice. The terminating party is not liable for damage the other party suffers as a result.
We may change these Terms under Article 548-4 of the Civil Code of Japan when either of the following applies: (1) the change conforms to the general interests of Customers; or (2) the change does not contradict the purpose of the contract and is reasonable in light of the necessity of the change, the appropriateness of the changed content, and other circumstances relating to the change.
When changing these Terms, we set an effective date and, by that date, publicize that these Terms will change, the changed content, and the effective date by posting on our website or by other means. For changes that are adverse to the Customer, we notify the Customer by its registered email address or on the Service at least 30 days before the effective date.
If we and the Customer separately agree in writing regarding the Service (for example, in an individual Enterprise plan contract), that agreement takes precedence over these Terms.
Neither the Customer nor we may assign its position or rights and obligations under these Terms to a third party without the other party's prior written consent. However, if we transfer the business relating to the Service to a third party (including by company split or any other form of business transfer), we may transfer our position, rights and obligations under these Terms, and Customer Data to the transferee, and the Customer consents to this in advance.
If any part of these Terms is held invalid, the remaining provisions remain in effect. Our failure to exercise a right under these Terms does not constitute a waiver of that right.
These Terms are governed by the laws of Japan. The Tokyo District Court has exclusive jurisdiction as the court of first instance for disputes between us and the Customer relating to the Service.
Effective date: October 29, 2026
Last revised: October 31, 2026