What the Prosights AEI results site stores, and how to delete it
This site keeps AEI Scan results for the people who upload them. Prosights, LLC runs the site on Wix. This page lists everything the site stores.
When you upload a result
- The results file. The site stores the fields that AEI Scan documents for
results.json: the scores, the levels, each check with its result and reason, the names of the files and settings the scan found, the locations the scan looked at, and the next actions. When you gave counts for each model, the file holds each model's name as you wrote it and those counts; the site stores them, shows them only on your result's page and never uses them in the benchmark. The site does not store the optionalmachinepart of the file (host name, user name and the repository's full path), even when your file contains that part. - A SHA-256 digest of the file. The site stores the digest of the file as you sent it and shows the digest with the report. The digest lets you check that the saved result is your file.
- A hash of your claim code. The site shows you the claim code once and stores only a SHA-256 hash of the code. The site erases the hash when a member claims the result.
- A hash of each network address your upload arrives with. The site uses the hashes to refuse more than 10 uploads per hour from 1 address. The hashes change every day. The site erases them when a member claims the result.
Nobody can read an unclaimed result on this site. A claim code stops working 7 days after the upload. The site deletes an unclaimed result at the first upload or claim, by anyone, after those 7 days.
When you register or sign in
- Your email address. Wix's login page creates your member account and keeps your email address. Wix checks your password; this site never receives your password. Wix's login page also offers sign-in with Google or Facebook; when you choose one of them, that company and Wix handle the sign-in.
- Which results are yours. When you claim a result, the site stores your member identifier with that result, and a marker that the result has been claimed. From then on, only you can read the result or delete it, unless you agree to share it with a portfolio (below).
- Cookies. Wix sets cookies on every page of this site, also before you sign in. Wix's cookies tie your browser to a session and keep you signed in. This site sets 4 cookies of its own. When you open a claim link, a cookie holds the claim code for at most 30 minutes, until you sign in. When you open an invitation link, a cookie holds the invitation code in the same way. When you open the link of a pre-deal request, a cookie holds the request code for at most 30 minutes; after that, open the link again. When you open a viewer's or an assessor's link, a cookie holds that link's code for at most 30 minutes, until you sign in.
When you share a result in the benchmark
Sharing is off for every result until you turn it on, on the claim form or on the result's page.
- Your choice and your answers. The site stores with the result whether you share it, and the industry, the number of people, the ownership and the funding stage you chose, if you chose any. The site keeps a funding stage only with the answer "Venture-capital-backed".
- What the site computes. From the shared results, the site computes the median and the 2 quartiles of the overall score and of each dimension's score: for all shared results, for each coding agent, each industry, each size, each kind of ownership and each funding stage. The site uses 1 result per member and coding agent, the latest run. A result graded with an earlier check catalog is left out.
- What every visitor can read. The number of shared results in each group and, for a group of at least 11 results, those medians and quartiles. The site shows a part of a larger group only when the rest of that group is empty or also has at least 11 results. The site publishes no single score, no mean, no lowest or highest score, no file name, no reason, no email address and no member identifier.
- Turning it off. Clear the box on the result's page and save. The site computes the figures again at each visit, so the next computation leaves the result out. A visitor who read the figures before and after may see that they changed.
- Sample files. The site marks an upload that is one of AEI Scan's own sample files and never counts it.
When you share results with a portfolio
A portfolio is a list that 1 member, its owner, keeps to read the results of several companies. Your results appear in a portfolio only after you opened an invitation link from its owner, signed in and agreed.
- What the site stores when you agree. Your member identifier with the invitation, the date, and the level at which you share.
- What the owner reads. For your most recent result graded with the current check catalog: the coding agent, the date of the run, the version of AEI Scan and the date of the check catalog; the overall score, the level, the coverage and the claim gap; the score and the level of each of the 16 dimensions; the industry, the number of people, the ownership and the funding stage that you answered for that result. Also, for each coding agent in your account: the date, the score and the level of each run. The owner reads the same for each result that you add later.
- What the owner reads only after a second choice. On the page "Sharing with portfolios" you can also share, for your most recent result: each of the 97 checks with its result and its reason; the names of the files and settings that the scan found; the next actions; the checks where the answers and the scan disagree; the counts that you gave for each model, with each model's name as you wrote it. You can go back to the scores at any time.
- What the owner never reads. Your email address, the SHA-256 digest of your file, a result graded with an earlier check catalog, and a sample file of AEI Scan. The owner sees you under the name the owner typed for the invitation. The owner sees whether the invitation was agreed to, declined or withdrawn from, and the date.
- What the owner can do. The owner can read the page, save the table as a CSV file and print a summary. The CSV file holds the scores and never the checks, reasons or file names. The owner cannot add, change, claim or delete a result in your account.
- Withdrawing. Choose "Withdraw from this portfolio" on the page "Sharing with portfolios". The site erases your member identifier from the invitation, and the portfolio no longer shows your results from the next page the owner opens. What the owner read, saved or printed before stays with the owner.
- Declining. The site stores that the invitation was declined, and the date. The site stores nothing of your account.
When you keep a portfolio
- The portfolio. The site stores the name you gave the portfolio, your member identifier and the email address of your account. Each member you invite reads the name and that email address.
- Each invitation. The site stores the name you gave the company, a SHA-256 hash of the invitation code, and the day the link stops working, 30 days after you made it. The site shows you the link once. The site erases the hash when the invitation is answered.
- Deleting. Removing an invitation or deleting the portfolio removes those records at once.
When a company is asked for a pre-deal assessment
A member, the requester, makes a request and sends its link to a company, the target. The target uploads with the request code and needs no account for that. The requester reads nothing of the results until the target agrees, signed in to an account that took the request. The request link alone shows nothing of the results, because the requester holds that link as well.
- What the site stores for the request. The code name and the text that the requester typed, the level asked for, the due date, the last day, the requester's member identifier and the email address of the requester's account, and a SHA-256 hash of the request code. The site shows the code once. The target reads the code name, that text and that email address.
- What the site stores for each upload. The results file as for any upload (above), its SHA-256 digest, the time of the upload and the name of the repository's folder as AEI Scan sent it. The site stores no network address and no claim code for these uploads.
- The scope. The number of repositories and the 2 texts that the target states in its account. The report shows them as the target's statement.
After the target agrees, the requester and each viewer the requester named read these parts:
- for each uploaded result: the name of the repository as the upload gave it, the coding agent, the time of the run, the version of AEI Scan, the date of the check catalog and the SHA-256 of the file
- the overall score, the level, the coverage and the claim gap of each result, and the score and the level of each of the 16 dimensions
- the share of the score at each evidence grade, and the number of open checks at each severity
- the scope that you state for this request
When the request asks for the checks as well, they also read:
- each of the 97 checks with its result and its reason
- the names of the files and settings that the scan found, and the locations it looked at
- the checks where the answers and the scan disagree
- the counts that you gave for each model, with each model's name as you wrote it
- the questions for management and the remediation plan that the site writes from the checks
- Evidence grades. The report gives each graded check 1 of 4 grades: Declared, Scanned, Witnessed, Verified by assessor. The site computes the grades from the results file and from what an assessor recorded.
- Viewers and assessors. For each person the requester names, the site stores the name the requester typed, the role, a SHA-256 hash of the link's code and the day the link stops working, at most 30 days after it was made. When that person signs in and accepts, the site stores the person's member identifier and erases the hash. A person named as assessor can grade only when Prosights has approved that person's account as an assessor; for that approval the site stores a name and the member identifier.
- What an assessor records. For a check: the grade, the date and a note on what was shown. For a run: that the assessor watched it, the date and a note on what was watched. The uploaded file stays unchanged.
- The view log. Each time the requester, a viewer or an assessor opens the report or a grading page, the site stores the time, the person's name as the requester typed it (for the requester, the email address of the account), the role and the page. The target reads this log in its account.
- Keeping the request in an account. When the target signs in and takes the request into an account, the site stores that member identifier with the request. Only that account reads the target's page, removes an upload, states the scope, agrees and withdraws. The first account to take the request keeps it; the requester's account cannot.
- Withdrawal, the end and the last day. The target can withdraw at any time, and the requester can end the request at any time. The last day is at most 180 days after the request was made. In each case the site deletes the uploaded results, the grades, the scope, the viewers and the view log, and the request code stops working. After the last day the site deletes them at the first page or upload, by anyone, that touches the request. The site keeps the code name, the text the requester typed, the dates and how the request ended, for the requester's list. What the requester or a viewer read, saved or printed before stays with them.
- Moving into a portfolio. The requester can ask to keep the results in a portfolio. Nothing moves until the target, signed in to the account that keeps the request, agrees. The site then copies the results into the target's account, unshared in the benchmark, and stores the agreement as an agreed portfolio invitation at the request's level. From then on the sections on portfolios (above) apply.
What the site does not do
- The site loads no script, font, image or tracker from another site. The 2 fonts and the mark in the header are files of this site.
- The site sends you no email. Wix sends the emails that belong to your account, for example to confirm your address or reset your password.
- The site shows a result to no member except the member who claimed that result and, when that member agreed, the owner of a portfolio, at the level that member chose. A result uploaded for a pre-deal request is shown, after the target agreed, to the requester and to the viewers and assessors the requester named. The benchmark shows figures of groups, never a result.
How to delete
- 1 result. Sign in, open the result or the list of your results, and choose Delete. The site removes the result at once.
- An unclaimed result. Do nothing: the site deletes the result after 7 days. To delete the result sooner, claim the result and then delete it.
- Your account and email address. Deleting a result does not delete your member account. This site has no page that deletes a member account. Wix keeps the account and your email address after you delete your results.
Questions about this page go to info@prosights.com.
Prosights.ai