InfraBrix
Back to home

Legal & trust

Privacy Policy

What you share with InfraBrix, how it is used, and the choices you have.

Effective and last updated: October 20, 2026

On this page

1.Who we are and what this covers

InfraBrix is operated by its founder, Chinaza Nwukwa, under the EnyLabs brand. EnyLabs is an unregistered brand and is not currently an incorporated company. In this policy, “we”, “us”, and “our” refer to the operator of InfraBrix.

This policy explains how information is handled when you visit our website, join the waitlist, create an account, contact us, or use InfraBrix. Contact us at mail@enylabs.com for privacy questions and requests.

If your organization connects repositories or cloud accounts containing other people’s information, you are responsible for having the authority and notices needed for that use. This policy does not replace any separate data-processing agreement your organization may need.

2.Information we collect

  • Account and security information: your email address, optional display name, password hash, sign-in sessions, passkey credential records, and the information needed to verify your chosen authentication methods. We do not receive your fingerprint, face scan, or device PIN when you use a passkey.
  • Project and connected-service information: repository files and metadata, application configuration, infrastructure plans and state, cloud resource identifiers, deployment records, cost and monitoring information, and the permissions or credential material needed for the connections you authorize.
  • Conversations and optional voice: prompts, project instructions, agent replies, tool activity, and approval records. If you choose voice mode, microphone audio is sent to the voice service to support the session, and transcripts and session records may be stored by InfraBrix.
  • Communications: waitlist email addresses, messages, feedback, bug reports, and information you share when booking a call or requesting support. Waitlist requests, account approval decisions and non-secret email notification content/delivery metadata are stored in our database. Feedback can also be stored in email and operational logs. Password reset links and verification codes are excluded from the notification outbox.
  • Technical and usage information: requests, device/browser details, error and security logs, and public-page analytics. Hosting and connected-service providers may also process network information such as IP addresses.

Provide only information you are authorized to share. Avoid putting secrets, sensitive personal information, or production customer data in chat messages or support reports when it is not needed.

3.Public architecture demo

The optional AI architecture demo sends your short application description and chosen cloud to our configured AI provider. It generates a conceptual diagram, without connecting to a cloud account or creating infrastructure. Do not submit secrets, sensitive personal information or production customer data.

Before generating, we ask you to agree to storing your description and the output for internal demo evaluation. We store successful and failed outputs, model and prompt versions, token usage, timing, consent version and request outcomes. These are unreviewed evaluation records, not automatically accepted reference answers. They are accessible only through platform administration and are not publicly searchable.

To control abuse and token costs, we record an encrypted IP address, a keyed network identifier, browser user-agent, the referring website origin, campaign labels and approximate country/region when our hosting provider supplies them. We do not send this network metadata to the model. Cloudflare Turnstile processes a human-verification token and IP address to check requests before generation.

Encrypted IP addresses are scheduled for removal after seven days; demo inputs, outputs and associated metadata after 90 days. An hourly cleanup runs while the demo gateway is configured. Separately downloaded evaluation exports and backups require their own deletion process. Evaluation exports exclude the recorded IP address, network identifier, user-agent and referring website. You can contact us about a demo submission using the request identifier.

4.How we use information

We use information to provide and maintain InfraBrix, authenticate users, analyze connected projects, prepare and run authorized workflows, maintain project history, respond to requests, investigate errors and abuse, and improve the product.

We use your contact details to send requested waitlist updates, account and security messages, and support replies. You can ask us to stop optional product updates; essential security and service communications may still be necessary.

Where applicable law requires a legal basis, these purposes may rely on performing our agreement with you, legitimate interests in operating and securing the service, compliance with legal obligations, or consent for an optional activity where required. You can contact us about the basis for a particular use.

5.AI providers and connected services

InfraBrix uses external AI services to process requests. Conversation content and relevant repository, project, or tool context may be sent to the configured AI provider. Supported integrations include OpenRouter and its model providers, Google’s Gemini services, and Groq; the providers used depend on the deployment and configuration.

Provider retention and model-training policies depend on the provider, model, account settings, and applicable agreements. Do not assume all requests have zero retention. OpenRouter describes these differences in its provider logging documentation.

GitHub and your connected cloud providers process information needed for the actions you authorize. Optional voice mode uses a voice service such as AssemblyAI. Optional Slack or other integrations exchange information needed for their enabled workflows. You can disconnect services or revoke permissions through InfraBrix where available and through the relevant provider.

6.When information is shared

Information may be processed by hosting, database, storage, AI, email delivery, analytics, monitoring, and other providers that support the service. Current integrations include services such as Vercel, GitHub, AWS, Google Cloud, OpenRouter/model providers, Groq, AssemblyAI, Slack, and the configured SMTP provider. Not every integration is active for every account.

Project information may be visible to authorized members of your organization and people or applications you grant access to. Booking a call through Calendly, visiting external links, or using a connected provider also involves that service’s own privacy practices.

We may disclose information when legally required, to respond to valid legal process, or when reasonably necessary to protect users and the service. If operation of InfraBrix is transferred, relevant information may transfer with it, subject to applicable law and appropriate notice.

7.Browser storage and analytics

InfraBrix uses browser storage to keep you signed in, remember your theme, and maintain interface preferences and onboarding progress. Clearing browser storage can sign you out or reset those preferences. Signing out revokes the current session when the request succeeds.

We use Vercel Web Analytics for public-page usage statistics when enabled in the deployment. Our analytics filter excludes account, sign-in, password-reset, project, and other private routes and removes query strings and fragments from public-page URLs before sending events. This does not remove operational logs maintained by our hosting or application services.

Vercel describes its Web Analytics as using aggregated usage data without third-party cookies. See its analytics privacy documentation for the information it processes. Third-party sites you visit may use their own cookies or tracking technologies.

8.Retention and deletion

We retain account and project information while it is needed to provide the service and for legitimate security, support, dispute-resolution, and legal purposes. Retention depends on the type of record, your account and project status, the purpose of processing, and applicable obligations; the beta does not use one fixed retention period for every record.

Deleting a project and archiving it have different effects. Archiving retains project records. Deleting a project does not necessarily delete infrastructure, provider records, email correspondence, security logs, or backups held separately. Cloud resources can continue running and billing until they are explicitly removed.

Contact mail@enylabs.com to request account closure, access, or deletion. We may need to verify your identity and authority, explain records that must be retained, and coordinate removal of connected resources. Stored copies and provider-held data may follow separate retention processes; we will explain relevant limitations when responding.

9.How we protect information

InfraBrix uses access controls, password hashing, session verification, protected authentication methods, and encryption for certain stored secret values. Access to connected systems is limited by the permissions you grant and the service’s workflow controls.

No online service can guarantee absolute security. Keep your sign-in methods secure, review connected permissions and infrastructure actions, and contact us promptly if you suspect unauthorized access. Do not send passwords, recovery material, or cloud keys in a privacy or support email.

10.Where information is processed

InfraBrix and its providers may process information in countries other than the country where you live. Locations depend on hosting, connected cloud regions, and the services and model providers used. We do not promise that all information remains within a single country.

Where cross-border safeguards or a separate processing agreement are required, these need to be addressed for the applicable service and relationship. Contact us before connecting information that requires a particular residency commitment or contractual safeguard.

11.Your choices and rights

You can update supported profile settings, manage authentication methods, disconnect integrations, and stop using the service. Depending on your location and circumstances, you may have rights to request access, correction, deletion, restriction, portability, or an objection to certain processing, and to withdraw consent where processing relies on it.

Send requests to mail@enylabs.com. We will handle them in accordance with applicable law, including any identity-verification requirements, exceptions, and response deadlines. You may also have the right to complain to your local data-protection authority.

12.Children’s information

InfraBrix is intended for adults using developer and business tools, not for children. If you believe a child has provided personal information through the service, contact us so we can investigate and take appropriate action.

13.Changes and contact

We may update this policy as the product, providers, or legal requirements change. We will update the date on this page and provide additional notice of material changes where required.

For questions, privacy requests, or concerns, email mail@enylabs.com. Your use of InfraBrix is also covered by the Terms of Service.