CREWLAB
Sign upSign up→

Legal information

Privacy Policy

This policy explains what CrewLab collects, how it is used, when it is visible to other members, and how to contact us about your information.

Last updated27 October 2026

Policies
  • Privacy Policy
  • Terms of Use
  • Community Guidelines
  • Grievance Redressal
01

Who is responsible

CrewLab is operated by Ujjwal baunthiyal, at Amarshahid Anand Colony, Ajabpur Kalan, Dehradun, Uttarakhand 248001. For privacy questions or requests, contact baunthiyalujjwal52@gmail.com.

02

Information we handle

When you create an account, CrewLab and its authentication provider process your email address and account credentials. CrewLab does not receive or store your plain-text password.

When you build a profile or use the app, we handle the information you provide and the records needed to run the service, which can include:

  • Profile details such as display name, username, short bio, interests, and skills.
  • Projects you create, project descriptions and status, join applications and availability details, membership records, and project discussion messages.
  • Events you create, notification status, and technical records needed to operate and protect the service.
  • If you connect GitHub: connection and installation identifiers, the repository selected for a project, and repository information retrieved to show its project crew.
03

What other members can see

CrewLab profiles and project listings are available to signed-in members. Information in an application is shared with the project owner for review. Project discussion is available to that project's accepted crew. Events are associated with their owner.

If a project owner links a private GitHub repository, the repository's metadata and selected read-only information can be shown to that project's crew. Crew members do not receive the owner's GitHub credentials or tokens. Do not put private or sensitive information in a profile, project listing, application, or discussion unless you intend to share it with the people who can access it.

04

Why we use information

We use information to provide authentication, profiles, project discovery, applications, crew management, discussions, events, notifications, and optional GitHub features; to respond to requests; and to secure, maintain, and improve the service. We do not sell personal information.

05

Service providers and sharing

Supabase provides authentication, database, and related infrastructure for the app. If you connect GitHub, the service communicates with GitHub to authorize the connection and retrieve the repository information you choose to share. We may also use hosting, security, or operational providers to run the website and app. These providers process information on our behalf under their applicable terms and safeguards.

We may disclose information when required by law, to respond to valid legal process, to protect users or the service, or in connection with a business transfer. We do not give one CrewLab member another member's GitHub authorization credentials.

06

Cookies and similar technologies

The app uses essential session and security technologies so sign-in and protected features work. We do not use non-essential cookies for advertising or cross-site tracking. Your browser may also store standard technical data needed to load and navigate the service.

07

Retention and your choices

We keep information while it is needed to provide the service, support your account, protect the community, resolve disputes, and meet legal obligations. We do not publish a fixed deletion timeline. The app does not currently offer self-service account deletion; to request access, correction, or deletion, contact baunthiyalujjwal52@gmail.com. We may retain limited records where a legal obligation, security need, or dispute requires it.

You can edit profile details in the app and disconnect GitHub from its settings. Disconnecting removes CrewLab's local GitHub connection record and stops future repository access through that connection; it does not delete content already shared by other members in project discussions.

08

Security and international processing

We use access controls and technical safeguards intended to protect information. GitHub user tokens used by the app are encrypted at rest and are restricted to server-side use. No online service can promise absolute security. Information may be processed in countries where our service providers operate, subject to applicable law.

09

Children

CrewLab accounts are for people aged 18 or older. The service is not intended for children under 18, and we do not knowingly invite them to create accounts. If you believe a person under 18 has provided account information, contact baunthiyalujjwal52@gmail.com.

10

Changes and contact

We may update this policy as the service or applicable requirements change. We will post the current version here with its updated date. For privacy questions, requests, or concerns, contact baunthiyalujjwal52@gmail.com. You may also use the grievance contact listed on our Grievance Redressal page.

This is general information and is not a substitute for advice from qualified counsel.
CREWLAB

Ideas to impact. Made for builders, by builders.

Find your crew

Find a cofounderFind developersStartup teamsSide projectsStudent projects

Product

Explore projectsHow it worksFeaturesGuides & resources

Company

AboutSign upDiscordInstagramX

Legal

Privacy PolicyTerms of UseCommunity GuidelinesGrievance Redressal
© 2026 CrewLab. All rights reserved.Made for builders, by builders
CREWLAB