Terms & support
Get help with Checktide
Email support@checktide.app. Every message gets a reply.
We don't set a deadline for the fix itself — we'll tell you what we know and what happens next.
Please do not send passwords, access tokens or production records by email.
Checktide Service Terms
Effective November 14, 2026
1. What Checktide does
Checktide verifies whether the behavior described in a Jira issue holds in an application environment you designate. When you open Checktide on an issue, we read it and propose the checks we can run; you start a verification by confirming them, and we run the checks and publish a report with observations and evidence. Checks are designed and carried out by people at Checktide, with Checktide's own tools; the conclusions are ours and are based on what we observed in your environment at the time of testing.
Checktide reads Jira data only through the permissions you granted at installation. Checktide never changes your Jira workflow or fields. On an issue where a verification was started, it adds a short comment that mentions the person who started it when it has a question, when the report is ready, when the report is corrected, when it cannot take the request on or stops it with nothing published, and when you cancel it while one of our questions is waiting for your answer; it changes nothing else on the issue. Those comments are part of the issue: they remain if our records are deleted or the app is uninstalled, and you can delete them like any other comment.
Reading an issue to propose checks. Checktide reads an issue's summary and description when someone opens Checktide on it while your site can start a verification — it still has credits, or this month's free verification. It uses them to propose what it can check and to say what it could not determine. It drafts a new proposal when the summary or description has changed since the last one, after a draft that failed, or when we update how Checktide reads issues. Nothing is tested and nothing is charged until you start a verification. The proposal is drafted by an AI service inside the Atlassian platform, so the issue's content does not go to any third-party AI service and stays within Atlassian cloud; that processing may take place outside your site's data residency region. We do not use the issue's content to train models. The proposal is kept with the issue in the Atlassian-hosted storage provided to the app, which follows your site's data residency location, and replaced when a new one is drafted. It is removed when you ask us to delete it; if you uninstall the app, Atlassian keeps the app's storage, the proposal included, for 28 days and then deletes it.
2. What you provide
- An environment you are entitled to have tested. You confirm that the environment, websites and accounts you provide may be used for testing, that you have authority to grant that use, and that testing there is permitted by your organization's policies and by any third party whose systems or data it touches.
- Test access and identities. Where testing needs accounts, data or network access, you provide test identities and data that are not production customer data unless you explicitly designate otherwise. Where a website needs a sign-in, you give us a test account on the environment's page in Checktide: its username and password, or an invitation to Checktide's test address, for which we set our own password so that you never send one; a password we set is deleted when that request closes, or earlier when you remove the account. The password is stored encrypted in Checktide's storage on your own Atlassian site. For each verification that needs it, the person at Checktide doing that verification takes one copy and deletes it when the verification ends, and the deletion is recorded; Checktide keeps the password nowhere else. You can change or remove the account on the environment's page at any time. Where your website lets anyone sign up and you have not given us an account, we sign up for a test account of our own. Do not put credentials in Jira comments or issue fields: Checktide reads and freezes the issue's comments and fields as part of the scope, so anything written there is captured in our records and we cannot detect or remove it afterwards. Checktide never asks for credentials in Jira.
- Notes and files. With the start of a verification you may send a note and up to six files (25 MB in all), and with an answer to one of our questions, text and files; a file comes from your device or is a copy of a file already on the issue. We read them for that verification only, and the report quotes from a file only what a check relies on. Keep passwords and tokens out of notes and files.
- The permitted actions. Testing may create, change or delete data in the environment (for example placing or cancelling orders). Before we test, you confirm which actions are permitted, and we do not exceed them. An action you have not permitted is not taken; you can permit it later from the issue. Where a check would require an action you did not permit, we record the check as not verified.
- Answers to consequential questions. We ask only when a gap changes what we would test or conclude, and we ask in a comment on the issue. Until you answer, the affected checks are not verified.
3. What we deliver
- Scope confirmation before testing: what we understood, which checks we will run, which actions they take in your environment, and what we could not resolve from your materials. You confirm it when you start the verification; if we could not propose checks before you started, we show them on the issue before we test. We do not add or remove a check you asked for without asking you first.
- A report for the confirmed scope and target version: for each check, the precondition, action, expected and observed behavior, evidence, and a verdict; a business-level conclusion; the checks that could not be verified and why; and the environment and version tested. A person at Checktide checks and confirms each report against its evidence before we publish it.
- One retest of the same scope on a corrected version, requested within 14 days of delivery, included in the price of the verification. A retest that reaches no result does not use it.
- Updates. We do not promise a fixed time for accepting a verification request or delivering its report, including a retest or a verification of our demo shop. The request shows its actual state: received, waiting for your answer, answer received, work in progress, or report published, as those events happen. If we cannot take a request on, we tell you in a comment on the issue, and nothing is charged. If we need to ask you something, we ask in a comment on the issue. We also comment when a report is ready or corrected.
- You can cancel a verification from the issue until its first report is published; a cancelled verification is not charged and uses no free verification.
Evidence and the report stay available for at least the retest window and for as long as Checktide remains installed on your site, unless you ask us to delete our records of the request they belong to, which also ends that request's included retest. If you uninstall the app, Atlassian keeps its storage, reports and evidence included, for 28 days and then deletes it. Reports are read inside Jira.
4. Prices, credits and payment
- Checktide is sold as a subscription through the Atlassian Marketplace, paid via Atlassian. Each subscription month grants credits to your site; one US dollar of subscription equals one credit. Credits you do not use carry over; they stay with your site and can be spent whenever it has an active subscription, while Checktide is installed on your site.
- Free for 30 days, and one free verification every month. During the trial that the Atlassian Marketplace gives your site, Checktide grants it the credits of a month's subscription for each month of the trial, at no charge. Every site also gets one free verification each calendar month (UTC), whether or not it has a subscription, starting in the month Checktide is installed; an unused one lapses when its month ends. Verifications of our demo shop, demo.checktide.app, are free, up to three a calendar month for each site: they use neither credits nor your monthly free verification.
- A verification is charged once, after delivery, for the time we spend working on it: $0.30 (0.30 credits) a minute, billed by the second and never rounded up. Its report lists each part of the work, such as reading your issue, each check and writing the report, with its time and credits; each part is charged $0.005 a second, rounded down to the cent, and the report shows the work step by step. Time spent waiting for you, such as for an answer or an invitation, is not counted; time spent waiting for your environment to answer, or for a test account you gave us to sign in again, is shown but not charged, and a check we run again because of it is charged once, for the run that completes. Time lost to our own errors, such as a failed tool, a misreading or a corrected report, is shown but not charged. So is a check your issue asked for that our reading missed and we added when we took the verification on. The charge is never more than your available balance at that time: if a verification takes more than you have left, the rest is on us. Nothing is set aside when a verification starts: you can start one whenever your site still has credits or a free verification.
- Clarifications, corrections of our own mistakes, the included retest, and any checks we add beyond the ones you asked for are not charged. Asking us to re-check a verdict against its evidence is free and does not use the included retest.
- If we correct or withdraw a report because of a mistake of ours, or cannot check something you asked for because of a fault on our side, that verification is free: anything deducted for it is returned, and no free verification is used.
- A verification is charged only when it reaches a result on at least one check you asked for. One that finds defects, or that reaches a result on some checks and says why it could not on the others, is a completed verification.
- A free verification covers one complete verification and is used only after complete delivery. When a verification could use either, the free verification is used unless you choose credits.
- Subscription billing, refunds of subscription fees and cancellation follow the Atlassian Marketplace terms; Checktide credits are Checktide's own entitlement and are not refunded in cash. If a subscription payment is refunded, the credits it granted that you have not used are withdrawn.
5. Responsibility and limits
- We test what you authorized, where you authorized it. Effects of permitted actions on your environment (such as test records created there) are yours to manage; we do not clean up environments unless agreed.
- We are not responsible for effects on systems you did not designate for testing, or that result from access or data you provided in breach of Section 2.
- Usage limits. Checktide runs on the Atlassian platform, within its limits. Reading your issues to propose checks is free; occasionally the checks are proposed only when you start the verification. A verification starts only while your site still has credits or a free verification, except on our demo shop (Section 4). If a platform limit stops a step of a verification, the issue says so, and that verification is treated as a fault on our side (Section 4).
- A report states what we observed at the time, in the version tested. It is not a certification of the application, a guarantee that no other defects exist, or advice on release decisions.
- To the extent permitted by law, Checktide's total liability under these terms is limited to the fees paid for the verification concerned.
6. Confidentiality and data
- Issue content we read to propose checks, materials you provide, including the notes and files you send, environment details, credentials, observations and evidence are used only to propose, perform and document verifications. We do not use them to train models, and we never submit the conversations of the AI tooling we use during delivery to the provider as feedback. Materials are not shared with third parties except the processors our privacy notice names or describes; a list of our sub-processors is available on request.
- Access to an online report follows the Jira permissions of the issue it belongs to. A published report is not withheld solely because your balance is zero, you cannot start a new verification, or its payment or credits status is unconfirmed or unsettled.
- Reports and evidence are stored in the Atlassian-hosted storage provided to the app. If that ever changes, this section and the privacy notice change first.
7. Term and changes
- These terms apply for as long as Checktide is installed on your site and to any verification requested while it was installed.
- We may update these terms; material changes are announced on the Marketplace listing before they apply to new requests. Requests already confirmed keep the terms they were confirmed under.
- Checktide is run by YIGOALQCTECHNOLOGY CO., LIMITED (億高企倡科技有限公司), a company registered in Hong Kong.
- Governing law and venue: the laws and courts of Hong Kong.