How Peer Rep Index handles information

This policy explains the identity, assessment, and service information used to operate Peer Rep Index, including information received when a manager signs in with Google.

Manager accounts and Google sign-in

Managers may create or access an account with email and password or with Google sign-in. When Google sign-in is used, Peer Rep Index requests only the standard openid, email, and profile scopes.

Google may provide a Google account identifier, name, email address, email-verification status, and profile image. The authentication service may also store provider account and token metadata needed to establish, link, secure, and maintain the account and session. Peer Rep Index does not request access to Gmail, Google Drive, contacts, calendars, or other Google Workspace content.

This Google identity information is used only for sign-in, account association, security, and displaying the manager's account identity. It is not used for advertising, sold to data brokers, or used to train general-purpose artificial-intelligence models.

Information used to provide the service

Peer Rep Index stores manager account details; organization, assessment, participant, invitation, and release configuration; respondent progress and responses while an assessment is active; finalized analytical results; transactional email delivery records; and security or operational records such as session, request, audit, and error metadata.

This information is used to authenticate users, administer assessments, save participant progress, calculate and release configured results, deliver transactional messages, prevent abuse, diagnose failures, and protect the service.

Assessment privacy through the lifecycle

During collection

While an assessment is open—or closed but not finalized—respondent, assignment, and rating linkage exists so participants can save and resume, duplicate responses can be prevented, and managers can monitor who has completed the workflow. Managers can see completion status, but not attributable rating content.

At finalization

Finalization creates the reportable aggregate records and removes live respondent-to-subject rating attribution. Reporting does not present individual ratings with respondent names.

Reputation Analytics

Subject-level aggregate results, rating distributions, and finalized result snapshots are retained for reporting without respondent labels. These results identify the participant being described, not the respondents behind individual ratings.

Relationship Analytics

Before directional attribution is removed, privacy suppression is applied and anonymous organization-level reciprocal-perception and Group Structure summaries are calculated. Groups smaller than five and complementary totals that could reveal them are removed before persistence. Only approved aggregate cells are retained; pair identities, nodes, edges, memberships, and reconstructable topology are not retained.

Participant result release

Participant access is controlled by the assessment's configured release policy. Manager Only denies participant access; other policies can provide a participant's own result and, where explicitly configured, anonymous group context or authorized named profiles.

Historical assessments

Assessments finalized before Relationship Analytics was available are not retroactively analyzed. Finalized analytical snapshots remain governed by the methodology active when they were created.

What anonymity does—and does not—mean

Managers do not receive a respondent-attributed rating report. Before finalization, the application temporarily retains the links needed to save responses, allow edits, monitor completion, and produce final results. In very small groups, aggregate patterns may make an answer easier to infer even though it is not labeled with the respondent's name.

After finalization, an individual directional relationship cannot be reconstructed from Relationship Analytics. Reputation Results continue to identify the participant whose aggregate result is being reported.

Storage, sharing, and protection

Information is stored in the application's hosted database and supporting service infrastructure. Authentication credentials and provider tokens are handled on the server and are not intentionally exposed in public pages or client-side application data.

Information is shared only as needed with service providers that host the application and database, authenticate accounts, provide abuse protection, and deliver transactional email, or when required by law. Google receives the requests necessary to complete Google authentication. Peer Rep Index does not sell personal information.

No public result page exposes respondent identities. Participant results are available only when an assessment manager authorizes a release and are limited by that release policy.

Retention and deletion

Account and assessment information is retained while it is needed to operate the account and preserve the assessment results described above. No automatic retention expiration is currently configured. Finalization removes attributable live rating data as described in this policy, while finalized analytical records remain available for reporting.

Disconnecting or revoking Google access stops that Google authorization but does not by itself delete the Peer Rep Index account or assessment records. A manager may contact the service operator to request account or associated-data deletion. A request may be limited where retention is necessary for security, legal obligations, or the rights of other authorized users.

Contact and policy updates

Peer Rep Index is operated by INAMCO. For privacy questions, access or deletion requests, or concerns about Google sign-in data, contact the operator through the INAMCO website.

This policy may be updated when the service or its data practices change. The current version will remain available at this public URL. Last updated August 19, 2026.

Use of the service is also governed by the Terms of Service.