Teams Privacy Policy

Effective October 22, 2026

Who we are and what this notice covers

NVORRA is offered to US businesses.

NVORRA LLC provides the NVORRA app for Microsoft Teams. Contact us at support@nvorra.com about privacy or support.

This notice describes the personal Teams bot used to connect a NVORRA workspace account, receive notifications, record attendance, and act on available approvals. It does not describe the entire NVORRA platform, marketing website, or the separate Microsoft 365 integration for email and calendars. Your organization manages your workspace membership and permissions. Microsoft processes Teams information under its applicable terms and your organization's Microsoft settings.

Information the integration processes

• Account connection information: NVORRA workspace and user identifiers, Microsoft tenant and user identifiers, Teams personal conversation identifiers and routing information, connection timestamps, and connection-code verification information.
• Bot interactions: messages, commands, submitted button actions, and activity identifiers used to associate requests with your account and prevent duplicate processing.
• Notifications: titles, message bodies, and links to workspace records delivered to your personal Teams conversation. These can include information about colleagues, customers, and work.
• Attendance information: clock-in and clock-out actions, office or remote selection, break actions, and resulting attendance records.
• Approval information: available leave, request, and workflow details; record identifiers and versions; and submitted approval or decline actions. Leave cards can include a person's name, leave type, and dates. Request cards can include a title and description.
• Operational records: connection audit events, activity-processing receipts, and delivery attempts and results.

Information comes from your interactions, your linked workspace, and Microsoft Teams. The personal bot does not provide access to unrelated chats, channels, email, or calendars. Its installation does not grant the separate Microsoft Graph permissions used by NVORRA's Microsoft 365 integration. Do not send passwords, API keys, or information unrelated to supported bot functions.

Why information is processed

The integration uses this information to connect the correct accounts, check permissions, deliver workspace notifications, process authorized attendance and approval actions, prevent duplicate processing, and operate and troubleshoot messaging.

Connection codes expire after 15 minutes and can be consumed once. NVORRA stores a hash for code verification. Sending a code to the bot also places it in Teams, where Microsoft's and your organization's retention settings apply. Expiry is not a promise that all copies or associated records are deleted.

Who receives information

Microsoft receives messages, notification and approval content, and identifiers needed for Teams messaging. NVORRA's application and database infrastructure process integration information. Authorized workspace users can access resulting business records according to their permissions. Your organization's Microsoft administrators may govern access to and retention of Teams content.

Your controls and requests

You can disconnect the integration in NVORRA Settings. Disconnecting clears the active account binding, conversation reference, and pending connection code in NVORRA. Delivery stops when the sender observes the disconnect; a message already in transit may still arrive.

Disconnecting or removing the Teams app does not erase attendance or approval records, audit history, processing receipts, backups, or messages already delivered to Teams. Changes to workspace permissions do not recall previously delivered messages. Contact your administrator about workspace records and your organization's Teams retention settings.

For questions or requests about personal information, email support@nvorra.com with enough information to identify your workspace. Do not include passwords or connection codes. We may need to verify your identity and authority and coordinate with your organization before disclosing or changing workspace information.

Retention and security

Connection-code expiry and notification delivery eligibility are operational limits, not deletion schedules. Disconnecting is not a request to delete workspace records.

The integration checks authenticated Microsoft bot requests and workspace permissions before processing supported actions. These controls do not guarantee that every security incident can be prevented.

Changes and contact

Updates will be posted with a revised effective date, with notices or other steps required by applicable obligations.

Privacy and support contact: NVORRA LLC, 747 Middle Neck Road, Great Neck, NY 11024, United States. Email: support@nvorra.com.

Platform privacy and retention

Following the end of paid service, the workspace owner may request an export through support@nvorra.com within 30 days. Requests require verification and exports are delivered securely. Customer content is deleted from active systems within 60 days after service ends, except for records subject to applicable legal obligations or documented holds. Backup copies expire 90 days after creation, so residual copies may remain for up to 150 days after service ends. Integration disconnection alone does not start this process. Copies already delivered to Microsoft Teams are subject to Microsoft and customer retention settings.

The Platform Privacy Policy describes service providers and platform-wide processing.