What NovaScan does
NovaScan is an engineering intelligence and project coordination application. Depending on the features enabled by your organization, it can organize projects and teams, connect GitHub, Slack, and Jira, analyze project events for potential risks, and present summaries and recommendations in a dashboard.
Projects and teams
Organization workspaces, projects, members, roles, and project assignments keep engineering work organized.
Connected tools
Admins can authorize supported GitHub, Slack, and Jira connections to bring project context into NovaScan.
Risk and delivery insights
Incoming project events can be analyzed and shown as risk summaries, recommendations, and dashboard activity.
Team workflows
Project tools include team coordination features such as assignments, standups, and notifications where configured.
Information we handle
Information depends on how your organization configures and uses NovaScan. It may include:
- Account and organization details, such as name, email address, role, and organization membership.
- Project details, team assignments, standup entries, and settings that users submit.
- Integration account identifiers, selected workspace or site details, granted scopes, and OAuth tokens needed to provide the connection.
- Project events and related context from connected services, such as pull request metadata or diffs, Jira issue details, and Slack messages made available to the integration.
- Risk results, recommendations, and operational information needed to run and secure the service.
How information is used
NovaScan uses this information to authenticate users, provide organization and project features, retrieve authorized context from connected services, analyze project events, deliver requested notifications, and maintain the application.
We do not describe connected-service access as unrestricted: each connection is limited by the scopes the user approves and by that user’s permissions in the provider service.
Connected services
An organization administrator or other authorized user starts an OAuth connection from a project and approves the requested permissions with the provider. NovaScan stores the resulting tokens for that project only. Each project must be authorized separately; connecting a tool to one project does not connect it to other projects in the organization.
GitHub, Slack, Atlassian, and any AI provider process data under their own terms and privacy practices. Disconnecting an integration in NovaScan stops future use of that connection by NovaScan; it does not necessarily revoke access at the provider unless the provider revocation flow is also completed.
AI processing
When risk analysis runs, relevant event context may be sent to the AI service configured for the NovaScan deployment. The current risk-analysis path uses Google Gemini when configured. This context can include event summaries and content from connected tools. Do not connect a source or submit information that your organization is not permitted to process this way.
Your organization should review the AI provider’s terms and data practices and configure its deployment accordingly. AI-generated risk scores and recommendations are assistive outputs and should be reviewed by people before important decisions are made.
Storage and security
NovaScan stores application information in the database configured for the deployment. OAuth access and refresh tokens are encrypted by the application before they are saved. The encryption key and database hosting are controlled by the deployment operator.
Authentication tokens are stored in the browser’s local storage by the current web application. No online service can guarantee that information is completely secure; organizations should restrict account access and protect their deployment credentials.
Retention and deletion
Information is retained in the configured deployment while it is needed to provide the application and its project history. Retention and backup schedules depend on the deployment. An organization administrator can request account, project, or integration data removal from the NovaScan service operator; connected provider access should also be revoked from that provider.
Your choices
- Authorized project admins and managers choose which services to connect for each project and can disconnect them from that project’s dashboard.
- Users should provide only project information their organization has authorized for use.
- You can ask your organization administrator to correct or remove information associated with your account or projects.
- Provider-side permissions and access can also be reviewed or revoked from GitHub, Slack, or Atlassian account settings.
Policy updates
This policy may be updated as NovaScan’s features, providers, or operating practices change. The effective date at the top of this page indicates when the current version was published. Material changes should be communicated through the application or another channel used by your organization.
Contact
For privacy questions, data requests, or concerns, contact your organization administrator or the NovaScan service operator who provided your account. If your organization hosts NovaScan itself, contact that organization’s application administrator.