Privacy notice
This webpage
Our web host may see your IP address and browser details to deliver and secure this page. The page itself has no contact form, scripts or tracking.
Version of November 11, 2026.
Who we are. Checktide is operated by YIGOALQCTECHNOLOGY CO., LIMITED, a company registered in Hong Kong (contact: support@checktide.app). This notice explains what Checktide reads, keeps and shares when you install the app from the Atlassian Marketplace and ask for a verification: Checktide testing, on your running site, what an issue describes.
Three things to know first.
- Every report is checked against its evidence and confirmed by a person at Checktide before it is published. Checktide does not outsource or crowdsource the work.
- A test account's password is stored encrypted in Checktide's storage on your own Atlassian site. Checktide's own tooling types it in when a verification signs in; no AI service ever receives it, and it is never written in a report or recording.
- In Jira, Checktide reads an issue only when someone opens Checktide on it or has started a verification there: its summary and description, to propose checks; and, for a started verification, its comments, the files you choose to attach, and the key, summary and status of issues linked to it. It never scans your other issues.
What Checktide reads in Jira
The app asks for these permissions, by the names your Jira administrator sees: View Jira issue data; Create and update comments and Create and update comment properties; View comments, View comment properties, View groups, View projects, View project roles, View users, View avatars and View application roles; and storage for its own records on your site. Jira requires the "View" permissions of any app that adds a comment. Checktide has no permission to create, edit or delete your issues. View application roles lets the app read how many users Atlassian bills Checktide for on your site, which sets the credits each month of your subscription brings; it reads that count with the app's own access, keeps only the credits, and sends the count nowhere.
Comment properties are two small labels the app puts on its own comments and on nothing else: one keeps the comment internal on a service-desk project, so your own customers never see it; the other stops the app from posting the same comment twice. Neither holds anything from your Jira.
It changes nothing in your Jira except one thing: 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 a 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. A comment holds fixed words and, for a report, its verdict, headline and conclusion with a link to it; never your words or the text of a question. Those comments are part of the issue: they stay if you later ask us to delete our records or uninstall the app, and you can delete them like any other comment.
Checktide reads an issue's summary and description — and counts its comments, which it reads only when it takes the verification on — to propose what it can check only when someone opens Checktide on that issue and your site can start a verification (it still has credits or a free verification), or when they choose to verify it on our demo shop. It reads that text again only when it has changed, after a draft that failed, or when we update how Checktide reads issues; reading is free, and occasionally the checks are proposed only when you start the verification; nothing is tested and nothing is charged at that point. From the same text it picks out the website addresses the issue mentions, to suggest which of your saved environments to verify on; they are shown to the person who opened Checktide there and kept nowhere. When you start a verification, it also reads, for that issue only:
- the issue's summary, description and last-updated time;
- comments the app can see, including ones restricted to a role or group, with who wrote them and when;
- the acceptance fields Checktide names for your request;
- for linked issues, their issue ID and key, summary, status, project, last-updated time and how they are linked to this issue — not their body or comments;
- the files on the issue that you choose to attach to the start or to an answer, copied as described under "What you provide directly" — never the issue's other attachments;
- the identity of the person acting (Atlassian account ID), together with your site and installation identifiers.
Anything you write in those places may contain personal data. Its home page also lists, for the person viewing it, the issues in progress they can see that changed in the last 14 days: key, summary, status and when each changed, read as that person, shown only to them and kept nowhere. To show times in your own time zone, it also reads the time zone set on your Jira profile, for the pages you open; it is used only to format those times and is kept nowhere. On any issue where Checktide's row appears, it asks Jira, as the person viewing the issue, whether they can see it and when it last changed, to show the row's state; it reads nothing else of the issue there and keeps nothing. When someone uses Send to developer on a report, it reads the issue's project and issue types as that person, to open Jira's create page filled in; it keeps nothing.
What you provide directly
Environment details: a name for the environment and, optionally, for each website; the websites' addresses and whether each is on a private network; the test accounts you give us for a website that needs a sign-in — a label of your own choosing and either the account's username and password, or an invitation to Checktide's test address, for which we set our own password so that you never send one; and an optional note on the request. 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; the deletion is recorded with the request. Checktide keeps the password nowhere else, and you can change or remove the account on the environment's page at any time. A password we set ourselves — for an account you invite to our test address, or one we sign up for on your website — is kept by Checktide outside your site, where only Checktide can read it, and is deleted when that request closes, or earlier when you remove the account. Checktide never asks for credentials in Jira: please do not write passwords into environment notes or Jira issues, because text written there is stored like any other content.
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 that you choose. Until you send it, your draft — the note and the files — stays only in your browser; it is never written to Jira. Pressing Send puts the files into the app's storage on your site; if the send does not complete, or you then remove a file, that file stays there, tied to no request, and is deleted the next time we check your site for requests, once it has been there for a day, or a little over an hour if you removed it; if we do not check again, it stays until you ask us to delete it (see Retention) or the app is uninstalled. What you send is stored with the request in the app's storage on your site and is read for that verification only; the report quotes from a file only what a check relies on. The person at Checktide doing the verification downloads a copy to read it; that copy is deleted once what we read in it has been captured for the scope, and at the latest when the request closes. Keep passwords and tokens out of notes and files.
Your answers to our questions, the actions you allow, and the words you type in Not what you meant? to correct a proposed check are kept with the request or the proposal; those words are read, with the issue, by the AI service that drafts the proposal.
Where the work happens
Your information lives on your own Atlassian site. Everything the app records lives in the app's storage on your site, under your Atlassian agreements. The proposal of what can be checked is drafted by an AI service inside the Atlassian platform: the issue's summary and description do not go to any third-party AI service and stay within Atlassian cloud, though that processing may take place outside your site's data residency region, and Checktide does not use them to train models. The copies Checktide holds anywhere else are the ones this notice lists: the working copies it makes to deliver a verification, described next; the passwords it sets itself, described above; and your mail to our support address, described under Retention.
Delivery does leave Atlassian: to test your running application, Checktide copies the request material — the issue content above, your environment details, the notes, files and answers you sent, and the frozen scope — onto Checktide's own testing environment, in the United States, and runs the agreed checks there with a browser, API calls and AI-assisted tooling, which also reads what the browser shows on your website. Every local copy Checktide made for the work — uploaded files, copies of issue attachments, evidence copies and recordings — is deleted in the same step that closes the request, and the instant of that deletion is recorded on the request. An uploaded file is deleted once what we read in it has been captured for the scope, and at the latest at the close. What remains in Checktide's delivery records afterwards is a line of identifiers, instants and amounts, plus our own working notes from doing the work: they can quote your issue and what we saw on your site, may cover several requests, and are not deleted request by request. The request record and the evidence published with the report stay in the app's storage on your site, as described under Retention.
While checking, Checktide notes a summary of the requests your page sends to your servers — the address, the status and the values the check is about — never cookies, tokens or whole responses. That summary is part of the report’s evidence and is kept and deleted with it.
While checking, Checktide also records the browser's screen as it works — a recording each time we check, so that the report can show the work step by step. We sign in for you; nothing is recorded while we type the password, and it is never written in the report. Nothing is recorded while we wait on our own side either. The recording is part of the report's evidence and is kept and deleted with it.
Checktide uses contracted third-party AI model providers to process the materials of your request — the issue text you hand over, the pages we test and the evidence we record — only to deliver that request. A list of our sub-processors is available on request. A provider receives the request material and what the browser shows on your website, never a password; that processing takes place in the United States, and the provider keeps what it receives for 30 days, or for up to 2 years if its safety systems flag a conversation as breaking its usage policy. Checktide never reports these conversations to a provider as feedback.
Where information goes
- Atlassian hosts the app, its storage and your Jira site, under your own Atlassian agreements. Checktide's support desk also runs on Atlassian's Jira Service Management: mail you send to support@checktide.app becomes a ticket there, and replies come from the same address.
- An AI service inside the Atlassian platform drafts the proposal of what can be checked from the issue's summary and description. For our demo issue, the proposal ships with the app and no AI service is used.
- Cloudflare serves this website and routes mail sent to support@checktide.app and to Checktide's test addresses.
- Checktide's own testing environment in the United States, described above.
- Contracted AI model providers in the United States, described above, which receive the request material and what the browser shows on your website during delivery; a list of our sub-processors is available on request.
- Google provides the mailbox that Checktide's test addresses forward to. Mail your product sends to one of them arrives there: the invitation for an account you invite, which we use only to set up that account, and mail that a check needs or that an account of ours receives, such as a password-reset link. A message a check is about may become evidence in the report; when a request closes, we delete its messages there and empty the mailbox's trash.
Checktide does not sell data, does not use advertising or analytics scripts on this site, and shares material only with the recipients listed here.
How information is protected
- Where records live. Everything the app records is kept in the app storage Atlassian provides on your site. Atlassian states that encrypting that storage at rest is its responsibility. The app can read your issues, add the comments described above and keep its own records; it cannot edit or delete your issues.
- Who can open a report. Anyone who can see an issue in Jira can open its report and the report's evidence, recordings included. A report is never a public link.
- Where the checks run. Checktide's own testing environment is encrypted at rest, and its traffic to Checktide's own services is encrypted in transit.
- Test accounts. Give Checktide test accounts and data that grant nothing outside the environment you ask us to test. Checktide never asks for credentials in Jira; a test account's password belongs on the environment's page, where it is stored encrypted on your site. Anyone on your site who can open Checktide can see that page — its websites, account labels and usernames, never a password.
Retention
Request records, scope revisions, clarification questions, and the notes and files you sent stay with the issue in app storage while the app is installed. The proposal of what can be checked, with a note of when it was read and how many checks it proposed, is kept with the issue and replaced when a new one is drafted; it is deleted when you ask us to delete our records, or with the app's storage after an uninstall. Uninstalling the app removes its storage on your site under Atlassian's rules (Atlassian keeps it for 28 days, then deletes it; a reinstall does not get it back). Each version of an environment you save — its names, website addresses, account labels and usernames — is kept, even after you change or retire the environment, until the app is uninstalled, and is not deleted when you ask us to delete a request's records; a password is deleted when its account ends. Your mail to our support address is kept as a ticket in our Jira Service Management until you ask us to delete it. What happens to the working copies made to deliver a verification is stated in "Where the work happens" above.
How long reports stay available
A report and its evidence, recordings included, stay available on your site for at least the 14 days in which you can ask for its retest, and for as long as Checktide remains installed, unless you ask us to delete the request's records.
- If you uninstall Checktide, Atlassian keeps the app's storage on your site, reports and evidence included, for 28 days and then deletes it. Reinstalling Checktide starts from empty storage; nothing the previous installation held is carried over.
- If you ask us to delete a request's records, its report and evidence leave the app's storage when we delete them, as described under "Your rights and contact". Atlassian keeps deleted evidence files recoverable for 30 days before removing them for good, and keeps its own backups of the app's storage on its own terms.
Your rights and contact
Write to support@checktide.app to ask what Checktide holds about a request, to have it deleted, or with any question about this notice. When you ask us to delete a request, we delete its records from the app's storage on your site once it, and any other request on the same issue, has ended, together with the notes and files you sent and the evidence its report cited, except what is listed next; deleting it also ends its included retest. What we keep holds nothing you wrote: a note that we deleted it, naming your support ticket; what the request was charged and which of your users' accounts authorized it; the log of when test accounts were handed to us for it and when our copy was deleted. Deletion is from the app's storage on your site; Atlassian's own backups of that storage are kept on Atlassian's terms, which Checktide does not control.
Changes
If where the work happens, what is stored, or who receives information changes, this notice changes first, and the version date at the top changes with it.