When you sign in with Google, we collect your name, email address, and profile picture as provided by Google OAuth. We do not collect or store your Google password.

When you connect your GitHub account, we access your public profile information, repository count, follower data, and programming languages used. We do not access private repositories unless explicitly granted.

We collect usage data such as pages visited, features used, tasks created, and activity patterns to improve platform performance and the AI recommendation systems.

Team interaction data — including messages, project updates, and meeting activity — is stored to provide the platform's core collaboration features.

Your profile data is used to personalize your experience, display your identity to teammates, and enable AI-powered skill matching for task distribution.

GitHub data is used to build your skill profile, populate the contribution graph on your dashboard, and improve task assignment accuracy.

Usage data is analyzed in aggregate to improve platform features, fix issues, and optimize AI model performance. Individual usage data is not sold.

Email addresses are used for authentication only and are not used for unsolicited marketing communications.

Your profile information (name, skills, public GitHub stats) is visible to members of your teams within the platform. This is necessary for collaboration features to function.

If you generate a public profile link, the information on that profile is accessible to anyone with the link.

We do not sell, rent, or trade your personal data to third parties for marketing or advertising purposes.

We may share data with service providers who operate parts of the platform infrastructure (hosting, database, AI APIs) strictly for the purpose of delivering the service.

All data is transmitted over HTTPS. Authentication is handled via NextAuth with industry-standard OAuth 2.0 flows.

Database access is restricted to authorized server-side code. Credentials and secrets are stored as environment variables and never exposed to the client.

We follow best practices for securing MongoDB connections, session tokens, and API key management.

While we take reasonable precautions, no system is completely secure. We encourage you to use strong passwords for your Google account and report any suspected issues promptly.

SPManager uses session cookies to maintain your authenticated state. These are essential for the platform to function and cannot be disabled while using the service.

We use next-themes to store your light/dark mode preference in a cookie on your device.

We do not use third-party advertising cookies or tracking pixels.

You can clear cookies via your browser settings, though this will sign you out of the platform.

You may request a copy of the personal data we hold about you at any time by contacting the platform administrator.

You may request deletion of your account and associated data. Note that some data (such as project history) may be retained if it is shared with a team.

You can disconnect your GitHub integration at any time from the platform settings. This will remove GitHub data from your profile.

You have the right to correct inaccurate profile information directly from your account settings page.

This Privacy Policy may be updated periodically to reflect changes in our practices or applicable laws. The date at the top of this page indicates when the policy was last revised.

We will make reasonable efforts to notify users of material changes. Continued use of the platform after changes are posted constitutes acceptance of the updated policy.

If you have questions about this Privacy Policy, how your data is handled, or want to exercise your data rights, please contact the platform administrator through the in-app messaging system.

We are committed to addressing privacy concerns transparently and in a timely manner.

When a manager invites a client through ClientDesk, the client's name, email, and the conversation transcript from the requirements session are stored to generate the requirements report.

Client session data is only accessible to the manager who created the session. It is not shared with other platform users.

Session links expire after 48 hours. Once a session is marked complete, the session token is permanently invalidated.

Client data collected through ClientDesk is used solely for generating the requirements report and creating the corresponding project. It is not used for any other purpose.

Managers may delete a client entry and all associated session data at any time from the ClientDesk dashboard.