Data, retention, and sharing

Know what your team uploads and who can access it.

What is uploaded#

CI uploads the built Storybook: compiled code, assets, fixture data, and any source maps included in the build. Native preview uploads a built capture app. Keep secrets, access tokens, and real customer data out of these artifacts.

Framecheck also receives the commit and pull-request metadata needed to associate results with your code change. Review the privacy notice for current data practices and GitHub permissions.

Project access#

Company membership and roles control dashboard access. Invite people individually and remove memberships when access is no longer needed. GitHub repository access alone is not the same as a Framecheck membership.

Sharing Storybook links#

Opening a saved Storybook creates an expiring access link. Only authorised members can create it, but anyone holding the link can use it during its lifetime. Do not paste it into a public issue unless you intend to share that build.

Retention#

Uploaded web builds are retained for 30 days. Screenshots and run history are retained while the project exists under the current published policy. An expired interactive build does not imply that the run's screenshot history has disappeared.

Availability of an image, Live view, or export can differ from the availability of the run record. Reopen an expired signed link from the dashboard; if the underlying build has expired, re-upload a new run rather than expecting the old interactive build to return.

Archive or delete#

Follow the project's archive/delete controls and read the confirmation carefully. Archiving a project is different from permanently deleting it. Company deletion and ownership changes have additional permissions. For account-data requests or an unclear retention case, contact support through the published privacy channel.