Your data

Intake Standards keeps two kinds of data in Forge hosted storage for your installation: the intake standards your project admins write, and a run log of the checks made against them. The requester's text also stays on the work item. The text is judged by the model, Atlassian-hosted AI (Forge LLMs); the app's code runs on Forge, and nothing leaves Atlassian.

Intake standards

Every version of every standard is kept: its checks (label, met-when rule and hint), the word minimum, the box wording, any skip rule and the template it started from. Each version records who saved it and when, and who enabled it and when; a retired version records when it was retired. The app never deletes a version.

Project admins read and edit standards on the Intake standards page under Project settings. Requesters see the labels, hints and box wording on the request form; the met-when rules never reach their browser. Who saved or enabled a version is stored as an Atlassian account id. The page looks the name up each time it shows the list and never stores it.

The run log

Each time the model checks a text against an enabled version, on the customer portal or in the agent view, the app writes one run log row. A check that ends Unverified because the model failed twice writes one too. A form that could not load its standard writes none, because no model was called. A row holds:

• the requester's text as checked, up to 10,000 characters;
• the outcome, and each check's verdict with its evidence quote or hint;
• the version of the standard and the source, customer portal or agent view;
• the requester's Atlassian account id, shown by name on the Run log tab, or as "Anonymous" when the portal did not identify the requester;
• when the check ran, how long it took, the tokens used, the number of attempts and any error code;
• the request key, once the request is created.

Checks on text the requester never sent are logged too. Text under the word minimum is not logged, because it fails on the count without a model call. Nor are checks on the Evaluate tab, or requests for a work type with no enabled standard.

Each row is written with a 30-day expiry. Forge deletes an expired row within about 48 hours, and the Run log tab hides rows older than 30 days in the meantime. Linking a row to its request key keeps the expiry it already had.

Only people with Administer Projects on the project see its run log, on the Run log tab. Every request the tab makes is checked against that permission; see Security.

The field itself does not tell requesters that AI reads their text or that the run log keeps it. Say so in the request form's help text if your policies need it.

On the work item

When the request is created, the Intake details field holds the requester's text, its status (Complete, Incomplete, Unverified or Not checked), each check's verdict with its quote or hint, the version of the standard and when the check ran. On creation the app also:

• Copies the text into Description when Description is empty. An agent or an Automation rule that wrote Description first keeps its text.
• Adds the label intake-unverified and an internal note when the value is not a verified pass, except a Not checked value on a work type with no enabled standard. The note names the reason and quotes nothing the requester wrote.
• Writes the issue property intake-gate with the status, whether the value was verified and flagged, the text's hash and the details of the check.

All of this follows the work item's own permissions, like any other field, label or comment. Requesters do not see internal notes. On the customer portal, the requester and anyone the request is shared with can see the Intake details field on the request: its status, the text and, under Show check details, each check's verdict with its quote or hint.

What the model sees

When a check runs, the app sends the model the requester's text, the checks of the standard with their met-when rules, and the app's own judging instructions. The model works on text only: attachments and screenshots are not sent, and nothing behind a link is opened. Its answer, a verdict, a quote and a hint for each check, is kept in the run log row and the field value.

Text pasted on the Evaluate tab goes to the model the same way and is not stored. How the check judges sets out the instructions the model is given.

Developer logs

The app's log lines carry ids, standard versions, outcomes, error codes, timings and token counts, never the requester's text or anyone's account id. Sientus Solutions sees production log lines in the Forge developer console only while your site admin leaves app-log access enabled. Security explains how the absence of text is tested.

If you uninstall

Uninstalling removes the field and its values and leaves the app's storage with Atlassian for 28 days. Install and uninstall sets out what returns on a reinstall and how to ask for a recovery. To stop checking a work type, disable its standard on the Versions tab instead.

Summary table