Trust & information

Privacy notice

How hosted Gitflare handles account information, repositories, AI requests and connected services.

Updated October 18, 2026 · nexarq AI (nexarq Technologies Pvt Ltd)

Who this notice covers

nexarq AI (nexarq Technologies Pvt Ltd) operates hosted Gitflare. This notice describes information processed to provide and secure the service. For a self-hosted installation, contact the organization operating it. Send privacy questions to privacy@gitflare.io.

Information we process

  • Account identity: Cloudflare user ID and email for Cloudflare sign-in; account profile, verification state and, for existing password accounts, password hashes and authenticator enrollment and recovery information.
  • Workspace access: memberships, roles, teams, invitations, sessions, credential hashes, resource grants and access audit records.
  • Code and collaboration: repositories, imported files, prompts, context, proposals, agent assignments, patches, check results, review comments, issues, releases and deployment records.
  • Connections: OAuth registrations, grants and scopes; connected account and resource identifiers; encrypted Cloudflare connection credentials.
  • Operational information: requests, errors, timing and diagnostic records produced by the application and its hosting services. Avoid including secrets in prompts, support reports or diagnostic material.

How information is used

We process this information to authenticate users, enforce access, host code, run requested workflows, manage connected services, provide support and investigate reliability or security issues. Workspace members and connected clients can access content according to their effective permissions. A workspace owner can manage access to workspace information.

Hosting and AI processing

The application uses Cloudflare services including Workers, Durable Objects, KV, Artifacts and Containers. Configured email services deliver account and invitation messages. Cloudflare processes information according to the services enabled for the installation.

When an AI feature runs, relevant prompts, repository content and tool results are sent through Cloudflare AI Gateway to the model selected for the workspace or run. The selected model provider and Gateway logging configuration affect subsequent processing and logs. Review the provider's terms before submitting sensitive information. Connecting an external AI client also shares the results of its permitted tool calls with that client, under its own provider's policies.

Storage and retention

Gitflare stores account, workspace and workflow records so the service can operate and preserve collaboration history. Some sessions and authorization records have expiry controls; expiry of a credential does not itself delete repository or workflow history. Retention also depends on connected providers and hosting configuration.

For account closure, access, correction, export or deletion requests, email privacy@gitflare.io with the account and workspace concerned. We may need to verify your identity and authority before acting. Revoking a client connection prevents further authorized use of that grant; it does not recall information the client already received.

Browser storage and your choices

Gitflare uses cookies for sign-in and authorization, and browser storage for interface preferences and navigation state. See the Cookie and storage notice for details. You can revoke sessions and connections through account settings and ask a workspace owner to change your membership. Rights available under applicable privacy law can be raised using the privacy contact above.

Changes

The date on this page identifies the current notice. Contact us if you need help understanding a change or how it applies to your use.