Privacy policy
What nibrun processes, why it is needed, and how to contact us about your data.
Last updated: .
In this policy, “nibrun”, “we”, “us”, and “our” refer to the operator of the nibrun service.
This policy covers the nibrun website, dashboard, CLI, and MCP integration. For privacy questions or requests, contact support@nibrun.com.
Information we process
- Account and sign-in information. When you sign in with GitHub, we receive account identifiers, your name, email address, and profile image. We store authentication records, sessions, tokens, and connection information, which can include IP addresses and browser details. Anonymous sessions let us associate a temporary app with its creator before sign-in.
- Your apps. We process uploaded executables, app settings, environment variables, deployment history, persistent files and databases, imports, exports, logs, and resource-usage information to host and operate your apps.
- Connected assistants. MCP requests can include app identifiers, deployment files or download URLs, configuration, SQL queries, and client or conversation references. Requested results, such as logs or database rows, are returned to the client you connected. They can contain personal information from your apps.
- Support messages. We receive your email address and the information you choose to send when you contact us.
- Website and dashboard activity. We collect page views, navigation, device and browser information, performance measurements, and events such as sign-in and deployment outcomes. Analytics can associate an opaque visitor identifier with your nibrun account ID. Session replay records interactions with the website and dashboard.
How we use information
We use this information to authenticate you, run your apps, persist and export their data, carry out requests from connected tools, provide support, investigate failures and abuse, secure the service, and understand how the website and dashboard are used.
If your app collects personal information, you are responsible for deciding what it collects and how it is used, providing the appropriate notices, and responding to your users. This policy does not replace the privacy notice for an app you operate.
Cookies and analytics
Sign-in uses session cookies. Website and dashboard analytics use a visitor-identifier cookie that lasts up to 90 days and a navigation-context cookie that lasts up to 30 minutes. These analytics cookies are shared between nibrun.com and app.nibrun.com.
Analytics and session replay use our self-hosted Umami installation. The nibrun analytics integration does not load when your browser sends Do Not Track with the value 1. You can also block the analytics host through your browser. Clearing cookies resets the browser identifier; it does not erase records already stored on the server.
Analytics events exclude names, email addresses, configuration values, and non-marketing query parameters. Session replay is a separate recording of page interactions. Our website analytics integration is not automatically installed in apps you host on nibrun.
Service providers and connected services
nibrun uses Amazon Web Services for application hosting and storage, Cloudflare for website delivery, HTTPS traffic, and domain services, and GitHub for sign-in. Support messages are processed through email. These providers process information needed for their role in delivering the service.
Application hosting and persistent storage are based in Frankfurt, Germany. Requests can pass through Cloudflare’s global network. GitHub and any AI provider you connect handle information under their own terms and privacy policies; their processing may take place in other countries.
Connecting an AI client authorizes it to request information and perform supported actions on your account. Information returned to that client leaves nibrun and is handled by that service. Disconnecting a client does not delete your apps or copies already received by that client.
Retention and deletion
App files and configuration remain available while the app is retained. Deleting an app starts its teardown and cleanup. Removal is asynchronous, and stored versions or backups can outlive removal from the active service.
- Temporary binary uploads and downloadable exports are configured to expire after one day.
- Imported data archives are configured to expire after 30 days.
- Service and application logs are configured to expire after 30 days.
- Platform database backups are configured to expire after 90 days.
- Daily infrastructure snapshots retain the most recent 14 copies.
Storage expiry is performed by background processes and is not an immediate erasure guarantee. Analytics records and stored binary versions currently have no automatic expiry. Contact us about account closure or removal of information retained outside an active app. Any retention required by applicable law still applies.
Your choices and requests
You can export or delete apps using the dashboard or CLI. Contact us to request account closure or access, correction, deletion, or a copy of personal information. Depending on the law that applies to you, you may also have rights to object to or restrict processing and to complain to a data-protection authority. We may need to verify your identity before fulfilling a request.
Send requests to support@nibrun.com. Requests about data collected by an app hosted on nibrun should normally go to that app’s operator.